I have setup some printers on a Windows Server 2008 R2 box with the Print Management role installed.  Everything looks good, double and triple checked all the standard permissions on the printers and the printer server (in the Print Management console). My clients can install the printer but always get an error when trying to print.  If I try to print on a client using my server domain admin account it works just fine.  This tells me it is a permissions issue buried somewhere on the server.

Any suggestions?

Hi all,

I cannot find this setting in the regedit nor in the setprinter.exe.

Any way to disable this setting via e.g. a script? I need to disable it on all queues on a server...

Thanks,

David

Hi, we have a client with Lotus Notes (the last version, in fact the release number i don't know but i know is the last version) nad we have installed and confgured a Fax Server in one physical server. Now our client wants integrate the Fax Server (based on Windows Server 2008 R2) with their Lotus Notes. We have searched but we dont get any document to make this.

Can someone help us?

Raulito

Hi,

I have a Server 2008 R2 print server, serving a mixture of clients 7,XP (32&64).  We have Papercut (print logging) software installed on the server.

We are seeing intermittent jobs on Print Queues logged as workstation name instead of username, it is on random jobs i.e. Word, PDF, Internet Explorer and random clients.  Unable to find a common link as to why it happens

See Papercut kb - www.papercut.com/kb/Main/JobsOwnedByComputer

We have denied computers object as well as individual workstations on the Print Queue but it still allows computers to print.  It seems like a bug in Windows that this is still allowed to occur.

Any ideas?

Cheers

Ross

I am trying to find a script for this:

If number of printed pages > 10 then print separator page with owner name, date, time

The purpose of this is that often times, clients print 10+ pages and never claim it.

Less than 10 pages, it will print without separator page.

Thanks in advance!

Hi every one! I have been trying trouble shoot my FRS for the past month and a half now, up to this point their is no success

can anyone help me resolve this problem? I have on my network two server (2003), one PDC and a BDC, the event viewer log on the pdc show these messages:

The File Replication Service is no longer preventing the computer xxxx_xxx from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. 

Type "net share" to check for the SYSVOL share

 HOWEVER THE BDC IS SHOWING THESE MESSAGES:

DNS WARNING MESSAGES:

The DNS server encountered a packet addressed to itself on IP address 192.168.0.1. The packet is for the DNS name "z.arin.net.". The packet will be discarded. This condition usually indicates a configuration error. 

Check the following areas for possible self-send configuration errors: 
  1) Forwarders list. (DNS servers should not forward to themselves). 
  2) Master lists of secondary zones. 
  3) Notify lists of primary zones. 
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless subzone is also on this server. 
  5) Root hints. 

Example of self-delegation: 
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com. 
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com, 
  (bar.example.microsoft.com NS dns1.example.microsoft.com) 
  -> BUT the bar.example.microsoft.com zone is NOT on this server. 

Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result.  If found, the subzone DNS server admin should remove the offending NS record. 

FRS LOG ON THE BDC DNS LOG IS ALSO FROM BDC:

The File Replication Service is having trouble enabling replication from XXX_XXXA to XXXXSERVERB for c:\windows\sysvol\domain using the DNS name XX

X_XXX.XXX.XXX. FRS will keep retrying. 
 Following are some of the reasons you would see this warning. 

 [1] FRS can not correctly resolve the DNS name XXX_XXX.XXX.XXX from this computer. 
 [2] FRS is not running on XXX_XXX.XXX.XXX. 
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. 

 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

Please someone i need your help on this, am very new to win 2003 server my knowledge is basic. (please make the solution instructive for me thanks) from gilliep

For the last couple of week I can't print anything from microsoft word 2008 for MAC. everytime I click on print preview it show me the page no problem, but it just run a blank page thru the printer. I have NO problem running a test page, printer connection is fine, printer ink is fine, test page looks great. I have NO problem printing everything else, e mails, pictures, anything from any other program.

Microsoft just does not like my printer anymore.

WB

Hi I have Server 2003 Printer server and I have just setup and installed Server 2012 with the Print Services. How can I migrate all the printers and drivers from Server 2003 to Server 2012.

