Yes Richard's concept is good, except that it also leaves room for the ever present file locking issue. If done during logon, could present an issue. If the machine could not get exclusive lock on the file, and you are set to have your systems wait for logon to process before loading the desktop. Example of 2,000 systems trying to write to that file... If it took 3 seconds or 30 minutes to get exclusive lock for writing, that client could not complete the logon until it wrote to the file.

Granted one would assume that on a fast network all 2,000 could complete an INI update within a couple minutes or so, but still a potential issue.

This is good stuff, but looking more and more like a KiX Golf game only geared towards best approach instead of least amount of code.

Where's LONKERO and his ideas? I'd think he would love to jump on this one as well. [Wink]