asked on

SEP MR4 Clients - Rehome to new SEPM

Hi,

I was recently forced to remove SEPM from the server that it was on. I've rebuilt a new SEPM box but it is on new hardware with a new hostname and, of course, new IP. I'd like to point my existing clients to the new SEPM but am having a difficult time finding any information on this. It doesn't seem to be as easy as the legacy product (using GRC.dat). Is there a way to rehome the clients or do I pretty much have to redeploy the packages to them from the new SEPM?

Thanks,
Lee

ASKER CERTIFIED SOLUTION

xmachine

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sprengy

Hi,

You can copy your new sylink file to all new clients and servers. After copying the enw file, you must restart the SEP service in order to apply all changes. This is the most easiest and quickest way to perform this action.

You are a lucky person when you have software delivery like RDP, SMS etc. Then you can push the new sylink and restart the service automatically on all clients and servers.

Suc6.

KLCrow

ASKER

Thanks so much for the suggestions. I did see the sylink file the other day and tried to copy the new one to one of the clients. However, I received a message stating that the file was currently in use and I could not overwrite it. I still received the message even after stopping all of the Symantec services. Any ideas regarding that?
Thanks!
Lee

xmachine

you can do this

start > run > smc -stop

replace the file

start > run > smc -start

The SylinkReplacer tool will fix all machines in your network with the new sylink.xml (of some group in the new server)

KLCrow

ASKER

Sylinkreplacer rocks! Thanks guys for both of your help!