THE OFFICIAL BLOG OF THE SBS "DIVA" : WSUS

931125 being reoffered over and over and over and....

bradley — Wed, 25 Nov 2009 02:01:00 GMT

If you are seeing 931125 being reoffered via WSUS it's due to the fact that the May 2009 update is not properly marked at "HasSupercedingUpdates" which is messing up the offering of the September update causing it to be reoffered. Decline both the Feb and May 2009 update in WSUS.

Then on the workstation if you are getting it still reoffered you have to clear it out of the software distribution folder.

Per Chuck on the SBS2k list -- To recap the fix for others.

1. Went to WSUS and manually declined both of the updates.
2. Stopped the Automatic update service on the affected workstations.
3. Deleted everything in C:\WINDOWS\SoftwareDistribution.
4. Restarted the automatic update service.
5. Restarted the work stations.

(edit ... you can also delete out just the cert folder under that softwaredistribution folder and just chuck that out the door)

Join me tomorrow on WSUS

bradley — Thu, 17 Sep 2009 05:42:00 GMT

I'm doing a geek presentation on WSUS tomorrow morning at

When: Thursday, Sep 17, 2009 12:00 PM (EDT)

Scheduled to Occur: Once

Duration: 1:30

Third Tier has invited you to attend an online meeting using

Microsoft Office Live Meeting.

https://www.livemeeting.com/cc/mvp/join?id=7R5BRQ&role=attend&pw=M%289zFMf48

Meeting time: Sep 17, 2009 12:00 PM (EDT)

Add to my Outlook Calendar:

https://www.livemeeting.com/cc/mvp/meetingICS?id=7R5BRQ&role=attend&pw=M%289zFMf48&i=i.ics

AUDIO INFORMATION

-Computer Audio(Recommended)

To use computer audio, you need speakers and microphone, or a headset.

FIRST-TIME USERS

To save time before the meeting, check your system to make sure it is ready to use Microsoft Office Live Meeting.

http://go.microsoft.com/fwlink/?LinkId=90703

TROUBLESHOOTING

Unable to join the meeting? Follow these steps:

1. Copy this address and paste it into your web browser:

https://www.livemeeting.com/cc/mvp/join

2. Copy and paste the required information:

Meeting ID: 7R5BRQ

