Michael Murgolo has a new post over on The Deployment Guys Blog.
I recently had the need to pop up a message box duing an LTI task sequence. I was creating a stand-alone wizard to allow a manually-initiated launch of a task sequence that would install the Service Pack 1 update on Windows Server 2008 R2. As part of this task sequence, if a certain software package was of a certain version or earlier we had to reinstall this software after the service pack installation. If this installation was not going to happen because a newer version was already installed, the customer wanted to notify the technician at the end of the process. Since this was to be a simple notification, a message box was sufficient. I could have simply created a VBScript that had a static MsgBox function call for this purpose.
However, I decided that I would make it more reusable than that. Instead I created an MDT script that would take the input arguments for the the MsgBox function as command line parameters. That way the script could be reused any time a message box was needed. The script can also optionally use the MsgBox return value as the script exit code and/or use it as the value for a task sequence variable.
This post was contributed by Michael Murgolo, a Senior Consultant with Microsoft Services – U.S. East Region