What's the word so far ?
Think that's bad. You ain't seen the ugly yet!
Are any of your clients running Win9x or Windows NT ?
You should see what's involved if you have to map drives based on group membership with 9x and NT4 !
1) WSH/VBScript requires the use of ADSI (with Windows NT service provider support) to be able to determine group membership in a standard Windows NT domain (non active directory domain I should say)... you think the above commands were interesting, wait till you see ADSI...
2) Windows 2000 ships standard with ADSI, but for Windows NT and especially for Windows 9x, you have to install the "ADSI Runtimes" (it's free) on ALL your client workstations for WSH/VBScript ingroup to work (actually, there is no ingroup() function in WSH - you have to write it yourself)...
The really nice thing about KiXtart is that all your logon functionality is built right into the language. Important things like USE and INGROUP() and all the @MACROS that are basic requirements for logon processing... WSH/VBScript is a general purpose scripting language and as such, requires extra teasing and poking and support modules (eg, ADSI)
So you may be asking why WSH needs ADSI and KiXtart doesn't - well KiXtart does have an ADSI for Win9x - it's called KXRPC - the nice thing about KXRPC is that it doesn't need to be installed on every workstation. KIX32.EXE and KIXRPC use Remote Procedure Calls (RPC's) to talk to each other about Domain issues ... no workstation component need apply - sweet eh ?
Anyway - I've rambled on long enough - if you really want to convince yourself (and your boss) that it's easier, cheaper and faster to stick with KiXtart - try this for an exercise ... write the equilvalent of this simple KiXtart script in WSH/VBScript and then get it to work on Win9X ...
IF INGROUP("DOMAIN USERS")
USE E: "\\SERVER\PUBLIC"
Then compare the differences and add up the costs - I think the bottom line is that you'll stick with KiXtart.
[This message has been edited by Shawn (edited 07 June 2001).]