Cloning systems with Sophos and Sysprep

During deployments of multiple systems with the exact same hardware configuration, Sysprep is the most common tool to assist this along with Ghost.

If you have Sophos on your original deployment image, you may find that you cannot access the Sophos console on cloned systems with Sysprep (or other tools that change the computer SID).

To repair this:

http://www.sophos.com/support/knowledgebase/article/12561.html


If you have already deployed cloned systems and need to repair your Sophos installation follow the instructions at the bottom of the article, “Changed SID values and Sophos Anti-Virus”:

On a computer where the SID value has been changed, open a command prompt and type the following command:

On Windows Vista the command is:

-

If you are doing this on the master image before you have deployed it or after you have deployed cloned systems, follow the link above.

  1. On the template computer, stop the following services (if they are present):
  1. Read the Microsoft warning about editing the registry.
  2. On the template computer, in turn, open each of the following registry keys (if they are present):

and, in each key, delete the following two entries

Note: These keys must not be removed from a server running Enterprise Console.

  1. Delete the following files from the template computer:
    C:\Program Files\Sophos\AutoUpdate\Data\Status\status.xml
    C:\Documents and Settings\All Users\Application Data\Sophos\Sophos Anti-Virus\Config\Machine.xml

Revision #1
Created 2009-10-09 00:47:53 UTC by Won, Brian J.
Updated 2009-10-09 00:47:53 UTC by Won, Brian J.