Hi All,
We have recently configured a new terminal server for our organisation. Normal domain users logon to this new server and need to connect to shared network printers located on other print server. When the users right click on the printer and select 'connect' they are presented with the following error message.
"You do not have sufficient access on your computer to connect to the selected printer."
I have investigated why this is occuring and have found that a few group policy settings need to be set to enable to the connection of the network printers. The group policy settings which I have set are as follows:
1. Devices: Prevent users from installing printer drivers = Disabled
2. Load and unload device drivers = Enabled (for authenticated users)
After setting these computer configuration group policy settings and applying it to the terminal server I am still receiving the error message.
Am I missing something here? Does anyone have suggestions as to why I am still receiving the error.
Many Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for the respose.
Michko, you are correct these settings need to be setup as well.
I actually found out that if you are running a terminal server 64bit OS and are trying to connect to the network printer from a domain user, you will get this same error if the print server does not have 64bit drivers. You will get a different error on the TS if logged in under admin ... something like cannot install printer driver.
Thanks for your help.
Glad I could help. And glad you got it.
If you solved your problem yourself, you can click on the Delete Question link that is in the post of your question. You will be able to enter the reason why you wish the question. If your question contains information that may be useful to others, you can request it be made into a zero point Previously Answered Question. Your points will be returned to you. See this link for more info.
http://www.experts-exchang
I answered my question myself. What do I do?
Thanks. You accepted while I was posting the above. I do appreciate it and was glad to help. However, if you want to apply for a refund (because technically you did solve the problem yourself), I won't object. Of course, I won't turn down the credit either. ;) Important thing is that your issue is resolved.
michko
Business Accounts
Answer for Membership
by: michkoPosted on 2008-02-12 at 05:40:25ID: 20874563
In both Computer Configuration and User Configuration go to Administrative Templates -> Windows Components -> Windows Installer and change the "Always install with elevated prifileges" to enabled.
You may want to force the change using gpupdate:
http://support.microsoft.c
I think you're on the right track with disabling the "Prevent users from installing printer drivers". This article from MS states that should resolve the problem. It also states you may need to reboot the server, or force the policy change.
http://support.microsoft.c