Re: 5.5 to 2003 (5.5 is on an NT 4 PDC) Help!



Create trusts between the domains (I assume each site is in its own domain),
ADMT to the main site or new site the user accounts, create blank mailboxes,
exmerge the data or move mailbox (depends on size and site link speed).

Is the standard way, but there are lots of others depending on what you want
to achieve, how fast, how expensively and how much downtime.

Nick


"mehul" <mehul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E742616F-0715-4B27-9839-9A3B81517071@xxxxxxxxxxxxxxxx
> Al, we have the exact situation. we have exchange running on 3 servers in
> 3
> sites and a bridgehead and they all aer on BDC. moving these BDCs to
> Member
> servers manually in 3 locations would be a lot of work. what do you think
> of
> tools like UPROMOTE to demote the BDCs first? then i can switch the
> domain/forest functional level to 2003 and proceed with the exchange 2003
> install.
>
> Alternately, as I show in this newsgroup, I can install another domain in
> the same forest that has the domain functional level of 2003 (the
> highest).
> This domain would hold the USG temporarily, till we switch the main domain
> to
> the native mode (domain functional and forest funtional to 2003).
>
> ANy suggestions? any documents I should refer to?
>
> "Al Mulnick" wrote:
>
>> Sounds exactly like what you should consider.
>> Al
>>
>> "Scott Schone" <ScottSchone@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:A130B6F5-9C94-4D08-9A40-4764CAEDBE8B@xxxxxxxxxxxxxxxx
>> > Al,
>> > Thanks. Currently I have installed NT 4 on a Dell PowerEdge SC interim
>> > computer as a BDC. Next I was planning to install Windows 2003 Server
>> > on
>> > this
>> > machine as an upgrade. During the upgrade I will have to choose a
>> > domain
>> > name
>> > (I'm guessing it will have to be a different domain name than the NT
>> > domain).
>> > I'm hoping the users will be automatically migrated during the upgrade.
>> > I
>> > will choose 2003 interim mode during the upgrade. At this point I'm not
>> > sure
>> > what to do next. I guess I could move the Exchange 5.5 to a member
>> > server
>> > (not sure how), decommission the BDC and then change to 2003 native
>> > mode
>> > and
>> > install Exchange 2003 on our new PowerEdge 2800.
>> >
>> > "Al Mulnick" wrote:
>> >
>> >> You can't upgrade the BDC anyway until you do something about 5.5
>> >> since
>> >> it
>> >> won't ride on W2K3 server OS.
>> >>
>> >> What you need to do is this:
>> >> a) take another look at the documents regarding the upgrade at
>> >> http://www.microsoft.com/exchange/library
>> >> b) plan on introducing your Exchange 2003 servers without doing
>> >> anything
>> >> with the domain. Note that you need a native mode domain to migrate to
>> >> because of USG interaction (universal security groups.) This can be
>> >> mitigated until you have a final migration.
>> >> c) Then go back and remove the BDC.
>> >>
>> >> Alternatively, you could introduce a new 5.5 server into the
>> >> environment
>> >> on
>> >> an NT or 2000 member server, move all of the mail resources over and
>> >> sunset
>> >> the existing BDC completely before continuing. Would be safer but
>> >> require
>> >> more machines.
>> >>
>> >> Al
>> >>
>> >>
>> >>
>> >> "Scott Schone" <ScottSchone@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> message
>> >> news:12007E12-A975-4701-A643-97C66B1EF61C@xxxxxxxxxxxxxxxx
>> >> > Initially I will install Exchange in 2003 Interim mode and then I
>> >> > want
>> >> > to
>> >> > go
>> >> > to 2003 native mode, but I am concerned that I will loose access to
>> >> > Exchange
>> >> > on the NT 4 BDC. I can't upgrade the BDC to 2003 because it is too
>> >> > old
>> >> > and
>> >> > I
>> >> > don't think you can demote it to a member server.
>> >> >
>> >> > "Al Mulnick" wrote:
>> >> >
>> >> >> What do you mean when you say native?
>> >> >> Forest functional level and domain functional level are the terms
>> >> >> I'm
>> >> >> more
>> >> >> familiar with in 2003 AD.
>> >> >>
>> >> >> Al
>> >> >>
>> >> >>
>> >> >> "Scott Schone" <Scott Schone@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> >> message
>> >> >> news:ED2AE930-C6D8-4D7C-BD49-BBD51F3ADA96@xxxxxxxxxxxxxxxx
>> >> >> >I am planning to install a temp NT 4 BDC, promote to PDC (this
>> >> >> >leaves
>> >> >> >my
>> >> >> > Exchange 5.5 on an NT4 BDC), install 2003 server upgrade on temp
>> >> >> > PDC.
>> >> >> > Can
>> >> >> > I
>> >> >> > go native on 2003 AD at this point and still access Exchange on
>> >> >> > BDC
>> >> >> > so
>> >> >> > that I
>> >> >> > can upgrade to Exchange 2003 on a brand new 2003 server?
>> >> >> >
>> >> >> > P.S. What about the domain name, why can't I keep the same domain
>> >> >> > name
>> >> >> > in
>> >> >> > 2003 as NT?
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>


.



Relevant Pages

  • Re: Linux vs FreeBSD vs SCO
    ... This happened in the past and I've not done a lot with Linux ... things I ever learned about robustness in servers - and I only putz ... Then there is the rpm upgrade path. ... often you install an upgrade, and you find it needs something else, ...
    (comp.unix.sco.misc)
  • Re: Re: NT4 to 2003 w/AD &amp; new servers
    ... >> as they also act as file servers with many shared folders on ... >> in-place upgrade of the PDC and then the BDC. ... * Install additional new hardware with W2K3 ... NeutralizeNT4Emulator registry key if you already have W2K/WXP/W2K3 ...
    (microsoft.public.win2000.active_directory)
  • Re: 2003 Enteprise SP2 or 2003 Enteprise R2
    ... If you run setup from disk 2 of the R2 set it will install this: ... SP 2 on *all* Win 2k3 servers. ... SP 2 is an OS upgrade that should be ...
    (microsoft.public.windows.server.general)
  • Long Login Times
    ... NT4: 1 PDC, 1 BDC ... Build a second BDC called UPG1a. ... put the Global Catalog on one or both of those servers. ... Took the Upgrade server down. ...
    (microsoft.public.windows.server.general)
  • Re: WARNING:DO NOT UPGRADE TO CORE 4]
    ... never use fc or even RHEL on production ..its pita maintain and install ... pakages and to upgrade .....I recently udgraded my servers to debian and ... freebsd ...with around 16000 pakages and very good uptime ... ...and assured upgrade ...
    (Fedora)

Loading