I’m upgrading my MDT-SCCM integrated build environment to MDT 2010 from MDT 2008 and SCCM SP2 from SP1.  I’m noticing a few quirks in my builds in my test environment since doing the upgrade.  Here’s the area where there seems to be some difference:

During my builds I call an HTA to gather user input from the technician if SQL data to automate the deployment is not available.  Within this HTA I call a couple external items from with my MDT Toolkit package like this:

wshShell.Run "%DEPLOYROOT%\Scripts\MoveTSWindow.exe",2,True

With MDT 2008 integration this has always worked fine.  It does not work with 2010.  It seems like the %DEPLOYROOT% and %SCRIPTROOT% variables are more restricted with 2010.  Has anyone else experienced this?  I’m trying to avoid using hardcoded paths to call the external items as this may be different in different deployment scenarios.  I’ve tried changing the calls to:

wshShell.Run oEnviroment.Item("DEPLOYROOT") & "\Scripts\MoveTSWindow.exe",2,True

That doesn’t work either.  Any ideas what changed here?  Seems to be something within the MDT scripts and possibly the stuff happening during the Gather action.

Thanks,

Eric Giroux

Unum Group