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

    I have a thought. Can you check if the same machine name or IP address exists in the 'all computers' list on the SEC screen. I encountered a similar (not quite the same) problem when I cloned machines. What I saw is the same machine appearing in 2 groups with different IP addresses one day then different machines with the same IP address the next. To get around this, I completely unintalled the RMS from the client (removed the RMS folder) and reinstalled. If the unique client id isn't unique, the SEC maybe sending the policy for another machine in another group out to this client.

    Matt

    :12833
Reply
  • 0

    I have a thought. Can you check if the same machine name or IP address exists in the 'all computers' list on the SEC screen. I encountered a similar (not quite the same) problem when I cloned machines. What I saw is the same machine appearing in 2 groups with different IP addresses one day then different machines with the same IP address the next. To get around this, I completely unintalled the RMS from the client (removed the RMS folder) and reinstalled. If the unique client id isn't unique, the SEC maybe sending the policy for another machine in another group out to this client.

    Matt

    :12833
Children
No Data