Post action in Task sequence


If you want to do stuff after you task sequence is finished, then you can use the variable “SMSTSPostAction”. Create a “Set Task Sequence Variable” step in the beginning of the Task sequence. In this example the computer will reboot at the end.

Name: Give it a name. Ex “Set SMSTSPostAction”
Task Sequence Variable: SMSTSPostAction
Value: shutdown /r /t 30

image

Increase error dialog timeout in OSD


The default error dialog timeout is 15 minutes. You can increase that timeout by creating a “Set Task Sequence Variable” step at the beginning of your TS.

Name: Give it a name. Ex “Set SMSTSErrorDialogTimeout to 24 Hours”
Task Sequence Variable: SMSTSErrorDialogTimeout
Value: 86400

image

SCCM Update not in console?


If the SCCM 1602 update doesn’t show up in the console. Then you can run this script “EnableUpdateRing.ps1

Running the Powershell script will make the update visible immediately. When running the Powershell script, you’ll need to provide your CAS or stand-alone primary site server name as an argument like so:

.\EnableUpdateRing.ps1 siteservername

(replace siteservername with the name of your CAS or stand-alone Primary).

Weekly email with OSD summery


With this guide I will show you how you can get an weekly email with last week deployment status.

1. Download OSDsummery.ps1 and save it to C:\Scripts

2. Change the following lines in the script:
– Line 4: Add your SCCM server
– Line 5: Add you SCCM DB
– Line 8: Add the name of your task sequence
– Line 13: Add your email address
– Line 14: Add the from email address
– Line 15: Add your email server

3. Create a service account for a scheduled task

4. Open “scheduled task” and create a task read more

Generate Webpage with MDT status


If you have set up MDT monitoring and have users that should access the monitoring data from MDT, but doesn’t have the console installed. Then you can follow this guide to create a webpage the contains the monitoring data. See this post to set up MDT monitoring. Thanks to Mikael Nystrom blog post for the inspiration. I have made a few changes to the script.

1. Download GenOSDStatus.ps1 to C:\Scripts

2. Modify the server url line 1 and point to your MDT server.

3. Modify “COMPANY” in line 33 and line 40. read more

Integrate DaRT Remote Viewer in ConfigMgr console


To remote control a Pc in WinPE from the SCCM console, follow the steps below. This guide assume that you already have added DaRT into you WinPe and installed MDT with monitoring enabled on your SCCM server. Otherwise see this post Remote Control Pc in WinPe and Enable MDT monitoring. Thanks to Nickolai’s post for the inspiration.

1. Close the SCCM console if it is open

2. Install Windows ADK
image

image

image

image

image

3. Install DaRT 10
image

image

image

image

image

image

image

4. Create a folder called “C:\Scripts” read more

Enable MDT monitoring


MDT monitoring comes handy if you want to see the progress with a OSD or remote control a Pc in WinPE. Here is the steps to enable monitoring in MDT. Thanks to Johan Arwidmarks post for the inspiration.

1. Install Microsoft Deployment Toolkit (MDT) 2013 Update 2 on your SCCM server with default settings.

2. Create a deployment share with the Wizard

3. Right click on the deployment share and choose “Properties”
image

4. Click on the Monitoring tab –> mark “Enable monitoring for this deployment share” –> type in your SCCM server name in “Monitoring host”
image read more

Remote control PC in WinPe


If you have remote locations that you support it could be handy to connect to a Pc that is in WinPe for trouble shooting. Here is the steps to prepare your boot image for this. Thanks to Johan Arwidmarks post for the inspiration.

1. Install Microsoft Deployment Toolkit (MDT) 2013 Update 2 on your SCCM server with default settings.

2. Run the MDT “Configure ConfigMgr Integration”
image

image

2. Install DaRT 10 on your SCCM server.

3. Go to “C:\Program Files\Microsoft DaRT\v10” and copy “Toolsx64.cab” to “C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64” read more

Send an Email if OSD fails


You can send an email if OSD fails on a Pc. Get the “SendMail.ps1” here and save the script on the SCCM server.

Changes the following lines in the script:

1. Add you from email address in line 7
2. Add you email address in line 9
3. Add the SMTP server in line 11

We are going to use status filtering rules to look for Message ID “11170”. This means that OSD have failed. Follow these step to set it up in SCCM:

1. Open the SCCM console and navigate to: Administration –> Site Configuration –> Sites
image read more