2007-09-17 06:20:01 UTC
We have a Win2K3 Std domain at Central Office. We have Win2K3 std DC at our
site. We have installed a new Win2K3 - R2 Std Server as File & Print Server.
This is a member of the domain.
The schema is upgraded to R2 Version 31. There are no DNS or Replication
There is an option from the Print Management in Win2K3 R2 to deploy the
printer with Group Policy. Link to same is -
Now when i follow the steps as mentioned in the above link, the printer is
not getting deployed with Per User settings. I used the parameter to log the
error and it was as below
Microsoft Windows Operating System Deploy Printer Connections Utility v1.0
Copyright (C) Microsoft Corporation. All rights reserved.
... Logging enabled by command line switch.
... Logging started at 11:52:41 AM 9/16/2007.
... Found and applied this GPO: DeployPrinters.
... Found Deployed Printer Connection setting \\server3\Printer in Active
... Failed to search local GPO. Access is denied.
... Registry search for installed printers failed. The operation completed
... Failed to deploy per user connection \\server3\Printer. Access is denied.
Since there was no mentioning about the printer sharing, i did not share the
printer. After i shared the printer with any name, the user were able to get
the printer connection. But i am not sure, that do we have to share the
printer or the script would connect it without sharing ? (wild thought !!!)
Further i have created a group and the required users are members of this
group. So only users i add in this group gets the connection to particular
printer. But when i remove the user from the group, the printer should not be
deployed for that user, but i see after deploying the printer once, it does
not get disconnected even if the user is not a member of the GP that deploys
that printer. Further if the printer gets deployed with GP then the log would
show the connection made, which does not. So the GP is not actually applied,
but the printer connections seems to be permanent.