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

Clients Pointing to Wrong SUM / EC! Frustrated.

closetgeek

We recently ran into a situation where sophos EC "crahsed" on the original server that hosted it. After many frustrating weeks of dealing with support, we removed all things Sophos from the server... Oops! This was done in haste and no certificate backups were taken.

Since then, we have reinstalled EC, Management Server and SUM on a fresh server. Clients are showing up and reporting to the new EC; however, they are still attempting to download their updates from the old SUM and showing as Out of Date in the new EC.   I have been pushing the updates to the SophosUpdate folder on the old server; however, this server will soon be gone completely, so this is not a viable long term solution.

I have used the HTA provided by Jak and the one provided by Sophos. I have been pushing this to clients via GPO for 2-3 weeks, but they still try to hit the old server.

What other options do I have? Very frustrating!

Rant!: I am an advid Sophos supporter and reccomend it to others in the IT world as often as I can, but we continue to have these little issues that make management a pain! Planning to move to the Sophos Web Control Appliance in the new year (replacing Websense), but these frustrations are starting to make me thing twice!

:35699


This thread was automatically locked due to age.
Parents
  • 0

    As QC says, if you have management of the computers using RMS you should be home and dry and the quick check that RMS is working on the clients is to look at the last message time column in SEC.

    For a computer pointing at the wrong location, check:

    1. The Group the client is in

    2. The Updating policy that is linked to the group.

    3. In the policy, ensure that a valid subscriton is selected and the update location is the SophosUpdate share on the new server.

    4. Maybe Make a change to the schedule update interval just to force it to go down to the client.

    5. The client should go to awaiting policy transfer, then within about 25 seconds, should report back as same as policy.

    Things to check onthe client include
    1. The adapter storage is update with new policy for AutoUpdate (\program data\sophos\remote management system\3\agent\adapterstorage\ALC\)

    2. The iconn.cfg, isched.cfg file is updated.  (\program data\sophos\autoupdate\config\)

    3. The Sophos Agent log should have references to it receiving the policy and applying it. (\program data\sophos\remote management system\3\agent\logs\)

    Regards,

    Jak

    :35703
Reply
  • 0

    As QC says, if you have management of the computers using RMS you should be home and dry and the quick check that RMS is working on the clients is to look at the last message time column in SEC.

    For a computer pointing at the wrong location, check:

    1. The Group the client is in

    2. The Updating policy that is linked to the group.

    3. In the policy, ensure that a valid subscriton is selected and the update location is the SophosUpdate share on the new server.

    4. Maybe Make a change to the schedule update interval just to force it to go down to the client.

    5. The client should go to awaiting policy transfer, then within about 25 seconds, should report back as same as policy.

    Things to check onthe client include
    1. The adapter storage is update with new policy for AutoUpdate (\program data\sophos\remote management system\3\agent\adapterstorage\ALC\)

    2. The iconn.cfg, isched.cfg file is updated.  (\program data\sophos\autoupdate\config\)

    3. The Sophos Agent log should have references to it receiving the policy and applying it. (\program data\sophos\remote management system\3\agent\logs\)

    Regards,

    Jak

    :35703
Children
No Data