Debugging SMS 2003 OSD Processes
One of the tricks i’ve learned over the years is a way to debug your rules and settings for your ZTI OSD process. If you make a small change, sometimes you just want to see if that change or rule is processed correctly. Which means you don’t want to have actually do a full ZTI every time you want to test a change. If you just want to test a change to your customsettings.ini you can create a quick script and copy a few files to a location and test. The end result will be the logs files you can review to verify the changes.
If you create a folder called “ZTI_Debug”, and then copy your customsettings.ini, ZTIGather.wsf, ZTIGather.xml, and ZTIUtility.vbs into that folder. Then you just need to create a batch file to run the process. The batch file should contain the following lines:
:Start:
if exist c:\minint\nul rd c:\minint /s /q
cscript.exe ZTIGather.wsf /debug:true
:End:
Now, whenever you run that batch file on the target machine or VM, it will process your ZTI rules/queries and output the result to the logs files. On the client under OSDLOGS, you will see the BDD.log, variables.dat, and ZTIGather.log. You can review those logs to verify that your cs.ini is processing successfully, or that your SQL queries are running properly. I often use this process to verify that my packages are being correctly identified, that desktops are getting desktop packages, and laptops are getting the laptop specific packages, etc or test any other changes to my cs.ini that doesn’t require a full refresh to test.
Just a great way to quickly run the rules and process your cs.ini rules without actually doing a refresh.
Hope this helps…