I’ve been installing a few lab and production ConfigMgr environments recently and found a little quirk with the versioning to go along with the service pack madness / confusion of the 2012 SP2 / 2012 R2 SP1 release. Here’s the
BITS error 0x80200013 during ConfigMgr client installation
When attempting to install the ConfigMgr / SCCM client on a few remote computers, the installation failed (more like stalled out) when ccmsetup.exe tried to download the full client binary files. The download couldn’t complete and the following error was
ConfigMgr OSD and the HP Virtual Install Disk
A recent customer was having an issue using ConfigMgr (SCCM) to deploy Windows on their new HP ProLiant Gen9 servers. Their existing hardware models and virtual machines worked fine, but the new HP Gen9 models were failing with the following
Unexpected reboot upgrading ConfigMgr Admin Console
Yesterday I upgraded my ConfigMgr 2012 R2 lab to SP1 and encountered a small bit of trouble. During the SP installation the Admin Console failed to uninstall; during installation the MSI performed an unexpected reboot. Scenario The primary site server
ConfigMgr 2012 Service Pack 2 confusion
On May 14, 2015, Microsoft released a Service Pack for ConfigMgr 2012 (awesome!). There has been some confusion as can be seen on the original announcement blog comments and the details of that confusion are laid out by Jason Sandys
Unable to find LiteTouch.wsf
Not long ago I was using MDT 2013 to develop a few images. Deploying from the server, whether booting from PXE, CD/DVD, or a USB drive worked fine. However, when I created a stand-alone ISO and extracted it to a
Windows 10 Technical Preview Build 9926 and ConfigMgr
It’s a good day to not be assigned to a customer… Microsoft released Windows 10 Technical Preview Build 9926! I took a moment to download all 4 ISO files (Professional and Enterprise, 32 and 64 bit), inventoried the ISOs to
BranchCache for Microsoft Windows Professional
If you ever looked into using BranchCache, you’re likely well aware that the Enterprise or Ultimate editions of Windows Workstation are required to get this peer-2-peer caching functionality. That’s a disappointment for many organizations who aren’t spending the extra money