asked on
Block all 'Domain Users' from logon to 30 critical PCs except a group of 40 authorized users
https://www.experts-exchange.com/questions/29056334/Steps-to-block-AD-IDs-from-login-to-30-critical-PCs.html
I'll need to revisit the above EE post : I've just implemented the simplest solution by Lee W ie
ID: 42292327 by removing "Domain Users" from the local "Users" group on 2 of the PCs, rebooted them but using one of the 'unauthorized' AD Id, could still logon to the 2 critical PCs, so this solution did not work. Why is it not working as Lee W suggested?
Under the local "Users" group, there are 2 more members (after removing "Domain Users"): could these 2 groups be the reason why the unauthorized AD Ids could still login?
1. NT AUTHORITY\Authenticated Users (S-1-5-11)
2. NT AUTHORITY\INTERACTIVE (S-1-5-4)
I guess it's not safe to remove the above 2 from local "Users" group, right?
I'm looking for the next simplest solution, so which among them are easiest
considering there are 30 PCs with 40 authorized staff?
Currently if we issue "Net user /domain any_AD_Id" , output will show
a line "Could logon to any workstations" : guess this is (one of) the problem
I'll need to revisit the above EE post : I've just implemented the simplest solution by Lee W ie
ID: 42292327 by removing "Domain Users" from the local "Users" group on 2 of the PCs, rebooted them but using one of the 'unauthorized' AD Id, could still logon to the 2 critical PCs, so this solution did not work. Why is it not working as Lee W suggested?
Under the local "Users" group, there are 2 more members (after removing "Domain Users"): could these 2 groups be the reason why the unauthorized AD Ids could still login?
1. NT AUTHORITY\Authenticated Users (S-1-5-11)
2. NT AUTHORITY\INTERACTIVE (S-1-5-4)
I guess it's not safe to remove the above 2 from local "Users" group, right?
I'm looking for the next simplest solution, so which among them are easiest
considering there are 30 PCs with 40 authorized staff?
Currently if we issue "Net user /domain any_AD_Id" , output will show
a line "Could logon to any workstations" : guess this is (one of) the problem
Windows OSActive DirectoryOS Security
Last Comment
sunhux
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
1. NT AUTHORITY\Authenticated Users (S-1-5-11)
2. NT AUTHORITY\INTERACTIVE (S-1-5-4)
I guess it's not safe to remove the above 2 from local "Users" group, right?
Why wouldn't it be?
As long as the user is a member of AT LEAST 1 group in the list of Users, that should be all you need.
I wouldn't remove Interactive, but I would definitely remove Authenticated Users - Any user that logs in is authenticated!
Further, it's extremely unwise implementing ANY forum recommendation without TESTING first. And testing is easy - setup a VM and TEST!
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
> I would definitely remove Authenticated Users - Any user that logs in is authenticated!
If we remove the above, then the authorized payment staff also won't be able to login then?
So do we still remove this??
I'm not Wintel-trained: care to provide step by step (with screenshots attached here) instructions?
MacClean's instructions are quite detailed but will help if screen shots are attached
If we remove the above, then the authorized payment staff also won't be able to login then?
So do we still remove this??
I'm not Wintel-trained: care to provide step by step (with screenshots attached here) instructions?
MacClean's instructions are quite detailed but will help if screen shots are attached
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
If we remove the above, then the authorized payment staff also won't be able to login then?
So do we still remove this??
Of course... and you ADD the payment staff's group...
You have to be careful with the allow log on to include all the requisite groups security group and administrators..
Another option is to use restricted groups on these systems, kicking out all users from users to only include a security group.
In either situation a member of this security group is authorized to access all the restricted PCs. If you need to more tightly manage access, this means you have to have a security group for each system where each system will only allow local login to members of the group named for the computer.
This way you more tightly control the number of individual who can have access to each system.
Another option is to use restricted groups on these systems, kicking out all users from users to only include a security group.
In either situation a member of this security group is authorized to access all the restricted PCs. If you need to more tightly manage access, this means you have to have a security group for each system where each system will only allow local login to members of the group named for the computer.
This way you more tightly control the number of individual who can have access to each system.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
So with the instructions from Arnold & Lee (the last 3 above), do I still need to:
a) create an OU to group these 30 critical PCs ? (this is rather complicated for me to comprehend as a non-Wintel person)
b) remove the following from being a member of the local "Users" group :
1. NT AUTHORITY\Authenticated Users (S-1-5-11)
2. NT AUTHORITY\INTERACTIVE (S-1-5-4)
a) create an OU to group these 30 critical PCs ? (this is rather complicated for me to comprehend as a non-Wintel person)
b) remove the following from being a member of the local "Users" group :
1. NT AUTHORITY\Authenticated Users (S-1-5-11)
2. NT AUTHORITY\INTERACTIVE (S-1-5-4)
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Very much appreciated Mclean.
Give me 2 more days & I'll close this
Give me 2 more days & I'll close this
Likely, the two users in question had membership in a group that at some point became authorized.
The other difficulty inherent to a situation you find your self in.
I know users can be limited to the computers to which they can login, have not looked wherhe the computer object can be set within ad which users, groups are authorized to access this system.