The Deployment Bunny

OS Deployment, Virtualization, Microsoft based Infrastructure…

  • Archives

  • Meta

Quick and Dirty – Testing customsettings.ini variables in MDT

Posted by Mikael Nystrom on April 27, 2011

One of the fastest “Quick n Dirty” you can do to test the behavior of customsetting.ini when you are on the deployment server is to create a batch file and store that in the scripts folder that will run the gather process and display the results. To be honest, make a good test bed is my number one priority, time is the enemy and testing just eats up the time. Here is how-to:

Download and install Trace 32 (you should have this already, but in case you don’t have, get it)

Create a batch file called testini.cmd that looks like this

del C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT /q
cscript ZTIGather.wsf /inifile:..\Control\CustomSettings.ini
“C:\Program Files (x86)\ConfigMgr 2007 Toolkit V2\Trace32.exe” c:\minint\smsosd\osdlogs\bdd.log

Now, just run it from an elevated command prompt in the scripts folder of your deployment root and you are done. If you don’t have trace 32 in hand, use notepad.exe instead, that is second “best”

If you need more logging and use notepad instead (I don’t recommend that)  just add /debug:true on ztigather.wsf part and replace trace32.exe with notepad, like this

del C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT /q
cscript ZTIGather.wsf /Debug:True /inifile:..\Control\CustomSettings.ini
notepad.exe c:\minint\smsosd\osdlogs\bdd.log

/mike

6 Responses to “Quick and Dirty – Testing customsettings.ini variables in MDT”

  1. […] https://deploymentbunny.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-in-mdt/ […]

  2. […] The best thing is that you can run this script without deploying any OS, so this way you can test the rules before you even begin deploying, and you can also test thousands of deployments in a couple of hours. (Here is a blog post on that https://deploymentbunny.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-in-mdt) […]

  3. […] The best thing is that you can run this script without deploying any OS, so this way you can test the rules before you even begin deploying, and you can also test thousands of deployments in a couple of hours. (Here is a blog post on that https://deploymentbunny.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-in-mdt) […]

  4. […] the deployment share.  There are a couple of ways that you can do this, one way is shown here https://deploymentbunny.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-in-mdt/, in my case I do it this […]

  5. […] Instructions on how to test customsettings.ini is here:https://anothermike2.wordpress.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-i… […]

  6. […] Instructions on how to test customsettings.ini is here:https://anothermike2.wordpress.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-i… […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: