MCA,
Please see my responses..
quote:
An alternative can be that you put those informative to the HKLM hive.
If you have a "locked down" user, would this still be available?
quote:
has to deal with the possibility that the environment variable %windir% doesn't exist.
Where in the world is this coming from? In time that we have been doing Computer Support (going on 8+ years now). This has never been true.. The only exception would be if you as the Technician were tweaking with the PATH. Why? Almost all programs out there need to know where WINDOWS is located. OK.. 16-Bit Apps? Sure, they need to know where to find WOWEXEC and NTVDM too.. Or, even %WINDIR%\command..
quote:
c:\scripts\kix32.exe
..other files..
In testing with various users on our domain, we decided to go with a folder outside of %WINDIR% as we had trouble copying a file there.
To Lonkero..
quote:
it's slow to run logon-from network but with even slow 256kb connection it's already quick enough to not need a dist...
We are starting to investigate this too. We are seeing some pretty dramatic results. You are 100% correct, you don't have to create distro package either.
Back to MCA..
quote:
When you have problem with the deletion of old file it will be good to include those
information also in f.e. control file. A control file which can be located on
the server too.
So.. Then, why not include this in the login log for the client.. You could check a database, currently we use a rather large text file (yes, a performance hit). But an Access or SQL Database, you could not only write the client login info, but KIX too. But, then again, if you keep the Executable and script on the server, is this needed? Sure, this is grand exercise for people that have not decided or cannot make this type of transistion.
Thanks,
Kent
