Endpoint Protection

 View Only
Expand all | Collapse all

SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

Migration User

Migration UserSep 30, 2009 07:00 AM

  • 1.  SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 06:09 AM
    Hi to you all,

      I'm sure most of you do know how to an unmanaged SEP client to the Symantec Endpoint Proctection Manager. Please do give me the exact procedure. Thanks!


  • 2.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 06:25 AM


  • 3.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager
    Best Answer

    Posted Sep 03, 2009 06:48 AM
    How to change a Symantec Endpoint Protection client from unmanaged to managed in MR1 and MR2.

    http://service1.symantec.com/support/ent-security.nsf/docid/2007082009543848

    after reading the doc above once you have found which is the correct sylink.xml you have to replace

    1. Make a copy of the file Sylink.xml on removable media.
    2. On the client computer, click Start> Run, type smc -stop, and click OK.
    3. Copy the Sylink.xml file from the removable media into the Symantec Endpoint Protection installation folder, and replace any existing Sylink.xml file.
      The installation folder may be either C:\Program Files\Symantec\Symantec Endpoint Protection\ or C:\Program Files\Symantec\Symantec AntiVirus\.
    4. Click Start > Run, type smc -start, and click OK.
    5. A green dot appears on the Symantec Endpoint Protection 11.0 icon in the notification area of the taskbar. This green dot indicates that it has successfully connected to the Symantec Endpoint Protection Manager.


  • 4.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 09:01 AM
    Apart  from the one mentioned above there are 3 more ways in which we can  make unmanged client managed.

    Sylink Drop

    Sylink Remote
     
    Sylink Replacer

    Sylink Remote and Sylink Replacer will replace the sylink on more than on machine at the same time automatically without going to each and every machine.

     


    Title: 'How to change a Symantec Endpoint Protection client from unmanaged to managed in MR3 and above.'
    Document ID: 2009030314365748
    > Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009030314365748?Open&seg=ent



  • 5.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 09:46 AM
    SEP v11 MR4 R2 has been recalled per Symantec 8.31.09 so I am sure your comments refer to another version of insanity. 


  • 6.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 09:59 AM
    What do you mean when you say 'recalled per Symantec 8.31.09'?

     MR4MP2 (11.0.4202.75) is the current, valid version of SEP as of 9.03.09.


  • 7.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 01:09 PM
    via WebEx session and v 11.0.4014.26, which is the version currently installed on the managing server, which is a performance hog and does not perform the unmanaged updates to the clients and has garbled the registries on all of our clients and servers, is the version I was told by Symantec that was recalled and then was told I HAD to install v12.  I REFUSED!!!


  • 8.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 01:25 PM
     11.4010.xxxx was recalled not 11.0.4014.26.The latest version is 11.0.4202.xx. Since you would be having a Small Bussiness Network ( less tha 100 computers) Support might have have suggest to switch to Version 12.


  • 9.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 02:30 PM
    Hi Vikram...I was told by Symantec that ALL 11.0.40XX.2X was recalled and whatever server or client this had been loaded on would need to be 1. uninstalled 2. run cleanwipe 3. clean the registry 4. run cleanwipe again.  I had just completed these steps to remove 10.2 'savmain' files and 'symantec v12' v12 files from the registry on each machine...and you are correct...our network consists of less than 100 clients...at 2-2 1/2 hours per machine, this is not good.  Kronos or a similar application will not work in this instance either because of the footprint that Symantec leaves...it is truly amazing...

    If the current version is 11.0.4202.xx and there is success out there, then WOW and blessings, but again Symantec, Engineers I might add, stated that if this version was loaded it will deifinately have to be TOTALLY removed using the above noted steps IF you want your network protected - IF.  ARGH!

    Thank you so very much for your reply as I have had a long frusterating experience here and I really appreciate the conversation!!! THANK YOU!


  • 10.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 02:35 PM

    Greetings again, I just wanted to add that I do hope the above steps help someone along the way.  I would swear by SAVCE 10.2 and before...  And I do utilize other Symantec products.



  • 11.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 02:39 PM
    lyndy333: Vikram Kumar is right and it seems that you have been misinformed about which version that was recalled. See link below about current version. If you login to fileconnect you will also see that this is the current available version. The newest version does have its flaws just like every version so far however I think it is still the best choice of all the versions available.


    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121216360648


  • 12.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 03, 2009 02:56 PM
     The version 11.0.4010.xx was recalled due to a issue in the firewall..it used to block file shares.
    << 1. uninstalled 2. run cleanwipe 3. clean the registry 4. run cleanwipe again.>>
    Whoever suggested this must be out of his mind that day or would have suggested you this for particular machine..

    To remove SEp you need to simply go to ADD/Remove Programs and you can remove it from there..

    The Latest Version in SEP is indeed 11.0.4202.xx and it has been the most stable almost Zero Bug build.

    But Still even I would recommend SEP 12 for you for reasons
    1.Less in Cost
    2. Smaller Footprint
    3.Easy to install and Configure
    4.Easy to Maintain and Administer
    5.Best suited for Small BUsiness requirements.


  • 13.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 09, 2009 11:09 PM
    Hi All,

    Has it been released yet ?

    i couldn't find it in my symantec file connect ?

    i can only find: Symantec Endpoint Protection 11.0 - International English - 11.0.4202 MR4 MP2


  • 14.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 10, 2009 01:06 AM
    Yes Albert SEP 12 SBS for has been relased. It has been more than 3-4 months
    Yoo will net get that on the fileconnect site
    For that you have to call symantec licensing and get the license forthat or you have to contact your reseller


  • 15.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 10, 2009 05:41 AM

    Yes SEP SBS 12.0 is now available and the reason you are not seeing it in  fileconnect was because you might be using a serial number for SEP 11.0.

    SEP SBS 12.0 is not upgrade for SEP 11.0. You would need to contact customer care to request for your migraton to 12.0. This will be free if you have valid maintenance.

    Cheers,
    Belle


  • 16.  RE: SEP - How to an unmanaged SEP client to the Symantec Endpoint Proctection Manager

    Posted Sep 30, 2009 07:00 AM
    Ok, thanks to you all.