Importing Sylink.XML into the newly upgraded SEPM ?
Created: 29 Nov 2012 | Updated: 30 Nov 2012 | 6 comments
This issue has been solved. See solution.
Hi,
Do I need to copy the Sylink.XML from the each subnet before creating new deployment package in the newly built SEPM ?
Thanks
Discussion Filed Under:
Comments 6 Comments • Jump to latest comment
You can just push the new upgrade client to your existing clients. They will upgrade and point to the server after the upgrade is done.
SEP Knowledge Base
Endpoint SWAT
Hi,
Check this artical.
How to point clients to a new SEPM after decommissioning or replacing the primary SEPM
http://www.symantec.com/docs/TECH92556
Thanks In Advance
Ashish Sharma
SEPM Knowledgebase Documents
Cool, so in this case I do not need to worry about keeping sample of the existing Sylink.XML because SEPM server has already take care of it.
Kind regards,
John Santana
Graduate IT Professional
--------------------------------------------------
Please be nice to me as I'm newbie in this forum.
Yes, that's correct. No need to replace.
SEP Knowledge Base
Endpoint SWAT
Hi,
No need to replace Sylink.xml.
The group which you select while exporting the package all the clients will check in to the same group.
Best option is to move the clients manually to the respective groups.
Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |
Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.&
great, many thanks all for the suggestion !
Kind regards,
John Santana
Graduate IT Professional
--------------------------------------------------
Please be nice to me as I'm newbie in this forum.
Would you like to reply?
Login or Register to post your comment.