Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 3472 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Deploying clients to remote offices with slow link

Uncle_Ben

Hi ALL,

We are deploying the sophos to the clients that are located in the remote offices and outlet with a slow link to HQ. I created another thread before saying that I change the Initial Install Source to a local server's folder but it's totally failed and I gave up. Next, I use the cmd line method to deploy the clients like this:

\\172.18.10.1\sophosupdate\CIDs\S000\SAVSCFXP\setup.exe -mng yes -crt R -updp \\172.18.20.1\SophosUpdate\CIDs\S000\SAVSCFXP -user 172.18.20.1\SophosUpdateMgr -pwd sophosupdate -G \SOPHOS1\TEMP -s

Local subnet: 172.18.10.0/24

Remote subnet: 172.18.20.0/24 (HQ)

Local PC to install Sophos: 172.18.10.60

Local server sharing the source for installation and first time update: 172.18.10.1

Remote server sharing the source for further updating: 172.18.20.1 (HQ)

With the above cmd line, I found some issues...  :smileysad:

[1] Once the client successfully installed the sophos endpoint, the update will pointing to the HQ server... that's good and as expected, but I thought the FIRST TIME update should using the one in the local source? The installation is smoothly and good, but the updating takes 2 hours....... it's no good for a slow link over IPSec VPN.

[2] The "-G" parameter is not function... even I tried to put the different groups... the result is, the new deployed client would just in "unassigned" group

My requirement is quite reasonable: Let the local PCs to install the sophos endpoint from the local shared folder (with all necessary update) and then pointing the update primary server to the remote one for any further updating.... as told by the Sophos guys, the regular update of definiation should be below 100kb... I set the periodically update for every 60 minutes~ I wonder why the first updating need to update so many files from the REMOTE server.... does there any way can do it as expected??

Any advise / suggestions are welcome and appreciated !! Many thanks !!!  :smileysurprised:

:4524


This thread was automatically locked due to age.
Parents
  • 0

    Solved is not "closed" and it can be helpful to have comments or other aspects on a thread.

    Now the original "solution" assumes that the client receives a valid updating policy (including the required credentials) from the management server. Otherwise it will either use a sauconf.xml from the CID or a command line argument to setup.exe. Look at what's in the iconn.cfg (or the update location in the GUI) after the initial install. Note that the credentials you used to access the share re not transferred to the config file (as they are not available). Running setup.exe without switches opens the install GUI which asks for credentials and saves them in the config.

    HTH

    Christian

    :10693
Reply
  • 0

    Solved is not "closed" and it can be helpful to have comments or other aspects on a thread.

    Now the original "solution" assumes that the client receives a valid updating policy (including the required credentials) from the management server. Otherwise it will either use a sauconf.xml from the CID or a command line argument to setup.exe. Look at what's in the iconn.cfg (or the update location in the GUI) after the initial install. Note that the credentials you used to access the share re not transferred to the config file (as they are not available). Running setup.exe without switches opens the install GUI which asks for credentials and saves them in the config.

    HTH

    Christian

    :10693
Children
No Data