Problem: When you upload your new Windows 10 ADK boot image to SCCM 2012 R2 SP1, the process ends with the error “The specified file is invalid. Only maximum compression type is supported”. Solution: Download the newest Windows ADK for Windows 10, Version 1511 here at Microsoft.
During an Operating System Deployment in SCCM 2012 R2, new notebook models crashed after installing the driver package. I couldn’t see the BSOD code because I wasn’t able to boot the computer in safe mode, but after taking some pictures with my phone of the BSOD screen, I found out that the error code was 0x0000007e. The next step: how are you going to troubleshoot 160 drivers that you deployed to those models with your new driver package? ...
Today I had an issue with one of our new notebook models at a client. Problem: After you PXE-boot the device, the device doesn’t get his advertisement from SCCM and goes in a reboot to the original OS. If you open the command prompt with F8 during the boot image startup process, no IP address is shown after you type in the command “ipconfig”. The driver package from the manufacturer we used included a Windows 7 NIC driver, which was good for the install image. ...
I had an issue within my lab with deploying Windows 8.1 drivers to Windows 10 with SCCM 2012 R2 SP1. It isn’t possible to make all Windows 8.1 drivers compatible with Windows 10 within the SCCM 2012 R2 SP1 console with just one click. Because I was running within a lab environment and I only had 2 driver packages for Windows 8.1 x64, I was able to make the drivers available for deployment to all platforms. You can do this with the magic of PowerShell: ...
I was doing a migration project from System Center - Operations Manager 2007 to System Center - Operations Manager 2012 R2. Some computers had troubles with the upgrade of the agent. I first tried to do a client push deployment. 80 % of the installations succeeded, but I had a couple of computers with failed installations/upgrades. 1. Start the agent installation manually on the failed computer. Run the MOMAgent.msi installer. 2. ...
Problem The following error occurs in the ccm.log when doing a remote client install: Unable to connect to WMI (root\ccm) on remote machine “COMPUTER” Solution Allow the following rules in Windows Firewall: Outbound and inbound: File and Printer Sharing Inbound: Windows Management Instrumentation (WMI)