Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 3735 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

Migrate unmanaged clients from SAV 7.6 to 9

C3PO

Hi Folks,

a quick question for the board...

I have SEC 4.0 and am migrating my Windows domain clients from SAV 7.6 to 9, no problem.

I also have many unmanaged non-domain (student) clients, which update via http from a CID on the same server.  What would be the best way to get these clients migrated from SAV 7 to 9?   I remember using ExportConfig many years ago, and wondered if this is still in use with the shiny new versions of Sophos?

Thanks all.

:6859


This thread was automatically locked due to age.
  • 0

    I remember using ExportConfig many years ago, and wondered if this is still in use

    Yup - use exportconfig to export the appropriate (new) updating policy and put the sauconf.xml in the sau folder of the current CID, run configcid.exe. After the next update the clients will use the new update location.

    Christian

    :6871
  • 0

    Thanks Christian.  I was thinking of hacking the sauconf.xml file in the current CID to point to the new CID.  Same difference, I guess.  Thanks again, and a Merry Christmas to you and all the sys admins on here :smileyhappy:

    :6919
  • 0

    Well, seem to have hit a little snag with this.

    I exported the new policy, dropped it into the current CID's 'sau' folder and ran configCID to finish.  All went fine and the web client then updated from SAV 7.6 to 9, with a reboot requested on the way.

    Just checking the client's update log and it's reporting an error...

    Download of SAVXP failed from [our web server] / CIDs / S000 / SAVSCFXP

    and the client is actually updatng from the secondary server (Sophos).

    I thought maybe I had set the details wrongly in the new policy, but the client says it is "Downloading product Sophos AutoUpdate" from the same URL without any problem, so it can obviously connect to the CID.

    Just wondered if anyone else had seen this problem?

    Thanks All.

    :6993
  • 0

    Could you paste a few lines from the ALUpdatexxxxx.log (in the ...\Sophos\AutoUpdate\Logs\ folder)?

    Christian

    :6997
  • 0

    Hi Christian,

    a few lines from the log file:

    Trace(2010-Dec-14 10:45:25): CIDUpdateLocation::SyncProduct - Updating Product: SAVXP
    Trace(2010-Dec-14 10:45:25): CIDUpdate(SyncProduct.Start): SAVXP, http:// [web URL] /CIDs/S000/SAVSCFXP/
    Trace(2010-Dec-14 10:45:25): CIDUpdateLocation::Sync - Updating from http CID: http:// [web URL] /CIDs/S000/SAVSCFXP/savxp
    Trace(2010-Dec-14 10:45:25): CIDSync(CidSyncMessage):
    Trace(2010-Dec-14 10:45:33): CIDSync(CidSyncMessage): Windows\winsxs\vxgs54we.kj4\8.0.50727.762.policy
    Trace(2010-Dec-14 10:45:33): CIDSyncCallback, SynchronisationTerminated - Code = -2147467259
    Trace(2010-Dec-14 10:45:33): CIDSyncCallback, SynchronisationTerminated - MapFile = C:\Program Files\Sophos\AutoUpdate\cache\savxp.map
    Trace(2010-Dec-14 10:45:33): CIDUpdateLocation::SyncProduct: Failed to update product (SAVXP) from "http:// [web URL] /CIDs/S000/SAVSCFXP/", Error is :Unknown HR: 80004005
    Trace(2010-Dec-14 10:45:33): CIDUpdate(CIDDownloadFailed): SAVXP, http:// [web URL] /CIDs/S000/SAVSCFXP/

    I have replaced the server URL above with  [web URL] 

    Here's the log info on AutoUpdate:

    Trace(2010-Dec-14 10:45:34): CIDUpdateLocation::SyncProduct - Updating Product: Sophos AutoUpdate
    Trace(2010-Dec-14 10:45:34): CIDUpdate(SyncProduct.Start): Sophos AutoUpdate, http:// [web URL] /CIDs/S000/SAVSCFXP/

    Trace(2010-Dec-14 10:45:34): Checksum found in master.upd matches cached cidsync.upd : 2443b62e. Skipping download
    Trace(2010-Dec-14 10:45:34): CIDUpdate(PrimarySuccess):

    Thanks.

    :7001
  • 0

    Very likely your webserver doesn't "serve" the mentioned file 8.0.50727.762.policy (note the extension "policy") unmodified. Please check its configuration.

    Christian

    :7003
  • 0

    Fixed!  Thanks Christian.

    I double-checked my mime types (IIS 7) against the list in

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

    and I did not have the last two in the list, namely .policy and .ini

    (perhaps these were added recently, as document shows last updated 14 Sep 2010)

    Thanks again!

    :7007
Unfiltered HTML