Enjoy Sharing

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.

4667.WSUS1.png-550x0[1]

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.LoadSettingsFromXml()
   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.

 

 

 

Enjoy!!!

Advertisements

6 responses

  1. Jose Angel Rivera

    Thank you, this worked nicely for me! 🙂

    September 30, 2013 at 11:23 pm

  2. Thank you so much, this got me out of a very tight spot.

    October 23, 2013 at 12:39 pm

  3. selim

    Thanks this solved my problem

    February 17, 2014 at 12:07 am

  4. thanks worked for me.

    April 8, 2015 at 6:23 pm

  5. Jose Angel Rivera

    Just for everyone to note, there is a similar error I got sometimes while configuring WSUS. On the log, it says something like:

    ImportDefaultDetectoids failed. Exception: System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
    Warning: The join order has been enforced because a local join hint is used. —> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
    at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
    at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()

    To fix that one, you need to give better hardware resources to the WSUS machine. In my case, I was using Dynamic Memory on the WSUS VM, so, I set the memory to be static and put some more GBs of RAM to it. It usually happens when you have set the VM to use Dynamic Memory. After the change, just retry the post-configuration.

    Regards,

    Jose Angel Rivera

    May 12, 2015 at 6:32 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s