SCCM

On Twitter I asked the following to David James (Director of Engineering, ConfigMgr, Microsoft) and Johan Arwidmark (CTO @ TrueSec): https://twitter.com/DevSecNinja/status/1024927840138145793 For example, I have 3 device collections in SCCM that I call: “Windows 10 Feature Updates - Test” “Windows 10 Feature Updates - Pre-Production” “Windows 10 Feature Updates - Production” With ADRs, that’s quite simple. Just add the deployment to the Software Update Group in SCCM and you’re done. But I was wondering if that is supported in the Servicing Plan scenario too, as with a Servicing Plan you define the amount of days it will take after a build release, before SCCM will deploy the feature update to the collection. ...

**With Windows 10 1607, Microsoft introduced Dual Scan functionality, which allows the computer to connect with Microsoft Updates besides using WSUS or SCCM. Steve Henry from Microsoft: “It is for the enterprise that wants WU to be its primary update source while Windows Server Update Services (WSUS) provides all other content.” I’ve seen various blog posts not covering all the steps I had to take to ensure Windows only looks to SCCM/WSUS. ...

So you are signing your PowerShell scripts as a Best Practice from Microsoft. Good job! You’ve configured the PowerShell Execution Policy as AllSigned and you’ve created an application in SCCM where you run the signed script as: PowerShell.exe -File .\Script.ps1 The application installs just fine on your machine from the Software Center. During the Task Sequence, the application cannot be installed and in the Event Viewer. You’ll find the following error message: ...

Recently I was trying to apply a lock screen image with a GPO. I distributed the image to the C:/Windows/Web/Wallpaper directory and configured the Windows 10 GPO to that location. After running the Windows 10 Task Sequence successfully, the default lock screen image came up. I was using a large image from the client so that it still looks good on bigger screens. I’ve found out that after resizing the image back to 1080P, the image was applied successfully after locking the machine. ...

Problem: Multicast during an SCCM 2012 R2 SP1 (1511 release) Task Sequence fails with error “Failed to get MCS key (Code 0x80004005)”. This error is found in the smsts.log log file on the (Windows 10 Enterprise x64 1511) client machine. SMSTS.log file contents CLibSMSMessageWinHttpTransport::Send: URL: SCCM01.CORP.DOMAIN.COM:443 CCM_POST /SMS_MCS_AltAuth/.sms_mcs?op=keyinfo ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290) In SSL, but with no client cert ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290) `Request was successful. ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,2054) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)reply has no message header marker ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,10358) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)oMcsRequest.GetMCSKey(mcsKeyInfoResponse), HRESULT=80004005 (e:\nts_sccm_release\sms\server\mcs\consumer\mcsisapiclient.cpp,429) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)Failed to get MCS key (Code 0x80004005) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)ClientRequestToMCS::DoRequest failed. error = (0x80004005). ...

Problem: If you see the following error in your IIS Logs (C:\inetpub\logs\LogFiles\W3SVC1), it’s possible that the CRL of your Certificate Authority isn’t reachable or valid anymore: GET /SMS_MP/.sms_aut MPLIST 443 - SMS_MP_CONTROL_MANAGER - 403 13 2148081683 5701 18 Solution: Export a certificate from your personal certificate store, for example, an SCCM Client Certificate to your C: drive. Open a command prompt with elevated rights and type: ...

Because I wanted to configure Device Guard with Windows 10, I need the Hyper-V Hypervisor to be enabled on Windows 10. I tried to do this with DISM and an answer file, but it’s not possible to enable Hyper-V during the Task Sequence Deployment because Hyper-V requires a couple of reboots. Solution Create a new “Set Task Sequence Variable” task in your Task Sequence. This will run the PowerShell command after the Task Sequence ends. I’ve set this task before enabling the Driver Package, but it should be possible to place this task anywhere you like. ...

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

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.

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.