Endpoint Protection

Hi All.

I have been testing installing SEP using GPO in our domain. That works fine so far.

I did not copy the sylink.xml file from the SEPM to the install package before GPO deployment - as described in the docs this seems to make the client install unmanaged.

Questions i have are:

How can you make this a managed client? .... is it by exporting sylink.xml from desired group in SEPM and then importing to unmanaged client?
How can you tell which sylink.xml file you will need if you have a load of folders?

Hope somone can kindly advise!

Thanks,

CL.

How to change a Symantec Endpoint Protection client from unmanaged to managed,
please see KB - http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008110714513748

Hope this helps.

There are a few tips here, and an article describing a better way to handle this with Group Policy will follow:

https://www-secure.symantec.com/connect/articles/creating-transform-mst-file-control-installation-symantec-endpoint-protection#comment-2672401

When and if Symantec approves it, here's the follow-up article that answers your specific question: 

https://www-secure.symantec.com/connect/articles/startup-scripts-and-sylinkdrop-better-together

Thanks Jeff & Cycletech....

I was able to make my unmanaged client appear in SEPM fine.

I have mutlple groups in SEPM, as i have imported my computer AD structure. If i wanted to use GPO for SEP deployment, would i have to create mutplie install msi packages with different sylink.xml files? is the only was to define what components are installed via GPO us using the MST file as Jeff described?

PS - Jeff, i couldnt open the 2nd link you posted - Access denied.

Thanks.