S
syshelp
I am attempting to set the default printer on a XP SP2 workstation
using the following command. The queue in question was added
previously to this same workstation using printui /ga command:
rundll32 printui.dll PrintUIEntry /y /n"\\ServerName\QueueName"
This command runs okay and sets the default queue correctly if run as a
logged in user (this test user also has admin rights on this
workstation).
However, if you try to run this same command on the workstation this
time using a domain admin account (either locally or targeting the
workstation remotely), the command fails with the following error:
"Operation could not be completed. Either the printer name was typed
incorrectly, or the specified printer has lost its connection to the
server"
Why ? The command syntax is obviously correct as it works fine for the
logged in user. The domain admin should have sufficient rights over
the workstation for this command to work in setting the correct per
workstation default printer.
We have hundreds of XP SP2 workstations in a public lab environment
locked down via Group Policy using 2003 DC's and AD (with a Windows
2000 print server). Each workstation has had a printui.dll /ga print
queue already added to it remotely via a script running with domain
admin rights.
We now wish to add a second queue via the same /ga method, and also set
the correct default printer on the workstation. Adding the second
queue via /ga works fine, but setting the correct default printer queue
on the workstation does not. The public lab user that logs in to the
workstation is a very limited account with heavy GP restrictions in
place, therefore trying to set default printer via the lab user's login
script won't work.
Any suggestions please ? Any alternative methods of setting default
printer that would suit this restricted environment ?
Thanks.
using the following command. The queue in question was added
previously to this same workstation using printui /ga command:
rundll32 printui.dll PrintUIEntry /y /n"\\ServerName\QueueName"
This command runs okay and sets the default queue correctly if run as a
logged in user (this test user also has admin rights on this
workstation).
However, if you try to run this same command on the workstation this
time using a domain admin account (either locally or targeting the
workstation remotely), the command fails with the following error:
"Operation could not be completed. Either the printer name was typed
incorrectly, or the specified printer has lost its connection to the
server"
Why ? The command syntax is obviously correct as it works fine for the
logged in user. The domain admin should have sufficient rights over
the workstation for this command to work in setting the correct per
workstation default printer.
We have hundreds of XP SP2 workstations in a public lab environment
locked down via Group Policy using 2003 DC's and AD (with a Windows
2000 print server). Each workstation has had a printui.dll /ga print
queue already added to it remotely via a script running with domain
admin rights.
We now wish to add a second queue via the same /ga method, and also set
the correct default printer on the workstation. Adding the second
queue via /ga works fine, but setting the correct default printer queue
on the workstation does not. The public lab user that logs in to the
workstation is a very limited account with heavy GP restrictions in
place, therefore trying to set default printer via the lab user's login
script won't work.
Any suggestions please ? Any alternative methods of setting default
printer that would suit this restricted environment ?
Thanks.