Windows 8 multiple domains

It incorrectly implies that you aren't signing in to the computer if you sign in through another domain. The whole point of all the screens and functions covered so far in the article, though, is to sign in to a computer , which is what you're doing whether you use a domain user account or a local user account.

Microsoft also ignored the fact that you can just type a period as a substitute for the computer name. The message in the little box above should really say something like this:.

To sign in to this computer using a local user account, precede your local user name with a period and backslash, like this:. There are more quirks you might discover on this particular sign-in screen, particularly related to local user accounts. But, these are beyond the scope of this article, which is meant to focus on signing in to the proper domain account on a standard business network.

Fox Micro Sawtelle Blvd. See Terms of Use. Your preference is set to , but this page was cached by your web browser in standard mode. Please refresh the page to see it in your preferred mode. Switch to tablet Switch to mobile phone Learn more. What is the reason for both domains? Would it make sense to migrate machines and roles from domain2 into domain1? The reason for the 2 domains is we were purchased by the home office company. All the accounting was done for our region here on an existing server.

The setup is Domain1, Domain2 with no trusts. Now that we are on the mpls and they have added our server to their DNS, mapped drives work fine going both ways. The issue is with an excel addin accounting uses that will only work here in this office. I've asked other questions about this in other threads. I was just seeing if since the people that came here this week but connect to the domain1 server were sitting 15 feet from the domain2 server, was there a way for them to switch domains and not have to connect to the remote desktop machines to run the addin.

I think the simplest solution would be to just provide them another laptop or a desktop for them to use while they are in the office. They'll have more screen real-estate and they won't need to worry about logging into and out of the system every time they need to make a change.

Other than that, I would think that what you're already doing RDP is the best solution. It sounds like this may only be temporary too. Details required :. Cancel Submit. Afzal Taher. Hi, This thread will be better suited in the Microsoft Technet forums as the computers are on a Domain. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Meeting business needs There are several business needs that might justify the creation of multiple domains.

Business needs can be broken down even further into organizational and political needs. One of the organizational reasons for using multiple domains is to avoid potential problems associated with the Domain Administrator account.

At least one user needs to have permissions at this level. If your organization is unable or unwilling to place this level of trust with all business units, then multiple domains may be the best answer. Since each domain maintains its own security database , you can keep permissions and resources isolated.

Through the use of trusts, however, you can still share resources. A political reason might arise if you had two companies that merged with two separate but equal management staffs, and two sets of officers.

In such a situation, you might need to have Active Directory split into two separate databases to keep the security of the two groups separate. Some such organizations may need to keep the internal groups separate by law. If this is the case, a multidomain architecture is born to provide exactly this type of pristinely separate environment. Many levels of hierarchy Larger organizations tend to have very complex internal and external business structures that dictate the need for many different levels of organization.

For example, two companies might merge and need to keep two sets of officers who are managed under two different logical groupings. As you will see in Chapter 5, "Administering Active Directory," OUs are used to help group different branches of the company so that you can assign permissions, or delegations, or whatever else you can think of without affecting anyone else.

Management of data becomes much easier when you're using OUs, and if designed correctly, will help you control your network right from one console. You may only need one level of management—your company may be small enough to warrant the use of the default OU structure you see when Active Directory is first installed.