I am aware of all that. It's more not being allowed to upgrade, than not knowing how to.

I appologize for not mentioning the version of Kixtart being used before. As far as the rest of "Section F". For security reasons, I cannot disclose any further details on my network environment.

Aside from waiting on permission to upgrade, I have limitations on upgrading. (SMS and other simular options are beyond my control)

Pretty much the only option I have for upgrading is via the login scripts themselves.

This is a very large network (over 5000 users), with a few dozen different login scripts depending on where users are assigned to. (trying to consolidate this mess down into one script)

A batch file cannot determine the version of Kixtart alread installed on the system. A Kixtart script can determine which version is running, however it cannot copy a new version over the top of itself, because kix32.exe will be in use while the script is running. (actually it can do this, but only if the upgrade code is at the very end of a script, and only one script is being run, however several scripts are currently being run at once)

Version determination is very important due to the volume of users on the network. Having a batch script blindly replace existing Kixtart files every time a user logs on, would result in unacceptable amounts of network traffic during peak logon times (shift changes), and could potentially cause many other problems.

I am considering having a text file copied along with the Kixtart files, and having the batch script copy the newer Kixtart files only if the text file is not present. This is the only feasable option I have been able to come up with thus far. Only obstacle in that is sorting through the mess of login scripts left by those who came before me.

So I'm stuck with 3.63 until authorization is given to upgrade, and must make due with features availible within it until then.