January 24 2013

Popup message during SCCM task sequence in full OS

So it’s pretty easy to create a VB script popup during a task sequence when it is running in WinPE, however it’s a bit more difficult to have a VB script popup to show to the user when the task sequence is still running in the full OS – eg Windows 7 with a user logged on.

 

This is one method that I used to get it working, maybe there are easier or cleaner ways, but this one works well for me. We can achieve something like this:

Popup

 

In the task sequence, somewhere after the MDT Use Toolkit Package step, add a command line step:

TS Warning

 

Use the following command line:

“%ScriptRoot%ServiceUI.exe” -process:tsprogressui.exe %SYSTEMROOT%system32wscript.exe “%ScriptRoot%Warning.wsf”

 

This is the warning VB script (Warning.wsf) that I’ve used in my example, you just need to put this in your MDT scripts folder:

 

<job id=”setEnv”>

<script language=”VBScript” src=”ZTIUtility.vbs”/>
<script language=”VBScript”>

Dim oTSProgressUI
set oTSProgressUI = CreateObject(“Microsoft.SMS.TSProgressUI”)
oTSProgressUI.CloseProgressDialog()

MsgBox “Popup warning message to go here. This is shown in the user session.” & chr(13) & chr(13) & “Press OK to continue.”,0, “Warning”

</script>
</job>

 

 

There is also a bit of info over here on ServiceUI.exe – http://blogs.technet.com/b/cameronk/archive/2011/01/25/can-i-use-serviceui-exe-to-launch-other-programs-besides-the-udi-setup-wizard.aspx

 

 



----------------------------------------------------------------------------
I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.

----------------------------------------------------------------------------

April 8 2011

x86 or x64 Boot Images during SCCM OS deployment

If you are wondering which architecture of boot image to use during SCCM OSD, the following table may assist you. When picking which boot image to use, it’s important to know there are different rules for Install Packages and Images.

Use of the wrong type of boot image may result in failure of the task sequence and an error in the SMSTS.log like:

The detected setup program architecture does not match the current boot image. You must correct your task sequence so that the installation package matches the boot image.