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

Migration from one server to another (EM 4.5) - clients updating from wrong "Primary Source"

kk20

Followed the migration guide without issues.  Clients have correct "C:\Program Files\Sophos\Remote Management System\mrinit.conf" (I looked inside it) which states the correct "new" server name for MRParentAddress and ParentRouterAddress - automatically updated presumably from the old SUM after the ConfigCID/Update computers bit 6.1.5(8).  Client's registry has the correct new server IP in "Parent Address" key.

New server SUM had downloaded packages correctly before I proceeded previously (as instructed).  New SUM policies had correct update source chosen, warning about propagating this change to the clients was OK'd (we only have two update policies so only 2 to change).  There are no child SUMs - simply the old one and the new one (the old one was removed as per instructions).

Clients still have their "primary location" pointing to \\oldserver\sophosupdate" rather than "\\newlocation\sophosupdate"

The old server has not been decommissioned yet although I did delete the SUM from the new server update managers as instructed in 6.1.6(8)

I have tried manually updating the clients, the log simply states:

Time: 18/04/2011 10:27:42
Message: AutoUpdate finished
Module: ALUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Installation of Sophos AutoUpdate skipped
Module: ALUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Installation of SAVXP skipped
Module: ALUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Installation of RMSNT skipped
Module: ALUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Downloading phase completed
Module: ALUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Product cache update from primary server successfully finished
Module: CIDUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Downloading product Sophos AutoUpdate from server \\OLDLOCATION\SophosUpdate\CIDs\S038\SAVSCFXPModule: CIDUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Product cache update from primary server successfully finished
Module: CIDUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Downloading product SAVXP from server \\OLDLOCATION\SophosUpdate\CIDs\S038\SAVSCFXPModule: CIDUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Product cache update from primary server successfully finished
Module: CIDUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:42
Message: Downloading product RMSNT from server \\OLDLOCATION\SophosUpdate\CIDs\S038\SAVSCFXPModule: CIDUpdate
Process ID: 4188
Thread ID: 4256

Time: 18/04/2011 10:27:40
Message: ***************          Sophos AutoUpdate started          ***************
Module: ALUpdate
Process ID: 4188
Thread ID: 4256

How do I update the clients to reflect "primary location" as "\\newlocation\sophosupdate"? Do I need to copy anything else into the \\oldlocation\sophosupdate?

edit:

additional information.

Client registry also has the "old SUM server name" in HKLM/software/sophos/EE/Management tools/   serverlocation"

I have not made any manual changes to either SUMs or clients.  It has all been performed as per the migration document.

:12063


This thread was automatically locked due to age.
  • 0

    Hello kk20,

    while the updating policies are (usually) transferred to the clients by means of RMS the addresses therein (MRParentAddress) have nothing to do with the updating source. Furthermore the location is not recorded i the registry but in [%ProgramFiles%|%ProgramData%]\Sophos\AutoUpdate\Config\iconn.cfg.

    In the (new) SEC's Endpoint View, tab Update Details you should see Same as policy in the Updating Policy and \\newlocation\SophosUpdate\CIDs\... in the Primary server column. The clients must of course be in a group other than Unassigned. Please check this.

    Christian

    :12067
  • 0

    It seems that patience would have been a virtue.

    The groups had migrated across properly and I imported from AD to see if any PCs were missing (none were).  Having left things overnight there are now approximately 150 PCs that are now complying with policy.  A handful that "Differ from policy" and maybe 50 that are awaiting policy transfer.

    I'll leave it a while to propagate through.  I may force the "differ from policy" to comply with updates in the meantime.

    edit: 

    Is it advisable to copy the iconn.cfg from a "working correct source" PC to a "tardy doesnt want to update to the new source" PC?  I may try on one of them anyway - I dont mind reprotecting the ones that have failed as it seems that most are going across over time.

    :12113
  • 0

    Is it advisable to copy the iconn.cfg

    If a client "refuses" to comply there's probably an issue with RMS or/and the Agent. Forcing an update from the correct location by replacing iconn.cfg might or might not resolve this issue. Personally I prefer the clients to follow the instructions from the console :smileywink: - manipulating local files/settings by other means is a last resort (if clients are still updating from an "old" location and refuse the policy I usually give SAUconf.xml a try to force the over to the new CID).

    Christian

    :12117
Unfiltered HTML