Would it be worth, if you run a separate EminentWare Server to your WSUS server, to shut it down for the duration of the SP2 install and start it up again after it has completed?
This probably isnt required. The main thing is to stop the EminentWare service IF it is on the machine as the WSUS server. This is mainly to deal with issues related to WSUS DLLs and assemblies used by the EminentWare service.
One important item is that if you are going to use Third Party Updates, you have to have a version homogenous WSUS/EW server.
What that means is that if you have, for example, a EW server on one computer and WSUS on another, the version of the EW servers WSUS console only installation needs to be the same as the WSUS server.
IOW, 3.2 to 3.2 is fine, however 3.1 to 3.2 or 3.2 to 3.1 is NOT OK.
Keep in mind that this limitation is specific to the Third Party Updates publishing capability in EW and not other functionality.
One other thing to note here...
If you dont upgrade to 3.0 SP2, then Windows 7 XXX will appear as Windows Vista in the WSUS computer views in EminentWare console.
If you know computers are running Windows 7 and they are appearing as Vista, then upgrade the WSUS console component (or WSUS console/server) on the EW server and you will get the correct OS description.
Filed under: WSUS 3.0 SP2