This is a weird one. I have a multiple server environment. All servers run some version of WIndows Server 2003, all with SP1.
SAV Corporate 10.0 is used throughout the network in a Client/Server form. The Parent Server for SAV is the Domain Controller. The SAV System Console on the domain controller was working fine and dandy until immediately after I installed SMSME 5.0 on a *completely* seperate server (the Exchange server obviously).
All SAV Clients throughout the network still point to the Domain Controller as the Parent Server. However, the client on the Domain Controller (a.k.a. the Parent Server for the SAV Corporate) doesn't show anything as the Parent Server.
everytime I clear the cache and run the discovery service, the discovery service finds the server and server group, but I still can't unlock the server group.
I found this article http://service1.symantec.com/support/ent-security.nsf/docid/2005051209365248?Open&src=tranus_ent_sl
I found that the Symantec Anti-Virus service was mysteriously stopped. So I started it. Still with no avail.
Then, I tried stopping the service again to continue with the KB article, and now that service will not stop. It's constantly in a "stopping" state.
Has anyone experience SMSME causing issues with SAV Corporate on a completely different server??
This network is a particular pain because it's a 24/7 operation. So restarting servers is a task.