Hi All ..
I have successfully moved SEPM from 400 more clients to other servers running on another location using a simple script .
I use Psexec.exe to run scripts remote computers
*****steps are as bellow
1.First export the Sylink.xml from the group you want your clients to report to initially from your old SEPM server.
Note: if you have more than one group you should get file "Sylink.xml" each group separately
2. Then follow the bellow steps
3. Now you ready to run scripts
Note:You should do the steps each group you have one by one Note : This Script can run only the Member of Doman Administrators or Local Administrator of Client PC
i think this will help to all..
Cheers
I'm new to managing SEPM but we have Version 12.1.6 (12.1 RU6 MP4) Build 6867. I'd like to use the same style of script but I'm confused. Do I have to export the SyLink.xml file from the old server or from the new?
Also, for the copy.bat script, I see "xcopy SyLink.xml \\ 192.168.1.1\c$ “. Is the IP referenced in this script the IP of the new server or is that where I'd have to list the IP for each client that needs to be moved over to the new server? Also, do I have to physically run the script on each system or can this be done remotely? Again, I'm fairly new to all of this. Please help. Thanks!
Hi dear,
i have a server that is installing SEPM and clients is sep-unmanager-12.1. Now i want to deploy sylink file to all clients. i have tried the above methods but they all isnot successful. Can anyone help me? if you have any suggestion, pls email me at huenc1@yahoo.com.
thanks in advance!
trkmany and Others,
We recently have lost connection to our management console thus leaving our agents in our network without connectivity for definition updates and so-on.
The method described above will not work for version 12 as the location for SMC.exe and the location that the XML file is located has changed for both 32-bit and 64-bit machines.
SMC.exe is located in:
32-bit: C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Bin\
64-bit: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Bin\
The area in bold changes as the application updates and causes issues with people who wants to write a PowerShell script to simply update the network PC's as the path changes with revisions.
Symantec is forcing you to use the SylinkDrop.exe utility and it simply drops the XML in the following location:
C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config\
I have confirmed that you can simply replace the XML file in this location and it will link back up with the management console.
The other issue at hand is that you cannot replace the XML file while the "Symantec Services" are still running. It order to replace the XML file on each PC you will have to run a "-stop" command against the SMC.exe file, Copy XML and then run a "-start" against the SMC.exe file.
As you can see, this is fairly ridiculous but can be accomplished if you have proficient skills in PowerShell. I am building a script with a partner of mine to fix this issue right now and I hope to have it done by April of this year.
The code will be freely available at Github and Bitbucket.
Updates to follow...
~bbunnelle
Hi All,
I have same scenario
Can this script work with SEPM 12.0
Thanks ..
can anybody tell me the ABOVE solution for SEPM 11.0
Hello Chinthakad,
Thank you for the great script...
I have reinstalled a new SEPM and replaced Sylink.xml to all my clients... BINGO!!!
Cheers,
-Charbel-