|
Mark,
Thanks for your enlightenment on the usage of various types of scripting languages. Although I agree with you in concept when referring to batch vs. KIX vs. VBScript, there are other factors to consider.
1. Management
2. Politics
3. Non-conformity of systems
4. WAN deployment
...
Although the first 2 are basically, the same, they have the power of two!.. 'Nuff said.
If I could do everything in KIX (via logon), I would at this point. There are many benefits to this:
1. Easier to use/understand than batch or VBScript
2. No need to deploy Kix32.exe to every workstation. It runs fine via netlogon.
3. Keeping things internal to the kixtart script minimizes troubleshooting headaches/platform differences.
4. Management has already approved the use of KIXtart for logon scripts (not so for VBScript.)
5. VBScript is updated by Microsoft and comes with SOME operating systems, but not all, which means that different OSes have different versions, and all need updating... especially whenever Microsoft decides to release a new security patch.
.....
After all that I said ^^^^^^ ... I would prefer to manage PCs without logon script. Whenever my organization has enough money to move everyone to Windows XP (by 2010, probably), then perhaps logon scripts will not be as necessary. Until that time, I try to make the script with the mostest -- using as little external code as possible. :-)
"To the IT person with the hammer, the monitor is the first thing to go, the brain the second"
Brian
| 
