Reminder concerning upgrading WSUS 3 to Service Pack 2 in an EminentWare environment.
After applying Service Pack 2 to your WSUS Server(s), it is necessary to restart the EminentWare DataGrid Service on your EminentWare Server(s). This can be done with the Restart option of the Services.MMC, or via the Command Line (net stop ewdgs; net start ewdgs).
Note: You cannot restart the EminentWare DataGrid Service from an EminentWare task if you have only one EW server. Stopping the EminentWare DataGrid Service via an EminentWare task will result in the task session terminating abnormally and the service may not restart. An alternative that can be used, however, is to configure a system restart task with a shutdown delay long enough to ensure all apps and services shutdown normally. Once the shutdown (with restart) task is handed off from the EW WorkerProcess to the Operating System, the EW server is safely out of the loop. The EminentWare DataGrid Service will restart automatically when the server has completed the reboot.
If you have multiple EW Automation Servers, you can use Automation Server 'A' to restart the service on Server 'B', and vice versa. In this scenario, you should also configure Automation Routing Rules to ensure an Automation Server is not managing itself.
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
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.