Point and Print Restriction Policy change

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

One other question, if AD group policy change can be used can it be changed
at an OU level or does it need to be done at a domain root level. Thank you.

"john" wrote:

> Hi, can someone tell me if the point and print restriction policy change can
> be pushed down to the client via an Active Driectory Group Policy change? Or
> can it only be changed through a local policy change? I am having the
> problem where non-local admins get the fiollowing error when installing new
> printers:
>
> A policy is in effect on your computer which prevents you from connecting to
> this print queue. Please contact your system administrator.
>
> I have read the following KB article and am still unsure the steps I need to
> take.
> http://support.microsoft.com/defau [...] -us;319939
>
> Would disabling the point and print restriction locally on the print server
> let non administrator XP clients install the printers without changing the
> client profile? Has anyone changed this policy successfully through the a
> registry change as the KB article mentions?
>
> Ideally I'd like to use AD to have the policy change but it is not
> propogating to the clients after the group policy change is made. Thus my
> question of how people are deploying the policy change to correct this issue.
>

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

You should be able to push this policy in the default GPO. Are you pushing
just the restriction policy of are you adding trusted servers to the
clients?

--
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.

"john" <john@discussions.microsoft.com> wrote in message
news:A00BB3AF-2968-413C-AD75-E9D66FAAF856@microsoft.com...
> bump, anyone??
>
> "john" wrote:
>
> > One other question, if AD group policy change can be used can it be
changed
> > at an OU level or does it need to be done at a domain root level. Thank
you.
> >
> > "john" wrote:
> >
> > > Hi, can someone tell me if the point and print restriction policy
change can
> > > be pushed down to the client via an Active Driectory Group Policy
change? Or
> > > can it only be changed through a local policy change? I am having the
> > > problem where non-local admins get the fiollowing error when
installing new
> > > printers:
> > >
> > > A policy is in effect on your computer which prevents you from
connecting to
> > > this print queue. Please contact your system administrator.
> > >
> > > I have read the following KB article and am still unsure the steps I
need to
> > > take.
> > > http://support.microsoft.com/defau [...] -us;319939
> > >
> > > Would disabling the point and print restriction locally on the print
server
> > > let non administrator XP clients install the printers without changing
the
> > > client profile? Has anyone changed this policy successfully through
the a
> > > registry change as the KB article mentions?
> > >
> > > Ideally I'd like to use AD to have the policy change but it is not
> > > propogating to the clients after the group policy change is made.
Thus my
> > > question of how people are deploying the policy change to correct this
issue.
> > >

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Yes it should. Are there any higher GPs that might be over writing this
setting? I'm not much help in the AD area, I'm just a printer guy.

--
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.

"john" <john@discussions.microsoft.com> wrote in message
news:C3CA0DED-274D-43D2-9996-B43746C67072@microsoft.com...
> I just want to push disabling the point and print restrictions so that any
> printer can be installed by non local admins. I have it set to push at an
OU
> level and it is not working.
>
> "Alan Morris(MSFT)" wrote:
>
> > You should be able to push this policy in the default GPO. Are you
pushing
> > just the restriction policy of are you adding trusted servers to the
> > clients?
> >
> > --
> > 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.
> >
> > "john" <john@discussions.microsoft.com> wrote in message
> > news:A00BB3AF-2968-413C-AD75-E9D66FAAF856@microsoft.com...
> > > bump, anyone??
> > >
> > > "john" wrote:
> > >
> > > > One other question, if AD group policy change can be used can it be
> > changed
> > > > at an OU level or does it need to be done at a domain root level.
Thank
> > you.
> > > >
> > > > "john" wrote:
> > > >
> > > > > Hi, can someone tell me if the point and print restriction policy
> > change can
> > > > > be pushed down to the client via an Active Driectory Group Policy
> > change? Or
> > > > > can it only be changed through a local policy change? I am having
the
> > > > > problem where non-local admins get the fiollowing error when
> > installing new
> > > > > printers:
> > > > >
> > > > > A policy is in effect on your computer which prevents you from
> > connecting to
> > > > > this print queue. Please contact your system administrator.
> > > > >
> > > > > I have read the following KB article and am still unsure the steps
I
> > need to
> > > > > take.
> > > > > http://support.microsoft.com/defau [...] -us;319939
> > > > >
> > > > > Would disabling the point and print restriction locally on the
print
> > server
> > > > > let non administrator XP clients install the printers without
changing
> > the
> > > > > client profile? Has anyone changed this policy successfully
through
> > the a
> > > > > registry change as the KB article mentions?
> > > > >
> > > > > Ideally I'd like to use AD to have the policy change but it is not
> > > > > propogating to the clients after the group policy change is made.
> > Thus my
> > > > > question of how people are deploying the policy change to correct
this
> > issue.
> > > > >
> >
> >
> >