Following a client upgrade, I did notice a niggle with one of Config Manager’s Components:
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:
It’s that most wonderful time of the month again, when Microsoft release the monthly Outlook show stopper. In November, we had fun and games with bad updates for Outlook 2010 and Outlook 2013.
Microsoft appear to have outdone themselves again, by releasing KB3114409. This December 2015 update causes havoc for Outlook 2010 users. thankfully this time round my beta testers actually told me about it. A quick Google of “Outlook 2010, reading pane, December updates”, and I was awash with unhappy punters.
In November we were well into the swing of a migration from Office 2010 to Office 2013. The vast majority of the update alpha test group were running Office 2010. The vast majority of the beta test group were Office 2013.
As part of the November 2015 monthly release, I deployed KB3101488. It went through the alpha testing and no issues were recorded… but as noted above, we were light on the ground for Office 2013
Following on from my blog here, I applied the server-side WSUS update, KB2938066. I then ran the server clean up wizard and was quite surprised at the numbers:
It does make me wonder if the server clean up wizard alone is enough. it’s something I need to look into… I would not have considered there to be so many deletions for a database that is cleaned up once a month. However I digress.