Re: Point and Print Restrictions policy
- From: "Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Dec 2005 16:19:29 -0800
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
.
- Follow-Ups:
- Prev by Date: Re: Name and time of Print out on each Page
- Next by Date: Re: Point and Print Restrictions policy
- Previous by thread: Re: Name and time of Print out on each Page
- Next by thread: Re: Point and Print Restrictions policy
- Index(es):
Relevant Pages
|
