Ensure that you have the ability to change settings and run LiveUpdate on the client before changing the client to unmanaged. If you change the client to unmanaged without ensuring that you can change settings on the client , you may need to uninstall and then reinstall the client if you need to change settings in the future.

To change the clients to unmanaged without reinstalling you may follow the following  link

http://service1.symantec.com/SUPPORT/ent-security....

PMF,

In SEPM CD1 you will have setup files & folders like Data, SEPM, SEP, SEPwin64 folders.

In SEP folder you will find sylink.xml file . This xml file is unmanaged & will get update from internet.

Ramji, thanks for your information. If it is right then the client I tested on should already be able to update itself.
Though I am not sure yet, because of Cycletech´s earlier answer.
Thank you all so far, I´ll keep you informed.!

@ PMF, Ramji's solution should work for you. As always test to verify.

Regards,
Thomas

Replace the Sylink.Xml file from the SEP Install Package (Folder )which you have Downloaded or from the Cd.

1. Open the SEP Folder from the which you have downloaded.
2. Copu the Sylink.Xml file
3. Then Go the Machine which you want to make Self Managed
4. Stop the Smc Service
5. Start-- Run-- Smc - Stop
6. Copy the sylink file to the Symantec Endpoint Protection  install Location
7. By Default it's on C\Program Files\Symantec\Symantec Endpoint Protection
8. Then Start the Smc service .Start-- Run--- Smc -Start

I followed the procedure as described by Ramji and Shaizad, but in SEP on the client the defenitions are still from 21 july. And SEP says 'no problems detected".
On purpose I waited for more than a week as the 'scheduled updates" in Live update showed every one week (greyed out though).
Also, the Live update button on the left side of the SEP-screen is greyed out and says "your adminstrator locked this feature".
It looks like the client is still 'managed' and is not updating.

You can enable  the Liveupdate buton by using the registry key bwlow:

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\LiveUpdate\AllowManualLiveUpdate

If you set the value to 1, the Liveupdate button will be activated.

then you can click on it to run the liveupdate

I like the registry method
I can query all my clients for the reg value to check if they are updating or not,
Is there anything in the Sym Admin Console to check for the same?

Thanks
Anesh

Steps to ON and Off the Liveupdate

1) It is advisable to backup the registry before editing.
2) Click Start > Run > Regedit.
3) In the Registry Editor go to HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\LIVEUPDATE.
4) In the right pane, locate the String Value “AllowManualLiveUpdate”.
5) Double click on the string value and change the Value data to zero.
6) Close the editor.
7) If the String Value “AllowManualLiveUpdate” is not present the you need to create it and you can do this by right clicking in a blank area of the pane and click on New and choose DWORD Value.
8) Name the new value “AllowManualLiveUpdate” ,without the quote marks, you can leave the default value of zero and this will disable the LiveUpdate button on the SEP client GUI. (Note: To Turn ON default value of 1)
9) Close the Registry editor.
10) Open the SEP client GUI and verify that the LiveUpdate button is disabled.

I think the registry option wont be possible if one has lots of clients.
The better option would be you can install a new SEPM on your site ( or if there is any SEPM in you test network ) & you can enable the live update tab & also the scheduling for live update. ( through live update policy) you can export that policy from any of the client that is reporting to the SEPM & then import it on to your client.

But again the easiest and simple would be to install a new SEPM & let all the clients communicate to the SEPM using the sylink replacer make the policy changes & if you want you can again uninstall all the clients.:)

Hi,

Could you please Let us know How amny Clients in total (along with Servers) do you have...??

This is important when it comes to providing you an exact solution... :)

Just a piece of advice you can try to replication the sepm and then create a policy for management server list where the new server is the priority one.hope this helps