Endpoint Protection

Hello everyone , I exported 12.1.6 MP2 package from a new SEPM server and installed it on an endpoint running 12.1.3 reporting to a diffrent SEPM server . Now in the logs I see that the installation was sucuesful but the client is not reflecting the change nor it is showing to the SEPM server. I am attaching the installation log for your reference for this particular client.I did the manual installation in the scnerio

 

Secodly there was another client on which I tried to do the same but via SEPM remote push and though it got updated but for some reasons it is not able to connect to the new SEPM server nor it can register itself.

 

Last thing I'd like to ask I installed this new SEPM via trial software and now recently I installed my legetimate SEP license on it and it is activated I believe that this reason was not becuase of this reason. Thanks 

 

 

Hi,

Thank you for posting your query in Symante community.

I would be glad to answer your query.

I would suggest to push out package by selecting following option.

Trial ware license can be upgraded to permenent license so this can't be the case.

Chetan while exporting the package I already selected.

Remove exisiting logs , policies and reset client server communication

 

 

In that case I believe that Client is still pending a Reboot, only after the reboot the Client with start to work as 12.1.6 SEP and will start to enfore the new policy.

In second scenerio client is successfully upgraded but not yet connected to the new SEPM.

Replace sylink.xml file maually on that machine and check whether client can connect or not.
 

HI chetan this is really strange . On two machines I installed new package while exporting I selected remove previous , logs , policies and reset client server communication but the thing is client get upgraded to the new version and when I go to Troubleshoot new SEPM is showing offline and when I go the connection status I see that they are typing to connect to the old SEPM . On both machines I am seeing same behavior . How can I fix this ? Because I have 1000+ clients I cannot manually replace Sylink file on every computer

The thing is while exporting the package I have set the setting to delayed reboot and after installation it asked for a reboot which i did even if I reboot it manually in the connection status I am seeing it is trying to connect to the old SEPM The client got upgraded in the client UI properties I am seeing that the client is also part of the same group it is showing but in the connection status It is still trying to connec to the old SEPM How can I resolve this ? Your comments would be appreciated

Hi,

Can you try to stop smc and again start smc on client machine. and then check the status.

can you try to install the package in a different computer and restart the machine as soon as it prompts to restart ?

 

As per the screenshot Management Server list is configured. Are they sharing same SQL database?

Could you PM me latest manager sylink.xml file.

If possible stop SEPM service & check newly upgraded clients can talk to the new SEPM?

 

hi everyone the ports were blocked on the firewall that is why there wasn't any communication between clients and SEPM . When required ports were opened on the firewall communication was established.