BDD 2007 - Time saving Tips - How To quickly test rules
When creating rules within BDD I find that it can take alot of time to tune them to provide the results that I am looking for. Each time I make a change I need to restart the entire build process to see if rules have the desired effect.
It is however possible to run BDD rule processing manually on a computer without needing to completely rebuild a machine. The following process is invaluable in configuring and troubleshooting rule processing within BDD.
The rules that are applied to a particular computer are gathered together using a script called “ZTIGather.vbs” in conjunction with “ZTIGather.xml”. These scripts can be run directly without the needing to launch the entire BDD process.
The steps below detail this process. These can be run when the computer is running the host operating system or WinPE.
- Copy ZTIGather.wsf, ZTIGather.xml, ZTIUtility.vbs, CustomSettings.ini, and any user exit scripts to your workstation
- Remove C:\MININT directory if it already exists (to start clean)
- Execute "cscript.exe ZTIGather.wsf /debug:true"
- Inspect the log C:\MININT\SMSOSD\OSDLOGS\ZTIGather.log
- Modify CustomSettings.ini, user exit script(s) or database
- Go to step #2.
Note: The process does not make any changes to the client computer.
I have found that creating a batch file with the following commands helps speed up this process.
rmdir c:\minint /s /q
cscript ZTIGather.wsf /debug:true
Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use .
Comments
Anonymous
January 01, 2003
When developing a build it is often useful to have it in debug mode. Debug mode is when log content isAnonymous
January 01, 2003
I am very happy with the progress of the deployment guys blog so far. Hopefully you all agree that we