Ask your advice on mixed DCs

Hi all,

We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional level is
windows 2003.

We want to introduce the one windows 2008 R2 domain controller. Is there
any problem when windows 2008 R2 domain controller and windows 2003 domain
controller exist together? Any cautions?

Thank you.

Howdie!

Am 05.04.2010 16:00, schrieb ed:
> We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional level is
> windows 2003.
>
> We want to introduce the one windows 2008 R2 domain controller. Is there
> any problem when windows 2008 R2 domain controller and windows 2003 domain
> controller exist together? Any cautions?

You'll have to update the Schema in order to promote that machine into
the domain. Other than that, there's nothing else you'll have to consider.

Since Server 2008R2 is a 64bit-only OS, a few considerations and tipps here:
- make the new DC a GC. Since it runs on 64bit, it'll perform slightly
faster when it comes to answering LDAP search queries
- if Exchange is pointed to the Win2k3 DCs for DC/GC searches, point it
to the new DC on 2008R2 now.
- if everything's working okay on the machine, consider moving the PDC
FSMO role to the new DC.

Cheers,
Florian

Hello ed,

No problem, only as Florian mentioned Exchange 2003 must have Exchange 2003
SP2 installed.

And i would also move the FSMO roles to the new OS domain controller. After
moving the PDCEmulator FSMO don't forget to reconfigure the previous and
the new one for the external time source if used or the internal hardware
clock.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi all,
>
> We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional
> level is windows 2003.
>
> We want to introduce the one windows 2008 R2 domain controller. Is
> there any problem when windows 2008 R2 domain controller and windows
> 2003 domain controller exist together? Any cautions?
>
> Thank you.
>

I have the same question as ed.
My plan is to introduce 1 W2K8 R2 as DC, phase out 1 W2K3 DC then introduce
another W2K8 R2 as DC and phase out the 2nd Wk3 DC, so eventually, this will
be an all W2K8 R2 domain. Would this strategy work?

I see that we will still have some W2K3 member servers running in hte new
A/D environment. Would that be a problem? Also, our Exchange 2007 server is
running on W2K3 64-bit, should it be upgraded to W2K8 R2 (or wait for
Exchange 2010)?

Thanks a lot

Bill
--------------------------

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:. com...
Hello ed,

No problem, only as Florian mentioned Exchange 2003 must have Exchange 2003
SP2 installed.

And i would also move the FSMO roles to the new OS domain controller. After
moving the PDCEmulator FSMO don't forget to reconfigure the previous and
the new one for the external time source if used or the internal hardware
clock.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi all,
>
> We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional
> level is windows 2003.
>
> We want to introduce the one windows 2008 R2 domain controller. Is
> there any problem when windows 2008 R2 domain controller and windows
> 2003 domain controller exist together? Any cautions?
>
> Thank you.
>

Hello Bill,

That way will work, se my article about the way to do it.
http://msmvps.com/blogs/mweber/archi...r-2008-r2.aspx

Member servers aren't a problem when raising the functional levels, only
DCs must have the correct OS for it.

If you upgrade Exchange depends on your needs, if it is interesting for you
to upgrade then make it together, OS change and Exchange.

You cannot inplace upgrade the Windows server 2003 with Exchange to Windows
server 2008. You have to install the OS and then Exchange and then move to
the new server.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I have the same question as ed.
> My plan is to introduce 1 W2K8 R2 as DC, phase out 1 W2K3 DC then
> introduce
> another W2K8 R2 as DC and phase out the 2nd Wk3 DC, so eventually,
> this will
> be an all W2K8 R2 domain. Would this strategy work?
> I see that we will still have some W2K3 member servers running in hte
> new A/D environment. Would that be a problem? Also, our Exchange 2007
> server is running on W2K3 64-bit, should it be upgraded to W2K8 R2 (or
> wait for Exchange 2010)?
>
> Thanks a lot
>
> Bill
> --------------------------
> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
> news:. com...
> Hello ed,
> No problem, only as Florian mentioned Exchange 2003 must have Exchange
> 2003 SP2 installed.
>
> And i would also move the FSMO roles to the new OS domain controller.
> After moving the PDCEmulator FSMO don't forget to reconfigure the
> previous and the new one for the external time source if used or the
> internal hardware clock.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>> Hi all,
>>
>> We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional
>> level is windows 2003.
>>
>> We want to introduce the one windows 2008 R2 domain controller. Is
>> there any problem when windows 2008 R2 domain controller and windows
>> 2003 domain controller exist together? Any cautions?
>>
>> Thank you.
>>

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message news:. com...
> Hello Bill,
>
> That way will work, se my article about the way to do it.
> http://msmvps.com/blogs/mweber/archi...r-2008-r2.aspx
>
> Member servers aren't a problem when raising the functional levels, only
> DCs must have the correct OS for it.
>
> If you upgrade Exchange depends on your needs, if it is interesting for you
> to upgrade then make it together, OS change and Exchange.
>
> You cannot inplace upgrade the Windows server 2003 with Exchange to Windows
> server 2008. You have to install the OS and then Exchange and then move to
> the new server.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>

Good blog, Meinolf! I'm glad to see you have your blogs up and running.

