Endpoint Protection

 View Only
Expand all | Collapse all

Remote site configuration

  • 1.  Remote site configuration

    Posted Aug 26, 2015 07:06 PM

    I have a customer with SEPM 12.1.6 (12.1 RU6) build 6168 installed on Site 1 - around 500 clients. They also have a remote site (Site 2) with <20 clients to manage. I would prefer to to decommission the SEPM installation on Site 2 and somehow manage these clients from Site 1.



  • 2.  RE: Remote site configuration

    Posted Aug 26, 2015 07:56 PM

    Are they setup as replication partners or separate from one another?

    If standalone, you can easily move over the small amount of clients by deploying a new communication file from the SEPM you want them to connect to.

    Restoring client-server communications with Communication Update Package Deployment

    If replication partners, simply edit the management server list and make the SEPM you want them to connect as Priority 1 and once they pick up the new policy they will move over to it.



  • 3.  RE: Remote site configuration

    Posted Aug 27, 2015 07:19 PM

    They are not replication partners. Seperate servers, different versions. Site 1 is up to date, Site 2 (the remote site), lagging behind.

    I tried to send a Communication Package from Site 1 to a client at Site 2, I can ping the client but the Communications Package won't deploy.



  • 4.  RE: Remote site configuration

    Posted Aug 28, 2015 12:49 AM

    please check if they have password to stop the smc service, in that case you need to enter it as well.



  • 5.  RE: Remote site configuration

    Posted Aug 28, 2015 02:12 AM

    The SmcService was running. I had no ability to stop it. Even as a local admin.

    The service is configured as a local system account under Log On.

    Does it require a port to be openend?



  • 6.  RE: Remote site configuration

    Posted Aug 28, 2015 03:41 AM

    you mean smc -stop command didn't work ? did you try it from command prompt or from run command ?



  • 7.  RE: Remote site configuration

    Posted Aug 30, 2015 06:41 PM

    Checked remotely via Computer Management. I doubt that is the issue anyway?



  • 8.  RE: Remote site configuration

    Posted Aug 30, 2015 09:16 PM

    Just FYI, by default, you won't be able to stop the SEP service through Services console. The service can be stopped only by executing the "smc -stop" command in "Run". However, you don't need to manually stop the SEP service to deploy the communication package from a SEPM.

     

    If the remote deployment of the communication update package fails, try saving the communication package and copy it to one of the clients in site2 and (after unzipping) manually execute the sylinkdrop.exe and chec if that works.



  • 9.  RE: Remote site configuration

    Posted Aug 30, 2015 10:18 PM

    They are behind a firewall, do I need to open certain ports?



  • 10.  RE: Remote site configuration

    Posted Aug 30, 2015 11:07 PM

    If the required ports are already not allowed, you will have to allow them for the deployment to work.

    Please check the acticle at the following link for details of ports used for remote deployment.

    http://www.symantec.com/docs/TECH163112



  • 11.  RE: Remote site configuration
    Best Answer

    Posted Sep 11, 2015 04:02 AM

    OK resolved. It was a routing issue on the management server. Can successfully send new communication settings to workstations.