Can't map printers in XP in 2008R2 domain

I'm hoping for some ideas here...

I have two policies set up in a 2008R2 domain. One maps network drives, the other is supposed to map printers. This all works fine on the Windows 7 machines. However the printers are not mapping on the XP clients, although they are getting the drive mappings.

Per other technical notes I have found, the 32-bit and 64-bit drivers on the print server are exactly the same version and name. I read this is required for mapping to work when a 64-bit server is involved. I can install the printers manually by connecting to \\server\share.

The printers are being pushed using global policy and this is working for Windows 7. It didn't work for XP, despite my creating a user based logon script to run pushprinterconnections.exe. I tried changing my script to use con2prt instead and that still doesn't work. There are no errors in the event viewer on the XP client.

A couple of notes about my first attempt with pushprinterconnections...
1. Despite my XP clients being 32-bit, Microsoft tech support says I should use the 64-bit version of the program because its a 64-bit server pushing the printer. Although I have tried both versions with no luck.
2. If I run the 32-bit version of pushprinterconnections manually on the client, the printers appear.

So I think the problem is that the policy is not executing, but it seems to be since the drive maps are appearing. Anyone have any more experience to add?
LVL 26
Brian BEE Topic Advisor, Independant Technology ProfessionalAsked:
Who is Participating?
Mike KlineCommented:
Never run into your issue but I'll look around and let you know if I find something.   Have you thought about using GPP to deploy the printers


Darius GhassemCommented:
Make sure you have the Windows XP Group policy extensions installed on the systems.
take a look at this article and see if it helps you figure out the xp clients.  It's based on 2003 r2 server but the delopyment/gpo part should be about the same. 
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Brian BEE Topic Advisor, Independant Technology ProfessionalAuthor Commented:
mkline71: I had tried that at some point, but I think it was before I got the whole "distributing 32-bit drivers from a 64-bit machine" thing working. I tried so many things, I can't remember the order any more. Anyway, I tried again (did a gpupdate /force on the client, too) and it didn't work.

dariusq: I already installed the patches KB943729 and KB974266 and that got the drive mappings to work.

micalkin: That is the article I used to set up the printer connections as they are now.
Are you modifying the default domain policy or you attaching a gpo to a ou?
I do know that modifying the default domain policy doesn't always work for XP computers.
Brian BEE Topic Advisor, Independant Technology ProfessionalAuthor Commented:
No, I'm making a new policy attached to an OU.

Having said that, now it works on my XP clients. Per my previous comment, I may not have done everything in the correct order before. So mkline's idea seems to be working.

Having said that, now my Win7 clients aren't getting the printers and drive mappings any more.
Brian BEE Topic Advisor, Independant Technology ProfessionalAuthor Commented:
Thanks to all who participated. mkline's suggestion was the core of the problem, but micalkin's suggestion is also useful.
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.