In our domain, we have just one copy of Kix for logon processing - in the NETLOGON share. It services the login script for workstations, servers, and the RDP farm. The Kix login script itself is there as well. Same deal at our clients - we never place Kix32 or scripts on local systems for login processing.
We do, however, install Kix32 on every server for admin scripting unrelated to logon. We NEVER place it into the Windows folder or any subfolder. If it isn't part of Windows, it doesn't belong in that directory structure. We create a folder under Program Files (32-bit on x64 platforms) called "ITCG" - our company initials - and place all config files there.. Kix and any scripts or other tools go into a BIN subfolder, and that folder is added to the system PATH. Thus, we can run any system tools, BAT or KIX files, utilities, etc - directly from the command line or the RUN option of the start menu.
Glenn
_________________________
Actually I
am a Rocket Scientist!
