Wednesday, January 23, 2013

Remote configuration failed on WSUS Server (part 2)

Two weeks ago I wrote a blogpost about WSUS issues after a System Center 2012 SP1 upgrade. This blogpost can be found HERE. I mentioned my environment was already provided with KB2720211 and KB2734608, and was working okay before the SP1 upgrade. Looking in the logfiles the following error messages were seen in: "Remote configuration failed on WSUS Server". Here we go again!
 
This time another message is seen in the wsyncmgr.log also, "DB Server not detected for SUP <ConfigMgr FQDN>".
 
 
In the WCM.log there's another error message seen: "Source file C:\Windows\TEMP\********.cs" could not be found. That's a nice one!
 
 
For me this did the trick:
  • Assign NETWORK SERVICE permissions on the Windows\Temp folder (List Folder/Read Data & Delete) 

After that WSUS synchronisation is running fine again! This permissions are needed to let NETWORK SERVICE write to the folder.
Posted by Henk Hoogendoorn at 9:42 AM
Labels: , ,

3 comments:

  1. AnonymousFebruary 18, 2013 at 9:21 PM

    Nice Post Thanks alot.

    Thanks & Regards,
    ZB

    ReplyDelete
  2. AnonymousNovember 15, 2016 at 4:43 AM

    Genius, simply genius, Henk.....This worked to get WSUS to sync up, and also now I've got Windows 10 Update options as well. Prior to seeing this error, I had to delete the WSUS Website in IIS to get past a previous error:

    http://adinermie.com/post-install-wsus-configuration-fails-with-error-http-status-503-service-unavailable/

    It's not the first time I've found the correct answer from Henk, and I'm sure it won't be the last. Many thanks and best wishes,

    Brian W.

    ReplyDelete
  3. AnonymousFebruary 16, 2017 at 9:01 PM

    Thank you, immediately worked out. It is a pity though that I have to run all over the web to find tweaks for Microsoft products to work. No doubt that they are really great products once they start properly operating.

    ReplyDelete

Subscribe to: Post Comments (Atom)