OK probably better to start of with what is Quiescing in regards to Visual Studio 2005 Team Foundation Server (TFS)?
The answer depends on who you ask…
In this case it’s the systematic shut down or manipulation of the TFS product and services in order to successfully install updates. When it works it’s a great idea but right now its still in its infancy and needs to grow up yet. There are updates coming that should have been released pervious to the TFS SP1 but some things were missed as many of you have seen.
If the installation fails there should be a msi*.log found in the %temp% folder. Look from the bottom up and search for "disablerollback" or "return value 3" and just above it for the real error. Look for the first error that is incurred so you may have to search up through a few errors.
Most common installation issues for the TFS SP1 and its Quiescing Hotfix are:
Is this pain really worth it?
Yes it is - there are several critical updates as well as many new enhancements which Brian has documented
Server Integration and Admin
Source Code Control
Work Item Tracking
Pasted from <http://blogs.msdn.com/bharry/archive/2006/12/19/update-on-bug-fixes-in-tfs-sp1.aspx>
Other issues of the week:
Visual Studio SP1 installations taking up too much space and it hasn't even installed successfully - the installer cache may have leftover *.msp files from the failed installs if you run out of disk space and the setup did not finish or fail gracefully. Look for multiple 436MB *.msp files. There is one for every VS client product you have installed so don’t just delete away or you will leave yourself in a broken state.