KiXtart: File Not Copied
In a KiX script, sometimes you may copy files from the server onto the client. In that case, you must be sure that the user has full access rights to the location where the file is being copied to, as well as read rights to the area where the file is coming from.
I saw this in one place where the login.bat file copied the kix32.exe file into the root of the C: drive before running the login.kix script on the client machine. Users without administrative rights could not run the script effectively, although they could run it once an admin user had logged in on their machines so that the kix32.exe file was copied to the machine.
Possible workarounds include:
- Copying to the user’s home directory (C:\Documents and Settings\<username>\ or
%HOMEDRIVE%%HOMEPATH%) - Placing the file in a shared drive that the user has rights to access
- Giving the user administrative rights on his / her assigned machine
The choice you pick depends on your organization's policy and the purpose of copying the file. Windows environment variables courtesy of Kenneth Hunt.


