Question : printer not listing properly in windows 2008 r2

I have been scratching my head and doing some research on this.  

I have a windows 2008 R2 DC and setup on a seperate server a hyper V print server.  
Before moving all this to 2008 R2, i was using 2003 DC and that doubled as a print server.and everything listed with no isses from anywhere on the LAN network.
I setup 64x and 32x drivers on the new virtual print server for which I have been shared and clicked on the listing,  I tested the printers drivers and work with no issues.

This is the issue, I have
For some reason when i try to add the printer from Win 7, by using the Add printer, it is not listed.  but when i go through the active Directory listing, It is there. BUT all the old printers which are on the now BDC, show up.

When i look at the administrative logs on the Hyper V - Virtual computer i see event ID 333 from the print service
"While attempting to publish the printer to the Active Directory directory service, the print spooler failed to create or update print queue CN=PRINT-SERVER -PRINTER SHARE in container LDAP://**BDC*/CN=PRINT-SERVER,OU=Virtualized Servers,DC=DOMAIN,DC=local.  Error: 80070005. The printer is not published in Active Directory and cannot be located by searching Active Directory."

Strange thing is that where is put "**BDC*", this shows that it is pointing to my old DC which is now BDC and is WIndows 2003 box.  

As stated before my DC is now WIndows 2008 R2, all roles have been transfered.

I looked around the Net and enabled the Group Policy Printer publishing fix.  but no go.  
For testing purposes i put the group policy to accept all shared printers.

I seems a bit confusing, if there is any clarification needed, pleas eask the questions.  


 

Answer : printer not listing properly in windows 2008 r2

Did you remove the printers from the old server?  You should.

Once AD purges the old printers then they should start to behave.

The new printer server is attempting to publish the printers into the container for the old server - it doesn't have permissions in the directory to do this.