Problem: In SCCM 2012 R2 SP1 CU2, I’ve created a package that deploys some files such as wallpapers with a .BAT file. When I check the execmgr.log, I see the following error: Script for Package:PR######, Program: Run Script failed with exit code 4. Solution: Under the program in SCCM, change “Run” from “Hidden” to “Normal”.
I had some issues with the newest Windows ADK (1511) with Configuration Manager 2012 R2 SP1 CU2. As of yesterday, it’s possible to download the newest version of Configuration Manager: 1511. Because I had issues with the newest ADK, I’ve asked Microsoft on Technet if we still need to use the older ADK (10.0.26624.0) or if we can use the newest 1511 version of the ADK: [ ](/images/2015/12/adkversion.png) Check the post mentioned in the image above to download the right ADK version when you are going to use the new Configuration Manager 1511.
I was capturing a new Windows 10 TH2 (1511) image with SCCM 2012 R2 SP1 CU2 when suddenly the capturing process stops and ends with a Blue Screen of Death: “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED”. Current environment: SCCM 2012 R2 SP1 CU2 Primary Site Local Distribution Point Windows Server 2012 R2 OS Based on Hyper-V 2008 R2 and 2012 R2. Windows 10 Template on Hyper-V Server 2008 R2 Cluster with VM Version 1. Firstly I thought that the boot image was corrupt or not working, so I tried to recreate the image using the following post. ...
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 deploying Windows 10 with SCCM 2012 R2 SP1 and the task sequence failed after “Installing device drivers” with error code 0x80070032 (or 80070032). The “Auto Apply Drivers” task works fine, but doesn’t install a lot of drivers. The smsts.log file: Dism failed with return code 50 Failed to add driver to driver store. Code 0x80070032 Failed to provision driver. Code 0x80070032 Exiting with return code 0x80070032 Solution: Make sure you’re using the latest MDT version, compatible with Windows 10. Make sure you’re using at least ADK 10. Check if your boot image has OS Version 10 or higher. If not, create a new boot image with MDT or ADK.
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)