Interactive Step in a Task Sequence, run within Windows.

 This is for SCCM 2007

Using TS for application distribution is not a bad thing, it gives us a fair deal of more possibilities for the distribution.
You can in a better way control each step needed which I specialy like when it comes to pre-req's

What is missing though is the possibility to make a step user interactive.
Sometimes you want the user to make a choice and this is not only a check box within the TS.

To simplify for all you out there with the same issue as I've run into, I here have a solution created by hours and hours of googling, mailing and talking in forums.
The solution below we also use for interactive HTA.
simply create an HTA instead of theInteractiveScript.vbs
and change the line for executing like this
from: %SYSTEMROOT%\SYSTEM32\wscript.EXE
to: %SYSTEMROOT%\SYSTEM32\mshta.EXE

1. Download MDT 2010 and install it on any given computer.
Copy the file 'ServiceUI.exe' into the folder for your package.
2. Create a vbs script in that folder called 'InteractiveLaunch.vbs'
3. Add script below into 'InteractiveLaunch.vbs'
Option Explicit
Dim ReturnCode
Dim objShell : Set objShell = CreateObject("WScript.Shell")
Dim GetScriptPath : GetScriptPath = Left(WScript.ScriptFullName, InstrRev(WScript.ScriptFullName, "\", -1, 1) - 1)
'**********
'* MAIN *
'**********
ReturnCode = objShell.Run ("cmd /c " & GetScriptPath & "\ServiceUI.exe -process:TsProgressUI.exe %SYSTEMROOT%\SYSTEM32\wscript.EXE " & GetScriptPath & "\yourInteractiveScript.vbs", 1, True)
Wscript.Quit(ReturnCode)
'**************
'* END MAIN *
'**************

3. Put whatever you need into yourInteractiveScript.vbs and save it into the same folder as 'ServiceUI.exe' and 'InteractiveLaunch.vbs'
4. Create a 'Run Command Line' Task. And choose the package where you have the 'ServiceUI.exe' file
5. Run the Command line 'Wscript.exe InteractiveLaunch.vbs'


That is in 5 simple steps creating an interactive task within a TS.

Start of SCCM blog

Well well well we'll see how this goes.

I've got a G+ page with same name, and so far only one post, but I believe it's a post that are useful for many.

I'm starting up this blog, to share some of the solutions I find (in collaboration with colleagues) to some SCCM issues. Or just some nice to know features that are not too obvious.

Let's hope it becomes useful for at least somebody.