Windows Server 2003 32bit Group policy deploy printer windows 7 64bit

My printer server is a 32bit Microsoft Server 2003.  I want to use group policy to push out a shared printer to Windows 7 64bit computers.  I set it up under both computer config/preferences/control panel settings/printers and user config/preferences/control panel settings/ printers and the gp results show it was applied but I don't see the printer.  What am I doing wrong?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Do you have x64 drivers installed for the printer?
jamiebehlAuthor Commented:
Yes.  I downloaded them and went into the printer properties sharing tab and added the 64 bit drivers.
Did you put the x64 bit Drivers?

Check this out:

Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

jamiebehlAuthor Commented:
These are great instructions but appear to be for Server 2008.
Listen, since you have Windows 7 machine, why don't you put RSAT on it & then make the Group Policy for printers from it.
You will get exactly the same interface as posted in the document.

Give it a go & tell what happens.
See here for adding drivers:

& the correct way of installing drivers:

I am not saying that you did something wrong, but it's always good to double check.
Are you running PrinterConnections.exe for this w7 box?  Seems to me that for w7, not only do you not need to run PrinterConnections.exe, but you must not.

Also, what's the printer?  There's a weird fix you need for some HPs.
jamiebehlAuthor Commented:
It is an HP P2055dn printers.  I think I am running printerconnections.exe somewhere on the server for other policies.
Yeah, I posted the fix already.
Put the W7 machine in a new OU, apply the policy & block inheritance on OU. Reboot W7 this will isolate other policies & make sure other printer policies are not enforced.
Or best is create a new GPO.
I found the link for that error I referred to.

Have you tried installing the printer manually (ie using Add Printer on the client)?  If this fails with a 0x7e error, check out this link:

I'm using the same fix they are, and I've not seen a problem.  Note that if you don't see the 0x7e error, don't mess with the registry.
NO CAN DO on a 2003 server...

X64 bit drivers are not supported and the policies to store the x64 drivers for Vista/W7 and 2008 server are also not supported.

What you have to do is snatch up a w7 PC and download the RSAT tools (remote server admin tools). This will allow you to deploy printers and save drivers for these newer machines. THEN, you can save deploy the printers using an ADMX or ADML template, rather than the latest legacy ADM templates for group policy and printer deployment...

I also highly suggest you read this article:

Otherwise:  Deploy a 2008 server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jamiebehlAuthor Commented:
I have a Domain Controller with 2008.  All of my other printers are on the older server.  I setup the printer on the new server and it works fine.
Since you already have a 2008 server, you might consider holding the FSMO roles on that server, and making sure it is a Global Catalog server. On a 2008 server you can host both legacy ADM template for 2003, xp, 2000, operating systems, as well as Vista, W7, 2008 ADMX and ADML templates...

2008 server also offers more granularity when configuring a domain password policy, (meaning you can create the password policy for OU's rather than the entire domain).

Making the 2008 server the PDC emulator, has fringe benifits even in mixed mode operations, especially within Group Policy deployment.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.