G
Guest
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/default.aspx?scid=kb;en-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.
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/default.aspx?scid=kb;en-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.