Posts Tagged ‘Scripts’

As a consultant, I have done numerous installations of Configuration Manager and one of the things that usually generate problems is when tasks are delegated from the Configuration Manager team over to other parts of the organization or third party. This solution will catch some of the most common issues that occur when handing over OSD to another team.

You as a deployment expert and the person who set up and have full control over your Configuration Manager environment will catch most of these issues without this tool. However, if a person on first line support is given the task to deploy new computers to end users he or she has no clue on what’s set up in the background and this tends to generate issues. An example being, deploying a computer model that has no driver packages assigned.

So I wanted to create a simple tool that check for the most common issues at the very beginning of the task sequence, no one wants to wait for several minutes just to find out that there is no driver package for this model. There are some solutions for this already out there but they are usually part of a UDI/Front-End solution or steps in the Task Sequence that give hard failure and fails the task sequence without any options to correct the problem. Therefore, I ended up with these criteria’s,

  • Must be dynamic, only appear if something will/could prevent the task sequence from completing successfully else continue as normal
  • Errors or warnings must appear at the very beginning of the task sequence, and it must be possible to correct these without the need for re-starting the task sequence
  • Provide information about the computer in case of an error or warning

What I ended up with looks like this in action:




Last year I blogged about how to show DP in use during OSD you can find that posting here.

I’ve gotten some questions on how to display the correct computer name in the background with bginfo instead of the MININT-XXXXXXX name.

I’ve created a script with the following lines;

'// Purpose: Used to display correct computer name during OSD
'// Version: 1.0 - April 17, 2015 - Odd-Magne Kristoffersen
'// This script is provided "AS IS" with no warranties
Set env = CreateObject("Microsoft.SMS.TSEnvironment")

and saved it as SetComputerName.vbs in the Tools\x86 folder of my MDT Toolkit Package.

I then modified STEP_01.BGI and STEP_02.BGI files provided in the MDT Toolkit Package to utilize this VBScript and display the information, below you see what changes you need to make to each of the provided BGInfo files. Alternatively, you can download a copy of them already modified here and replace the ones already existing in you Tools\x86 folder of your MDT Toolkit Package.
23When done update the MDT Toolkit Package and start a new deployment and you’ll be able to see the correct computer name during deployment as shown below.


Updated post here: Office 365 ProPlus Application Selection

There are a lot of posting out on how to deploy Office 365 ProPlus from an on-premises location, but I could not find anyone with a walk-through of doing a custom installation. All the postings I found takes an all or nothing approach when installing Office 365 ProPlus, but what if I only want some of the components installed? This is straightforward in the traditional installer or with Office Customization Tool.1 2

To accomplish this with the Office 365 ProPlus installation, we first need to download the Office Deployment Tool for Click-to-Run and install it. It will provide you with two files, setup.exe and configuration.xml. When this is done, we are ready to start the process of making a customized Office 365 ProPlus Installation.


Last year I blogged about how to add Lenovo and HP warranty information to Configuration Manager 2012, you can find this blogpost here.

Since that HP have changed their warranty lookup website so the script in the previous blogpost has stopped working. Yes the script solution is dependent on the output from the webpage to provide the information, so if the webpage change, the script most likely will stop to function again. But I’ve rewritten the scripts to make it easier to adjust if this happens.

You can download the updated scripts here; HP Lenovo – Dell


Below are some questions that tends to come up when working with OSD and Task Sequences;

  • Where are the content comming from when running the task sequence?
  • Is the Task Sequence downloading the packages from local DP or remote DP?

These types of questions typically comes when a customer have multiple DPs and would like to know if the “correct” DP is used during OSD. Offcourse you can always find this information in logs or by looking at the traffic, but most customer wants this to be displayed while the TS is running without having to do something extra.

So I’ve made an addon to the BgInfo Status Screens that are built-in to the task sequence, when you integrate MDT with SCCM, to display this information.