TechShizz | All posts tagged 'WSUS'

WSUS Crashing - WSUSPOOL Stopping in IIS

Problem

 WSUS MMC Crashes and WSUS Generally unreliable.

Cause

 Application Pool "WSUSPool" Stopped in IIS

Solution

To improve WSUS availability, you need to increase IIS Private Memory Limit. The default limit is set to 1843200KB. And when an IIS worker process uses more than 2GB WSUS crashes and the problem occurs.

Change Private Memory Limit (KB) to a higher number that fits your server specifications or simply 0 , which means no limit, instead of the hard-coded 1843200. Follow this path to find the setting:

 

WSUS Application Pool IIS Advanced Settings

Internet Information Services (IIS) Manager → Server → Application Pools → Select “WSUSPool” → Actions Advanced → Recycling → change “Private Memory Limit (KB)“.

This’ll improve WSUS availability.

How to Move the WSUS Database


  1. Launch SQL Server Management Studio Express console as an administrator. It is located under Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express. 
  2. Fill in the following information and then click Connect
    • Server type: Database Engine
    • Servername: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
    • Authentication: Windows Authentication 
      clip_image004
  3. Expand Databases and right-click on SUSDB and select Tasks > Detach… from the context menu. 
    clip_image006
  4. Select the "Drop Connection" checkbox and click OK. 
    clip_image008
  5. Open explorer and move the C:\WSUS\SUSDB folder to the <new drive>:\WSUS directory.
  6. To reattach the database, right-click on Database and select Attach… from the context menu. 
    clip_image010
  7. On the Attach Databases page select the Add button. 
    clip_image012
  8. Browse to the new location of the SUSDB.mdf database and select OK twice to complete the move. clip_image014

Windows Update not syncing with WSUS Server?

Sometime Windows Update on Windows clients wont sycronize with your WSUS server, or wont download an update that recently been pushed out.
If that happeneds try this:

net stop wuauserv

REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v LastWaitTimeout /f

REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v DetectionStartTime /f

REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v NextDetectionTime /f net start

wuauserv wuauclt /detectnow

HTTP Error 500.19 with Error Code 0x8007007E

Error meaage reads:
Module: DynamicCompressionModule or StaticCompressionModule
Notification: SendResponse
Handler: StaticFile
Error Code: 0x8007007e

This issue occurs when you have WSUS installed on a server with a webiste. It's caused by conflicting modules from the top level server node and the web site node in IIS. Here is how to fix it.

1. Run CMD as administrator: and run

%windir%system32inetsrvappcmd.exe add backup "My Backup Name"

This will backup your IIS config,

2. 
Removing DynamicCompressionModule and StaticCompressionModule from IIS:
a. In IIS manager, click on the Server node for the IIS server.
b. Double click on the Modules icon

c. Find
DynamicCompressionModule and click "Unlock"
d. Find
StaticCompressionModule and click "Unlock"
e. Now click on you're website node, and open the Modules config.
f. Select
DynamicCompressionModule and then click "Remove"
g. Select
StaticCompressionModule and click "Remove"

3. Restart IIS



Outlook 2010 Opening in Safe Mode

If outlook keeps opening in Safe Mode, this could be due to a KB Microsoft pushed out (KB3114409). This was removed by Microsoft as it did't work as expected.

To resolve the issue remove the KB from the client machine. If there is a WSUS server on site it will also need the update Approving and the Approving for Removal. Set a deadline to make it happen ASAP.

https://support.microsoft.com/en-us/kb/3114409