Solved

Disabling the "Windows Server Post-Setup Security Updates" Screen

Posted on 2011-09-14
3
1,160 Views
Last Modified: 2012-05-12
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 http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_25974353.html#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\Windows\CurrentVersion\ServerOOBE\SecurityOOBE /v DontLaunchSecurityOOBE /t REG_DWORD /d 0

 HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ServerOOBE\SecurityOOBE
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.

"Windows Server Post-Setup Security Updates" Screen
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?
0
Comment
Question by:ACECORP
  • 2
3 Comments
 
LVL 13

Expert Comment

by:Govvy
ID: 36536635
Set this in registry:

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.
 

0
 
LVL 5

Author Comment

by:ACECORP
ID: 36537028
I already did that. It doesn't work as described in detail in my posting above.
0
 
LVL 13

Accepted Solution

by:
Govvy earned 500 total points
ID: 36537078
Sorry in that case add this to the unattend script:

ServerWelcome=No
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have never ceased to be amazed how many problems you can encounter on a fresh install of a Windows operating system.  This is certainly case in point& Unable to complete ANY MSI installation.  This means Windows Updates are failing and I can't …
This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…

937 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

4 Experts available now in Live!

Get 1:1 Help Now