best bet at this moment is to collect some debug logs to see what is happening at startup.
stop groupshield service
open regedit to hklm\software\wow6432node\mcafee\groupshield for exchange\trace
look for dword "level" and set the value to 3 - create the dword if it isn't there
look for string "path" and give value of folder location. ex c:\temp - create string if not present
start groupshield service up.
once service starts set level value back to zero.
Next i would suggest you call into support to open a ticket and get the logs to whom ever you talk to so we can see what is going on.
I did what you ask for and it generates a lot of log files, I also have reviewed these log files but I could not find anything that look like an error to fail connation.
The following registry keys need to be set to make it work.
GroupShield For Exchange\E2007\ExSvrRole = 3
GroupShield For Exchange\E2007\HubTxSvrAddr = <local IP Address>
The ExSvrRole key mentioned would be best set according to the role of the Exchange server - values this key can have :
0 -- Exchange 2003
1 -- Exchange 2007 Mailbox only role
2 -- Exchange 2007 Hub only role
3 -- Exchange 2007 Mailbox + Hub server role
4 -- Exchange 2007 Edge server role
No need to remove - try to ensure you have correct exclusions in place for VirusScan OnAccess Scanner for GSE and Exchnage components/folder structures.
KB51471 in the McAfee Knowledgebase.