Recently I connected System Center – Virtual Machine Manager with WSUS. The WSUS server is installed on the primary site server of my SCCM 2012 R2 SP1 CU2 installation. After I configured my SCCM WSUS server as an update server for VMM, the distribution point in the office stopped working. You will see HTTP ERROR “12030” in your logs and the PXE request on a client will fail. Browsing to the website of the SCCM Primary Site server will fail too.
I found out that the certificate of IIS on my primary site was gone. There was no certificate selected for the Default Website. After adding the certificate again and restarting IIS, PXE started to work again.
Recently I found the following error in the SMSPXE.log log file on my newly created distribution point:
CryptVerifySignature failed, 80090006 SMSPXE <REMOVED TIME> 2500 (0x09C4)
untrusted certificate: <REMOVED CERTIFICATE> SMSPXE <REMOVED TIME> 2500 (0x09C4)
Failed to get information for MP: https://SCCMPRIMARY.DOMAIN.TLD. 80090006. SMSPXE <REMOVED TIME> 2500 (0x09C4)
After recreating my certificate template for the IIS Service on the primary site server, it fixed the problem. Check the online documentation of SCCM for the details of this certificate template.
Sometimes it’s possible that the registry keys SerializedMCSKey and SignedSerializedMCSKey in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\MCS location are empty after a fresh installation or after reinstalling multicast.
Patience… It took like 5 or 6 hours to get those values populated by SCCM / WDS. I’ve searched for a way to force this, but I couldn’t find anything online. I’ve tried to reboot both machines, without any luck. If you know a way to force this, please let me know.
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″