RE: NT4 to 2003 server upgrade including Exchange 5.5 to Exchange 2003



Hi Ashley,

After reading your post, my understanding of your current issue is totally
related to Exchange 5.5 upgrade to Exchange 2000. Therefore, I think
following newsgroup would be more approprate for your issue:

microsoft.public.exchange.setup

Thanks for understanding.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
>>Thread-Topic: NT4 to 2003 server upgrade including Exchange 5.5 to
Exchange 2003
>>thread-index: AcYEtmNcIA/HQ4i5RxiqrEI4mrme7A==
>>X-WBNR-Posting-Host: 24.225.11.141
>>From: "=?Utf-8?B?TmV4LVRlY2ggU3VwcG9ydCBTdGFmZg==?="
<NexTechSupportStaff@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>Subject: NT4 to 2003 server upgrade including Exchange 5.5 to Exchange
2003
>>Date: Mon, 19 Dec 2005 08:08:02 -0800
>>Lines: 56
>>Message-ID: <C6D9AEC6-27EE-4C3D-B5C8-D2DA4F8A3341@xxxxxxxxxxxxx>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 8bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>>Newsgroups: microsoft.public.windows.server.migration
>>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:21760
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>The issue I have is this. I am in the middle of a NT4 to 2003 server
upgrade
>>including Exchange 5.5 to 2003 and NT4 Directory to Active Directory.
>>
>>The network started out as follows, three different domains, A, B, and C
for
>>this document. Domain A includes the Exchange 5.5 server which B and C
also
>>access via trusts between all the domains. All domains are single DC
domains
>>and none contain BDCâ??s. The Domain A PDC is the same box that Exchange
>>resides on as well.
>>
>>The customer wants to upgrade Domain A and then B and C at a later date
when
>>the money and time is available.
>>
>>They have two new servers, one that will be the new DC for Domain A and
one
>>that will host Exchange 2003.
>>
>>I brought in a temporary server and installed NT4 on it as a BDC in
Domain A
>>and then promoted it to PDC for the upgrade. I then did an upgrade on the
>>server to 2003 server and also the AD upgrade for the domain. All of this
>>went super smooth and I also joined and promoted the new DC server to the
>>domain and transferred the FSMO roles to it so that the temp DC is now
not
>>really needed but is still there.
>>
>>Everything is running smooth at this point and I was ready to start on
the
>>Exchange upgrade. According to the docs on the upgrade I need to clone
the
>>accounts from domain B and C to domain A so that when I install the ADC
it
>>will be able to match the mailboxes owned by users in those domains to a
user
>>in Domain A. It would then use the SID history attribute to match
accounts
>>from the other domains and allow them to authenticate and get to their
>>mailboxes.
>>
>>I was going to use the ADMT to do this but failed to realize that the
target
>>domain has to be in native mode to make this happen. Currently Domain A
is in
>>interim mode due to the fact that the old PDC is still running as a BDC
in
>>the domain.
>>
>>I canâ??t just get rid of this box because Exchange is on it. So I am
stuck. I
>>canâ??t migrate to 2003 without those accounts, I canâ??t get rid of the
server
>>because Exchange is on it.
>>
>>So what is the best way to get around this issue? I have done some
looking
>>but canâ??t really find anything simple.
>>
>>The only things Iâ??ve been able to see is a utility called Upromote
>>http://utools.com/UPromote.asp which would allow me supposedly to remove
the
>>server as a BDC and bring it back as a member server which would allow me
to
>>go to native mode or I was also thinking that maybe I could bring up the
temp
>>server after demoting it with NT4 on it and put Exchange 5.5 on there and
>>move everything to that server for the upgrade.
>>
>>Any other ideas or any info on these strategies would be appreciated.
>>
>>Thanks,
>>
>>Ashley Heaton
>>aheaton@(nospam)nex-tech.com
>>
>>

.



Relevant Pages

  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Validation for 2000 to 2003 upgrade
    ... Concerning the Exchange attribute in schema that will get duplicate during ... I don't want to have to run the adprep from the exchange server cdrom before ... Inplace upgrade will work without problem from 2000 to 2003, ...
    (microsoft.public.windows.server.active_directory)
  • Re: forestprep and domainprep on a Windows 2000/Exchange 2000 Dire
    ... You can not upgrade the schema until you change the names with the .ldf script. ... During the upgrade phase it will use the RFC compliant name versions, that are not existing, because Exchange 2000 use names that where not RFC compliant as stated in the document. ... OK with the Windows Server 2003 forestprep/domainprep? ...
    (microsoft.public.windows.server.active_directory)
  • Re: WinNT Domain to Win2K Active Directory? Help!!!
    ... ---domains can remain NT until those Admins feel like doing their upgrade? ... Microsoft Online Partner Support ... Also, we already have a Server 2000 running our DNS and WINS, do I need ... Perform an inplace upgrade to Exchange 2000. ...
    (microsoft.public.windows.server.migration)
  • Re: Exchange 2000 SP3 Server has been hijacked
    ... Your understanding of my problem is correct. ... MessageLabs thus your mail server would not be exposed. ... Oue Tape backup is in for service and I use to backup entire exchange ... Symantec has not turnup any trojans except that wins.exe keeps coming ...
    (microsoft.public.exchange.admin)

Loading