Windows Server 2003 SP2 - Windows XP Pro SP2
--
Dennis
Go to computer configuration>Windows settings>security settings>File system.
On the right pane rightclick and take Add File. Browse to the default location
from the file you like to restrict on one workstation and set the security
settings like you want. Test it on one machine and then deploy the policy
to the OU where the workstations of the users are.
Best regards
Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders
It is perfectly useless to know the right answer to the wrong question.
"Dennis" <Den...@discussions.microsoft.com> wrote in message
news:4BEAAEF4-4AE4-4D93...@microsoft.com...
Your user(s?) appear(s) overpowered.
Addressing that would be the infrastructurally correct approach.
Assuming excess privs is required, whyever, then look in the User
branch in GP in admin templates, where in Windows Components
you will find Microsoft Management Console, which has an agile
restricted/permitted snap-ins capability (you can even frustrate a
Domain Administrators member with it).
You might want to also alter permissions on services as the User
could adjust services without use of any mmc like services.msc.
That is touchy, especially if there are administrative duties of the
(not) overpowered user(s), repetitive (automate with sc), difficult
to maintain in face of future new services, but doable.
Roger
Roger