Jean-Paul van Ravensberg

Jean-Paul van Ravensberg

SerializedMCSKey and SignedSerializedMCSKey registry keys are empty - SCCM

Problem: 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. Solution: 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.

Script for package failed with exit code 4 in SCCM 2012 R2

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”.

Which Windows ADK version to use with Configuration Manager 1511?

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.

BSOD when capturing image with SCCM 2012 R2 SP1

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.

Windows 10 - Intel Bluetooth can't connect to devices after reboot in TH2

Recently I had an issue with my work notebook, a Dell Latitude E6540. After upgrading to the new Windows 10 TH2 version, my Bluetooth keyboard and headset started couldn’t connect after a shutdown. I had to reconnect the Bluetooth devices again to temporarily fix it. I was looking for a recent driver for my Intel Centrino Advanced-N 6235 network card, but it was already up-to-date because of a manual Windows Updates action I did after the upgrade to TH2.