Endpoint Protection

Hello, I recently built a new  SEPM and have started cutting a small amount of machines over from our old SEPM to the new one.  I'm expanding my test group to now include end-users and have picked about 6 I will cutover to the new SEPM.  When push out the communication update package it appears to have gone through.  I get a green arrow in both fields and after it says it was successful. 

However, the new clients do not appear on the new server and the client is still pointing to the old SEPM.  Has anyone come across this and have a solution?  Any help you can offer would be appreciated.

What's the SEP/SEPM versions? I assume you're on at least RU2 if you're doing it from the SEPM?

Is there a password needed to stop the smc?

Hi

Please refer the following

What are the OS if its Windows 7  if yes then

1. Base filtering engine service must started.

2. UAC must be disabled

3. Disabled the Tamper Protection

Regards

Hello,

in the end, the communication settings which allow clients to connect to the manager are in sylink.xml.

Whatever is the method you use to move the clients from a SEPM to another, it must result in a new sylink.xml in the clients, does it get replaced or not? You may check timestamps and content of that file, you will easily spot the management server list to determine if it is or not the expected one.

If it is the expected one but the clients are still connecting to the old SEPM, it means they are using the backup of the old sylink.xml because the new connection fails, likely due to a firewall in the middle.

If the sylink.xml does not get replaced, something is wrong in the procedure you use to do it.

Hmmmm, I'd recommend reviewing these articles.  They discuss teh various methods of replacing teh sylink file (pointing client at new server), and what can sometimes happen to cause them to fail back to the source sepm.

http://www.symantec.com/docs/TECH92556
http://www.symantec.com/docs/HOWTO55428
http://www.symantec.com/docs/TECH205252

Any update on this?

Hi Mohan, we had an issue with the content revisions consuming all of the hard drive space where SEPM is installed.  I had to manually go in and purge them earlier, as they were not clearing on their own even after reducing the revisions from 42 to 10.  I have to go back and delete and re-add clients.

Hi,

If client version is 12.x then  you need to stop/disable tamper protection from SEPM.

http://www.symantec.com/business/support/index?page=content&id=TECH192023

I have the same kinda issues on about 25% of my SEP12.1.3 client upgrades from 11.7.1. So what I do is remove them from 11SEPM (using "Search Client", delete) as I add them to SEPM 12 Install wizard. And after client restart I send them a communication update through the same install wizard. and then I also login to each client and update policy through "troubleshooting on client and watch it flip to proper SEPM 12 server and group. And even after all that I get a few pop up as "Disabled" or Offline" the next day. So I then either login to client and do a SMC -stop, smc -start, "update policy" and/or send them another communication update through install wizard.

Hope this helps.