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

    Eps,

    We use a central default Domain Policy script to install Sophos on all of our clients. If a new machine (or any machine for that matter) boots up and is not found to have Sophos client, it will auto install on first boot. We haven't had a single hitch. You can test it by putting this in a .bat for your Windows Startup script on an OU. If it works then it should work domain-wide. Like Jak said though, you would need to check for the ALsvc.exe. If it's already there, you'd have to omit those lines that check for it or either modify it.

    There is also a tool that you can use to obfuscate the domain admin username and password as well in the script so it's not in plaintext.

    @ECHO OFF
REM --- Check for an existing installation of Sophos AutoUpdate
if exist "C:\Program Files\Sophos\AutoUpdate\ALsvc.exe" goto _End
if exist "C:\Program Files (x86)\Sophos\AutoUpdate\ALSVC.exe" goto _End

REM --- Check for servers not to install to
if %COMPUTERNAME% == <COMPUTER YOU DON"T WANT SOPHOS ON HERE>goto _End
if %COMPUTERNAME% == <COMPUTER YOU DON"T WANT SOPHOS ON HERE> goto _End

REM --- Deploy to Windows 2000/XP/2003
\\SERVERNAME\SophosUpdate\CIDs\S000\SAVSCFXP\Setup.exe -updp "\\SERVERNAME\SophosUpdate\CIDs\S000\SAVSCFXP" -ouser "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -opwd "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -mng yes
REM --- End of the script
:_End

    P.S. - Make sure there is no word-wrapping being done on the script or it won't run correctly. The line which references your setup.exe file is one HUGE line.

    :10203
Reply
  • 0

    Eps,

    We use a central default Domain Policy script to install Sophos on all of our clients. If a new machine (or any machine for that matter) boots up and is not found to have Sophos client, it will auto install on first boot. We haven't had a single hitch. You can test it by putting this in a .bat for your Windows Startup script on an OU. If it works then it should work domain-wide. Like Jak said though, you would need to check for the ALsvc.exe. If it's already there, you'd have to omit those lines that check for it or either modify it.

    There is also a tool that you can use to obfuscate the domain admin username and password as well in the script so it's not in plaintext.

    @ECHO OFF
REM --- Check for an existing installation of Sophos AutoUpdate
if exist "C:\Program Files\Sophos\AutoUpdate\ALsvc.exe" goto _End
if exist "C:\Program Files (x86)\Sophos\AutoUpdate\ALSVC.exe" goto _End

REM --- Check for servers not to install to
if %COMPUTERNAME% == <COMPUTER YOU DON"T WANT SOPHOS ON HERE>goto _End
if %COMPUTERNAME% == <COMPUTER YOU DON"T WANT SOPHOS ON HERE> goto _End

REM --- Deploy to Windows 2000/XP/2003
\\SERVERNAME\SophosUpdate\CIDs\S000\SAVSCFXP\Setup.exe -updp "\\SERVERNAME\SophosUpdate\CIDs\S000\SAVSCFXP" -ouser "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -opwd "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -mng yes
REM --- End of the script
:_End

    P.S. - Make sure there is no word-wrapping being done on the script or it won't run correctly. The line which references your setup.exe file is one HUGE line.

    :10203
Children
No Data
Unfiltered HTML