Deploy Printers in Server 2008 R2

I am trying to deploy printers in a Native 2008 R2 DC enviroment. We have currently removed all server 2003 DC's. Both Domain and Forest Levels were raised 4 days ago. I have configured the printers on the Dedicated Print server through printer management. I have deployed the printers through GPO. These printers will deployed to Win XP 32bit and Windows 7 32bit and 64bit. 98% of the machines is Windows XP. I am unable to get these printers to actually deploy via GPO. I have one test group setup with my account added. The GPO is applied to that test Group. I have done gpupdate /force and rebooted more times than I can count for the last 2 days. I have seen several refernces to PushPrinterConnections.exe for Server 2003 R2 but can not find any info on using that for Server 2008 R2 Any help would be greatly appreciated.
sumgAsked:
Who is Participating?
 
Encrypted1024Connect With a Mentor Commented:
Windows 7 and Vista work way better for this style of Printer deployment. I am not sure why you are having the issues with the printers coming back, especially after you have removed them from the domain.
XP doesn't remove the printers after the policy is removed like Win 7. I use a script to delete printers I no longer want. This script will delete ALL network printers but leave local printers.  
Make sure you are testing with x86 XP machines. Like I said before I am not sure if that ppc.exe works with x64.
I am not sure why you are having issues with the user logon script. It should work with the instructions I gave.
Here is another article on it. Read through it, maybe it will help.
http://technet.microsoft.com/en-us/magazine/2006.08.manageprinters.aspx
 

DeletePrinters.zip
0
 
IntechnicalCommented:
You may need to install Client Side Extensions on the XP computers, Have you also set the targeting options in the GPO?
0
 
Encrypted1024Commented:
I bet you will find that the Visat and newer clients are working properly. You will need pushprinters.exe for the XP clients. Set up your GPO's so that the pushprinters.exe is only applied once per computer otherwise you may experience long log in times.
Microsoft in their infinite wisdom decided not not include pushprinters.exe in 2K8 R2. Their are two versions of pushprinter.exe, x64 and x86. You will need to copy the appropriate version for your clients from a W2K3 R2 box.
The other option is to use Group Policy Prefferences to deploy your printers. This will work with XP and newer clients without pushprinters.exe but I have experienced issue with this method such as long log in times and have reverted back to the Printer Manger method.
 
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
sumgAuthor Commented:
I have installed the CSE on this machine, the test Drive mapping I created started working after I installed CSE. I am not sure what you mean by set the targeting options in GPO. I have created a test group and OU, I placed my account in that group and OU.

So far as I can tell the printers are not working on Vista or Win7 or Server 2008. When I log into other machines these printers do not show. We do not have any Windows 2003 R2 32bit servers. I have the OS disk but only finding the pushprintersconnections.ex_ file

We use Scripts currently to push the printers to users from our old setup of Server 2000 and Server 2003. This is the first DC and Print server running 64bit.

0
 
sumgAuthor Commented:
On another note I forgot to mention. One of my main systems is a Server 2008 R2. When I open GPO I can see Deployed Printers in the Policy. If I remote into any of the 3 actual DC's they will not show the Deployed Printers in the Policy. It is not a issue of replication. I can change domain controller on my system to any of the 3 DC's and see Deployed printers just fine. But when I remote to that machien it does not show it. Very stange.
0
 
Encrypted1024Commented:
That is normal behavior. The printing deployment is not very well thought out by MS. If you look at GPMC in an older DC (2003) it will not show up in GPMC.
Here is the x86 version of pushprinters from a x86 W2k3R2 server.
I have had better luck with a computer based policy on this one. So remember it has to be a start up script for computer policy and a logon script for user policy.

pushprinterconnections.zip
0
 
sumgAuthor Commented:
I have pushed the PPC.exe to my XP system with no success. All the servers are 2008 R2 I am testing with. The 3 DC's are Server 2008R2, my server is 2008 R2 and same thing with a Co-worker has Server 2008 R2. My server and his server both see Deployed Printers in the GPO just fine. The 3 2008 R2 DC's will not see the Deployed Printers.

I copied the PPC.exe to the sysvol through startup scripts and hit add, selected the ppc.exe file and applied it to the GPO. I have moved my XP machines to the OU and added it to the group affected by the policy. 3 gpupdate /force with reboots and still no go. I do see the ppc.exe in the prefetch folder now added on todays date. So the ppc.exe did get pushed but the printers will not install. I have verified there are x86 drivers on the print server. I can manually install the printers on a XP machine with no errors.
0
 
sumgAuthor Commented:
Another update to the system. I have built a Windows 7 64bit VM and added to the domain. I put the PC in the same OU and applied the policy to this machine. It as well is not pulling the printers.
0
 
Encrypted1024Commented:
Okay, lets look at the Print Management MMC. First create a GPO called "Deploy Printers" on the Windows XP computer OU. Set the ppp.exe as a startup script. Open Print Management on your print server. Select printers. Right click on a printer and select "Deploy with Group Policy". Select the OU that you just created and add it as a computer policy.
gpupdate /force
Then reboot and login.
0
 
sumgAuthor Commented:
This has worked by pushing to computer only. I do wonder why this will not push to users though. Pushing to computers is going to make things much more difficult. Do you know of a way to correct this?

0
 
Encrypted1024Commented:
Yes, you can push to users but it will be difficult. The ppc.exe needs to be x86 for x86 computers and x64 with x64 computers (Thats wat the documentation says. I have not tested that. You may be able to use the x86 version for both, but definately not the other way around). I can send you the x64 version if you need it.
If you want to make it work with users you need to make a couple of changes.
- Attach GPO to user OU.
- Add ppc.exe to logon script in User Policy instead of startup script
- Select user policy when adding deployed printer through Print manager.
0
 
sumgAuthor Commented:
I have followed your instructions for user push and it fails. I have attached the error I receive on the XP machine. I do not receive this error if I use a startup script, only on the logon script. I believe once I can resolve this logon script everything should work fine, because everything seems to be trying to work now where before we started I was getting no where.

Windows 7 is now getting the printer from the Per User GPO
error.JPG
0
 
sumgAuthor Commented:
Last issue I am seeing is that once those printers were installed on XP from the computer policy there is no way to delete them. I have disabled the policy, moved the PC from the Group and OU. I have also removed the pc from the domain and they will still come back. Pretty strange they wont stay away now. The windows 7 system dropped the printers with no problem.
0
 
sumgAuthor Commented:
Thank you very much for all of your assistance. This has been a huge help. I will stick to script printer distribution until we phase out XP all together.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.