wsusscn2.cab file not getting to clients

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

wsusscn2.cab file not getting to clients

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> wsusscn2.cab file not getting to clients

Page: [1]

Message

<< Older Topic Newer Topic >>

wsusscn2.cab file not getting to clients - 11/13/2008 4:02:51 PM

lpoling

Posts: 1
Score: 0
Joined: 11/13/2008
Status: offline

Hello all, I've discovered that the wsusscn2.cab file is not being updated on the SMS clients and therefore the monthly Microsoft Security Updates are not getting installed. The package runs fine and reports successful, but since an old cab file is being scanned, nothing is really getting installed onto the workstations.

I searched on the SMS (2003) server for that file and found that when everything was working fine, the file shows up in "E:\SMS_CCM\Cache\DCH00002.x.system" where x is an incrementing number. That is the case up to August. There is nothing for Sept. or Oct. and there is a new one for Nov. located at E:\Microsoft Updates Inventory Tool\PkgSource. I did a rerun advertisement this morning and I think that's what got that one downloaded to the SMS server albeit in a different location.

I manually copied the contents of that location to a workstation's C:\WINDOWS\SYSTEM32VPCACHE\DCH00002 folder and ran the packge for November's updates and it worked fine. What I don't know is what got broken on the SMS server that the wsusscn2.cab and other files are no longer getting to the workstations. Given the different locations noted above on the SMS server for the November files vs. previous months, I suspect the root of the problem lies there.

The only change that I can think of that's been made was a scheduling change back in Sept. for either the advertisement which causes the SMS server to get the files from M$, or the advertisement that causes the workstations to check the SMS server for a new set of files.

Any recommendations as to what can be jiggled would be greatly appreciated.

Lawson...

Post #: 1

RE: wsusscn2.cab file not getting to clients - 11/13/2008 4:23:23 PM

skissinger

Posts: 2291
Score: 145
Joined: 9/13/2001
From: Sherry Kissinger
Status: offline

If you haven't already confirmed it, check that your Package has been updated successfully to all of your DPs. Since you indicate the source folder shows the right .cab file; that should trigger your clients to know to get new package content.

It sounds like you already suspect the 2 advertisements' scheduling. Have you checked them? I would guess that the one that the server runs to download the updated cab would run at a minimum once a month, sometime in the afternoon of the 2nd Tuesday of the month. I used to run it nightly, then on Tuesday manually kick it off. But that was me...

For the Clients, at a minimum you'd want them to run the scan ad once a month as well--probably an hour or so after your monthly download of the updated .cab. I used to run it daily on patch week, then step it back to weekly; back & forth.

To see if either advert is failing, check the Advertisement Status messages; or the Advert reports.

_____________________________

mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com
My Blog
Microsoft MVP - ConfigMgr

(in reply to lpoling)

Post #: 2

RE: wsusscn2.cab file not getting to clients - 11/14/2008 2:57:58 PM

criticalerror

Posts: 110
Score: 0
Joined: 6/19/2007
Status: offline

Our environment:

I run the sync tool at 1am every second wednesday of the month (new cabs are released the second Tuesday of every month by MS)
I then run the update tool EVERY wednesday at 4am to update the cab on clients. I run it weekly because sometimes MS released emergency additions to the cab outside the normal second tuesday. In that case I manually run the sync tool on the server and can rest assured the clients will update.

Troubleshooting tips:

You are confident the sync is working and the cab in the source is correct. If you have problems with sync this is a good resource for troubleshooting:
http://myitforum.com/cs2/blogs/mlucero/archive/2007/05/22/sms-2003-security-compliance-manually-updating-wsusscan2-cab.aspx

Like Ski said, make sure your DPs are updating correctly with the latest version of the source. In the package settings you can autoupdate DPs with new source files. I do this monthly about an hour after the sync occurs.

Check for errors in the advertisement status. Check log files on trouble clients.

You can also check the SMS flowcharts for a detailed look at whats happening when an advertisement runs on the client.

(in reply to skissinger)

Post #: 3