RE: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
What's weirder is if you search for an issue, find a post that turns out to be your own, and then also find you solved the problem years ago but have subsequently forgotten the solution: http://www.activedir.org/ListArchives/tabid/55/view/topic/postid/22657/Default.aspx From: Andrew S. Baker [mailto:asbz...@gmail.com] Sent: Thursday, 6 September 2012 1:26 AM To: NT System Admin Issues Subject: Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins >> Ha! I'll admit that I've done some searching on the web for issues I've run >> into... and I found somebody who has simular issues... only to discover that >> it's my own post! Sm:)e. Been there, done that. :) ASB http://XeeMe.com/AndrewBaker Harnessing the Advantages of Technology for the SMB market... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
That is bad. Worse is when you find a post about the problem you are looking for a solution for only to have the final post being "Figured it out" and no further info supplied. James. From: Andrew S. Baker [mailto:asbz...@gmail.com] Sent: Thursday, 6 September 2012 1:26 AM To: NT System Admin Issues Subject: Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins >> Ha! I'll admit that I've done some searching on the web for issues I've run into... and I found somebody who has simular issues... only to discover that it's my own post! Sm:)e. Been there, done that. :) ASB http://XeeMe.com/AndrewBaker Harnessing the Advantages of Technology for the SMB market. On Wed, Sep 5, 2012 at 10:45 AM, Matthew W. Ross wrote: > Drivers would be available via the ADMIN$ share of the machine, I would > expect. Okay, I'll take that answer... but then why wouldn't the printer be installed once the admin logged in? Why do the printers disappear afterwards? And why isn't there any good data about the failure in the event viewer? (Why, Microsoft? Why?) > Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ Ha! I'll admit that I've done some searching on the web for issues I've run into... and I found somebody who has simular issues... only to discover that it's my own post! Sm:)e. --Matt Ross Ephrata School District - Original Message - From: Andrew S. Baker [mailto:asbz...@gmail.com] To: NT System Admin Issues [mailto:ntsysadmin@lyris.sunbelt-software.com] Sent: Wed, 05 Sep 2012 05:02:36 -0800 Subject: Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins > Drivers would be available via the ADMIN$ share of the machine, I would > expect. > > Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ > > > * * > > *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of > Technology for the SMB market. > > * > > > > On Wed, Sep 5, 2012 at 3:52 AM, Matthew W. Ross > wrote: > > > I finally figured it out. I figured that I'd share: > > > > I was sorting my labs AD Computers into OUs. I then assigned a blank group > > policy for the printers on that OU. Using the Printer Manager, I installed > > the printers and drivers as a TCP/IP printer on my print server. I then > > used the "Deploy Printer" option to configure the until now blank group > > policy. > > > > This was all working perfectly. I had not had any problems doing it this > > way. This installs the printers on the client machines as TCP/IP printers, > > so none of them are dependent on a print server. > > > > My mistake was that I forgot a crucial step in this kind of deployment > > process: I still had to share the printer from the print server. Doing > this > > allowed the computers to install the necessary drivers from the print > > server. > > > > what I can't figure out is how the administrator accounts could see and > > use use the printers, but the non-admins could not. Is there a hidden > > administrative share that holds the drivers? Was Windows able to install > > local drivers each time? > > > > Anyways, as usual, something small and somewhat obvious was preventing it > > from working. > > > > > > --Matt Ross > > Ephrata School District > > > > > > - Original Message - > > From: Matthew W. Ross > > [mailto:mr...@ephrataschools.org] > > To: NT System Admin Issues > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > Sent: Tue, 04 Sep 2012 > > 09:24:52 -0800 > > Subject: RE: Deploying Printers in Group Policy not working > > for non-admins > > > > > > > As student's are not admins, they don't have the option to install the > > > printers. Especially as I'm trying to install them via IP. > > > > > > I'm about to install the printers via script, as they need printers > > working, > > > with or without group policy. > > > > > > > > > --Matt Ross > > > Ephrata School District > > > > > > > > > - Original Message - > > > From: Kelsey, John > > > [mailto:jckel...@drmc.org] > > > To: NT System Admin Issues > > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > > Sent: Tue, 04 Sep 2012 > > > 06:11:38 -0800 > > > Subject: RE: Deploying Printers in Group Policy not working > > > for non-admins > > > > > > > > > > What happens if the student tries to install the printer manually? > > D
Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
*>> Ha! I'll admit that I've done some searching on the web for issues I've run into... and I found somebody who has simular issues... only to discover that it's my own post! Sm:)e. * Been there, done that. :) * * *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of Technology for the SMB market… * On Wed, Sep 5, 2012 at 10:45 AM, Matthew W. Ross wrote: > > Drivers would be available via the ADMIN$ share of the machine, I would > > expect. > > Okay, I'll take that answer... but then why wouldn't the printer be > installed once the admin logged in? Why do the printers disappear > afterwards? And why isn't there any good data about the failure in the > event viewer? (Why, Microsoft? Why?) > > > Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ > > Ha! I'll admit that I've done some searching on the web for issues I've > run into... and I found somebody who has simular issues... only to discover > that it's my own post! Sm:)e. > > > --Matt Ross > Ephrata School District > > > - Original Message - > From: Andrew S. Baker > [mailto:asbz...@gmail.com] > To: NT System Admin Issues > [mailto:ntsysadmin@lyris.sunbelt-software.com] > Sent: Wed, 05 Sep 2012 > 05:02:36 -0800 > Subject: Re: SOLVED RE: Deploying Printers in Group Policy > not working for non-admins > > > > Drivers would be available via the ADMIN$ share of the machine, I would > > expect. > > > > Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ > > > > > > * * > > > > *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of > > Technology for the SMB market… > > > > * > > > > > > > > On Wed, Sep 5, 2012 at 3:52 AM, Matthew W. Ross > > wrote: > > > > > I finally figured it out. I figured that I'd share: > > > > > > I was sorting my labs AD Computers into OUs. I then assigned a blank > group > > > policy for the printers on that OU. Using the Printer Manager, I > installed > > > the printers and drivers as a TCP/IP printer on my print server. I then > > > used the "Deploy Printer" option to configure the until now blank group > > > policy. > > > > > > This was all working perfectly. I had not had any problems doing it > this > > > way. This installs the printers on the client machines as TCP/IP > printers, > > > so none of them are dependent on a print server. > > > > > > My mistake was that I forgot a crucial step in this kind of deployment > > > process: I still had to share the printer from the print server. Doing > > this > > > allowed the computers to install the necessary drivers from the print > > > server. > > > > > > what I can't figure out is how the administrator accounts could see and > > > use use the printers, but the non-admins could not. Is there a hidden > > > administrative share that holds the drivers? Was Windows able to > install > > > local drivers each time? > > > > > > Anyways, as usual, something small and somewhat obvious was preventing > it > > > from working. > > > > > > > > > --Matt Ross > > > Ephrata School District > > > > > > > > > - Original Message - > > > From: Matthew W. Ross > > > [mailto:mr...@ephrataschools.org] > > > To: NT System Admin Issues > > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > > Sent: Tue, 04 Sep 2012 > > > 09:24:52 -0800 > > > Subject: RE: Deploying Printers in Group Policy not working > > > for non-admins > > > > > > > > > > As student's are not admins, they don't have the option to install > the > > > > printers. Especially as I'm trying to install them via IP. > > > > > > > > I'm about to install the printers via script, as they need printers > > > working, > > > > with or without group policy. > > > > > > > > > > > > --Matt Ross > > > > Ephrata School District > > > > > > > > > > > > - Original Message - > > > > From: Kelsey, John > > > > [mailto:jckel...@drmc.org] > > > > To: NT System Admin Issues > > > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > > > Sent: Tue, 04 Sep 2012 > > > > 06:11:38 -0800 > > > > Subject: RE: Deploying Printers in Group Policy not wo
Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
> Thanks for the follow-up. Much appreciated Indeed(tm) Always appreciate the tickets being closed and KB updated :) From: Andrew S. Baker [mailto:asbz...@gmail.com] Sent: Wednesday, September 05, 2012 5:03 AM To: NT System Admin Issues Subject: [dkim-failure] Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins Drivers would be available via the ADMIN$ share of the machine, I would expect. Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ ASB http://XeeMe.com/AndrewBaker Harnessing the Advantages of Technology for the SMB market... On Wed, Sep 5, 2012 at 3:52 AM, Matthew W. Ross mailto:mr...@ephrataschools.org>> wrote: I finally figured it out. I figured that I'd share: I was sorting my labs AD Computers into OUs. I then assigned a blank group policy for the printers on that OU. Using the Printer Manager, I installed the printers and drivers as a TCP/IP printer on my print server. I then used the "Deploy Printer" option to configure the until now blank group policy. This was all working perfectly. I had not had any problems doing it this way. This installs the printers on the client machines as TCP/IP printers, so none of them are dependent on a print server. My mistake was that I forgot a crucial step in this kind of deployment process: I still had to share the printer from the print server. Doing this allowed the computers to install the necessary drivers from the print server. what I can't figure out is how the administrator accounts could see and use use the printers, but the non-admins could not. Is there a hidden administrative share that holds the drivers? Was Windows able to install local drivers each time? Anyways, as usual, something small and somewhat obvious was preventing it from working. --Matt Ross Ephrata School District - Original Message - From: Matthew W. Ross [mailto:mr...@ephrataschools.org<mailto:mr...@ephrataschools.org>] To: NT System Admin Issues [mailto:ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>] Sent: Tue, 04 Sep 2012 09:24:52 -0800 Subject: RE: Deploying Printers in Group Policy not working for non-admins > As student's are not admins, they don't have the option to install the > printers. Especially as I'm trying to install them via IP. > > I'm about to install the printers via script, as they need printers working, > with or without group policy. > > > --Matt Ross > Ephrata School District > > > - Original Message - > From: Kelsey, John > [mailto:jckel...@drmc.org<mailto:jckel...@drmc.org>] > To: NT System Admin Issues > [mailto:ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>] > Sent: Tue, 04 Sep 2012 > 06:11:38 -0800 > Subject: RE: Deploying Printers in Group Policy not working > for non-admins > > > > What happens if the student tries to install the printer manually? Does > it > > complete or does it bomb out? > > > > -Original Message- > > From: Matthew W. Ross > > [mailto:mr...@ephrataschools.org<mailto:mr...@ephrataschools.org>] > > Sent: Friday, August 31, 2012 11:04 AM > > To: NT System Admin Issues > > Subject: Re: Deploying Printers in Group Policy not working for non-admins > > > > Here are some more oddities for this lab: > > > > 1) The printers are an HP Laserjet 4250 and a HP Color Laserjet 4700. We > > have other labs with the same model printers deployed from the same print > > server and this problem does not exist with them. > > 2) The printers show up if I log in as an administrator... but if I > > immediately log off, and log in as a generic student account, the printers > > are no longer there. Shouldn't the printers be installed already? > > > > > > --Matt Ross > > Ephrata School District > > > > > > - Original Message - > > From: Christopher Bodnar > > [mailto:christopher_bod...@glic.com<mailto:christopher_bod...@glic.com>] > > To: NT System Admin Issues > > [mailto:ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>] > > Sent: Fri, 31 Aug 2012 > > 05:22:56 -0800 > > Subject: Re: Deploying Printers in Group Policy not working for non-admins > > > > > > > Too funny, I was just about to type up the exact same question. I ran > > > into this same scenario last night. The only thing that I found > > > different was between 2 different printers. In my case the printers are: > > > > > > Canon iR3245 > > > HP Officejet 8600 > > > > > > So I deployed the iR3245 first via GPO using the Print Management > >
Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
> Drivers would be available via the ADMIN$ share of the machine, I would > expect. Okay, I'll take that answer... but then why wouldn't the printer be installed once the admin logged in? Why do the printers disappear afterwards? And why isn't there any good data about the failure in the event viewer? (Why, Microsoft? Why?) > Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ Ha! I'll admit that I've done some searching on the web for issues I've run into... and I found somebody who has simular issues... only to discover that it's my own post! Sm:)e. --Matt Ross Ephrata School District - Original Message - From: Andrew S. Baker [mailto:asbz...@gmail.com] To: NT System Admin Issues [mailto:ntsysadmin@lyris.sunbelt-software.com] Sent: Wed, 05 Sep 2012 05:02:36 -0800 Subject: Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins > Drivers would be available via the ADMIN$ share of the machine, I would > expect. > > Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ > > > * * > > *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of > Technology for the SMB market… > > * > > > > On Wed, Sep 5, 2012 at 3:52 AM, Matthew W. Ross > wrote: > > > I finally figured it out. I figured that I'd share: > > > > I was sorting my labs AD Computers into OUs. I then assigned a blank group > > policy for the printers on that OU. Using the Printer Manager, I installed > > the printers and drivers as a TCP/IP printer on my print server. I then > > used the "Deploy Printer" option to configure the until now blank group > > policy. > > > > This was all working perfectly. I had not had any problems doing it this > > way. This installs the printers on the client machines as TCP/IP printers, > > so none of them are dependent on a print server. > > > > My mistake was that I forgot a crucial step in this kind of deployment > > process: I still had to share the printer from the print server. Doing > this > > allowed the computers to install the necessary drivers from the print > > server. > > > > what I can't figure out is how the administrator accounts could see and > > use use the printers, but the non-admins could not. Is there a hidden > > administrative share that holds the drivers? Was Windows able to install > > local drivers each time? > > > > Anyways, as usual, something small and somewhat obvious was preventing it > > from working. > > > > > > --Matt Ross > > Ephrata School District > > > > > > - Original Message - > > From: Matthew W. Ross > > [mailto:mr...@ephrataschools.org] > > To: NT System Admin Issues > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > Sent: Tue, 04 Sep 2012 > > 09:24:52 -0800 > > Subject: RE: Deploying Printers in Group Policy not working > > for non-admins > > > > > > > As student's are not admins, they don't have the option to install the > > > printers. Especially as I'm trying to install them via IP. > > > > > > I'm about to install the printers via script, as they need printers > > working, > > > with or without group policy. > > > > > > > > > --Matt Ross > > > Ephrata School District > > > > > > > > > - Original Message - > > > From: Kelsey, John > > > [mailto:jckel...@drmc.org] > > > To: NT System Admin Issues > > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > > Sent: Tue, 04 Sep 2012 > > > 06:11:38 -0800 > > > Subject: RE: Deploying Printers in Group Policy not working > > > for non-admins > > > > > > > > > > What happens if the student tries to install the printer manually? > > Does > > > it > > > > complete or does it bomb out? > > > > > > > > -Original Message- > > > > From: Matthew W. Ross [mailto:mr...@ephrataschools.org] > > > > Sent: Friday, August 31, 2012 11:04 AM > > > > To: NT System Admin Issues > > > > Subject: Re: Deploying Printers in Group Policy not working for > > non-admins > > > > > > > > Here are some more oddities for this lab: > > > > > > > > 1) The printers are an HP Laserjet 4250 and a HP Color Laserjet 4700. > > We > > > > have other labs with the same model printers deployed from the same > > print > > > > server and this problem does not exist with the
RE: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
Thanks for this! -Original Message- From: Matthew W. Ross [mailto:mr...@ephrataschools.org] Sent: Wednesday, September 05, 2012 12:52 AM To: NT System Admin Issues Subject: SOLVED RE: Deploying Printers in Group Policy not working for non-admins I finally figured it out. I figured that I'd share: I was sorting my labs AD Computers into OUs. I then assigned a blank group policy for the printers on that OU. Using the Printer Manager, I installed the printers and drivers as a TCP/IP printer on my print server. I then used the "Deploy Printer" option to configure the until now blank group policy. This was all working perfectly. I had not had any problems doing it this way. This installs the printers on the client machines as TCP/IP printers, so none of them are dependent on a print server. My mistake was that I forgot a crucial step in this kind of deployment process: I still had to share the printer from the print server. Doing this allowed the computers to install the necessary drivers from the print server. what I can't figure out is how the administrator accounts could see and use use the printers, but the non-admins could not. Is there a hidden administrative share that holds the drivers? Was Windows able to install local drivers each time? Anyways, as usual, something small and somewhat obvious was preventing it from working. --Matt Ross Ephrata School District - Original Message - From: Matthew W. Ross [mailto:mr...@ephrataschools.org] To: NT System Admin Issues [mailto:ntsysadmin@lyris.sunbelt-software.com] Sent: Tue, 04 Sep 2012 09:24:52 -0800 Subject: RE: Deploying Printers in Group Policy not working for non-admins > As student's are not admins, they don't have the option to install the > printers. Especially as I'm trying to install them via IP. > > I'm about to install the printers via script, as they need printers > working, with or without group policy. > > > --Matt Ross > Ephrata School District > > > - Original Message - > From: Kelsey, John > [mailto:jckel...@drmc.org] > To: NT System Admin Issues > [mailto:ntsysadmin@lyris.sunbelt-software.com] > Sent: Tue, 04 Sep 2012 > 06:11:38 -0800 > Subject: RE: Deploying Printers in Group Policy not working for > non-admins > > > > What happens if the student tries to install the printer manually? > > Does > it > > complete or does it bomb out? > > > > -Original Message- > > From: Matthew W. Ross [mailto:mr...@ephrataschools.org] > > Sent: Friday, August 31, 2012 11:04 AM > > To: NT System Admin Issues > > Subject: Re: Deploying Printers in Group Policy not working for > > non-admins > > > > Here are some more oddities for this lab: > > > > 1) The printers are an HP Laserjet 4250 and a HP Color Laserjet > > 4700. We have other labs with the same model printers deployed from > > the same print server and this problem does not exist with them. > > 2) The printers show up if I log in as an administrator... but if I > > immediately log off, and log in as a generic student account, the > > printers are no longer there. Shouldn't the printers be installed already? > > > > > > --Matt Ross > > Ephrata School District > > > > > > - Original Message - > > From: Christopher Bodnar > > [mailto:christopher_bod...@glic.com] > > To: NT System Admin Issues > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > Sent: Fri, 31 Aug 2012 > > 05:22:56 -0800 > > Subject: Re: Deploying Printers in Group Policy not working for > > non-admins > > > > > > > Too funny, I was just about to type up the exact same question. I > > > ran into this same scenario last night. The only thing that I > > > found different was between 2 different printers. In my case the printers > > > are: > > > > > > Canon iR3245 > > > HP Officejet 8600 > > > > > > So I deployed the iR3245 first via GPO using the Print Management > > > method and none of the users received the mapping. But I could map > > > the printer manually. So I finally decided to test using the 2nd > > > printer, using the same method and the OfficeJet mapped > > > successfully. I then went and published the iR3245 via GPO preferences, > > > and that worked. > > > The only thing I can think of is that for some reason its a driver > > > issue, but I can't think of what that would be. > > > > > > Not sure if this is relavent, but this is a ThinClient environment. > > > All Hyper-V hosts with RDS and clients are Wyse C10LE. All >
Re: SOLVED RE: Deploying Printers in Group Policy not working for non-admins
Drivers would be available via the ADMIN$ share of the machine, I would expect. Thanks for the follow-up. Much appreciated. http://xkcd.com/979/ * * *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of Technology for the SMB market… * On Wed, Sep 5, 2012 at 3:52 AM, Matthew W. Ross wrote: > I finally figured it out. I figured that I'd share: > > I was sorting my labs AD Computers into OUs. I then assigned a blank group > policy for the printers on that OU. Using the Printer Manager, I installed > the printers and drivers as a TCP/IP printer on my print server. I then > used the "Deploy Printer" option to configure the until now blank group > policy. > > This was all working perfectly. I had not had any problems doing it this > way. This installs the printers on the client machines as TCP/IP printers, > so none of them are dependent on a print server. > > My mistake was that I forgot a crucial step in this kind of deployment > process: I still had to share the printer from the print server. Doing this > allowed the computers to install the necessary drivers from the print > server. > > what I can't figure out is how the administrator accounts could see and > use use the printers, but the non-admins could not. Is there a hidden > administrative share that holds the drivers? Was Windows able to install > local drivers each time? > > Anyways, as usual, something small and somewhat obvious was preventing it > from working. > > > --Matt Ross > Ephrata School District > > > - Original Message - > From: Matthew W. Ross > [mailto:mr...@ephrataschools.org] > To: NT System Admin Issues > [mailto:ntsysadmin@lyris.sunbelt-software.com] > Sent: Tue, 04 Sep 2012 > 09:24:52 -0800 > Subject: RE: Deploying Printers in Group Policy not working > for non-admins > > > > As student's are not admins, they don't have the option to install the > > printers. Especially as I'm trying to install them via IP. > > > > I'm about to install the printers via script, as they need printers > working, > > with or without group policy. > > > > > > --Matt Ross > > Ephrata School District > > > > > > - Original Message - > > From: Kelsey, John > > [mailto:jckel...@drmc.org] > > To: NT System Admin Issues > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > Sent: Tue, 04 Sep 2012 > > 06:11:38 -0800 > > Subject: RE: Deploying Printers in Group Policy not working > > for non-admins > > > > > > > What happens if the student tries to install the printer manually? > Does > > it > > > complete or does it bomb out? > > > > > > -Original Message- > > > From: Matthew W. Ross [mailto:mr...@ephrataschools.org] > > > Sent: Friday, August 31, 2012 11:04 AM > > > To: NT System Admin Issues > > > Subject: Re: Deploying Printers in Group Policy not working for > non-admins > > > > > > Here are some more oddities for this lab: > > > > > > 1) The printers are an HP Laserjet 4250 and a HP Color Laserjet 4700. > We > > > have other labs with the same model printers deployed from the same > print > > > server and this problem does not exist with them. > > > 2) The printers show up if I log in as an administrator... but if I > > > immediately log off, and log in as a generic student account, the > printers > > > are no longer there. Shouldn't the printers be installed already? > > > > > > > > > --Matt Ross > > > Ephrata School District > > > > > > > > > - Original Message - > > > From: Christopher Bodnar > > > [mailto:christopher_bod...@glic.com] > > > To: NT System Admin Issues > > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > > Sent: Fri, 31 Aug 2012 > > > 05:22:56 -0800 > > > Subject: Re: Deploying Printers in Group Policy not working for > non-admins > > > > > > > > > > Too funny, I was just about to type up the exact same question. I ran > > > > into this same scenario last night. The only thing that I found > > > > different was between 2 different printers. In my case the printers > are: > > > > > > > > Canon iR3245 > > > > HP Officejet 8600 > > > > > > > > So I deployed the iR3245 first via GPO using the Print Management > > > > method and none of the users received the mapping. But I could map > the > > > > printer manually. So I finally decided to test using the 2nd printer, > > > > using the same method and the OfficeJet mapped successfully. I then > > > > went and published the iR3245 via GPO preferences, and that worked. > > > > The only thing I can think of is that for some reason its a driver > > > > issue, but I can't think of what that would be. > > > > > > > > Not sure if this is relavent, but this is a ThinClient environment. > > > > All Hyper-V hosts with RDS and clients are Wyse C10LE. All servers > > > > are Windows 2008 R2. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Christopher Bodnar > > > > Enterprise Architect I, Corporate Office of Technology:Enterprise > > > > Architecture and Engineering Services Tel 610-807-6459 > > > > 3900 Burgess Place, Bethlehem, PA 1801
SOLVED RE: Deploying Printers in Group Policy not working for non-admins
I finally figured it out. I figured that I'd share: I was sorting my labs AD Computers into OUs. I then assigned a blank group policy for the printers on that OU. Using the Printer Manager, I installed the printers and drivers as a TCP/IP printer on my print server. I then used the "Deploy Printer" option to configure the until now blank group policy. This was all working perfectly. I had not had any problems doing it this way. This installs the printers on the client machines as TCP/IP printers, so none of them are dependent on a print server. My mistake was that I forgot a crucial step in this kind of deployment process: I still had to share the printer from the print server. Doing this allowed the computers to install the necessary drivers from the print server. what I can't figure out is how the administrator accounts could see and use use the printers, but the non-admins could not. Is there a hidden administrative share that holds the drivers? Was Windows able to install local drivers each time? Anyways, as usual, something small and somewhat obvious was preventing it from working. --Matt Ross Ephrata School District - Original Message - From: Matthew W. Ross [mailto:mr...@ephrataschools.org] To: NT System Admin Issues [mailto:ntsysadmin@lyris.sunbelt-software.com] Sent: Tue, 04 Sep 2012 09:24:52 -0800 Subject: RE: Deploying Printers in Group Policy not working for non-admins > As student's are not admins, they don't have the option to install the > printers. Especially as I'm trying to install them via IP. > > I'm about to install the printers via script, as they need printers working, > with or without group policy. > > > --Matt Ross > Ephrata School District > > > - Original Message - > From: Kelsey, John > [mailto:jckel...@drmc.org] > To: NT System Admin Issues > [mailto:ntsysadmin@lyris.sunbelt-software.com] > Sent: Tue, 04 Sep 2012 > 06:11:38 -0800 > Subject: RE: Deploying Printers in Group Policy not working > for non-admins > > > > What happens if the student tries to install the printer manually? Does > it > > complete or does it bomb out? > > > > -Original Message- > > From: Matthew W. Ross [mailto:mr...@ephrataschools.org] > > Sent: Friday, August 31, 2012 11:04 AM > > To: NT System Admin Issues > > Subject: Re: Deploying Printers in Group Policy not working for non-admins > > > > Here are some more oddities for this lab: > > > > 1) The printers are an HP Laserjet 4250 and a HP Color Laserjet 4700. We > > have other labs with the same model printers deployed from the same print > > server and this problem does not exist with them. > > 2) The printers show up if I log in as an administrator... but if I > > immediately log off, and log in as a generic student account, the printers > > are no longer there. Shouldn't the printers be installed already? > > > > > > --Matt Ross > > Ephrata School District > > > > > > - Original Message - > > From: Christopher Bodnar > > [mailto:christopher_bod...@glic.com] > > To: NT System Admin Issues > > [mailto:ntsysadmin@lyris.sunbelt-software.com] > > Sent: Fri, 31 Aug 2012 > > 05:22:56 -0800 > > Subject: Re: Deploying Printers in Group Policy not working for non-admins > > > > > > > Too funny, I was just about to type up the exact same question. I ran > > > into this same scenario last night. The only thing that I found > > > different was between 2 different printers. In my case the printers are: > > > > > > Canon iR3245 > > > HP Officejet 8600 > > > > > > So I deployed the iR3245 first via GPO using the Print Management > > > method and none of the users received the mapping. But I could map the > > > printer manually. So I finally decided to test using the 2nd printer, > > > using the same method and the OfficeJet mapped successfully. I then > > > went and published the iR3245 via GPO preferences, and that worked. > > > The only thing I can think of is that for some reason its a driver > > > issue, but I can't think of what that would be. > > > > > > Not sure if this is relavent, but this is a ThinClient environment. > > > All Hyper-V hosts with RDS and clients are Wyse C10LE. All servers > > > are Windows 2008 R2. > > > > > > > > > > > > > > > > > > > > > Christopher Bodnar > > > Enterprise Architect I, Corporate Office of Technology:Enterprise > > > Architecture and Engineering Services Tel 610-807-6459 > > > 3900 Burgess Place, Bethlehem, PA 18017 christopher_bod...@glic.com > > > > > > > > > > > > > > > The Guardian Life Insurance Company of America > > > > > > www.guardianlife.com > > > > > > > > > > > > > > > > > > > > > > > > From: "Matthew W. Ross" > > > To: "NT System Admin Issues" > > > Date: 08/30/2012 06:02 PM > > > Subject:Deploying Printers in Group Policy not working for > > > non-admins > > > > > > > > > > > > Good Afternoon. > > > > > > I'm deploying printers using Group Policy. We have Windows Server > > > 20
