[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2263
  • Last Modified:

Restrict logon with Group Policy

I have a Windows 2k domain with XP workstations.  I have one workstation that I want to restrict logon to one user, let's call him joe.  I would like to make this change on the server rather than on the client to make it easier to manage.
I created a new OU and placed the computer in that OU.  I then created a new group policy object for that OU and I defined the 'Log on Locally' to have just joe in the list.
I then when to the client machine and ran gpupdate and restarted.  I tried logging on with a different user(besides joe, and not an aministrator) and it still let me login.
I looked at the Local Security Policy on the client and it had inherited the correct settings from Active Directory - that is, Log On Locally had Administrators(which I guess is just thrown in by default) and Joe in the list.  I could tell that it had inherited because the icon was different and I was not able to update it.
So, even through only Administrators and Joe are in the list, it is still letting others logon.  The only way that I have found to keep other users out is to add them to the Deny Log On Locally but I don't want to use that because then I would have to modify that list every time I create a new user.
Also, I do not want to create a group that contains all users except Joe.
0
ErnieExpert
Asked:
ErnieExpert
  • 3
  • 2
  • 2
2 Solutions
 
IsigowCommented:
Add 'Domain Users' to the Deny logon Locally list
That should remove all other users from the ability to logon, except that Joe has an exception already so he should still be able to.

Isi
0
 
ErnieExpertAuthor Commented:
no, that will not work because Deny permissions take precedense and since Joe is member of Domain Users, Joe would then be denied permission.
0
 
chadCommented:
you may have a domain policy that is overriding this setting.
also check the permissions on the gpo for the computer OU.  joe needs read and apply


http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/gpotool-o.asp
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/gpresult-o.asp
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
ErnieExpertAuthor Commented:
The domain policy does not have anything defined for 'Log on Locally'  so I don't think that that is conflicting.
I checked the permissions and Authenticated Users have Read and apply permission

I ran gpresult on the workstation and it showed that it was in the new OU that I created for it.  It also reported that it was applying the group policy from the new OU so that confirms that it is applying it.

0
 
IsigowCommented:
Odd thing is, I just tried this on a 2k server and it worked fine, on an XP workstation it still allowed Domain Users in...
Anyone know of why XP (and possible 2k workstation) does this while server does not? (not a DC, just a standard server)

Isi
0
 
chadCommented:
you best bet maybe to edit the local policy on the machine. instead of the OU level.
this will ensure there are not any compatibility issues.

http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
0
 
ErnieExpertAuthor Commented:
Thanks Isigow for taking the time to test this out.  I ran the same test and came out with the same results.  I tried kabaam's suggestion and that worked.  It did not exactly answer my request bacause I said that I wanted to be able to manage it from the server, however, this seems to be the best solution for now.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now