Group Policy v System Policy Editor 1

[mattsummat]

I am in the process of upgrading from Windows NT 4 server to Windows 2000 Server. I have two questions that I would be extremely grateful for any answers to:

1)Is the Group Policy editor in 2000 server supposed to be a replacement in every respect to Poledit? i.e. Is there anything that can be achieved through Poledit that Group Policy does not support?

2)I have followed all the instructions in the Sybex MCSE manual on configuring Group Policy. However the group Policy object that I am trying to create - one that sets restrictions on users' desktops - works on the server only, it does not affect any of the client machines. I have created an OU, linked it to a Group Policy and added a group and user to the OU. When I logon as that user to the server, Group Policy works. However when I attempt to do this on the client machine Group Policy appears to be bypassed. I am running a network with one domain and no local policy is defined on the client machine. Can some one please tell me how I can replicate the function of Poledit to restrict users on all machines through the use of Group Policy - or is this something that Group Policy is not designed for? Again, many thanks in advance to anyone who can help.

 

[greg013]

One thing to keep in mind: GPOs work with W2k clients only. If you have downlevel clients (NT, ME, 9x) the GPOs will NOT work.

As far as your first question, I'm pretty sure you can do everything with Group Policy Editor you could with Poledit.

 

[Breadmaster]

I have the same problem, i can make the policy work on the server but not on the workstations!

poledit at least was straightforward.

can anyone help (us)?

 

[brontosaurus]

More often than not, this is a DNS issue. Install the W2K support tools and run a NETDIAG to view if there's any DNS resolution problems. If so, they might be repaired by running a NETDIAG /FIX. In addition, if you run the tools DCDIAG and GPRESULT you may get more insight....

 

[Breadmaster]

I have solved this problem by specifying a DNS server on the workstations......doh! my bad.

cheers for the help!