bertelsenbo

Excellent article Niall. I hope it's OK I take the opportunity to ask PatchMyPC a question or two. - Are you patches always both for x64 & x86 editions? - Is it possible downloading old versions of software you have packaged? - Regarding the number of Applications that can be patched; do you have any comparison against other services like Flexera, SoftwareCentral+ Packages etc?

You can test this powershell script that can set the rate limits (it worked for me for regular DPs): https://gallery.technet.microsoft.com/scriptcenter/Set-Rate-Limits-for-SCCM-d4740238

Does this apply to new packages too? Or only existing? If newly created packages are without errors, you could recreate them. I know that's a LOT of work, but there might be some powershell scripts out there that can help.

If the WinPE boot image loads, but just instantly reboots (quits) after loading. You need to take the SMSTS.log from the Hyper-V PC (press F8 when it boots to get a CMD and prevent it from shutting down again). If F8 doesn't bring up the CMD, it's because you haven't checkmarked "Enabled command support (testing only)" on the customization tab for you boot image. You need to update the boot image, redistribute it and make new media's too (ISO etc.). The SMSTS.log is found at: x:\windows\temp\SMSTSlog\smsts.log This should give you a heads up to what's wrong to begin with. Most likely just missing the driver to the network card? Do an IPCONFIG with the command prompt in PE (F8). (not likely, but: If the error 0x8007ee7 is present its likely because there’s no DNS server added to DHCP scope.) I don't know what's the cause of the main problem, but maybe the you can find out by starting with the WinPE issue and get more clues from the SMSTS log file. Good luck

Hi king13p, It's most likely stuck in provisioning mode from the Task Sequence not being complete. Do you have a Software Update step to install client patches? If so, there might be one of Microsoft infamous double reboot patches in there. They will break the task sequence and leave the clients in a provisioning mode state (see list here: https://support.microsoft.com/kb/2894518?wa=wsignin1.0 ). Set provisioning mode to false manually after installation by either: 1. Powershell command: powershell Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false 2. Registry edit: HKLMSOFTWAREMicrosoftCCMCcmExecProvisioningMode = False HKLMSOFTWAREMicrosoftCCMCcmExecSystemTaskExclude = (no value, should be blank) This is just a workaround (by GPO as a temp fix). The solution would be to take these patches out of Software Updates and patch your baseline image. If that's not your problem it's probably that the there's: a. Something wrong with the certificate b. SCCM site pointer is set to something wrong? (does the client appear in SCCM configmgr console after installation? Do you need to approve it?) Good luck

Not an actual solution, but just a workaround you could try to prestage it instead and transfer it to the DP's and load it.