Entry Code: M(9zFMf48

Location: https://www.livemeeting.com/cc/mvp

If you still cannot enter the meeting, contact support:

http://r.office.microsoft.com/r/rlidLiveMeeting?p1=12&p2=en_US&p3=LMInfo&p4=support

Running the wizard on WSUS 3 sp2

bradley — Mon, 07 Sep 2009 06:23:00 GMT

After the WSUS 3 sp2 installs, there is a wizard that pops up. You can hit cancel... or you can just be a SBSer and click next next next next next next......

How to run the WSUS 3 sp2 wizard and not break the WSUS integration with SBS 2008 (or 2003 for that matter)

Click start connecting

Ensure you pick English (or your specific language), Next

Leave it at ALL PRODUCTS. Next

(This doesn't download Biztalk patches to your server, this setting just ensure that as you add new computers with various products it will offer up the proper patches)

Ensure you pick at least Critical Updates, Security Updates, and Service Packs are selected under Synchronization Options, Products and classifications, update classifications. I unchecked drivers as a FYI. Next.

Set a auto sync -- or leave as is. Next.

Click finish.

The one area that most uncheck things which in turn "breaks" the integration is the "all products" section.

100% foolproof way to apply patches and ensure that they never ever have issues...

bradley — Sat, 29 Aug 2009 18:59:00 GMT

...doesn't exist. Anytime you make any sort of changes you introduce risk. But the question you have to ask and decide is when the benefits of the patch outweigh the risks of the patch.

One person's patch pain does not mean that you will see it too. One server's patch pain does not mean you will see it on all of your servers.

HAVE A GOOD BACKUP before you start ANY service pack.

So far when installing WSUS 2003 sp2 I've seen (so far) two sorts of errors. One is a 1602 permission error which I've only seen one of at this time. The rest are 1603 errors. 1603 errors look to me to be installer issues and so far I've seen some being solved from using the office installer fix up tool. http://support.microsoft.com/default.aspx/kb/290301

The benefit of this patch is that it supports Win7s for patching purposes.

I'd recommend if you have issues with this service pack to post in the SBS 2008 partner forum http://social.microsoft.com/Forums/en-US/partnerwinserversbs/threads and zip up and park in a skydrive the WSUS setup files from this location --

c:\users\name of your admin\appdata\local\temp look for the WSUS setup logs

You will need to set the ability to view hidden folders from the folder properties to see that location.

If you have not signed up for the partner forums...
https://partner.microsoft.com/US/40058790 go to that location and sign up.

To those that say that Microsoft needs to test better.. they did. On all of my servers in testing I never had issues. Installer issues are not unique to this patch, nor are they unique to Server 2008. The cause of this issue is not the underlying way that WSUS is patched. If you see people saying a patch blew up, there's more than likely 20 other folks that it worked just fine on. They just don't run to the forums or newsgroups shouting "It worked"!

And the reality with our mutliple use boxes is that one cannot test for 100% no issues. There may be during install. That's why we get paid the big bucks. The key is to decide which patches are worth the possible risk and the best timing to do it. But we have just too much software n the world to have 100% perfect installs and updates. It's just not a realistic attitude to take. So plan on failure. By that I mean ensure you have a backout plan. A place to go to for help (newsgroups or forums). Ways to restore the server. Instructions on how to repair. No service pack should be considered to be a trivial thing. HAVE A BACKUP.

And to those that say that when I blog about patch pain that I'm showcasing why the cloud is superior are full of it. Clouds have patch pain too, they just hide it. Furthermore their maintenance windows/risk of patching/what gets updated and what doesn't is on their schedule not yours.

Repairing WSUS 3 on SBS 2008

bradley — Thu, 27 Aug 2009 07:25:00 GMT

To repair WSUS 3 on a SBS 2008 box is actually relatively easy (at least as compared to ripping out SBS 2003 monitoring and putting it back)

Repair Windows Server Update Services:
http://technet.microsoft.com/en-us/library/dd443475%28WS.10%29.aspx

Make a c:\wsus and type in the commands to run the install

Check that the folders were installed

Once WSUS is reinstalled put back in the products (ALL products)

Select the classifications (I do all but drivers)

Ensure you do languages section (I missed that in the instructions the first time)

Manually type back in the categories

Ensure that the group policy settings are back in place (most of the time they are where they should be already)

And voila... green button not gray button again

If you can't get it installed, dig out the log files.

First uncheck the button in folder view so that hidden files are seen (I ALWAYS DO THIS) and while you are there untick the "hide known file extensions".

Under the c:\users\name of your admin\appdata\local\temp look for the WSUS setup logs

Review them and see what they say. If something looks funky, holler!

Installing WSUS 3 sp2

bradley — Thu, 27 Aug 2009 06:10:00 GMT

Installing WSUS 3 sp2 is needed to support patching Win7 on your network.

To install, you'll see that you'll need to run through the install process by clicking next, next, next......... and importantly at the end...cancel.

Click to accept the install

When you click FINISH, there's a final important step

When the wizard begins, hit CANCEL, and your install will be done. It will pick up your existing settings and make no changes.

In past installs it might also look to the largest free drive, so just in case you may want to temp disable a large external usb drive just to be sure.

Don't forget (as I just did)

From: Dave Nickason FYI, when you install WSUS 3.0 SP2, you need to upgrade to the newest
version of the report viewer. I've installed both the SP and the viewer on
my SBS 2003 and my Vista workstation. Both installed easily and with no
reboot required. After the server install the configuration wizard starts -
just cancel it.

Microsoft Report Viewer Redistributable 2008
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cc96c246-61e5-4d9e-bb5f-416d75a1b9ef

Content file download failed. Reason: CRC verification failure

bradley — Wed, 05 Aug 2009 07:44:00 GMT

So if you happen to see that your server is having issues downloading a file, it's probably a defender update that is getting stuck.

WSUS Synchronization problem:
http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/9bf24ba5-91f9-4581-970c-a9cfaed89f50

EVENT #      368437
EVENT LOG     Application
EVENT TYPE     Error
SOURCE     Windows Server Update Services
CATEGORY     Synchronization
EVENT ID     364
COMPUTERNAME       DOMAIN
DATE / TIME       8/4/2009 11:40:49 PM
MESSAGE     Content file download failed. Reason: CRC verification failure. Source File: /msdownload/update/software/defu/2009/08/mpas-fe_784912957724639d6a9c4e0ae747a3ec7cdf318c.exe Destination File: e:\WSUS\WsusContent\8C\784912957724639D6A9C4E0AE747A3EC7CDF318C.exe.

Decline that update

And if you want to know how to add a file view, thanks to Harry Johnston, right mouse click and add a column to the view... learn somethin' new

It's Summertime and it's WSUStime

bradley — Wed, 24 Jun 2009 06:48:00 GMT

That's right it's WSUS clean up time. If you are not doing a regular schedule.. once a month.. once a quarter ...once a Solstice... to clean up your WSUS, now's the time to do so....

Go into the WSUS console on SBS 2003 or SBS 2008 and click on each of those categories one at a time and run those clean up routines.

Support for WSUS 2

bradley — Thu, 09 Apr 2009 19:01:00 GMT

If you are running SBS 2003 R2 that still has WSUS 2, ensure that you update it to WSUS 3. WSUS 2 is going off of support.

http://blogs.technet.com/sus/archive/2009/04/09/a-quick-note-on-the-windows-server-update-services-life-cycle.aspx

We often get questions about when the support End of Life (EOL) is for a particular piece of software so I thought I’d mention some of the important dates for WSUS in case you were still running any of the older versions.

WSUS 2.0 RTM support has already ended.

WSUS 2.0 SP1 support ends at the end of the month in April 2009 (two years after WSUS 3.0 was released). Yes, that’s this month so if you’re still on WSUS 2.0 SP1 then you need to start thinking about an upgrade.

WSUS 3.0 RTM support ended this February 2009.

WSUS 3.0 SP1 is still under support and will be until 1 year after SP2 releases (This version will be released within one month of Windows Server 2008 R2 RTM).

The Windows Server Update Services Life Cycle has been published for a long time so this is probably old news but since WSUS 2.0 SP1 support was ending this month I thought it would be worth a mention. You can find more information on this at http://technet.microsoft.com/en-us/wsus/bb980625.aspx.

Killing off the Red X

bradley — Tue, 17 Feb 2009 02:59:00 GMT

In the SBS 2003 R2 patch report sometimes you'll get a computer that indicates it has patching issues:

So you go in and see that a workstation is having issues....

And when you click on it, it says..."What errors?"

So what's going on here is that an event does occur with the patch. But the workstation usually fixes itself up. BUT that error only gets cleared out of the Update screen after 15 days. Sooooooo.... you have two choices -- live with it for 15 days.... or.... you delete the computer from the WSUS database and when the computer checks back into the server (and it will in a few hours) you will have no red X and a happy report once again.

Go into the WSUS 3 console, find the offending workstation, right mouse click and delete. Don't worry you aren't deleting the computer out of AD, you are only deleting it out of the WSUS database.

This is only taking it out of the WSUS database, again, this is not impacting AD.

You will notice that the offending computer immediately drops out of the Error screen. And in a few hours it will check back into the WSUS backend and report for duty.

Again, you can just be patient for 15 days for the error to go away, or if you are impatient you can do that little trick of giving the workstation a push.

You can do a wuauclt /detectnow command but it will still take a smidge of time before the workstation checks back in.

If you are STILL impacted by monitoring reports not working

bradley — Thu, 04 Dec 2008 20:10:00 GMT

To put all the steps in one place here's the three recommended:

1. uncheck the drivers in WSUS -- http://msmvps.com/blogs/bradley/archive/2008/08/22/time-to-uncheck-the-driver-category-on-wsus.aspx
2. Run the driver clean up tool http://blogs.technet.com/sus/archive/2008/08/20/a-large-number-of-driver-updates-showing-up-in-wsus.aspx specifically --- http://www.codeplex.com/WSUS/Release/ProjectReleases.aspx?ReleaseId=16459
3. Run the clean wizard -- http://msmvps.com/blogs/bradley/archive/2008/08/05/cleaning-up-wsus.aspx

If after those three steps, unchecking the driver category, running the driver clean up tool and then the clean up wizard in WSUS and you STILL don't have the monitoring reports working, can you ping me via the contact box on the blog?

Silverlight on WSUS

bradley — Tue, 21 Oct 2008 06:01:00 GMT

http://blogs.technet.com/wsus/archive/2008/10/21/silverlight-now-available.aspx

On your WSUS tonight is Silverlight 2.0.

For those that consider Java evil, Flash even more evil, consider that Silverlight is the less evil one. But regardless, until there is an overwhelming need to run an application, you can simply not approve the update.

Declining those drivers

bradley — Tue, 02 Sep 2008 18:59:00 GMT

The WSUS Support Team Blog : A large number of driver updates showing up in WSUS:
http://blogs.technet.com/sus/archive/2008/08/20/a-large-number-of-driver-updates-showing-up-in-wsus.aspx

For those of you with WSUS 3 boxes if you haven't ran this tool to decline the drivers, do so. It will take a while but will clean out all those gazillions of drivers up there.

If you can't run this script because you are getting a "GetUpdates failed. Reason: The operation has timed out", hang loose as I'm investigating what you can do to overcome that.

Time to uncheck the driver category on WSUS

bradley — Fri, 22 Aug 2008 15:58:00 GMT

The WSUS Support Team Blog : A large number of driver updates showing up in WSUS:
http://blogs.technet.com/sus/archive/2008/08/20/a-large-number-of-driver-updates-showing-up-in-wsus.aspx

Read more on that blog post. No, unchecking drivers will not "blue check" a R2 install.

Drivers again in WSUS

bradley — Wed, 20 Aug 2008 07:30:00 GMT

Yes, I know, I should unclick drivers and just ignore this, but sometimes there are some interesting drivers that are sync'd up to WSUS.

Tonight (or rather today), we have drivers again (approx 600 or so) syncing up to the WSUS server. So if you see the WSUS email that says a lot of patches were sync'd up tonight.. don't worry most are old drivers from June, July, Sept of 2007

Just looking for those folks that even AFTER running the WSUS clean up tool that their Server Monitoring reports are not firing as they should

bradley — Sat, 16 Aug 2008 03:34:00 GMT

Installing Windows Server Update Services 3.0 on Windows Small Business Server 2003:
http://technet.microsoft.com/en-us/library/cc708091.aspx

Hardware Component	Requirement
Processor	Modern processor of at least 1 GHz
System memory	1 GB (2 GB recommended)
Hard disk drive system partition	1 GB
Hard disk drive content storage	20 GB
Hard disk drive SQL Server installation	2 GB

To all of those who are seeing their Server Monitoring Reports not being sent out and even AFTER they run the WSUS clean up tool it's still not being fixed/sent, can you let me know if the servers you have meet those specs?

Again, just looking for those folks that even AFTER running the WSUS clean up tool that their Server Monitoring reports are not firing as they should.

Cleaning up WSUS

bradley — Wed, 06 Aug 2008 01:31:00 GMT

So what maintenance should we be doing each month and we're not on our WSUS's?

Les Connor recommends these:

In WSUS v3 SP1, it's a wizard run from the 'options' page of the management console. Click on that Server clean up wizard...

And then do the clean up ...one at a time. I've been running that "Unused updates and update revisions" all day and it's still going.

In WSUS v2, it's command line only... more info here:

http://www.wsuswiki.com/MowingtheGrass

WSUS/SCCM top issues

bradley — Tue, 15 Jul 2008 00:39:00 GMT

In this Issue:

TOP SUPPORT ISSUES
NEW & UPDATED KB ARTICLES
NEW & TOP DOWNLOADS
NEW WEBCASTS

TOP SUPPORT ISSUES
===============
The following "hot topics" were posted and resolved during the month of
July:

Issue #1
======
Problem Description
-------------------------
Certain SCCM client doesn't show their scanned status back in SCCM console

Cause:
-------------
We found that the policy has arrived the client but doesn't get applied,
this verified by looking at key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer
doesn't exist
This is caused by corrupt WMI repository.

Resolutions
---------------
To clean it out, we reinstall the client to fix the namespace issue per the
following steps:

1. Run ccmclean or ccmsetup /uninstall to uninstall the SCCM client.
2. Once done remove the c:\windows\smscfg.ini file.
3. Go into the registry and delete the HKLM\software\microsoft\ccmsetup and
\sms keys.
4. Delete the system32\ccmsetup and ccm directories if they are there
5. Delete the computer from SCCM console.
6. Finally reboot the client and let AD system discovery method to
rediscover the machine and push install the client to the machine.
7. Wait for a while and verify the following:
a.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer
is set to your SUP server.
b. ConfigMgr Software Updates Agent is enabled.
c. Software Updates Scan Cycle is listed in Actions, and then high light the
"Software Updates Scan Cycle", select "initiate Action"
d. Wait for about 3 hours and check from console to see if the client is
reported.

Issue #2
=======
Problem Description
-------------------------
Windows Server 2008 is unable to request the certificate from the Windows
2003 CA

"In order to complete certificate enrollment, the Web site for the CA must
be configured to use HTTPS Authentication".

Resolution
--------------
1. Open the Internet Explorer (right click on the Internet Explorer and
choose Run as a administrator), go to Internet Options, click Security,
click Trusted Sites.

2. Click Custom Level>ActiveX controls and plug-ins>Enable the following
settings.

"Initialize and script ActiveX controls not marked as safe"

Issue #3
======
Problem Description
--------------------------
Unable to perform a clean install the SCCM 2007 and it prompts to upgrade.

Cause:
-----------
The SMS 2003 is installed in the current domain and it is removed forcefully
without uninstalling

Resolution
-------------
- Delete the SMS objects in the AD database:

1. Logon as the domain administrator on the primary domain controller.
Install the Windows support tools from Windows Server 2003 CD media.
2. After installing the support tools, please click start>run>Adsiedit.msc,
open the AD database.
3. Expand the "DC=your domain, DC=com", Expand CN=System, please check if
the "CN=System Management" still there, if so, please delete this object and
all subfolders.
4. On the DC Server, open "Active Directory Users and Computers", check
whether SMS accounts exist, please delete them if yes
5. Wait for the changes are replicated to other domain controllers if there
are more than one DC in the current domain.

- Remove the User Account created by the SMS installation

Issue #4
=======
Problem Description
-------------------------
In SCCM server, we notice the following error:
Component: SMS_POLICY_PROVIDER
Message ID: 5115
Description: SMS Policy Provider has failed to sign one or more policy
assignments. It will retry this operation automatically.

Cause
--------
STATMSG: ID=5115 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_POLICY_PROVIDER"
SYS=TSTSCCM01 SITE=S00 PID=5608 TID=5516 GMTDATE=Thu Jun 12 18:27:44.206
2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=0 SMS_POLICY_PROVIDER 1/1/1601 12:00:00 AM 5516
(0x158C)
Failed in CryptAcquireCertificatePrivateKey(...): 0x8009200b.
SMS_POLICY_PROVIDER 1/1/1601 12:00:00 AM 5516 (0x158C)

0x8009200b means "Cannot find the certificate and private key for
decryption". If you drag and drop, or copy and paste, or improperly export
and import, then you will break the Private Key on the certificate and this
will cause the seen issue.

Resolution
-------------
We recreate the Site Server Signing Certificate Template and did not select
the option "CA certificate manager approval". Then regenerate a new
certificate which solves the problem.

Issue #5
=======
Problem Description
-------------------------
When you run a report within the SCCM server, it keeps asking you for
credentials although you are domain admin and add the server name to
trusted sites.

Cause
-------------
The problem occurs because the computer name portion of the requested URL
contains periods (such as http://www.microsoft.com and http://10.0.0.1),
Internet Explorer assumes that the requested address exists on the Internet
and does not pass any credentials automatically. Addresses without periods
(such as http://webserver) are considered to be on the intranet (local);
Internet Explorer passes credentials automatically. The only exception is
addresses included in the Intranet zone in Internet Explorer.

Resolution
-------------
Add the server name to Intranet sites.

Internet Explorer May Prompt You for a Password
http://support.microsoft.com//kb/258063

Issue #6
=======
Problem Description
-------------------------
Windows Update package isn't installed

Cause
-------------
The Package needs 60 minutes to run

Resolution
-------------
Extend the time for the Update to 60 minutes and the update is installed
successfully.

Issue #7
=======
Problem Description
-------------------------
Notification icon does not appear on WSUS client computer when updates are
available.

Cause
-------------
"Configure automatic updating" policy need to be configured in GPO as: "2-
Notify for download and notify for install" or "3- auto download and notify
for install".
Is there any communication problem between WSUS server and client?

Resolution
-------------
Confirm the GPO settings.
WSUS MPS Report on WSUS server and WindowsUpdate.log on WSUS client.

Issue #8
=======
Problem Description
-------------------------
SCOM2007 Event 33333 and 10801 are logged periodically for two objects.
These two objects has basemanagedentityid:

2536f9ff-9777-2497-fac2-07ac7e701afb
abd11adc-6cd5-85d0-dca9-ba78a11680d5

Cause
-------------
Events 33333/10801 can occur in SCOM2007 if one of the following is true:

1. Agent does not have permission to upload the data if option "allow this
agent to act as a proxy and discover managed objects on other computers" is
not enabled.
2. The agent is in another forest.
3. There is not enough space for database files.

Resolution
-------------
Enable option "allow this agent to act as a proxy and discover managed
objects on other computers" for these two agents.

Issue #9
=======
Problem Description
-------------------------
one SQL 2005 x64 server is not discovered in SCOM2007 correctly.

Cause
-------------
This issue can occur if the agent installed is not correct version.

Resolution
-------------
Install X86 agent on the Server. Then it is discovered correctly.

Useful Article:
==============
SC Ops Mgr 2007 Resource Kit - Operations Manager Cleanup Tool
http://www.microsoft.com/downloads/details.aspx?FamilyID=14ff7073-c71b-4ad0-805a-a8e458d2c9e0&DisplayLang=en

NEW & UPDATED KB ARTICLES
====================
(949957) - Fixes a problem in which the Active Directory System Discovery
process and the Active Directory System Group Discovery process run much
more slowly in a Configuration Manager 2007 site than in a Systems
Management Server 2003 site.
- 6/19/2008 - /default.aspx?scid=kb;en-us;949957

(954214) - Fixes a problem where the SMS_Site_Component_Manager service
stops unexpectedlyin a certain scenario.
- 7/1/2008 - /default.aspx?scid=kb;en-us;954214

(949225) - Describes a problem in which not all advertised task sequences
are processed in Microsoft System Center Configuration Manager 2007.
Provides a hotfix that resolves this problem.
- 7/1/2008 - /default.aspx?scid=kb;en-us;949225

(952939) - Describes a problem that occurs after hotfix 933870, hotfix
941214, or hotfix 941395 is installed on SMS 2003 site servers. Provides a
resolution.
- 6/25/2008 - /default.aspx?scid=kb;en-us;952939

(951527) - Fixes a problem that occurs after you upgrade Operations Manager
2007 to Operations Manager 2007 Service Pack 1. You receive an error message
when you try to modify Web applications that were created before the
upgrade.
- 6/16/2008 - /default.aspx?scid=kb;en-us;951527

(951526) - Fixes a problem in which the Root Management Server component in
System Center Operations Manager 2007 Service Pack 1 becomes unstable or
unusable after a management pack is imported.
- 7/8/2008 - /default.aspx?scid=kb;en-us;951526

(951148) - Fixes a problem in which the installation of Operations Manager
2007 Reporting fails if the SQL Server Reporting Services instance takes
more than 60 seconds to start.
- 7/1/2008 - /default.aspx?scid=kb;en-us;951148

(951380) - Fixes a problem in which some computer properties of a cluster
node are not collected when you run the discovery process in System Center
Operations Manager 2007 Service Pack 1.
- 6/17/2008 - /default.aspx?scid=kb;en-us;951380

NEW & TOP DOWNLOADS
================
Microsoft Windows Server Update Services (WSUS) (KB954960)
http://www.microsoft.com/downloads/details.aspx?FamilyID=6aa8a49d-170c-4077-8b9b-61f7bf5a1281&DisplayLang=en

Microsoft System Center Configuration Manager 2007 SP1 Update
http://www.microsoft.com/downloads/details.aspx?FamilyID=5aae62e8-4b7f-4af7-be01-aefaa4bf059a&DisplayLang=en

Windows Server 2008 Security Configuration Wizard and SC Configuration
Manager 2007 Service Pack 1
http://www.microsoft.com/downloads/details.aspx?FamilyID=8a08a66b-ea5b-423f-9c5d-04205f5a25ef&DisplayLang=en

Microsoft System Center Capacity Planner 2007 Model for Microsoft System
Center Operations Manager 2007
http://www.microsoft.com/downloads/details.aspx?FamilyID=6fec1f12-a62c-4e8d-8a19-56879192adc3&DisplayLang=en

NEW WEBCASTS
==========
N/A

Just say no

bradley — Tue, 20 May 2008 14:44:00 GMT

For some reason WSUS apparently thinks we need Silverlight on our workstations and servers.

(and is there any wonder why I don't have auto updates turned on?)

The password on the email

bradley — Sat, 09 Feb 2008 23:52:00 GMT

Advanced Business Computing Solutions, Inc.: WSUS SP1 Install Error - SMTPUserPassword:
http://abc-solutions.spaces.live.com/blog/cns!F616727CACD12943!477.entry

Jeff said I must not have a Admin password over 12 characters...but I do.... as he did and hit an error when installing WSUS 3.0 sp1. Mine is over 14 to ensure that password hashes are not saved (along with the group policy setting to not save them). The difference is in how I set up the email server.

He has his like this:

Mine is local to the box and thus doesn't need authentication, I just put in the local IP address of the server and it emails out just fine.

But good to know if you hit this.