Avoid waiting for its DC while on other networks....
Hi, Scenario: Win2008 domain controllers and win7pro clients. The clients are used in three different network environments, at their own office, at foreign domain network locations and at home. They are only connected to our domain when being at their office. We want these client computers ONLY to search / wait for response from their default domain controller when connected to our office network. A simple check at its leased IP address should tell windows if it is connected to the office network and therefore should try to connect to the DC: How can we make these clients to be intelligent enough to not wait and search for their default domain when they are *not connected at all* or *connected to another subnet*? I just feel it's not very user-friendly to wait for minutes for a domain controller which one knows is not present on certain subnets, and I hoped that win7 / win2008 finally had come up with something elegant to improve this...... Thanks for comments on this. regards Tor
February 17th, 2010 11:01am

The best workaround is using other user accounts when not connecting to the domain.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2010 9:35am

I am looking for the same fix. This has been a Windows problem for many versions that I had hoped MS would fix in this release since they were so focused on boot times. Pretty much still sucks to boot a domain computer off network.
March 5th, 2010 6:08am

The best solution would be for MS to improve the software. Giving users two accounts to deal with is not ideal.
Free Windows Admin Tool Kit Click here and download it now
March 5th, 2010 6:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics