vcloudnine.de
… virtualization on cloud 9
WSUS on Windows 2012 (R2) and KB3159706 – WSUS console fails to connect
5 years years old. You should keep this in mind. IT is a short living business. This information might be outdated.
As any other environment, my lab needs some maintenance from time to time. I use a Windows 2012 R2 VM with the Windows Server Update Service (WSUS) role to keep my Windows VMs up to date. Like many others, I was surprised by KB3148812 (Update enables ESD decryption provision in WSUS in Windows Server 2012 and Windows Server 2012 R2), which broke my WSUS. But the fix was easy: Uninstall KB3148812 and reboot the server. The WSUS product team published an artice about this known issue in their blog: Known Issues with KB3148812. In the meantime, Microsoft has published a new update, which supersedes KB3148812: KB3159706.
WSUS dead again?
Today I wanted to check the update status of my VMs. Unfortunately, the WSUS console was unable to connect to the WSUS server.
Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0
I checked the status of the service and found the WSUS service stopped. But even after I had started the service, the WSUS console was unable to connect to the server. I found an error in the event logs (ID 507, source Windows Server Update Services), but the message “Update Services failed its initialization and stopped” wasn’t helpful. More helpful was a log entry:
After some searching and examination of the recently installed updates, I came across KB3159706.
Manual steps required to complete the installation of KB3159706
Open an elevated CMD and run this command:
The output should look similar to this:
Then you have to install the “HTTP Activation” feature under “.NET Framework 4.5” features.
Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0
After a restart of the WSUS service, the WSUS should work again.
Summary
The installation of KB3148812 on a WSUS server will break the WSUS installation. Because of this, Microsoft has published KB3159706. If you install this update (in my case it was installed automatically over WSUS…), you have to execute some manual steps to ensure that WSUS works as expected. The WSUS product team is aware of this and they pointed this out in their blog article “The long-term fix for KB3148812 issues” (you will find a hint directly at top of the blog article).
WSUS 2012 R2 KB3159706 manual steps
I’ve been monitoring what’s going on with WSUS updates and Microsoft WSUS team kept us posted on their official blog:
The TLDR version is KB3148812 was a disaster and now KB3159706 replaces it but still requires some manual steps afterward.
I’ve decided to share my recent experience with KB3159706. Please note that I didn’t installed KB3148812 and even if I had I’d have restored my WSUS to a previous state instead of trying to uninstall this KB.
- Step1: Make a backup of your WSUS server and its Database and be prepared to restore it
- Step 2: Before doing anything, read the above blog posts and the manual steps documented on the KB3159706 page under the “more info” section.
- Step 3: install KB3159706, it’s available on Windows Update as a recommended update
- Step 4: Reboot the WSUS server
- Step 5: In a DOS command prompt running as local administrator, type:
NB1: All you should see is a line indicating where the log file is written and 2 lines ‘Post install is starting’ and ‘Post install has successfully completed’
NB2: I copied the log file somewhere else under a meaningful name and opened it to check that there isn’t any error mentioned
- Step 6: Install the ‘HTTP Activation’ feature under .NET Framework 4.5 Features
I first identified its Name and its state. It appeared mine was ‘Removed’. It means that I’ll have to provide a source to install it.
My WSUS server has access to the Internet (it downloads updates from Microsoft), so I used ‘Windows Update’ as a source:
- Step 7: Restart the WSUS service
My WSUS server is running under HTTPS, so I also performed the following steps:
- Step 8: Copy the web.config file
- Step 9: Edit the copied web.config file and make the appropriate changes (see KB3159706)
NB1: Basically you need first to copy the 2 existing endpoints under the services node and change their bindingConfiguration to “SSL”. You’ve now 4 endpoints instead of 2.
NB2: And you need to add multipleSiteBindingsEnabled=”true” almost at the end of the file.
- Step 10: Replace the original web.config file with your modified version.
To achieve that, there’s no need to modify the ACL of the original web.config.
You can actually use the “restore mode” of robocopy.exe to overwrite a file where the Builtin\Administrators have only read and execute permissions.
Side notes:
My first attempt wasn’t successful, I forgot to remove bindingConfiguration=”ClientWebServiceBinding” and had 2 bindingConfiguration lines. D’Oh!(My Bad).
When I restarted the WSUS server, I had an error message saying: The Client Web Service is not working .
I fixed the typos I made in my D:\web.config file and restored it again with the “backup mode” of robocopy.exe.
I then checked that my problem was solved by running:
Share this:
Like this:
Related
23 thoughts on “ WSUS 2012 R2 KB3159706 manual steps ”
I got a negative result. Unfortunately.
Hi,
Can you please give more details about what failed? If there’s an error message, what does it say?
All that needs to be done is to remove the WSUS Administration site on IIS Manager and that’s it!
Thanks for this – saved my ass.
Couldn’t find any relevant information on my problem with post-installation steps. I did as suggested:
“C:\Program Files\Update Services\Tools\wsusutil.exe” postinstall /servicing
Got the following program output:
Log file is located at C:\Users\regul8or\AppData\Local\Temp\tmpD0AC.tmp
Post install is starting
Post install has successfully completed
The tmpD0AC.tmp file contain the following:
2016-05-27 16:19:17 Postinstall started
2016-05-27 16:19:17 Detected role services: Api, UI, WidDatabase, Services
2016-05-27 16:19:17 Start: LoadSettingsForServicing
2016-05-27 16:19:17 WID instance name: MICROSOFT##WID
2016-05-27 16:19:17 End: LoadSettingsForServicing
2016-05-27 16:19:17 Stopping service WSUSService
2016-05-27 16:19:18 Stopping service W3SVC
2016-05-27 16:19:20 Servicing WID database…
2016-05-27 16:19:20 Servicing the database…
2016-05-27 16:19:20 Establishing DB connection…
2016-05-27 16:19:21 Checking to see if database exists…
2016-05-27 16:19:22 Database exists
2016-05-27 16:19:22 Switching database to single user mode…
2016-05-27 16:20:02 Loading install type query…
2016-05-27 16:20:02 DECLARE @currentDBVersion int
DECLARE @scriptMajorVersion int = (9600)
DECLARE @scriptMinorVersion int = (18324)
DECLARE @databaseMajorVersion int
DECLARE @databaseMinorVersion int
DECLARE @databaseBuildNumber nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name=’SUSDB’)
BEGIN
SELECT 1
END
ELSE
BEGIN
SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = ‘CoreDB’)
SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = ‘CoreDB’)
DECLARE @delimiterPosition INT = CHARINDEX(‘.’, @databaseBuildNumber)
IF (@delimiterPosition = 0)
BEGIN
RAISERROR(‘Invalid schema version number’, 16, 1) with nowait
return
END
SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition – 1)
SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 – @delimiterPosition))
IF @currentDBVersion @databaseMajorVersion OR
(@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
BEGIN
SELECT 2
END
ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
@scriptMinorVersion = @databaseMinorVersion)
BEGIN
SELECT 0
END
ELSE
BEGIN
SELECT 4
END
END
END
2016-05-27 16:20:02 Install type is: Reinstall
2016-05-27 16:20:02 Install type is Reinstall, but should be Upgrade. Cannot service the database
2016-05-27 16:20:02 Swtching DB to multi-user mode……
2016-05-27 16:20:03 Finished setting multi-user mode
2016-05-27 16:20:03 Starting service W3SVC
2016-05-27 16:20:03 Starting service WSUSService
2016-05-27 16:20:04 Postinstall completed
Don’t understand if it’s correct behavior or if there’s an error. WSUS is working, workstations receive Windows 7 and other updates. Designated workstations see Windows 10 upgrade package but don’t install it
Hi,
My tmp file contains: “Install type is: Upgrade”
and then it modifies the database, creates tables, views,…
Did you install kb3148812 ? perform the manual steps? uninstall kb3148812?
Kb3159706 windows server 2012 r2
Вопрос
I’m having a problem when I try to install the KB3159706 on my WSUS Server (Windows Server 2012 R2 Standard Version 6.3 Build 9600).
Whenever I try I get this error message «The updates is not applicable to your computer.«
If I look at the Windows Event Viewer it shows me the error below:
Windows update could not be installed because of error 2149842967 «» (Command line: «»C:\Windows\system32\wusa.exe» «C:\Downloads\windows8.1-kb3159706-x64_034b30c6c261d4e76b8c6f8fe3cc9fa5fa4e977b.msu» «)
Since this update is necessary to provide the Windows 10 upgrades, I have been having problems to accomplish this.
These are the updates already installed:
Hotfix(s): 153 Hotfix(s) Installed.
[01]: KB2868626
[02]: KB2883200
[03]: KB2887595
[04]: KB2894856
[05]: KB2903939
[06]: KB2911106
[07]: KB2919355
[08]: KB2919394
[09]: KB2920189
[10]: KB2928680
[11]: KB2934520
[12]: KB2938066
[13]: KB2954879
[14]: KB2955164
[15]: KB2961072
[16]: KB2961908
[17]: KB2962806
[18]: KB2967917
[19]: KB2973351
[20]: KB2975061
[21]: KB2977765
[22]: KB2978041
[23]: KB2978126
[24]: KB2979576
[25]: KB2989930
[26]: KB2999226
[27]: KB3000483
[28]: KB3000850
[29]: KB3003057
[30]: KB3004361
[31]: KB3004365
[32]: KB3004545
[33]: KB3012702
[34]: KB3013172
[35]: KB3013769
[36]: KB3013791
[37]: KB3013816
[38]: KB3014029
[39]: KB3014442
[40]: KB3018467
[41]: KB3019978
[42]: KB3021910
[43]: KB3022777
[44]: KB3023222
[45]: KB3023266
[46]: KB3024751
[47]: KB3024755
[48]: KB3029603
[49]: KB3030377
[50]: KB3030947
[51]: KB3032663
[52]: KB3033446
[53]: KB3034348
[54]: KB3035126
[55]: KB3035527
[56]: KB3036612
[57]: KB3037579
[58]: KB3037924
[59]: KB3038002
[60]: KB3038562
[61]: KB3041857
[62]: KB3042058
[63]: KB3042085
[64]: KB3043812
[65]: KB3044374
[66]: KB3044673
[67]: KB3045634
[68]: KB3045685
[69]: KB3045717
[70]: KB3045719
[71]: KB3045755
[72]: KB3045992
[73]: KB3045999
[74]: KB3046017
[75]: KB3046737
[76]: KB3047255
[77]: KB3048043
[78]: KB3054169
[79]: KB3054203
[80]: KB3054256
[81]: KB3054464
[82]: KB3055323
[83]: KB3055343
[84]: KB3055642
[85]: KB3058168
[86]: KB3059316
[87]: KB3059317
[88]: KB3060681
[89]: KB3060716
[90]: KB3060793
[91]: KB3061512
[92]: KB3061518
[93]: KB3063843
[94]: KB3065822
[95]: KB3067505
[96]: KB3068708
[97]: KB3071663
[98]: KB3071756
[99]: KB3073874
[100]: KB3074228
[101]: KB3074548
[102]: KB3075220
[103]: KB3075853
[104]: KB3077715
[105]: KB3078071
[106]: KB3078676
[107]: KB3080042
[108]: KB3080149
[109]: KB3081320
[110]: KB3082089
[111]: KB3082353
[112]: KB3083325
[113]: KB3083711
[114]: KB3083992
[115]: KB3084135
[116]: KB3086255
[117]: KB3087038
[118]: KB3087041
[119]: KB3087137
[120]: KB3087390
[121]: KB3092601
[122]: KB3092627
[123]: KB3095113
[124]: KB3102939
[125]: KB3108381
[126]: KB3109103
[127]: KB3110329
[128]: KB3121918
[129]: KB3126041
[130]: KB3126434
[131]: KB3126587
[132]: KB3132080
[133]: KB3133043
[134]: KB3139398
[135]: KB3139914
[136]: KB3146723
[137]: KB3153704
[138]: KB3155784
[139]: KB3156059
[140]: KB3159398
[141]: KB3161949
[142]: KB3161958
[143]: KB3162343
[144]: KB3169704
[145]: KB3170455
[146]: KB3172729
[147]: KB3173424
[148]: KB3175024
[149]: KB3178539
[150]: KB4012213
[151]: KB4022717
[152]: KB4025333
[153]: KB4025336
