Remove: Windows Server Post-setup Security updates screen

Hey

How do i remove the "Windows Server Post-setup security updates" nag screen?

By commandline? reg? ...

Windows 2003 R2

Thanks
LVL 1
mikeydkAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mikeydkAuthor Commented:
BTW: I'm auto deploying WIndows 2003 servers...
dmarinenkoCommented:
Run the Security and Configuration Wizard
mikeydkAuthor Commented:
Arghh, still... I have to do it silent...
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Brian PiercePhotographerCommented:
Go to
HKEY_LOCAL_MACHINE->SOFTWARE->Microsoft->Windows->CurrentVersion->ServerOOBE->SecurityOOBE
Add or modify the key
"DontLaunchSecurityOOBE"=dword:00000000
dmarinenkoCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ACECORPCommented:
Neither of the two accepted solutions listed here worked for me.

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

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" nag screen
Anyone have any idea of what the real fix is for this?

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, that way as soon as the operation system deployment is done, I can immediately access the server remotely without having to walk to the server and click finish to react to this nag screen.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.