+1 I don't believe you're going to see the value actually listed in the log files. Michael Niehaus provided a really easy script for doing this awhile back: http://blogs.technet.com/b/mniehaus/archive/2010/04/26/dumping-task-sequence-variables.aspx
-Phil From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, March 11, 2014 8:56 AM To: '[email protected]' Subject: RE: [MDT-OSD] Device variables You could always drop in a script that will dump all of the TS variables to a text file. Then you can drop that step into your TS at key points (like immediately prior to steps that leverage those variables). That is what I do. This way I can check the output of the script and see exactly what the value of the variables are at any point in the TS. Mike From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of HELMS, DAVID C Sent: Tuesday, March 11, 2014 8:37 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Device variables I am testing a TS in which depending on variables that are set will perform different action's, such as load a particular OS, add it to the appropriate domain, etc.. . I can see in the smsts.log where it is evaluating the action and then it performs the step if the condition is True or passes it if it is False. What I haven't been able to find is where in the log does it show what the value of the variable I'm setting. Anyone know if this information would be in plain text? [cid:[email protected]] ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments.
<<inline: image001.png>>
