Im a bit confused about Controlled Updates and Test Computers.
1. Our intension was that Client Endpoints get their updates when they are released but only on a specific day.
2. Server Endpoints have a test group we update to latest version on a patchday
2.1 Server Endpoints not belonging to the test group are updated to the latest version on the patchday after the first patchday.
We did this in the past with a Update policy for Clients and selected a day. And the Test Server Group in Controlled Updates for Servers.
We were fine with that.
Now I can find conflictng settings in Global, Client and Server settings.
I think with the settings shown on the screenshots, our clients will not get updates, unless we click the button
"Update to match test computers"
Can you confirm this?
How can I test updates only for servers and let clients be up-2-date when Sophos publishes updates?
Global Settings
Global Settings > Controlled Updates is showing:
(which is actually the same as for Servers)
Client Endpoints
are showing this:
Overview > Endpoint Protection Dashboard > Global Settings > Controlled Updates
Control Updates Manually - Currently Selected
Server Endpoints:
are showing this:
Overview > Server Protection Dashboard > Global Settings > Controlled Updates
showing the same as Global Dashboard
Hi LHerzog,
Your understanding is correct. You will need to select "Update to match test computers" if you wish for the non-test computers to update.
For your Endpoint environment, I recommend the option "Pause Updates Now" as opposed to "Control Updates Manually". If you don't have a need to test the latest release on your endpoints prior to deploying, this may be more straightforward to utilize.
When you are navigating into the "Global Settings" menu, there’s a separate "Controlled Updates" option for Server and Endpoint devices respectively.
The following video does a great job of explaining how to use Controlled Updates.
- Sophos Central: How to Configure Controlled Updates
thank you. test updates for endpoints have been enabled in the past but then we decided to disable that.
it is a bit intransparent that if you click here:
you re-enable the test mode again without beeing asked to save some change
someone probably did that.
I gut it sorted out now.