Bobbie Harder (MSFT) has posted a list of Top known issues whilst upgrading WSUS to WSUS SP1 on microsoft.public.windows.server.update_services. These issues will be updated in a KB and in the online WSUS SP1 readme. 1. If you are using a proxy server, in some cases the SP1 upgrade may clear the proxy configuration username and password. This may cause synchronization of updates from Microsoft Servers to generate an “invalid parameter” error. To address this issue, reset the proxy configuration username and password and re-synchronize your server. 2. Remote SQL deployments: WSUS SP1 is not updating WSUS servers which are setup using remote … Continue reading WSUS SP1 Known Issues
You see the following error in %Windir%\WindowsUpdate.log SYMPTOMS 2006-06-15 17:02:23 2104 83c Misc =========== Logging initialized (build: 184.108.40.2069, tz: -0400) =========== 2006-06-15 17:02:23 2104 83c Misc = Process: C:\WINDOWS\system32\wuauclt.exe 2006-06-15 17:02:23 2104 83c Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2006-06-15 17:02:23 2104 83c DtaStor FATAL: Failed to initialize datastore, error = 0xC800021F 2006-06-15 17:02:23 2104 83c Misc =========== Logging initialized (build: 220.127.116.119, tz: -0400) =========== CAUSE It looks like the client datastore failed to initialize. WORKAROUND 1. Open a CMD prompt on the client. 2. Type “net stop wuauserv” (without quotes) <hit enter>. 3. Type “cd %Windir%\SoftwareDistribution“. 4. Type “RD /s … Continue reading Error 0xC800021F
Ten Principles of Microsoft Patch Management By Christopher Budd, Security Program Manager, Microsoft Corporation 1. Service packs should form the foundation of your patch management strategy. 2. Make Product Support Lifecycle a key element in your strategy. 3. Perform risk assessment using the Severity Rating System as a starting point. 4. Use mitigating factors to determine applicability and priority. 5. Only use workarounds in conjunction with deployment. 6. Issues with Security Updates are documented in the Security Bulletin Master Knowledge Base Article. 7. Test updates before deployment. 8. Contact Microsoft Product Support Services if you encounter problems in testing or … Continue reading Ten Principles of Microsoft Patch Management
To identify if you have installed WSUS SP1; You can check the version number for the wsusservice.exe file located in %ProgramFiles%\Update Services\service\bin\wsusservice.exe. OR, check the WSUS Build number from WSUSAdmin home page (bottom of the page – Last line) WSUS SP1 Build 18.104.22.16820WSUS RTM Build 22.214.171.1242WSUS RC Build 126.96.36.1990
SYMPTOMS After updating WSUS to WSUS SP1… You might see Red X on WSUS Updates Window in WSUSAdmin console and eventually Synchronization fails. Content file download failed. Reason: The parameter is incorrect. Source File: /msdownload/update/v3-19990518/cabpool/windowsmedia10-kb917734-x86-enu_499fe88d62843835153a4225712e1b2f19120527.exe Destination File: d:\WSUS\WsusContent\27\499FE88D62843835153A4225712E1B2F19120527 Source: Windows Server Update Category: Synchronization Event ID: 386 Description:- Synchronization failed. Reason: The underlying connection was closed: Unable to connect to the remote server. KNOWN ISSUE This is a known issue. Once you upgrade to WSUS SP1, you might want to re-configure Synchronization Options (proxy settings – proxy password) in WSUSAdmin console as they are lost during the upgrade. Save the settings and perform … Continue reading After updating WSUS to WSUS SP1…
The other day, Dave (poster on http://patchmanagement.org/) wanted to know the best resource for finding up to date information on whether or not there is exploit code available for Microsoft Security Patches? Susan immediately replied to check www.incidents.org. They also have an archive http://www.incidents.org/diary.php?date=2006-06-14. Get the feed.
There is some confusion in updating WSUS to WSUS SP1 on remote SQL deployments to run with (Front end and Back end) switches. WSUS SP1 update must be initiated on the backend WSUS Server first followed by the front end WSUS Server. According to Bobbie Harder (MSFT): You do have to run the setup package (WSUS SP1) on both the back-end Server (first run on back-end server) and then on front-end server without passing any switches. The steps which have been tested and validated should be: 1) Run the setup package on the front-end with no switches and choose to upgrade. 2) … Continue reading Upgrading WSUS to WSUS SP1 on remote SQL deployments
Brian McCann wants to know a better way to Check the Version of Windows Installer. According to Windows Installer Team blog, “If you want to check the version of the Windows Installer on your system, check the version of MSI.DLL in the Windows\System32 folder. If the version is 3.1.4000.2435, you have the latest version. One common point of confusion is that even if you have the latest version of Windows Installer 3.1 on your system and you type in msiexec.exe /? from a command-window, you will still be told that you are on version 3.1.4000.1823 or 3.1.4000.1830. This is because … Continue reading Checking the Version of Windows Installer
WSUS SP1 is finally released. Besides delivering updates, Windows Server Update Services with Service Pack 1 (WSUS SP1) includes support for Microsoft SQL Server 2005 and the forthcoming Windows Vista operating system. It also provides additional stability and performance improvements. After you install WSUS SP1, you may be required to restart your computer. Note: You cannot remove WSUS SP1 after you install it. Download Windows Server Update Services with Service Pack 1http://www.microsoft.com/windowsserversystem/updateservices/downloads/WSUSSP1.mspx Download WSUS SP1 only – Download the KB919004-x86.exe package now.http://download.microsoft.com/download/f/6/d/f6d9eb30-2612-47f7-b14a-41a47e8a9a8e/wsus2-kb919004-x86.exe Description of Windows Server Update Services Service Pack 1 http://support.microsoft.com/?kbid=919004 Updating Microsoft Windows Vista Beta 2 Computers via WSUShttp://technet2.microsoft.com/WindowsServer/f/?en/Library/70c3aea9-4dc2-49ad-a085-dc1b59f1af7d1033.mspx … Continue reading WSUS 2.0 SP1
So, before you apply Microsoft Security Bulletin MS06-019 on Exchange Servers – Be careful. Take a look at the known issues. 912918 (http://support.microsoft.com/kb/912918/) Users cannot send e-mail messages from a mobile device or from a shared mailbox in Exchange 2000 Server and in Exchange Server 2003. First, Find accounts that have the Full Mailbox Access permission without the Send As permission using the script from http://support.microsoft.com/kb/912918/ and grant the Send As permission either manually using DSA.msc or using the script -SetAll switch. And then, you are ready to apply MS06-019.