Windows 7 and nt domains

McDonald's quietly revealed its stunning future -- and some customers will like it. If you use Google Chrome, you need to install this now. AWS launches new EC2 instance type for high performance computing tasks. Developers, DevOps, or cybersecurity?

Which is the top tech talent employers are looking for now? You agree to receive updates, promotions, and alerts from ZDNet. You may unsubscribe at any time. By signing up, you agree to receive the selected newsletter s which you may unsubscribe from at any time. You also agree to the Terms of Use and acknowledge the data collection and usage practices outlined in our Privacy Policy.

What are you looking for? However, as I pointed out in a comment to my question, windows network authentication reqts for SQL server were driving me towards actually joining the domain. Have you considered using VMs for this purpose? Create a VM for each of the domains and switch between them on demand. The simple answer is that you cannot. A machine can only be in one domain at a time. The Microsoft way to deal with this would be for you to have your own domain, and for each of these other domains to trust yours.

Good luck convincing your customers to do this, even for one-way trust. No, Windows 7 is identical to Windows XP in regards to joining multiple domains. Very poor form on MS behalf, We have been asking this for a long time. Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 12 years, 2 months ago. Active 10 years, 2 months ago. Viewed 22k times. Improve this question. Question: Why do you need to join the domain? I know very few IT guys that us the "Domain Computers" security group regularly. Also, part of what I do there is network admin I have domain admin privileges at the two sites where I spend the majority of my time.

Add a comment. Active Oldest Votes. Improve this answer. After the computer restarts, wait 10 minutes to make sure that all security policies are applied and the effective settings are configured.

We recommend that you wait 10 minutes because Active Directory policy updates occur every 5 minutes on a domain controller, and the update may change the security setting values. After 10 minutes, use Security Configuration and Analysis or another tool to examine the security settings in Windows and Windows Server This section, method, or task contains steps that tell you how to modify the registry.

However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: How to back up and restore the registry in Windows. In Windows NT 4.

Click Start , click Run , type regedt32 , and then click OK. Expand the following registry subkeys, and then view the value that is assigned to the RestrictAnonymous entry:. Expand the following registry subkeys, and then view the value that is assigned to the LM Compatibility entry:. Expand the following registry subkeys, and then view the value that is assigned to the EnableSecuritySignature server entry:.

Expand the following registry subkeys, and then view the value that is assigned to the RequireSecuritySignature server entry:. Expand the following registry subkeys, and then view the value that is assigned to the RequireSignOrSeal entry:. Expand the following registry subkeys, and then view the value that is assigned to the SealSecureChannel entry:.

Expand the following registry subkeys, and then view the value that is assigned to the SignSecureChannel entry:. Expand the following registry subkeys, and then view the value that is assigned to the RequireStrongKey entry:. Make sure that the Everyone group is in the Access this computer from the network list. Verify that there are no principle groups in the Deny access to this computer from the network list, and then click OK.

For example, make sure that Everyone, Authenticated Users, and other groups, aren't listed. To verify the required user rights on a Windows NT Server 4. In the Right list, click Access this computer from the network. If a trust is set up between the domains, but you can't add principle user groups from one domain to the other because the dialog box doesn't locate the other domain objects, the "Pre-Windows compatible access" group may not have the correct membership. On the Windows based domain controllers and the Windows Server based domain controllers, make sure that the required group memberships are configured.

Click Built in , and then double-click Pre-Windows compatible access group.