WSUS Post-deployment Configuration Failed
In order for ConfigMgr 2012 to install a Software Update Point or SUP, WSUS must first be installed and configure…just in case you missed that. Now when you tried to install the SUP role in ConfigMgr you realise it fails, and it fails because though you’ve got your WSUS component installed, it has not yet run the post-deployment configuration. Sounds easy enough, just go to the Server Manager and kick off the post-deployment configuration which should be marked as a notification.
If you get an error running it (like me), you’d probably get an error saying it failed and to go check out a log file for more details.
Here are the contents of my log file that would probably be located at C:\Users\<username>\AppData\Local\Temp\<something>.tmp. Mine was tmp617.tmp.
2013-08-30 13:45:50 Postinstall started
2013-08-30 13:45:50 Detected role services: Api, UI, WidDatabase, Services
2013-08-30 13:45:50 Start: LoadSettingsFromXml
2013-08-30 13:45:50 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2013-08-30 13:45:50 Value is true
2013-08-30 13:45:50 End: GetConfigValue
2013-08-30 13:45:50 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2013-08-30 13:45:50 Config file did not contain a value "ContentDirectory"
2013-08-30 13:45:50 Microsoft.UpdateServices.Administration.CommandException: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.
at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
at Microsoft.UpdateServices.Administration.PostInstall.Initalize(Parameters parameters)
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String arguments)
Fatal Error: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.
I believe the problem was it was trying to kick off WSUSUtil.exe but failed. So we’ll execute it manually using PowerShell. You must run PowerShell as administrator. Change to the directory where the WSUSUtil is located (typically located in C:\Program Files\Update Services\Tools) and then run the command below:-
.\wsusutil.exe postinstall content_dir=<directory to store content> sql_instance_name=%computername%
I replaced <directory to store content> with C:\WSUS and %computername% with, well…my computer name. I’m not gonna share that with you 🙂 Hope that works for you too!
p/s: Tribute to Reshard for this solution.