Cloning a Symantec Endpoint Protection for Macintosh client
| Article:TECH183447 | | | Created: 2012-03-09 | | | Updated: 2012-03-09 | | | Article URL http://www.symantec.com/docs/TECH183447 |
Problem
This document lists the best practices for cloning a Symantec Endpoint Protection for Macintosh client in either a physical or virtual environment. If this document is not followed then cloned Endpoint Protection clients will have duplicate identifiers which will result in problems with management and reporting. These instructions are for the Macintosh client. For Windows clients, see Configuring Symantec Endpoint Protection for deployment as part of a drive image.
Solution
Prepare the base system.
- Install the operating system, applications, and patches.
- Install the unmanaged Symantec Endpoint Protection Client and update the definitions.
The following step is necessary only if clones of this system are to be managed: - Just prior to creating an image of this system, put a sylink.xml file into place as per the manual instructions in How to convert an unmanaged SEP for Macintosh client to managed. Do NOT use the SyLinkDrop tool or restart the smclient service.
- Create an image of the base system, and use this image for cloning operations. When a clone starts up for the first time, any sylink.xml file will be processed and the client will be converted into a unique managed client.
If a SEP client that is already managed is cloned, this will cause duplicate client entries in the SEP Manager (or only one entry for several Macintoshes). To correct this problem, uninstall and re-install the SEP client on the affected Macintoshes. This is the only way to force a regeneration of the unique identifier used by a managed SEP client on the Macintosh; there is no "ClonePrep" tool in SEP for Macintosh.
|
|
Article URL http://www.symantec.com/docs/TECH183447
Terms of use for this information are found in Legal Notices
Thank you.