I'm wondering how much your "caching" is really helping vs complicating the environment.
When I deployed my login script at the travel agency, we had several store locations connected with 128K Frame Relay connections. The old login script took over 90 seconds to run, even with Kix installed locally. I removed the local copy of Kix, updated to the new login script, and ran everything from Netlogon and got the script execution down to 40 seconds. After enabling local caching of just the LOGIN.INI file, the time reduced to 12 seconds cached and 15 seconds uncached. (reading the INI file contents over the WAN resulted in very poor performance, so we only cached that file.) Times for login script execution on the LAN were just under 6 seconds. This points to a time to load Kix32 and the Kixtart.Kix script taking just 6 seconds over the WAN link.
Just something to consider, as it's unlikely that you have 56K or dialup links nowadays.
Glenn
_________________________
Actually I
am a Rocket Scientist!
