User account control preventing loginscript printer installation
We have a working loginscript that among other things takes these actions: 1. If printer objecst referring to old print server are present, delete them 2. If printer objects referring to new print server are not present, add them This loginscript runs via a GPO and is working for all Windows XP computers This loginscript runs via a GPO for Windows 7 computers as well, but during the printer installation phase (If it was determined that a printer object referring to the new print server was missing), the loginscript will not execute. The end user receives no onscreen prompts that the loginscript is running or has completed running. When running the loginscript directly (by executing the underlying .vbs file from the command line of Windows 7 computer) I can see that the loginscript is unable to add the new printers due to "permission denied". I assume this is related to user account control settings which are at the Windows 7 default value for a standard non-admin user account (Notify for non-Windows executables). With Windows XP, loginscripts from a GPO execute with elevated privileges. How do I modify my loginscript, UAC or other setting to allow my loginscript to handle the UAC properly?
March 31st, 2010 9:01pm

Standard users should be able to install new printers without requiring elevation. Two things: are the drivers associated with the printers WHQL-signed? They have to be for a standard user to be able to use them, otherwise Windows detects this as an attempt to install untrusted software, which needs admin rights Can you distribute the printers using GPO preferences rather than a logon script?
Free Windows Admin Tool Kit Click here and download it now
November 17th, 2010 7:04pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics