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

Windows 7 64bit and Sophos 9.7 Problem

Trevor

Hi,

Bit of a issue here which is baffling me.

Set up a new Subcription to 9.7 Recommended and created a new CID on AV server.

Setup a new Policy with the correct subscription which applies to a number of XP machines and 4 Windows 7 64bit machines.

The XP machines are all compliant with the new policy and have automatically upgraded from 9.5 to 9.7.

I've manually installed 9.7 to the Win 7 machines from the new CID (S002).

The issue I'm having is after 60 mins or so (automatic update schedule) the Win 7 workstations are checking for updates and then downgrading themselves back to version 9.5!

Both Win 7 and XP machines are sharing the same updating policy.

Any ideas?

:12561


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

    Hello Trevor,

    sorry, left immediately after my post.

    The keys become effective after a (re)start of the agent and router. The logs are in %ProgramData%Sophos\Remote Management System\3\[Agent|Router]\Logs.

    The interesting part is the updating policy. So it's best to either run the install from the S002 CID again, reboot the client and if it afterwards points to S000 collect the logs (using SDU) or (if the client is pointing to S000 at the moment but should point to S002) on the console edit and save (without changing anything) the applicable policy (this should change compliance to Awaiting transfer). If it does not comply then, collect the logs. If it does, force an update, see if it has still S002. If not, collect the logs. Otherwise reboot and collect the logs afterwards (assuming it now again points to S002). Don't worry, it takes longer to write this than to do it :smileyhappy:.

    In the meantime - do you have any groups using the Default policy?

    Christian

    :12801
Reply
  • 0

    Hello Trevor,

    sorry, left immediately after my post.

    The keys become effective after a (re)start of the agent and router. The logs are in %ProgramData%Sophos\Remote Management System\3\[Agent|Router]\Logs.

    The interesting part is the updating policy. So it's best to either run the install from the S002 CID again, reboot the client and if it afterwards points to S000 collect the logs (using SDU) or (if the client is pointing to S000 at the moment but should point to S002) on the console edit and save (without changing anything) the applicable policy (this should change compliance to Awaiting transfer). If it does not comply then, collect the logs. If it does, force an update, see if it has still S002. If not, collect the logs. Otherwise reboot and collect the logs afterwards (assuming it now again points to S002). Don't worry, it takes longer to write this than to do it :smileyhappy:.

    In the meantime - do you have any groups using the Default policy?

    Christian

    :12801
Children
No Data