Endpoint Protection

 View Only
  • 1.  deploying client to unmanaged approx 80 computers fails - help !

    Posted Mar 02, 2011 05:58 PM

    I am trying desperately not to have to go to all of the many dozens of Windows workstations to re-establish communications with the SEP Management server, so that's why I'm giving this forum a shot.  The management server has to be reinstalled from scratch with no backup or restore available.  All of the client computers already were communicating and updating before this happened.  All I want to do is re-establish communications with their parent Management server for Symantec Endpoint Protection (SEP 11.0.6200.754) but nothing is working outside of having to go to EACH WORKSTATION in person to stop the SMC service, replace the sylink.xml file, then restart the SMC service again.  This is very unpracticle as we have several sites across town and about 80 machines.

    I have tried the "Find unmanaged computers" option in the console, but that isn't working whether or not the deployment status comes back successful OR failed.  I've used the "Sylinkreplacer" utility and that isn't working.  Lastly, I've also tried the Migration and Deployment Wizard on SEPM server and that isn't working at all.  All of these options will produce a status of "successful", but the client never shows up in the management console.

    Please help !  Many thanks crying



  • 2.  RE: deploying client to unmanaged approx 80 computers fails - help !
    Best Answer

    Posted Mar 02, 2011 06:21 PM

    1. SylinkReplacer tool should work in your case

    http://www.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

    2. If that doesn't work. Create a new installation Setting usng "remove previous logs and reset client-server communication" From SEPm-Admin-Install Packages.

    Then use this eith using Find Unmanaged Computer or Export a installation Package using this a deploy using Deployment Wizard.

    Check this link

    http://www.symantec.com/business/support/index?page=content&id=TECH104955&locale=en_US



  • 3.  RE: deploying client to unmanaged approx 80 computers fails - help !

    Posted Mar 03, 2011 01:59 AM

    Hello

    1.Try to locate the domain ID from the sylink.xml file on the client not communicating located at:

    C:\program files\symantec\symantecendpoint protection

    Right click on the file, and open with notepad.

    Locate the domain ID in the file, copy and paste it on the notepad.

    2. Browse to SEPM select Admin option on the far left.

    3. Select add domain, new window pops-up. Give this a new name, and select the advanced radio button.

    4. Once you click on Advanced, it will ask for the Domain ID.

    5. Copy the Domain Id that was pasted on the notepad in step1. here.

    6. Click "Default" domain, and under tasks select disable. SEPM logs off.

    7. You will notice the clients communicating with the new SEPM, once  that starts to happen, delete the "Default" Domain ID.

    Please note: The clients where you already replaced sylink.xml, will not be able to communicate after performing these steps, please replace the sylink later onne rest of the clients are communicating fine.



  • 4.  RE: deploying client to unmanaged approx 80 computers fails - help !

    Broadcom Employee
    Posted Mar 03, 2011 05:36 AM

    Hi,

    When you run sylink replacer, is it discovering all those clients in network where you want to replace sylink.xml ?

    Make sure you have sufficient privilege, when you run sylink replacer it will ask to have member of groups to replace sylink.xml.



  • 5.  RE: deploying client to unmanaged approx 80 computers fails - help !

    Posted Mar 03, 2011 10:34 AM

    http://www.symantec.com/business/support/index?page=content&id=TECH104753&locale=en_US

    This may assist, provided that you are able to actually have a deployment status of successful. It will not assist in scenarios where the SEPM is not able to successfully deploy the installation package.

    Also something to note, deployment status successful does not necessarily mean that the installation completed successfully. This simply informs us that the SEPM was able to copy the installation files over to the machine. In order to confirm successful installation you would need to check for an updated installation log of the SEP client, sep_inst.log. Typically this will be located in the temp directory, which can be accessed by going to Start>Run %temp% and hit OK. If the file is not in that location you can also check the Windows\Temp directory as well.

    If you open the log file in notepad, and perform a CTRL+F for "Value 3", without quotes, you should be able to locate if the install was successful or failed. If you do find a "Value 3" in the log, this typically means the installation failed. You could either call into support, or post the log file here for further assistance.

    Regards,