after SP4 where to make Registry changes

  • Thread starter Thread starter Djis
  • Start date Start date
D

Djis

I have single label domain.
Two 2000 DCs they are also DNSs, and I have XP Prof and
2000 Prof clients.

After SP4, I need to do Registry changes on DC's, member
servers, and XP i 2000 clients.
I read KB 300684, but I don't understand where to make
which Registry changes.

AllowSingleLabelDnsDomain and
UpdateTopLevelDomainZones .

Can someone help me?

best regards
Djis
 
In
Djis said:
I have single label domain.
Two 2000 DCs they are also DNSs, and I have XP Prof and
2000 Prof clients.

After SP4, I need to do Registry changes on DC's, member
servers, and XP i 2000 clients.
I read KB 300684, but I don't understand where to make
which Registry changes.

AllowSingleLabelDnsDomain and
UpdateTopLevelDomainZones .

Can someone help me?

best regards
Djis
Click to expand...

If you do not understand how to use regedt32 I would suggest you get someone
to make the registry entries.

Using regedt32 expand to those keys then in the menu click Edit, New Value
for the value name use for example AllowSingleLabelDnsDomain, Data type
REG_DWORD, click OK then set the Data to 1
 
I know how to make changes in Registry, but I did'nt
understand on which machines I need to do changes. In
text (KB 300684) I am not sure who are domain members?
Are Domain members all XP Pro, 2000 Pro clients and all
DNS and DC?

KB 300684 recomands to do changes for DCLocator on each
domain member, also DNS Client Configuration on DC and
domain members.

Does it mean that I need to do both changes on all
machines?

Yesterday I did:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DnsCa
che\Parameters

UpdateTopLevelDomainZones (REG_DWORD) registry value to
0x1

And after this there is no more warnings on server (which
is DC and DNS):

Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 18.12.2003
Time: 13:08:07
User: N/A
Computer: BIGMAMMA
Description:
Dynamic registration or deregistration of one or more DNS
records failed because no DNS servers are available.
Data:
0000: 2a 23 00 00 *#..


Djis
Thanks
-----Original Message-----
In Djis <[email protected]> posted a question
Then Kevin replied below:

If you do not understand how to use regedt32 I would suggest you get someone
to make the registry entries.

Using regedt32 expand to those keys then in the menu click Edit, New Value
for the value name use for example
Click to expand...
AllowSingleLabelDnsDomain, Data type
 
In
Djis said:
I know how to make changes in Registry, but I did'nt
understand on which machines I need to do changes. In
text (KB 300684) I am not sure who are domain members?
Are Domain members all XP Pro, 2000 Pro clients and all
DNS and DC?

KB 300684 recomands to do changes for DCLocator on each
domain member, also DNS Client Configuration on DC and
domain members.




Does it mean that I need to do both changes on all
machines?
Click to expand...
Make the registry entries on all machines, it won't affect the non members
they are not gonna register anyway but if you want to join them you'll have
to make the entries.
****************************************************************************
***************
All Windows XP and Windows 2000 SP4-based DNS CLIENTS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DnsCache\Parameters

UpdateTopLevelDomainZones

***************************************************************************

For Windows Server 2003, the UpdateTopLevelDomainZones value has moved to
the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient

****************************************************************************
********

ALL MACHINES These configuration changes should be applied to all domain
controllers and members of an Active Directory domain
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

UpdateTopLevelDomainZones

****************************************************************************
*
DCLocator Configuration

To enable such a domain member to use DNS to locate domain controllers in
domains with single label DNS names in other forests, set the
AllowSingleLabelDnsDomain (REG_DWORD) registry value to 0x1 under the
following registry key on each domain member:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

****************************************************************************
********
 
thank you for support

Djis
-----Original Message-----
In Djis <[email protected]> posted a question
Then Kevin replied below:
Make the registry entries on all machines, it won't affect the non members
they are not gonna register anyway but if you want to join them you'll have
to make the entries.
********************************************************* *******************
***************
All Windows XP and Windows 2000 SP4-based DNS CLIENTS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DnsC ache\Parameters
******************

For Windows Server 2003, the UpdateTopLevelDomainZones value has moved to
the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient
*******************
********

ALL MACHINES These configuration changes should be applied to all domain
controllers and members of an Active Directory domain
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpi p\Parameters
*******************
*
DCLocator Configuration

To enable such a domain member to use DNS to locate domain controllers in
domains with single label DNS names in other forests, set the
AllowSingleLabelDnsDomain (REG_DWORD) registry value to 0x1 under the
following registry key on each domain member:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netl ogon\Parameters





.
Click to expand...
 
Back
Top