Discussion Locked

System Policies

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I've set up a system policy, on NT Server (PDC) which is supposed to restrict the user from accessing the 'DISPLAY' in Control Panel. I've then gone and rebooted the users Win XP Pro PC and can still access the DISPLAY. I've also set other restrictions that haven't worked. Is there something I've missed out?

2 replies

by erikdr

System policies on NT Servers end up in a file called NTCONFIG.POL. This, in turn, is automatically applied upon logging on to, yes, a NT Workstation.

Sorry, you can _not_ use them to apply policies to W2K Pro and XP clients. Logical - the desktop has many many settings which a NT Server has not a clue about, and MS did never want to make any mapping. (Novell ZENworks however did make it, you can have a single policy there valid for NT/W2K/XP/W9x....)

Normally MS would recommend using W2K and W2K3 Group Policy for doing what you want, including ADS. There is a reasonable workaround however in your case. I don't know all the details but can help you a bit on the way (others please follow up?!):
1) Take one reference XP Pro machine.
2) Design a 'group policy' on this machine using the same MMC snapin that is used on ADS servers Group Policy.
3) However, do not save the settings in ADS (which you do not have in place of course...) but as a file on the server.
4) Upon login, force the XP workstations to apply this file similarly as a NT Workstation would apply NTCONFIG.POL.

I've read a few stories of people who got this working (after all it is exactly the same model which Novell ZEN for Desktops uses to store group policies in, in their case, eDirectory and still have them applied to XP desktops upon login). So good luck!

At your service,

- The Netherlands

This discussion is closed to new replies.