Endpoint Protection

Hi All,

I hope someone can enlighten me,

situation:
we are migrating some of the clients (mostly server type) to our newly installed SEPM,
1st: create a package and install it to one of the client
2nd: copy the sylink.xml manually from the exact location of the sylink file (we did not export the policy or communication from the 1st client by going to help>troubleshooting>management)
3rd: use the copied sylink.xml file and IMPORT IT on the other workstations

problem: on the sep client side we can see that they are reporting to our SEPM and the status is updated and connected but upon checking on the management console, we cannot see anyone from 9 servers that having the same sylink.xml from the 1st client that we install the newly created package

i have seen some article and suggestion regarding the duplicate Hardware IDs but upon checking the sylink.xml, i'm not sure but i have not seen any hardware ID stated or included in the sylink.xml

before, those workstations are all reporting in our old sepm, meaning they all have unique hardware ID, my question is if we only copy the sylink.xml is it possible that they're going to also have the same hardware ID?

Please advice

let me know if you have any clarification

The Hardware ID is actually located on the client side - C:\ProgramData\Symantec\Symantec Endpoint Protection\PersistedData\sephwid.xml

Are the replcation set up between the old & new SEPM server? Or both are separate?

Importing the new sylink.xml file should have updated it to look at the new SEPM server.

Hi Tony,

For now i'm unable to check the client side but i also tried looking on that path to see the Hardware ID of the client,

We have existing 2 SEPMs and currently replicating, this newly built SEPM is dedicated to handle servers only so this one is separated

but those server type are also from those 2 SEPM and we just want to migrate them on this newly built single SEPM

Yes, on the client side we can see that there's a green dot and the IP of the new SEPM is defined on the connection status but when we are checking on the console no client is showing.

if we just copy the sylink.xml from its exact location from one of the sep, (not importing) and transfer it from another computer (exporting) would that cause any issue? like this one.

Have you sorted the Management Server Lists yet? It sounds like the old server is still the priority.

To ensure the policies are all correct, you're best off with exporting the xml file fro the new server (from the correct group) and then importing it to the client.

Hi Tony, yes as i have mention, the very 1st package that we extracted is from the newly built SEPM so i think it should be reporting on the new sepm. but will also consider taking a look at that.

thanks

You could have done this also if both SEPM's can communicate with each other. Setting up the new SEPM as a replication partner with the old SEPM. Then moving the servers you want on the new SEPM to a new group within the old SEPM and then updating the management server list (policies > policy components > Managment server list) on the new group to put the new SEPM as priority 1 for the new servers. Then the next time they checked in they would have swapped over SEPMs and you wouldn;t have to install new clients on them. Then you could either leave the old SEPM as priority 2 for resilience purposes or once all your servers have moved over remove the old SEPM from that managment server list.