Local users and groups

i have a windows 2003 server and i can't find "local users and groups."  i have gone to the computer management screen and i thought that "local users and groups" should be on that screen under "system tools" but it is not there.  what am i missing?
LVL 1
scottspiveyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jay_Jay70Commented:
Sounds like your machine is a Domain Controller. Once its a DC, there is no more SAM (local Users and Groups), you access users through the AD Users and Computers snap in
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
scottspiveyAuthor Commented:
so when i go to administrative tools and i have AD users and computers that is all i will have on this server?  so then do i set up users as administrators and such when my machine is a domain controller?  i need to add a user to allow them to logon to the server through RPD but i don't want them to have full access to my machine.  i thought i controlled that by the group i added them to.
0
mikeleebrlaCommented:
yes that computer is a domain controller.

>>then do i set up users as administrators and such when my machine is a domain controller?
no, there is NO such thing as a local user or a local group on a domain controller,,,, that is why you don't see the local users and groups in system tools
if you would like to allow a user to log into your DC via remote desktop connection
1. enable remote desktop connection on that machine if you haven't already
2. create an account for them in active directory users and computers
3. go back into remote desktop connection and allow that person to use RDC
4.  if you allow a user to log in 'locally' like this to your DC, they can do basically whatever they want unless you REALLY tweak their account

0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Jay_Jay70Commented:
you want to keep that machine away from users as much as possible, this is like the entire engine of your domain
0
scottspiveyAuthor Commented:
so then if i go to each individual user account can i keep them from being able to access this machine through RDC?
0
mikeleebrlaCommented:
>>so then if i go to each individual user account can i keep them from being able to access this machine through RDC?
no, just the opposite.  Only select the users you WANT to give access to when you are setting up RDC.  you do this by rightclicking 'my computer' choose properties, then go to the remote tab, then select 'select remote users'
0
Jay_Jay70Commented:
you can also enable or disable the terminal service logon right on the user account itself - if they are going to log on they will need to be part of the "remote desktop users group"
0
scottspiveyAuthor Commented:
preciate the help guys and the quick response.  i will get this all cleaned up and be on my way.

thx.
0
Hypercat (Deb)Commented:
On a domain controller, there are no local users and groups, they are all domain-level users and groups.  Access to the domain controller itself is, as you thought, controlled through group membership.  The only user that, by default, has the ability to log on directly to the domain controller is the Administrator account, by virtue of its membership in the Built-in Administrators group.  When you create new users in AD Users and Computers, their default group membership is the Domain Users group as well as several "hidden" group (hidden in that they don't show on the group membership list), one of which is Authenticated Users.  This Domain Users group has access to the domain controller machine and files and folders stored or applications running on it only by logging on at a workstation that is a member of the domain.  The Authenticated Users group is a built-in group that can be used to specify that a right or permission is given to the users only after they have been authenticated (i.e., logged in) on the domain.  

You do NOT want to allow your users to log directly on to the domain controller.  This is a huge security risk to your software and data.  However, there are some types of connections that require the user to have "log on locally" rights, even though they are not actually physically sitting at the machine.  If this is the case, you can give the Authenticated Users group "log on locally" rights by editing the Domain Controllers Security Policy.  To do this:

1. Open the DC security policy management console from your Administrative Tools menu. Expand the Security Settings/ Local Policies object and click on User Rights Assignment.

2. On the right-hand pane, there is a list of rights.  Find the "Log on locally" right, double-click it and click Add User or Group to add the Authenticated Users group to this right.

Hope this helps!
0
Jay_Jay70Commented:
Cheers mate and all the best
0
internethotspotCommented:
I am in the same boat, HOWEVER I don't want to continue using the machine as a 'Domain Controller'.  Instead, I clicked on Start - Run - DCPROMO /FORCEREMOVAL

This should force the removal of the domain controller, essentially demoting the machine back to a member server instead of it being a domain controller.

However this is esentially a rollback, and everything the Active Directory created will be removed and control given back to the registry & SAM.  If this doesn't work, I will reinstall the entire server... ack!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.