Originally Posted By: eappelstein
The current work around is people in that office are running their logon script from a different domain controller in a different office.
Kix32.exe should not be running in the RAM of the server except when logging into the server itself. Users should not be logging into a server, merely loading the file from the netlogon or GPO share and running it within the RAM of their workstations.

Something smells fishy.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.