However, when an actual Deployment is run via Internet Explorer, a CAB file is downloaded, extracted and installed automatically to:

C:\Windows\System32\Citect

If a user is not a member of the Administrator group, then this automatic installation will fail, and the WebClient deployment will fail to open.

The web address of the WebClient Server may also need to be added as a Trusted Site, either manually, via a Batch file that modifies the registry, or via a GPO or your Domain Group Policies.
To run WebClient as a restricted user, WebClient either needs to be run once on that machine by a user with administrator privileges, or the CAB file can manually be extracted and the installer that it contains (setup.exe) can be run by a user with administrator privileges.

This process can also be automated, and installed on a machine in a ‘Silent’ mode.

To run the process in silent mode, call Setup.exe with the following Command-Line switches:

“Setup.exe /S /v/qn”

This will execute the Setup.exe function silently, however the user that runs this exe still needs Administrator privileges, however, the RUNAS command could be used to bypass this.

runas /user:administrator “c:\<directoy>\setup.exe /S /v/qn“

You may even be able to use AT commands to schedule a task on other users machines. Alternatively the JT commands may provide further flexibility (available from <ftp://ftp.microsoft/com/reskit/win2000 JT.exe>)

Or you should be able to get your IT department to use their standard procedures for ‘pushing’ updates and files to all machines. This could include Group Policies, login scripts or batch files.