Stop Win2k clients from "running home"

These registry hacks keep Win2k clients from "running home" to the main DC to cause broken login scripts and slow access.

In a large environment that may have domain controllers spread out across a WAN, you do not want to begin your

Win2k implementation at your main site and have any of your W2k clients "run home" to this DC. It will overwhelm the DC and could cause login scripts to break and slow access times.

The fix is to add a registry hack that will cause the DC to look like an NT 4.0 PDC, and therefore your Win2k clients will authenticate with their normal or closest DC. This will cause one issue in regards to bringing up more Win2k DCs into your domain. You will get an error that there are no Active Directory domains. The second registry hack will solve this problem. You will need Service Pack 2 for both of these.

First registry hack:

HKLMSystemCurrentControlSetServicesNetlogonParameters

Value: NT4Emulator
Type: REG_DWORD
Data: 0x1

Second registry hack:

HKLMSystemCurrentControlSetServicesNetlogonParameters

Value: NeutralizeNT4Emulator
Type: REG_DWORD
Data: 0x1


This was first published in October 2001

Dig deeper on Windows Operating System Management

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchServerVirtualization

SearchCloudComputing

SearchExchange

SearchSQLServer

SearchWinIT

SearchEnterpriseDesktop

SearchVirtualDesktop

Close