ACECORP
asked on
Disabling the "Windows Server Post-Setup Security Updates" Screen
I am trying to completely disable the "Windows Server Post-Setup Security Updates" Screen during my Windows 2003 R2 w/ SP2 operating system deployment via System Center Configuration Manager.
I followed the advice from the post at https://www.experts-exchange.com/questions/25974353/Remove-Windows-Server-Post-setup-Security-updates-screen.html?anchorAnswerId=36536497#a36536497
However the advice listed did not work.
I ran the following command during my os deployment and the registry key was indeed properly inserted.
REG ADD HKLM\SOFTWARE\Microsoft\Wi ndows\Curr entVersion \ServerOOB E\Security OOBE /v DontLaunchSecurityOOBE /t REG_DWORD /d 0
However, when the OS deployment was finished, I could not remotely access the server, so I figured the "Windows Server Post-Setup Security Updates" nag screen was up and all communication to the server was still blocked due to that fact.
I was correct with my assumption because when I logged into the freshly imaged server, the "Windows Server Post-Setup Security Updates" nag screen was up, even though the registry key specified at http://technet.microsoft.com/de-de/library/cc757061%28WS.10%29.aspx was present and set correctly.
I need to run some kind of script during operating system deployment that will prevent this "Windows Server Post-Setup Security Updates" nag screen from ever functioning.
Anyone have any idea of what the real fix is for this?
I followed the advice from the post at https://www.experts-exchange.com/questions/25974353/Remove-Windows-Server-Post-setup-Security-updates-screen.html?anchorAnswerId=36536497#a36536497
However the advice listed did not work.
I ran the following command during my os deployment and the registry key was indeed properly inserted.
REG ADD HKLM\SOFTWARE\Microsoft\Wi
However, when the OS deployment was finished, I could not remotely access the server, so I figured the "Windows Server Post-Setup Security Updates" nag screen was up and all communication to the server was still blocked due to that fact.
I was correct with my assumption because when I logged into the freshly imaged server, the "Windows Server Post-Setup Security Updates" nag screen was up, even though the registry key specified at http://technet.microsoft.com/de-de/library/cc757061%28WS.10%29.aspx was present and set correctly.
I need to run some kind of script during operating system deployment that will prevent this "Windows Server Post-Setup Security Updates" nag screen from ever functioning.
Anyone have any idea of what the real fix is for this?
ASKER
I already did that. It doesn't work as described in detail in my posting above.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
DontLaunchSecurityOOBE (DWORD) in:
HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Windows \Current Version \ServerOOBE \SecurityOOBE
This key does not exist by default.
The key can exist or not exist. If the key exists, Post-Setup Security Updates does not display. The numerical value of this setting is irrelevant.