Re: Windows 2003 64-bit domain rename
- From: "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname@xxxxxxxxxxx>
- Date: Fri, 23 Jan 2009 12:43:34 -0500
In news:5cbcf65f-e223-47ac-a5a5-bf82e1736ff9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
Mike Honeycutt <mhoneycutt@xxxxxxxxxxxxxxxx> requesting assistance, typed the following:
I have a fairly simple network with a Windows 2003 R2 64-bit domain
controller. It is the only DC. There are 2 other member servers and
about 60 XP and Vista client systems. Exchange is not in the mix, but
there are several databases in the mix, some on MS SQL, however, for
the most part they are web backends and not using the Windows accounts
for permissions. In addition there is one MAC OS 10 server and about
15 MAC clients. The Windows and MAC systems share data across
platforms. I don't want to have to rebuild from scratch just to get
an additional DC on the network. The Forest is at Windows 2000
Functional Level and the Domain is Windows 2000 Mixed Functional
Level. The domain was originally set up incorrectly as
intranet.domainname.com. They utilize http://intranet.domainname.com
for their intranet, so adding another DC blows up the reference to
their intranet site. From what I've been able to find, there is not a
supported renaming of 64-bit domains.
Has anyone tried adding a 32-bit domain controller to a 64-bit domain
and doing the rename process on the 32-bit DC? If so any caveats? I
know the functional level will need elevated, but do I need to move
all the roles to the 32-bit DC? Any other considerations?
Thanks for your input.
I think adding the other DC, which each DC adds the LdapIpAddres record, that shows up as:
(same as parent) A <IpAddress>
Some call this the "blank domain entry" whereas in a website, you connect to a website without the 'www' portion. With AD, this is a necessary record for all DCs to find themselves, as well as GPO acquisition by clients when they run the GetGpoList function (in the background), as well as for DFS and other background AD funtions. This may be causing the issue if the service is being hosted on the first DC. You cannot change this.
You can circumvent this by installing IIS on all DCs. Then in the default website properties on each DC, redirect it to www.intranet.domainname.com. THen in DNS, create a www record under intranet.domainname.com, and point it to the first DC's IP address. But you MUST always now use www in front of it to make it work.
Even if the intranet site is on a non-DC, it would still cause a problem because of the LdapIpAddress record. The above workaround works with such a scenario.
If I assumed incorrectly concerning your intranet site, please elaborate more on how your intranet site is configured, what server it;s on, etc.
--?
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
aceman@xxxxxxxxxxx This Part.org
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
I
.
- References:
- Windows 2003 64-bit domain rename
- From: Mike Honeycutt
- Windows 2003 64-bit domain rename
- Prev by Date: Re: [WARNING] Failed to query SPN registration on DC
- Next by Date: Re: Deployed printers with Gourp Policy and now they will not delete
- Previous by thread: Re: Windows 2003 64-bit domain rename
- Next by thread: Re: Windows 2003 64-bit domain rename
- Index(es):
Relevant Pages
|
