Client can't find its Management point

Having a site configuration with several MP's, a few in untrusted forest can be a challenge. Especially combined with complex and firewall micro segmented network. We had an issues with clients, that couln't find the correct MP during OSD and application delployment.  This resultet in time-out errors, causing the installation to fail. The locationservice.log showed that the agent tried the entire MP list. one by one until it finally came to one it was able to communicate with. We talked about setting a static reg key allowedMP like Annop also explains in his blog post below. Setting the AllowedMP will enforce an agent always to communicate with the the MP in the registry, but it will at the same time remove the flexibility build in the agent. So we decided a mixed solution. First step was to solve the timeout issue during OSD. Set allowedMP in the begining of the OSD TS Remove allowedMP at the

PXEboot and DHCP option 82

Some network requires option 82 in the pxeboot package to ensure the client is trusted. Option 82 is removed from the package, if you’re using the traditionel pxeboot configuration. To fix this switch to the pxe responder.

Let user reinstall thier own device

If you want to let users reinstall thier own device using the your standard OSD tasksequence it is pretty easy. Requirement : the tasksequence must be deployed to the device as available. Add a new group at the very top og your tasksequence. Name it eg. Restart in WinPE Add a condition to run only if <part>ccmexec.exe exits. Add a restart command, where you configure it to reboot into the tasksequence bootimage This will make it possible to use the tasksequence for both the bare metal installation and the user initiated reinstall. The ‘Restart in WinPE’ group will only run if ccmexec.exe exits. (Full OS) Applications deployed after OSD will be installed, when OSD is done. Therefore advise users to start the reinstall when they are leaving the office. Ps/ VPN is not supported Wifi is not supported

SCCM WSUS updates - search criteria

Have you ever noticed the "review" button, when you set upa search criteria? The result of the configured criteria

Pxeboot over slow line - speed it up

Playing around with TFTPWindowsSize  can result in faster pxeboot process over a slow line. One of my colleagues has optimized the pxeboot process by adjusting the TFTPWindowsSize. In our case the load of the pxe wim vent down from 20 min to 2 min. The default value i 1, and the test ended with 16. it migth be required with some test in your environment to find the "right" value for you. The change did not impact the pxe process on VMWare. PS/ Do not change the TFTPBlocksize, this will break the pxe process! Next step will bo to implement BranchCache, to get additional performance improvements

Just a link to the old blog..

SCCM CB Monitoring | Deployment Reporting using SQL

I have been look for a way to report deployment status, without using Monitoring | Deployment in the console. The trick was to monitor SMSPROV.LOG while I activated the monitoring  | deployment in the console. After some digging around in the log, I found the select statement below. I have modified it a bit and added some comments. select   all SMS_DeploymentSummary . ApplicationName , SMS_DeploymentSummary . AssignmentID , SMS_DeploymentSummary . CI_ID , SMS_DeploymentSummary . CollectionID , SMS_DeploymentSummary . CollectionName , SMS_DeploymentSummary . CreationTime , SMS_DeploymentSummary . DeploymentID , SMS_DeploymentSummary . DeploymentIntent , SMS_DeploymentSummary . DeploymentTime , SMS_DeploymentSummary . DesiredConfigType , SMS_DeploymentSummary . EnforcementDeadline , SMS_DeploymentSummary . FeatureType , SMS_DeploymentSummary . ModelName , SMS_DeploymentSummary . ModificationTime , SMS_DeploymentSummary . NumberErrors , SMS_Deployme