In
David V said:
We currently have a number of issues with Win2K3 and W2KSP4. We are
an online stock brokerage. Our internal stock trading platform has a
number of incompatibilities with SP4, with which I am not totally
familiar. The problem with moving to W2K3 is that the stock trading
app relies on MSMQ2, but is so far incompatible with MSMQ3 - our
developers are working to correct that now. It also works with .Net
Framework 1.0, but not yet with .Net Framework 1.1. Once these
issues are cleared up, we want to move to W2K3. The snag there is
that our root domain has a single-label DNS name, which is not
supported by W2K3. The idea is to first promote the DCs to W2K3,
then run the Domain Rename tool to add a .local to the root domain.
We have already added the UpdateTopLevelDomainZones registry value to
all the DCs in the forest to enable the upgrade to W2K3, and we have
one functioning W2K3 DC (out of 12). It is in preparation for this
operation that I am attempting to build a test lab that, as much as
possible, mirrors our production environment. Funny thing is - in
the test lab, I can create child domains of the root domain, but not
of existing child domains. Also, AD Sites and Services does not show
NTDS connections for all domain controllers, but only for a few. I
had the domain structure built at one time, but after we decided to
rebuild 2 DC2 on a blade server, things started going wrong.
Hi David, and thanks for getting back to me with an update. Well, it seems
you have multiple issues going on, and I guess the first on the front burner
is the app. As for the single label name, I have one word for that: "OUCH!".
THat is causing you most of the problems. Now I can only suggest, to
eliminate possible DNS lookup failures, is to point DNS from all machines to
the servers in the forest root. Then I would try to add a child domain under
that. But as you already saw, it can be very problematic. GPOs and DFS also
fails with single label names and there's really no way to force them to
work.
When you use the rename tool, there are considerations if you have Exchange
2003 installed, which you'll need to upgrade that and install SP1 on it
before you can rename it. Here's more info on the:
Windows Server 2003 Active Directory Domain Rename Tools
http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx
Good luck with everything!
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.