Re: Records not created for Forward zone

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 03/26/04 

Date: Fri, 26 Mar 2004 11:05:18 -0500

In news:A646F637-B36A-4A01-9035-C61967FF91BE@microsoft.com,
Samantha <anonymous@discussions.microsoft.com> posted their thoughts, then I
offered mine
> Hi Kevin,
>
> All our DC are W2k, so promoting a NT4 to PDC will not work.
> However, I am trying at this moment the fix for the single label name
> in the article you directed me towards. I am to set the DWord value
> to 0x1, but how do I do that, the best I can get is 0x000001, which
> to me is not the same thing. Thanks.

The idea is to not promote an NT4 to a PDC at first, but to rather install
it into your current domain as a BDC. Then retire your two W2k domain
controllers by demoting them. SInce you are having problems they may not
demote and would have to force them to demote. Then once they are out of the
picture (off the network), then we promote the BDC to a PDC. Then once
that's done, we then install another NT4 as a BDC. Then once that's done,
upgrade the PDC to W2k but this time when dcpromo runs, choose the correct
AD DNS non-single label domain name.

This method will insure that you do NOT lose your current users and groups
nor do you lose your computer accounts. It will however, fix your single
label domain name instead of hacking ever machine's registry to bandaid this
problem, as it appears you're trying to do. Beleive me, you'll be happier in
the long run doing what Kevin and I described to fix this issue. 

-- 
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
-- 
=================================

Relevant Pages