Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 6763 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

Move clients to a new server

Eps

Hi All,

A company I look after has just had their SEC server fall over and die. All the 300 clients are still fine, but they are now server-less. The plan is to permanantly move the clients to a new server which is already named and will not be renamed as the naming convention is required for other software.

I have setup SEC on the other server and have my 300 clients imported from AD. My question now, is how can I get them all to connect to this new server and update from 7.x to 9. I have set update policys and everything. I just need to wrap my head around getting these clients to report to this server.

Any help is appreciated :)

:9929


This thread was automatically locked due to age.
Parents
  • 0
    Hi,
    You should be able to redeploy be it via:
    1. A protect from SEC (downsides being a bit slow and the clients need to be on and you need to be able to connect to them to create a scheduled task so a few dependencies)
    2. Running setup.exe from the central installation directory manually
    3. Running setup.exe from the central installation directory with switches to automate it
    The switches can be found on this article:
    http://www.sophos.com/support/knowledgebase/article/12570.html
    I find the easiest way to get the right command is to protect a test machine from SEC, monitor its scheduled tasks and as soon as the install job is created open the properties of it and grab the command line.  This will give you all the switches including an obfuscated username and password, which I find quicker than fiddling around with obfuscationutil.exe
    You might find it easy to deploy this command with a startup script.  There was one example here:
    http://www.sophos.com/support/knowledgebase/article/13090.html
    which details how to deploy with an AD statup script but not to keep running setup.exe by checking for the presence of Alsvc.exe.  Obviously you would need to change this check to a file that only exists on 9.5 otherwise it would not re-run.
    Checking for:
    C:\Program Files (x86)\Sophos\AutoUpdate\SingleGUIPlugin.dll
    C:\Program Files\Sophos\AutoUpdate\SingleGUIPlugin.dll
    might be one option taking a quick glance.  This only exists on a 9.5+ install.
    I would suggest only linking such a GPO to an OU of clients rather than all machines on the network initially until proven to work. :)
    Which ever way you do, be it the VBScript method or re-running setup.exe, I would suggest trying the method on 1 or 2 machines to ensure it works before rolling it out to others.
    Regards,
    Jak
    :10125
Reply
  • 0
    Hi,
    You should be able to redeploy be it via:
    1. A protect from SEC (downsides being a bit slow and the clients need to be on and you need to be able to connect to them to create a scheduled task so a few dependencies)
    2. Running setup.exe from the central installation directory manually
    3. Running setup.exe from the central installation directory with switches to automate it
    The switches can be found on this article:
    http://www.sophos.com/support/knowledgebase/article/12570.html
    I find the easiest way to get the right command is to protect a test machine from SEC, monitor its scheduled tasks and as soon as the install job is created open the properties of it and grab the command line.  This will give you all the switches including an obfuscated username and password, which I find quicker than fiddling around with obfuscationutil.exe
    You might find it easy to deploy this command with a startup script.  There was one example here:
    http://www.sophos.com/support/knowledgebase/article/13090.html
    which details how to deploy with an AD statup script but not to keep running setup.exe by checking for the presence of Alsvc.exe.  Obviously you would need to change this check to a file that only exists on 9.5 otherwise it would not re-run.
    Checking for:
    C:\Program Files (x86)\Sophos\AutoUpdate\SingleGUIPlugin.dll
    C:\Program Files\Sophos\AutoUpdate\SingleGUIPlugin.dll
    might be one option taking a quick glance.  This only exists on a 9.5+ install.
    I would suggest only linking such a GPO to an OU of clients rather than all machines on the network initially until proven to work. :)
    Which ever way you do, be it the VBScript method or re-running setup.exe, I would suggest trying the method on 1 or 2 machines to ensure it works before rolling it out to others.
    Regards,
    Jak
    :10125
Children
No Data