Every now and then I’ll work through the Fallback Status Point deployment failures; it’s good to keep on top of the numbers and it’s obviously needed if you wan to patch your PCs. There are naturally an abundance of errors, but this one was quite interesting:
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
So, Config Manager version 5.00.8239.1000 is upon us. I wasn’t too excited about this, till I realised that you can now treat Management Points in the same way as Distribution Points for preferred Content Access.
It’s a very straight forward task, assuming you already have your boundaries configured. Personally, I already had all my Management Point and Distribution Point servers assigned to an AD site boundary, and set for FAST or SLOW accordingly.
If you have a site distributed over a wide geographical area, you might find that you have problems with how clients retrieve their content. We had a situation to which I alluded here, namely a remote site downloading all its Config Manager data over a throttled WAN link.
Anyway as promised, I thought I’d put my thoughts into a blog relating to content access and remote sites.
My site already had two boundaries set. One for the main Config Manager geographical location (we’ll call it SCCM_Boundary1), and another for location elsewhere in the United Kingdom (SCCM_Boundary2). These geographical locations are defined in AD as AD sites, so we’ll call them AD_Site1 (main) and AD_Site2 (remote) for ease here.