Ok, so UR3 installs fine on all our servers in our DEV environment, but come time to patching PROD...well, it breaks our HUB servers like many people have posted. I have to say this is a very inconsistent patch.
One individual changed the service to logon as Local System, but I've confirmed that the service was set to logon as the local Network Service account prior to the installation of the patch. I would change the logon method, but I'm afraid of the consequences
that much ensue from doing so (especially since our DEV environment did not require such a change):
http://forums.msexchange.org/m_1800480695/mpage_1/key_/tm.htm#1800480729
http://forums.msexchange.org/m_1800480695/mpage_1/key_/tm.htm#1800480729
Has anyone discovered why this is occuring? Any solutions besides changing the account which the service logs on as?