Machines changing from SEP-managed to self-managed
Updated: 22 May 2010 | 10 comments
Hello!!
Since a few days, I have checked that a lot of machines changed their status from managed (connected to SEP server) to self-managed but I dont know why.
The strange is that those machines appears in symantec endpoint manager with the green dot, as connected to the server, but they are not receiving my policies. The update policies option is not available when they are self-managed
Somebody suffered the same problem? Is there any solution to re-connect those machines to server, Or I must have to replace their incorrect sylink.xml from the correct version? (using the netlogon script for example)
Why symantec not provide a tool to replace sylink.xml remotely?
The most important to me is to know the reason of this behaviour.
Thanks in advance!!!
Discussion Filed Under:
Comments
This can happen if you installed the SEPM and created the installation packages via an RDP session. If this is the case, to resolve this issue you will need to completely remove the product and install it while local to the SEPM machine. You will also want to make sure you are running the current build, MR2MP1.
Message Edited by Ted G. on 06-13-2008 07:28 AM
Message Edited by Knottyropes on 06-13-2008 01:54 PM
Let me clarify.
...Installed/created in an RDP session that did not have console level access to the machine.
If you are going to use RDP to install the product and create installation packages you MUST ensure you have console level access to the machine, as I stated in another thread. Knotty knows this, as he has read and participated in that thread. No clue why he is so upset.
My bad for not posting that information here.
In order to see what type of connection you have to the machine, while remotely connected to said machine, open a DOS box on the machine you are remoted into and type "set" without the quotes. Scroll down until you find the "SESSIONNAME=" line. If it says anything other than Console, you do NOT have console level access to the machine.
For information on how to establish console level acces in RDP and install our products, please refer to the following document:
Title: 'How to install Symantec Endpoint Protection and Symantec Endpoint Protection Manager through Remote Desktop'
Document ID: 2008030509272248
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008030509272248?Open&seg=ent
Hi Greg,
That is an excellent question! I consulted some other techs here and we all came to the conclusion that running cleanwipe and re-deploying would be the best way to handle this. I know it's a pain, and I sincerely apoligize for that. But it really is the best way to ensure optimal results. We determined that over-installing would most likely not clean up whatever was causing the issue in the first place.
If you need the cleanwipe utility, you will need to call in to support and have a technician mail you the instructions for obtaining it. It's always best to use the latest version even if you have an old one laying around on a disk, or in a folder somewhere.
Would you like to reply?
Login or Register to post your comment.