The Patch 1 and Hf would be strongly recommneded on E2010SP2 - especially if running Edge\Hub Transport Roles (or like HUB\MB combo roles) as the transport agents will not work - therefore no transport or spam scanning (if antispam is installed).
Two most common things that show "McAfee GroupShield for Exchange is not currently available. Please try again later." with StandaloneUI.exe (interface)
a) Quarantine Database (Postgres) issues - there is a new DB system in the Patch 1. So if this is your issue then the Patch should sort this out.
b) UAC - usually right-click icon (on desktop or start menu) and select "Run as Administrator" will take care of that.
Yes there could be reboots with installation of Patch or HF - if a file is locked and cannot be updated - it will be marked for replacement - and the Patch or HF exe will ask for reboot.
If you can stop the McAfee Groupshield Service and McAfee Framework service before running the Patch and then same for HF - it will lessen the likelihood of reboot request.
one more question concerning this case:
Readme to the Hotfix suggests the following installation order:
- Patch1 should be installed before installing Microsoft
Exchange 2010 Service Pack 2.
- Microsoft Exchange 2010 Service Pack 2 should
be installed before installing this hotfix.
Our situation is, that we have installed Microsoft Exchange 2010 Service Pack 2 and now want to install Patch 1 and the hotfis.
Could this cause any problems to Exchange or Groupshield?
Did not get a failure message, because on our Server following registry key HKLM\Software\WOW6432Node\McAfee\GroupShield for Exchange\E2007\E2K10SP1 still exists.
so no reboots were necessary for Patch 1 and the Hotfix. Only thing was that after Patch 1 Service MS Echange Information Store did not start automatically.
But after that no problems.
thanks for all