Endpoint Protection

The W2K server with our Symantec System Center crashed and burned.  I do not have access to the old System Center at all.  I installed SSC on a new server (Win Server 2003), and tried to do Client Remote Install on a couple of clients.  It completes but the clients are still showing the old parent server.

I've copied the grc.dat file as well as pki roots certificate to the clients, and this doesn't show the new parent server either.  I don't want to uninstall and reinstall on all the clients, but this seems to be the only option. 

We've moved SSC before, and did not have this issue.  Does anyone have any suggestions?

I have a call in to support, but they seem to only call me after hrs.  Please help!!!!!

Hi,

Because you have copied the pki folder already to the clients, you could try to change the parent server straight in the registry. SSC is just a console and it can be run from any computer, but the server is the more important component of SAV.

- Jukka

I'm not really sure what registry change you're talking about.  Are you talking about changing something in the server registry or client registry?

If it's on the clients, I really don't want to go around to all of our clients.  Isn't there another way to push it out through Client Remote Install?  Why did the Client Remote Install work on a different server, but not this one? 

Could it be because there is no communication with the old parent server?

Hi,

Those registry keys are explained in this document. http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2003022009543548?Open&docid=2005033015282148&nsf=ent-security.nsf&view=0

You could run reg-files in a login script or with some other method.

Or you could also just upgrade the server and SSC and then push never version of SAV to the clients from SSC, so you would not have to go through them all.

- Jukka

Thank you for your help.  However, changing the registry did not work for me.  Symantec tech support finally called me, and helped me resolve this issue.  They gave me a batch file to run, which pushed it out to all clients.  It seems that something may have been wrong with our grc.dat file.