Your help will be much appreciated, thak you.

Hey guys,

Got a problem which is driving me mad and I can't find anything anywhere!

• We have server 2008 R2 with Print Management hosting all our shared printers.
• All printers are deployed by GPO to the correct computers.
• There's a GPO running to set default printers at the user level.

This works perfectly, however, our problem is that randomly some printers show up greyed out and there is no fix other than leaving it for a while or logging off and on or restarting the computer!

This is starting to drive our users mad and also causing a lot of unwanted work for something so trivial.

Please say there's someone out there who has had this issue as we need a fix ASAP!!!

Many thanks

Perry

I have a windows 2008 x64 server that I am using as my print server.   It was working well for a while now all of a sudden I cannot install any new printers or printer drivers.

If I install a printer, any manufacturer and both x86 and x64 driver I get the error:

unable to install <printer> type 3 - user mode, x86 driver. access is denied

If I try and add a printer it gets to 0x0000002 error.

Not sure where in the process but I have also seen an error telling me that the core driver package is not installed (which I think is but I don't have access).

I think this happened when I uninstalled a wireless printer.

p.s. following a suggestion to look at the security tab for the printers, but it is missing.

Hi

Virtual print queue not listing for all the users in the specific Active directory site,

Can Any one tell how to list the virtual print queue to all the users in the Active directory site. User needs to browse the printer via

Start / Devices and Printers / Add a printer / Add a network, Bluetooth or wireless printer /

We are not using any group policy for the printer listing, users able to list the Virtual print queue via Active Directory

Hi,

I installed printer server on windows 2008 R2 std and added all printers, now my users accessing and printing without any issues.

My Question is, is there any way to get all the details, like,... total count, total count of each printers, count user wise etc... 

Mafeer CM

0558131136

Good morning,

In our environment we have multiple servers on 2008R2 and one on 2012.  Currently our 2012 machine is run through HyperV.  We have an issue where this 2012 terminal server maxes out its memory usage giving all of the available RAM to the print spooler if we let it go.

We have updated the drivers for the printers, removed the printer redirection from clients, and got rid of any old printers that were in the mix.  Unfortunately, the issue persists.

Although restarting the service is an easy fix for the short term, we are looking for a permanent fix so that we can take this off of our radar.  Right now I am logging on about twice a day to restart the spooler service and when I do it is usually hogging up about 12GB of RAM.

Any help is appreciated!

Isaac

Hi,

I couldn’t get 2 Dell Lat E5530 running W7 SP1 x86 to connect to a printer, now I can’t print at all!

OK so yesterday we had our Ricoh MFD upgraded from an Aficio MP C4000 to an MP C5503...All installed ok and all I did at the time was just upgrade the driver within the print queue. I checked by doing a test print from my laptop which by the way is running W7 SP1 x64, and this went through ok... We have 12 teachers here all running W7 SP1 x86 on Dell Lat E5530 they all have the same build as I used WDS to deploy the software.

 Now 2 of these laptops (the other 10 are working fine) couldn’t connect to the printer. When I tried to add the printer from the list it goes off to windows update to try and retrieve the driver after about 10mins it says it couldn't find a suitable driver so I then tried to add the x86 driver from the cd but it said it couldn’t find it even though I navigated through the x86 folder to the *.inf file.

So I then tried to add the printer using a local port with the IP address and the UNC path neither of these worked either. Then I thought I would try and delete the print queue from the server stop and start the spooler service then re-add using the disk provided, this seemed to do the the trick I can now add the printer to the client machines but I cannot print at all now from any PC or the print server itself to this printer… All test prints appear to go through the queue but nothing comes out at the printer end. I can ping the printer from both the server and the client machines, the queue is empty and I have stopped and started the spooler but all to no avail. All other printers on server are working fine.

I have changed no other setting except for the drivers, can someone point me in the right direction please.

We currently have instances where multiple instances of the same printer are showing up on some machines.  I can go and remove the extra printers, but the printers will reappear only a few seconds later.  One machine has over 300 instances of the same printer listed in 'Devices and Printers'. From reports users receive an error when trying to print to some printers. They re-add the printer and then are able to print. It happens on domain and non-domain machines. It happens with different model printers using different drivers. Any suggestions would be appreciated.

Thanks

Hi,

I am having an issue using Microsoft Fax Server. I have been using Microsoft Fax Server for many years now. All faxes were submitted from Windows XP x86 clients and I never had problems.

I just upgraded clients to Windows 7 x64. Since there, people have issues when submitting faxes. I have not changed anything on the server side.

Here are the issues :Often (about 30% of the submitted faxes), the fax job is aborted with the error 0x0000000c  (Unknown fatal error). After that, all the next faxes get the same error.

Is there something wrong with Windows 7 ? Maybe the x64 version ? What can I do ? We submit lot of faxes and I have to resolve this issue as quickly as I can.

Thank you for helping me.

Best regards.

Matteo, .NET Developer and System Engineer

Just like this old post (http://social.technet.microsoft.com/Forums/windowsserver/en-US/c9a445e2-b28f-4e57-bfef-c1a2f89b8cd6/printers-not-being-published-in-active-directory) I'm noticing some issues with printers being published to AD.   However the error code I'm seeing is 8007200d. 

Q:\>err 8007200d
# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x200d
# for hex 0x200d / decimal 8205 :
  ERROR_DS_ATTRIBUTE_OR_VALUE_EXISTS                            winerror.h
# The specified directory service attribute or value already
# exists.
# 1 matches found for "8007200d"

An example of the event which only has fired for this specific printer.  ItIS published in AD however and can be found with the Find Network Printer wizard.   It's been on this print server for well over a year too.

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          9/13/2013 10:47:07 AM
Event ID:      322
Task Category: Publishing a printer in the Active Directory
Level:         Error
Keywords:      Active Directory,Classic Spooler Event
User:          SYSTEM
Computer:      PrintServer.MYDOMAIN.COM
Description:
While attempting to publish the printer to the Active Directory directory service, Windows failed to publish property printBinNames at LDAP://its-ad-a1.MYDOMAIN.COM/CN=PrintServer-AA-BB-4SE-COLOR-FXLSR,CN=PrintServer,OU=Level5,OU=Servers,OU=ManagedObjects,DC=ABC,DC=MYDOMAIN,DC=org.  Error: 8007200d

Using ldifde I queried AD to find out what it has about this specific printer:

ldifde -s its-ad-a1.ABC.MyDomain.org -r objectclass=printqueue -d "CN=PrintServer-AA-BB-4SE-COLOR-FXLSR,CN=PrintServer,OU=Level5,OU=Servers,OU=ManagedObjects,DC=ABC,DC=MyDomain,DC=org" -f test2.txt

Oddly enough, there is no printBinNames in the output:

dn: CN=PrintServer-AA-BB-4SE-COLOR-FXLSR,CN=PrintServer,OU=Level5,OU=Servers,OU=ManagedObjects,DC=ABC,DC=MyDomain,DC=org
changetype: add
objectClass: top
objectClass: leaf
objectClass: connectionPoint
objectClass: printQueue
cn: PrintServer-AA-BB-4SE-COLOR-FXLSR
description: 172.28.30.26, HP CM1415fnw
distinguishedName: 
 CN=PrintServer-AA-BB-4SE-COLOR-FXLSR,CN=PrintServer,OU=Level5,OU=Servers,OU=
 ManagedObjects,DC=ABC,DC=MyDomain,DC=org
instanceType: 4
whenCreated: 20130911233154.0Z
whenChanged: 20130911233204.0Z
uSNCreated: 629573861
uSNChanged: 629573861
name: PrintServer-AA-BB-4SE-COLOR-FXLSR
objectGUID:: b51qMLuOCUmGgwWkBWarAg==
flags: 0
uNCName: \\PrintServer.ABC.MyDomain.org\AA-BB-4SE-COLOR-FXLSR
versionNumber: 4
location: XXX
serverName: PrintServer.ABC.MyDomain.org
portName: 172.28.30.26
driverName: HP Universal Printing PCL 6 (v5.6.5)
priority: 1
printStartTime: 60
printEndTime: 60
printMaxResolutionSupported: 600
printOrientationsSupported: LANDSCAPE
printOrientationsSupported: PORTRAIT
printCollate: TRUE
printColor: TRUE
printLanguage: PCLXL
printShareName: AA-BB-4SE-COLOR-FXLSR
printSpooling: PrintAfterSpooled
printKeepPrintedJobs: FALSE
driverVersion: 1025
printMaxXExtent: 4318
printMaxYExtent: 9144
printMinXExtent: 762
printMinYExtent: 1270
printStaplingSupported: FALSE
printMemory: 131072
printRate: 12
printRateUnit: PagesPerMinute
printMediaReady: Letter
printNumberUp: 6
printMediaSupported: Oficio 8.5x13
printMediaSupported: Custom
printMediaSupported: 16K 197x273 mm
printMediaSupported: 16K 184x260 mm
printMediaSupported: 16K 195x270 mm
printMediaSupported: 10x15cm
printMediaSupported: 5x8
printMediaSupported: 4x6
printMediaSupported: Double Japan Postcard Rotated
printMediaSupported: A6
printMediaSupported: Japanese Postcard
printMediaSupported: Envelope Monarch
printMediaSupported: Envelope B5
printMediaSupported: Envelope C5
printMediaSupported: Envelope DL
printMediaSupported: Envelope #10
printMediaSupported: B5 (JIS)
printMediaSupported: A5
printMediaSupported: A4
printMediaSupported: Executive
printMediaSupported: Legal
printMediaSupported: Letter
printerName: AA-BB-4SE-COLOR-FXLSR
printPagesPerMinute: 12
url: http://PrintServer.ABC.MyDomain.org/AA-BB-4SE-COLOR-FXLSR
objectCategory: 
 CN=Print-Queue,CN=Schema,CN=Configuration,DC=rootad,DC=MyDomain,DC=org
shortServerName: PrintServer
printDuplexSupported: FALSE
dSCorePropagationData: 16010101000000.0Z

Why then would Windows through EventID 322? printBinNames doesnt exist to conflict with per the error code thrown.

Even more odd is that I believe this error was preventing another newly crated printer from being published.   A new printer was created on the PrintServer. But the printer would now show up in the Find network printer wizard.  Right at the same time I added this new printer, the Event ID 322 for the unrelated printer (AA-BB-4SE-COLOR-FXLSR) was logged.  Odd.

I then unpublished and republished the AA-BB-4SE-COLOR-FXLSR printer.  Windows logged both success and the same failure!  Also interesting is the published name it used is different

9/13/2013 12:47:19 PM - The printer was successfully removed from the Active Directory directory service. Print queue CN=PrintServer-AA-BB-4SE-COLOR-FXLSR was successfully deleted from container LDAP://its-ad-a1.ABC.MyDomain.org/CN=PrintServer,OU=Level5,OU=Servers,OU=ManagedObjects,DC=ABC,DC=MyDomain,DC=org. The printer can no longer be located by searching Active Directory. No user action is required.

9/13/2013 12:47:19 PM - The printer was successfully published to the Active Directory directory service. The print queue CN=PrintServer-AA-BB-4SE-C0064222313 was successfully created in container LDAP://its-ad-a2.ABC.MyDomain.org/CN=PrintServer,OU=Level5,OU=Servers,OU=ManagedObjects,DC=ABC,DC=MyDomain,DC=org. No user action is required.

9/13/2013 12:47:19 PM - While attempting to publish the printer to the Active Directory directory service, Windows failed to publish property printBinNames at LDAP://its-ad-a2.ABC.MyDomain.org/CN=PrintServer-AA-BB-4SE-C0064222313,CN=PrintServer,OU=Level5,OU=Servers,OU=ManagedObjects,DC=ABC,DC=MyDomain,DC=org.  Error: 8007200d