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

    The (sub) groups are independent but newly discovered groups inherit the policies of their parent. The policy for a client is the one of the "lowest" group it is in - there is no conflict (as long as a machine does not belong to more than one sync'd OU of course).

    I'd check the database with SQL for multiple occurrences of the (Win7) clients based on Jak's example in this post:

    SELECT 	c.Name,
	c.Description, 
	c.DomainName, 
	c.OperatingSystem, 
	c.Managed, 
	c.Deleted, 
	c.Connected, 
	c.insertedat, 
	c.IdentityTag, 
	c.DNSName,
	c.IPAddress,
	c.MessageSystemAddress,
	cgm.GroupID,
    g.Name
FROM [SOPHOS47].[dbo].[ComputersAndDeletedComputers] as c
    inner join [SOPHOS47].[dbo].[ComputerGroupMapping] as cgm on cgm.ComputerID = c.id
    inner join [SOPHOS47].[dbo].[Groups] as g on g.id = cgm.GroupID
where c.Name in(
	SELECT  c.Name 
	FROM [SOPHOS47].[dbo].[ComputersAndDeletedComputers] as c
	GROUP BY c.name
	HAVING ( COUNT(c.name) > 1)
)
order by c.name

    Perhaps you could modify the WHERE clause to select one or more of the Win7 clients by name (WHERE c.Name LIKE ....)

    Christian

    :12707
Reply
  • 0

    The (sub) groups are independent but newly discovered groups inherit the policies of their parent. The policy for a client is the one of the "lowest" group it is in - there is no conflict (as long as a machine does not belong to more than one sync'd OU of course).

    I'd check the database with SQL for multiple occurrences of the (Win7) clients based on Jak's example in this post:

    SELECT 	c.Name,
	c.Description, 
	c.DomainName, 
	c.OperatingSystem, 
	c.Managed, 
	c.Deleted, 
	c.Connected, 
	c.insertedat, 
	c.IdentityTag, 
	c.DNSName,
	c.IPAddress,
	c.MessageSystemAddress,
	cgm.GroupID,
    g.Name
FROM [SOPHOS47].[dbo].[ComputersAndDeletedComputers] as c
    inner join [SOPHOS47].[dbo].[ComputerGroupMapping] as cgm on cgm.ComputerID = c.id
    inner join [SOPHOS47].[dbo].[Groups] as g on g.id = cgm.GroupID
where c.Name in(
	SELECT  c.Name 
	FROM [SOPHOS47].[dbo].[ComputersAndDeletedComputers] as c
	GROUP BY c.name
	HAVING ( COUNT(c.name) > 1)
)
order by c.name

    Perhaps you could modify the WHERE clause to select one or more of the Win7 clients by name (WHERE c.Name LIKE ....)

    Christian

    :12707
Children
No Data
Unfiltered HTML