I am using MDT to populate some dynamic Task Sequence Variables, After the gather stage I take my MDT properties and use them to set TS Variables which are used to help simplify tasks at a later stage in the TS. The variables all seem to working during the Windows PE part of my OSD TS, however this does not appear to be the case in the full client OS.
For example I install Windows Language Packs dynamically based upon the TSVariable "%TargetComputerLanguage%" - this is simply a Run Command Line task;
DISM.exe /image:%OSDTargetSystemDrive%\ /ScratchDir:%OSDTargetSystemDrive%\windows\TEMP /Add-Package /PackagePath:%TargetComputerLanguage%\lp.cab
This task works without issue.
Later on, following reboots etc I try to use the same variable again in another Run Command Line task which should install the required IE10 language pack to match the Windows LP installed earlier;
C:\Windows\System32\wusa.exe X86\IE10-Windows6.1-LanguagePack-x86-%TargetComputerLanguage%.msu /quiet /norestart
This task fails every time. I know the TS variable exists as this task has a condition which will not action unless the variable exists.
Looking at the smsts log I can see that the command executed is not being populated with the value of %TargetComputerLanguage% - just the string that represents the variable itself i.e. "%TargetComputerLanguage%". Of course this fails.
I understand that the variables are not directly accessible following reboot into the full Operating System Environment, but I am calling this variable from the TS, so I understood this to be OK. Any ideas as to why this is failing - am I trying to do something here that will never work.
Thanks for taking a look and any thoughts/advice.
Chris
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk