![]() If the policy is still there, you could be looking at a DFS replication issue isn't pulling your GPO changes across the DCs. If you are still pointing at a WSUS server, then I recommend gpresult /h c:\gpresult.htm and looking through the first section labeled Computer Details to determine if anything is still coming through on the Windows Update section. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012. $MUSM.Services | select Name, IsDefaultAUService Note that it's not in Windows Update section of Administrative Templates, but rather System > Internet Communication Management, and so might not necessarily been included in your old WSUS GPO(s).Īfter that, for testing purposes, pick a server to work on, export (for backup) HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, delete the registry key, gpupdate /force, then $MUSM = New-Object -ComObject "" If that's on somewhere else in GPO, it needs turned off. Go to Computer Configuration / Policies / Windows. ![]() Right click on the 1 strategy and click on Edit 2. ![]() ![]() I'm referencing it because of the GPO setting Computer Configuration > Policies > Administrative Templates > System > Internet Communication Management > Internet Communication Settings > Turn off access to all Windows Update features Open the Group Policy Management Console, right-click 1 on the location where the policy is to be applied and click Create GPO in this field, and link it here 2. Windows Server 2016 not updating through WSUS discusses where the Server 2016 install would not talk to WSUS.
0 Comments
Leave a Reply. |