W
whiteone69
Guest
In XP we used a domain account called “clone” to set up network printers connected from a print server. Once the network printers were added to this user we would log in as another user and copy clone to default user. This would give all users the network printers we wanted them to have when they logged in.
In windows 7 this is not an option. So we have been using another way of making changes to the default user from here. Basically we set up a local admin called “USER” and with the printers and assign a default. Then we restart the computer and log in as administrator and make a copy of user and rename it to default.
Now when users log in they get all the printers expected but get an error. They are grayed out and have an error. When you click on them a message box with the title of “Printers” comes up. The message is “Operation could not be completed (error 0x00000005). Access is denied.” You can remove the printer and then the user can add them back in but most of our users are not knowledgeable enough to do this. If we make any of the users in question a local admin they get the printers like normal but as soon as this is removed the access denied comes back up. As everyone knows we don’t want all of our normal users being local administrators.
I found one KB 2023766 with this error but it is related to using sysprep. The fix does work but we can’t deploy machines where we would have to run a registry edit after users log in. I also tried giving everyone full permissions to the registry keys mentioned in the article with no luck. Does anyone know how to fix this error globally for all user?
We went this route because we want the printers to be there for the users when they log in and not have to wait on scripts or anything else. We looked at using local group policy or rundll32 printui.dll commands but these methods take a few seconds after the user logs in for the printers to show up on the system. This leaves chance that a script could error out even with a wait timer programmed in it to run the set as default command and as we said we don’t want anything noticeable to the end user. Our network admins also do not want to use GPO as we would have to have a GPO for each computer. We also thought about setting them up as local printers by IP but that defeats the purpose of having a print server. I know sysprep is an option as well to set these up but it is not a very efficient way to set up network printers globally for all users on a windows 7 system.
Continue reading...
In windows 7 this is not an option. So we have been using another way of making changes to the default user from here. Basically we set up a local admin called “USER” and with the printers and assign a default. Then we restart the computer and log in as administrator and make a copy of user and rename it to default.
Now when users log in they get all the printers expected but get an error. They are grayed out and have an error. When you click on them a message box with the title of “Printers” comes up. The message is “Operation could not be completed (error 0x00000005). Access is denied.” You can remove the printer and then the user can add them back in but most of our users are not knowledgeable enough to do this. If we make any of the users in question a local admin they get the printers like normal but as soon as this is removed the access denied comes back up. As everyone knows we don’t want all of our normal users being local administrators.
I found one KB 2023766 with this error but it is related to using sysprep. The fix does work but we can’t deploy machines where we would have to run a registry edit after users log in. I also tried giving everyone full permissions to the registry keys mentioned in the article with no luck. Does anyone know how to fix this error globally for all user?
We went this route because we want the printers to be there for the users when they log in and not have to wait on scripts or anything else. We looked at using local group policy or rundll32 printui.dll commands but these methods take a few seconds after the user logs in for the printers to show up on the system. This leaves chance that a script could error out even with a wait timer programmed in it to run the set as default command and as we said we don’t want anything noticeable to the end user. Our network admins also do not want to use GPO as we would have to have a GPO for each computer. We also thought about setting them up as local printers by IP but that defeats the purpose of having a print server. I know sysprep is an option as well to set these up but it is not a very efficient way to set up network printers globally for all users on a windows 7 system.
Continue reading...
