orlandoayerszi

In a KiX playscript, sometimes you may copy files from the waiter onto the client. Therein instance, you must
be sure that the user holds full entree rights to the location where the file is being copied to, too as read rights to the country where the file is coming from.

I saw this in one spot where the login.bat
file copied the kix32.exe
file into the root of the C: thrust before running the login.kix
book on the client machine. Users without administrative rights could not run the playscript efficaciously, although they could
run it once an admin user holded log-in on their machines so that the kix32.exe
file was copied to the machine.

Possible workarounds include:

• Copying to the user 's place directory ( C: \Documents and Settings\ & lt; username & gt; \ or %HOMEDRIVE%%HOMEPATH%
  


• Setting the file in a shared thrust that the user holds rights to access


• Giving the user administrative rights on his / her designated machine

The pick you pick depends on your organisation policy and the intention of copying the file. Windows environment variables courtesy of Kenneth Hunt

Related posts:
Business Automobile Policy

Definition of a Social Insurance Program

Praying with Hypoglycaemia

The Offering

the modern Muse