Archive | Microsoft Deployment Toolkit

Use the integrated MDT 2013 Execute Runbook task with SCCM 2012 together with Orchestrator using SSL

When using the SCCM 2012 integrated MDT 2013 Execute Runbook task together with an Orchestrator web service that are SSL encrypted one need to add this to the input. Below is an example how to add the port and https to get this to work.

https://OrchestratorServerName:<port>

The port at the end is only needed if not using the standard port 443 for SSL.

1

Add a Custom Entry in the Configuration Manager SMSTS Log

In this post I will describe how to add a custom text entry in the SMSTS.LOG. In this example I use the integrated MDT 2013 Task Sequence (TS) in Configuration Manager 2012 R2.

To add a SMSTS entry do the following

In the Task Sequence add a “Run Command Line” step. In this example it is called “LAB – Custom Entry in SMSTS Log 1”. In the “Command Line” box add “cmd /c echo <text that should be printed>”.

Below you can see an example screenshot of a TS with the step.

Add Custom Entry in the Configuration Manager SMSTS Log1

How it looks like in the SMSTS.LOG.

Add Custom Entry in the Configuration Manager SMSTS Log2

0

Check the customsettings.ini file and its prameters

Here is a reminder post on how to check the customsettings.ini file before deploying it with the Microsoft Deployment Toolkit (MDT) Task Sequence that for example can be integrated in System Center Configuration Manager (SCCM).

Start off by copying the script folder from the MDT deploymentshare down to a client.

Check the customsettings.ini file and its prameters1

Then copy the x64 and x86 folder from the Tools folder, in the MDT deploymentshare on the server, into the scripts folder, you just copied, on to the client.

Check the customsettings.ini file and its prameters2

Also copy the customsettings.ini file that you want to check into the scripts folder on the client.

Open a Dos or PowerShell prompt on the client and go to the scripts folder. I have choose to use a PowerShell prompt in my example.

Run the command: cscript.exe .\ZTIGather.wsf

Check the customsettings.ini file and its prameters3

The result should look something like this.

Check the customsettings.ini file and its prameters4

When running the command it creates a C:\MININT folder. Delete this one after running the command.

Check the customsettings.ini file and its prameters5

0

Use customsettings.ini to generate computer name and place computer in OU depending on type

If there is a need to generate a computer name automatically and place the computer in a specific OU depending on if it is a laptop or desktop, this is how it could be done.

The products used in this example is Configuration Manager (SCCM) with the integration of Microsoft Deployment Toolkit (MDT).

I use the MDT integrated Task Sequence in SCCM together with some changes in customsettings.ini. Below is my customsettings.ini that generates the computer name and puts it into the OU.

Use customsettingsini to generate computer name and place computer in OU depending on type

If the deployed PC is a laptop the result will be

Computer name: LT-EEEEEE
OU: OU=Laptop,DC=LAB,DC=DOMAIN

0