I leave KiX on the /netlogon share and have the clients call it from there, EXCEPT for our VPN users (checked by looking for VPN software) which I roll KiX out to the machine locally, as well as having a hook checking file versions so if I update KiX at the server, the users get an update automatically. Having KiX locally it runs about 40% faster in my testing, but my network is so spread out I haven't gone "full local" yet, but yes it does run faster this way
I am in the process of consolidating all our scripts into one master script - we started out with over 25 scripts as each location had once scripts for remote users and another for local. I have moved probably 12 of the scripts into the new "master" one. The master script has calls to other scripts (usually inventory type), and it sure is nice not having to touch 25 scripts to run a simple audit. It sounds like you're in a very similar situation as far as mappings dependant on group membership, this is why my script is so big. I don't believe there is a significant performance issue if the script is wrote cleanly. KiXtart v4.1x only looks up group membership once, so the first INGROUP check results are cached in RAM, so subsequent INGROUP checks in the script doesn't create any additional delays or LAN/WAN traffic. My "dirty" big KiX script is 17Kb, and if the script was truly big enough to be slow loading, copying the KiX file locally and calling it from batch would alleviate any hit from the file size. Only the periodic updates (if any) would be slow. If your NT group memberships aren't set up cleanly (ours aren't perfect), you will get unpredictable results. Feel free to contact me off-list, as like I said I am in the midst of consolidating our many varied scripts. Dave Lum - [EMAIL PROTECTED] Sr. Network Specialist - Textron Financial 503-675-5510 PS Julian (if you read this far), how is the curve from going from KiX to VBS? -----Original Message----- From: Weatherly, Rob [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 06:48 AM To: NT 2000 Discussions Subject: RE: KiXtart I really appreciate all your help And the messagebox line worked great Now since I am new to this I will ask some more questions I have a 500+ user environment About 400 of them in my corp office When it comes to installing/rolling out the KiXtart files; should I leave them on the server and run them from there? I was originally thinking of copying all of the needed files to the desktops using a batch file, then calling the .kix script from within the batch file. Installing the RPC service on the win2k DC's and then for the user's profiles entering the script.kix in the logon script path in AD account properties. The other question is I would like to have as few scripts in my netlogon as possible. Is it feasible to have 1-5 scripts for all of my corp users. Keeping in mind that there would me many dept. and each one would need specific drive and printer mappings. I am sure it is possible, but is it efficient to have all of the users running such a large script. Are there any performance issues? -------------------------------- Rob Weatherly -------------------------------- ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
