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.

  1. Add a new group at the very top og your tasksequence. Name it eg. Restart in WinPE
  2. Add a condition to run only if <part>ccmexec.exe exits.
  3. 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


Comments

Post a Comment

Popular posts from this 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...
Read more

Client can't find its Management point

-
Image
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. https://www.anoopcnair.com/sccm-mp-rotation-issue-sup-rotation-fix/ 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 ...
Read more

PXEboot and DHCP option 82

-
Image
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.
Read more