Re: Point and Print Restrictions policy

Thank you for taking the time to suggest your response Alan.

I'm not sure I know how to have a cluster's name show up as a computer
account. I did a search of the computers in this domain (domain A in my
example) and it did not show up. The computer names of the nodes show up of
course.

Our cluster is as follows.

entserv01 (node1 computer name)
entserv02 (node2 computer name)
entserv (cluster name)
entserver (printer virtual server name)

Yes we can print to printers on this cluster (across domains) successfully
if the driver is already present with a normal user.

Thanks for your suggestion on making changes at the client level however, we
are trying not to have to do this since we have many clients to touch.

Can you elaborate on your suggestion given this new information?

Please let me know if I can give you any more information that might be of
help.

Brandon

"Alan Morris [MSFT]" wrote:

> The cluster may not have a machine account on the domain thus the policy
> cannot verify the machine is "trusted". What are the cluster name
> parameters?
>
> This policy blocks the installation of the driver unless the driver is inbox
> on the XP client. Can you make a connection to a printer that is in the
> list of XP print drivers?
>
> When disabling the policy there is nothing to do on the server. The policy
> must be disabled on all clients. You can also add the clustername and the
> node names to the trusted server list on each client.
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "JB" <JB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:471E3B3E-B83D-4342-92A7-0671DCAF746E@xxxxxxxxxxxxxxxx
> > Hello,
> >
> > We have an issue with the Point and Print Restrictions policy. We are
> > getting the following message when trying to connect to a printer:
> >
> > "A policy is in effect on your computer which prevents you from connecting
> > to this print queue. Please contact your system administrator."
> >
> > We have found the following document that refers to this error message...
> > http://support.microsoft.com/?kbid=319939
> >
> > Our configuration is as follows:
> >
> > A Windows XP SP2 user in Domain B is attempting to add a new printer from
> > a
> > Windows 2003 print cluster in Domain A. Both domains are in the same
> > forest.
> >
> > Domain A is our Windows 2000 AD Forest root. Domain B is another domain
> > in
> > the forest.
> >
> > This is a new print cluster that has worked for months in testing with
> > admin
> > level users. However we didn't do much testing for normal (non local
> > admin)
> > users and now realize we have this issue.
> >
> > We've found that if an admin logs in and maps the drive first then the
> > printer will then map and print correctly for the normal user. This
> > implies
> > that the issue is the normal (non-admin) user copying the printer drivers
> > for
> > the first time.
> >
> > We have verified the setting is disabled in reference to
> > http://support.microsoft.com/?kbid=319939 at the domain level for Domain
> > A,
> > at the domain level of Domain B and locally for each Windows 2003 print
> > cluster node.
> >
> > We have also verified there isn't any group policy print driver loading
> > restrictions in either domain.
> >
> > In searching for other people experiencing this issue via google it
> > appears
> > others have solved their issue via the article's suggestions. We however
> > have not and the way we read the article is that it applies to cross
> > forest
> > printing - which is not our case.
> >
> > Any suggestions on what else to look for in our situation is greatly
> > appreciated.
> >
> > Brandon
>
>
>
.

Relevant Pages

  • Re: XP pcs cannot add printer as user
    ... Windows Printing Team ... >> impacts installing a printer driver. ... >> If you have an NT4 based domain, this policy will not work properly ... this policy setting is not configured. ...
    (microsoft.public.win2000.printing)
  • Re: cscript prndrvr.vbs doesnt work with Windows 2003 server in clust
    ... On Windows XP and Windows ... Windows NT/2000/2003 Cluster Technologies ... > I'm trying to install a printer on Windows 2003 server cluster. ... I use the option -s to install the driver on cluster ...
    (microsoft.public.windows.server.clustering)
  • Re: cscript prndrvr.vbs doesnt work with Windows 2003 server in clust
    ... On Windows XP and Windows ... Windows NT/2000/2003 Cluster Technologies ... > I'm trying to install a printer on Windows 2003 server cluster. ... I use the option -s to install the driver on cluster ...
    (microsoft.public.win32.programmer.wmi)
  • Re: Restricting Desktop Computers to view USB Flash Drive
    ... Not in a secure way. ... Disbaling the driver via ADM: ... POLICY "USB-MassStorageDriver" ... Mark Heitbrink - MVP Windows Server ...
    (microsoft.public.win2000.group_policy)
  • Re: Driver deleted by policy
    ... The policy disabled the service "Windows Image ... > the policy runs only the scanner driver disappears the printer driver is ... >> setting on Windows Server 2003 family products, the installation of ...
    (microsoft.public.win2000.group_policy)
Loading