Windows Forum

Ask something
Discussion Locked

Local Policy Settings

0 helpful
7 replies

by jknowledge

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running a Win2k upgrade from 98 that was installed by a previous NetAdmin who no longer is in contact with the company. When I set the machine to logon to the network, it restarted, and now no matter how I log on, it tells me that the Local Policy will not allow for Interactive Logon. I have tried disconnecting the Machine from the network and logging on, and logging on to the local machine, instead of the network. Is there any way to recover this without reinstalling the OS?

7 replies

by caliche

Everytime a W2K workstation is added to the network, your network ID has to be added either to the local users group or the powerusers group or the administrators group (depending on the kind of local rights you need). You have to sign on to the local machine using the local administrator account to be able to add your network account to the local groups. After this is done you should not have any problems signing on using your network account.

by timwalsh

Couple of things to check:
1. You mention attempting to log on to the local machine. Did you do so using the local Administrator account? If not, try that and reset the policy.
2. Domain Group Policy will overide local policy settings. If this particular policy is not defined at the domain level, the local policy will remain in effect. Try defining the policy at the domain level. NOTE: Since security policies are propogated during boot-up, make sure you reboot the workstation after changing the domain group policy.

Hope this helps.

by junething

WOW, I see u're name quite often USER DELTED!!! =) K, now for u're answer.

In Win2k networked enviorment, there are two choices, peer-to-peer and Domain. In peer-to-peer, u would only have to worry about the "local policy settings". However, in a Domain network, there are 4 different policies u need to check.

There are:
1. Local
2. Site
3. Domain
4. OU

Little explaination, when win2k boots up, it loads the local policy, then it logs on to the network, and gets the Site policy, then it goes to the domain policy and finally, OU policy. Reason for this is beyond the answer, but lets me just tell u that, one of those policy is over riding the pervious one. Suggestion, work backward. See if u have any OU policys that prevent "log on locally", then go to Domain policys, then go to site, then go to local.

Always, there is MMC for Local Policy and for domain (if u know how to use it). One cool thing is that u can't export the settings for lets say OU policys to another computer, but u can link it using the MMC.

Good luck

This discussion is closed to new replies.