Deployment

Quick and Dirty – Testing customsettings.ini variables in MDT

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

Categories: Deployment

Tagged as:

7 replies »

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 )

Google photo

You are commenting using your Google 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 )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.