And I agree about Exchange. It wasn't indicated, but if Exchange is on a DC, it has to be removed before a DC can be demoted. So that means some juggling. I haven't tested Exchange 2007 on 2008 R2, but in this scenario, I would probably, if possible, setup a new server with 2008 R2 and install Exchange 2010, move everything over, and remove Exchange off the old box, that is if it is on a DC.

If not on a DC, I wouldn't upgrade the 2003 installation to 2008. I am not fond of upgrades, and rather have a clean, new installation.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

Hello Ace Fekay [MVP-DS, MCT],

Thanks Ace, take some time but works. :-)

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
> news:. com...
>
>> Hello Bill,
>>
>> That way will work, se my article about the way to do it.
>>
>> http://msmvps.com/blogs/mweber/archi...ding-an-active
>> -directory-domain-from-windows-server-2003-to-windows-server-2008-or-
>> windows-server-2008-r2.aspx
>>
>> Member servers aren't a problem when raising the functional levels,
>> only DCs must have the correct OS for it.
>>
>> If you upgrade Exchange depends on your needs, if it is interesting
>> for you to upgrade then make it together, OS change and Exchange.
>>
>> You cannot inplace upgrade the Windows server 2003 with Exchange to
>> Windows server 2008. You have to install the OS and then Exchange and
>> then move to the new server.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> Good blog, Meinolf! I'm glad to see you have your blogs up and
> running.
>
> And I agree about Exchange. It wasn't indicated, but if Exchange is on
> a DC, it has to be removed before a DC can be demoted. So that means
> some juggling. I haven't tested Exchange 2007 on 2008 R2, but in this
> scenario, I would probably, if possible, setup a new server with 2008
> R2 and install Exchange 2010, move everything over, and remove
> Exchange off the old box, that is if it is on a DC.
>
> If not on a DC, I wouldn't upgrade the 2003 installation to 2008. I am
> not fond of upgrades, and rather have a clean, new installation.
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
> & MCSA 2003/2000, MCSA Messaging 2003
>
> Microsoft Certified Trainer
>
> Microsoft MVP - Directory Services
>
> If you feel this is an urgent issue and require immediate assistance,
> please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message news:. com...
> Hello Ace Fekay [MVP-DS, MCT],
>
> Thanks Ace, take some time but works. :-)
>

You are welcome! :-)

Ace

Thanks for ALL your help.
so, I can mixed windows 2003 Sp2 32bit DC with windows 2008 R2 64 bit DCs
32BIT DCs and 64 bit DCs in the same forest? no iisue, right?

thank you.
"Florian Frommherz" wrote:

> Howdie!
>
> Am 05.04.2010 16:00, schrieb ed:
> > We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional level is
> > windows 2003.
> >
> > We want to introduce the one windows 2008 R2 domain controller. Is there
> > any problem when windows 2008 R2 domain controller and windows 2003 domain
> > controller exist together? Any cautions?
>
> You'll have to update the Schema in order to promote that machine into
> the domain. Other than that, there's nothing else you'll have to consider.
>
> Since Server 2008R2 is a 64bit-only OS, a few considerations and tipps here:
> - make the new DC a GC. Since it runs on 64bit, it'll perform slightly
> faster when it comes to answering LDAP search queries
> - if Exchange is pointed to the Win2k3 DCs for DC/GC searches, point it
> to the new DC on 2008R2 now.
> - if everything's working okay on the machine, consider moving the PDC
> FSMO role to the new DC.
>
> Cheers,
> Florian
> .
>

That's correct. As long as the Schema has been updated, the operating
system architecture is transparent. Having DCs exist in a mixed
sceanrio is no problem. I usually move the FSMO roles to the new DCs.

Keep in mind, some features have been added in the newer operating
systems, such as DNS replication (compared between 2000 and 2003). If
for example, you have all your mixed DCs that are DNS servers, it is
better to administer them from the 2000 servers. If you attempt to
administer DNS from the 2003 or 2008 servers in such a scenario, and
choose an option that doesn't exist in 2000, then it will cause
problems.

I hope that helps.

Ace


On Thu, 6 May 2010 13:17:01 -0700, ed <>
wrote:

>Thanks for ALL your help.
>so, I can mixed windows 2003 Sp2 32bit DC with windows 2008 R2 64 bit DCs
>32BIT DCs and 64 bit DCs in the same forest? no iisue, right?
>
>thank you.
>"Florian Frommherz" wrote:
>
>> Howdie!
>>
>> Am 05.04.2010 16:00, schrieb ed:
>> > We have win2k3 DCs and exchange 2003 Sp2 envir. and the functional level is
>> > windows 2003.
>> >
>> > We want to introduce the one windows 2008 R2 domain controller. Is there
>> > any problem when windows 2008 R2 domain controller and windows 2003 domain
>> > controller exist together? Any cautions?
>>
>> You'll have to update the Schema in order to promote that machine into
>> the domain. Other than that, there's nothing else you'll have to consider.
>>
>> Since Server 2008R2 is a 64bit-only OS, a few considerations and tipps here:
>> - make the new DC a GC. Since it runs on 64bit, it'll perform slightly
>> faster when it comes to answering LDAP search queries
>> - if Exchange is pointed to the Win2k3 DCs for DC/GC searches, point it
>> to the new DC on 2008R2 now.
>> - if everything's working okay on the machine, consider moving the PDC
>> FSMO role to the new DC.
>>
>> Cheers,
>> Florian
>> .
>>