| Event Id | 36 |
| Source | |
| Description | PrintQueue CN=VM-MEMBER-01-testprinter740 was successfully created in container LDAP://vm-child2-dc1.child2.ROOT.COM/CN=VM-MEMBER-01,OU=Print Srv,DC=child2,DC=ROOT,DC=com. |
| Event Information | If a large number of printers is already installed on a Windows 2000 print server (for example, more than 400), if you remotely create and configure more printers, the List in the directory printer property is no longer checked for all the newly created printers. This problem occurs even if you do not change the default setting to publish new printers or if you explicitly configure a separate Group Policy object (GPO) that automatically publishes new printers in Active Directory. This problem only occurs if you remotely create and configure these printers by using a script, for example, if you use the Prncfg.vbs script from the Windows 2000 Resource Kit. CAUSE: If you remotely create a printer, Windows does not check the default setting or the GPO to publish new printers in Active Directory. RESOLUTION: To resolve this issue, use the Prncfg.vbs script from the Windows 2000 Resource Kit, and then set the "List in the directory" flag for remote creation, for example: cscript prncfg.vbs -s -b "\\print server\printer to publish" +published If this problem occurs, the List in the directory printer property is still checked automatically in the following scenarios: You use the graphical user interface (GUI). You run the same script locally on the print server. After the List in the directory printer property is set during remote creation, the following event ID message will be logged in the system event log of the print server. |
| Reference Links | "List in the Directory" Printer Property Is Not Automatically Checked on New Printers |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.