WSUS Boot-Strapper Error

Following a client upgrade, I did notice a niggle with one of Config Manager’s Components:

So fustrating at times... the error doesn't really tell what the real issue is.

So frustrating at times… the error doesn’t really tell what the real issue is.

A constant stream of:

WSUS Configuration Manager failed to publish client boot-strapper package

So basically something is wrong, but there were no details to give me a definitive direction. I delved into the logs, and headed straight for the WSUS logs. I opened the WCM.log, and although nothing was flagged in red, I did find some interesting text:

So why couldn't this be said elsewhere?

So why couldn’t this be said elsewhere?

…so there is a mismatch! I compared the three servers, and found that one of them was missing a WSUS update. I’m not sure how, but this wasn’t my handy work 😉

Okay, one of the servers running WSUS, and its hotfixes.

Okay, one of the servers running WSUS, and its hotfixes.

Ohhhh ding! We have a winner.

Ohhhh ding! We have a winner.

So one of the servers was missing KB2938066.

However this wasn’t the only symptom! As perviously mentioned, we use a Software Update Based Deployment for the Config Manager client. Since the upgrade, I had noted that there was a discrepancy between the available version and the “published” version. With hindsight, this ties in with the error above where the boot-strapper failed to “publish” a package.

To get to the Software Updated Based installation, drill down into the Client Installation Settings menu:

This really is a nice way to deploy the client!

This really is a nice way to deploy the client!

…and you can clearly see the discrepancy twixt the two:

No errors are offered -_-

No errors are offered -_-

If one tried to update the package, Config Manager would go through the motions but nothing would actually change. When you went back to the window, it still had the client version mismatch. No errors would be given via the GUI either. Pretty slack…

Why you no give error?

Why you no give error?

I installed the missing update, no issues there. After a short period of time, the boot-strapper published:

Sorted !

Sorted !

…and finally the Software Update Based deployment updated the client version and it remained so:

...and we're back on an even keel.

…and we’re back on an even keel.

Done.

 

Advertisements

2 thoughts on “WSUS Boot-Strapper Error

Flame on xD

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s