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.
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:
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”.
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. Unfortunately, the BSOD comes up with both boot images.
Use a Generation 2 VM instead of a Generation 1 VM.
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”.
Continue reading ““The specified file is invalid. Only maximum compression type is supported” – SCCM 2012 R2 SP1″
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.
Continue reading “Troubleshoot BSOD after deploying driver package in SCCM 2012 R2”
Today I had an issue with one of our new notebook models at a client.
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”.
Continue reading “Intel I219-V Ethernet Connection driver doesn’t work in WinPE (SCCM)”
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:
Continue reading “SCCM 2012 R2 SP1 – Make Windows 8.1 drivers supported on Windows 10 with PowerShell”