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

Do you have x64 drivers installed for the printer?

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:
http://www.petenetlive.com/KB/Article/0000492.htm

A

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.
A

See here for adding drivers:
http://serverfault.com/questions/54781/problem-adding-windows-7-64-bit-print-drivers-to-a-32-bit-windows-2003-print-ser

& the correct way of installing drivers:
http://support.microsoft.com/kb/2028992

I am not saying that you did something wrong, but it's always good to double check.
A

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.

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.
A

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: http://www.networksteve.com/windows/topic.php/32bit_windows_7_can%27t_add_network_printers/?TopicId=18606&Posts=1

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.

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.