It’s been quite a while that I was able to blog something, but I was quite happy to attend the Microsoft Ignite 2018 conference in Orlando. Living in Florida made this a nice experience since travel wasn’t too bad and required no airport. I was also very pleased to see and feel more of a centralized vision when it comes to the direction in which Microsoft is going and how they plan to have solutions to meet the needs of their customers while on-premise, in the cloud or both (hybrid).
Seeing all of these new benefits Windows 10 1607 had brought to the table, I thought it would be a good idea to finally get something running in my lab environment through SCCM via the Windows 10 Servicing Plans. Initial experience was quite positive as everything went according to the book without the prior issues experienced in SCCM 1511, where the servicing plan would attempt to download every single copy of Windows 10 on every language known to man kind. Thanks Microsoft, my drive was not worthy of that much data so it filled up.
However, this time the challenges started right away by having to patch WSUS once again with KB3159706 which includes a set of additional annoying steps. Then I experienced additional problems on the client side that led me through loops of depressing troubleshooting steps. This time errors 0x8024200D, 0xC1800118 and 0x80240022 kept coming up on my client machine causing a lot of headaches.
Microsoft has recently released the System Center Configuration Manager 2012 Service Pack 2 and 2012 R2 Service Pack 1. These can be downloaded oddly from Microsoft’s evaluation page for System Center in a strangely and confusing manner unlike previous service packs. The updates come in two files that also confuse most folks with an awkward naming scheme, which is why so many folks have needed further clarification on their intended use.