Discussion Locked

2Kas in an NT4 Domain Applying Policies

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hey All,

I was forced to do an on the fly install of several Win2kAS app and terminal servers in an existing NT4 Environment. The sr. administrator at the site has engineered his environment so that user policies and machine policies are downloaded upon login. One of these happens to be global IE lockdown policy which criples the GUI of a 2K box. Has anyone ran into this before in an environment undergoing migration to 2K. My fears have been realized in that the admin has lost trach of what policies are downloaded and their cumulative effect.

Any Sage advice on handling this would be appreciated.TIA

Nomad

7 replies

by mrtibbs

We had a possibly related problem: We couldn't get 2K workstations to recognise their network policy.
Our work-round was to view the pc's local policy files with a different adm filter. This revealed the location of the network .pol file it was trying to load and allowed us to point to a different one customised for our 2K boxes.

by jaystar

Since they are not working anyway, I would build a BDC for the domain, copy the netlogin directory over to it, isolate the servers in a lab environment, promote the bdc to a pdc, and go through the ntconfig.pol file to find out what policy is killing you. Since these are newly configured machines we know they had to pull the initial .pol from the ntconfig.pol in the netlogin directory from one of the BDC's or the PDC.
From there I would find out if it was a Machine or User issue by creating a new computer with your terminal server's computer name and removing all the custom settings.

Good luck -
Jay

by timthetoolman

The domain level policies take preference over any local policies you try to add - so dont bother looking at the Win2K server...

You'll have to go to the PDC and modify its policies (the ones being applied to your new servers) to exclude the Win2K servers.

Cheers,
Tim.

This discussion is closed to new replies.