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

Sophos Endpoint Security and Control Version 9 install issue

ATLTech

Some machines were previously updated via a network application push from just having Sophos AV (whatever the last client was) to having SES and C Version 9. Now, the machines that had the auto-install on the network show a primary and seconday server location for AutoUpdates. However, machines that have SES and C installed manually (navigating to the file and running setup.exe) from the same location don't show the secondary server information, resulting in users who are remote not being able to update their definitions without first connecting to VPN as our primary server is internal.

What could possibly be the issue? One of our system admins did a network push to a basic Windows XP Pro machine without any additional software on it and it never had Sophos installed. The secondary server info was missing after it installed and was rebooted.

Also, we have desktop images set up so when the machine is imaged and joined to the domain, it will pull Sophos down per the instructions here: http://www.sophos.com/support/knowledgebase/article/28591.html

Is there something in the registry we have to change for machines that previously had Sophos AV and then was manually updated to SES and C version 9 and then taking the snap via the directions above? This is boggling my mind on why new machines are not catching the secondary server info but older machines are from a recent network push.

:2393


This thread was automatically locked due to age.
  • 0

    Hi ATLTech,

    You shoud check what groups the machines that you have installed to manually have entered in the Enterprise Console.  If you install manually, the machines will end up in the unassigned group unless you specify the group correctly in setup.exe (if you enter a group for them to join, but do it incorrectly, they will default to unassigned).

    Machines in the unassigned group will not receive any policies, so the only updating location that they will know about will be the one that they installed from.  Machines that you pushed out from the console will likely be in the correct group already and so will receive their correct updating policies with both primary and secondary servers.

    Hope this helps,

    Stephen.

    :2396
Unfiltered HTML