{"id":24766,"date":"2021-10-05T16:11:52","date_gmt":"2021-10-05T15:11:52","guid":{"rendered":"https:\/\/www.n-able.com\/?p=24766"},"modified":"2022-11-17T17:56:38","modified_gmt":"2022-11-17T17:56:38","slug":"windows-11-how-to-configure-an-auto-patch-decline-in-n-central","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/pt-br\/blog\/windows-11-how-to-configure-an-auto-patch-decline-in-n-central","title":{"rendered":"Windows 11: how to configure an auto-patch decline in N‑central"},"content":{"rendered":"

Note: As of November 17, 2022, we have published an update to this blog that also covers how to prevent Windows 11 update using the Registry and Powershell. Click here to read the new blog<\/a>.<\/strong><\/h2>\n

 <\/p>\n

Oh, happy days\u2014it\u2019s October 5 and Windows 11 release day! We have tested remote control, agents and probes, and monitoring and management functions, which all appear to be working seamlessly. However, there are still many good reasons for your MSP customers to wait to upgrade from Windows 10.<\/p>\n

To make sure you keep control of the upgrade, let\u2019s start by removing any current feature upgrades (FUs) you may already have set up. Under the Service Organization Level > Configuration > Patch Management, click into automatic approvals. Review all of your current auto approvals and pull out both feature packs and upgrades. Though we don\u2019t anticipate it will be classified as a feature pack, it\u2019s better to err on the side of caution.<\/p>\n

This is what it should look like after you update your automatic approvals:<\/p>\n

\"\"<\/p>\n

Image 1: Update your automatic approvals<\/em><\/p>\n

 <\/p>\n

If you are currently auto-approving upgrades, there is a chance some computers could get one.<\/p>\n

Here\u2019s a quick step-by-step guide on how to auto-decline Windows 11 in N‑central\u00ae<\/sup>:<\/p>\n

Create an auto-decline rule. Yes, I know it\u2019s called automatic patch approval rule, but it does both.<\/p>\n