The following is an example that illustrates the potential complexity of Windows host accounts interacting with Windows Domain accounts. Suppose Windows Workstation host named CRUNCH has a local user account named Peter. This Windows Workstation is part of the domain named ENGINEERING. This domain is provided by a Windows Server which also has a user account named Peter. In this example, the ENGINEERING domain is the default domain of the host named CRUNCH. The following table shows the possible results of what would happen if a person tried to login to CRUNCH.
Table B–1 Using Domain Accounts|
Login Name |
Result |
|---|---|
|
CRUNCH+Peter |
Peter is logged in with his account as a local user of the machine CRUNCH. |
|
ENGINEERING+Peter |
Peter is logged in with the account provided by the Windows Server hosting the ENGINEERING domain. |
|
Peter |
This approach is equivalent to using ENGINEERING+Peter because CRUNCH has ENGINEERING as it's default domain. Otherwise, the local account would be used. |
Each domain has a special user account providing super user access. The default name for that account is Administrator. Only this Administrator can start applications on behalf of other user accounts without needing to know the Windows password for each account. So, a local administrator can start applications for local users and a domain administrator can run processes under the account of domain users.