Nex-Tech Support Staff
Guest
|
 Posted:
Tue Dec 20, 2005 5:58 pm Post subject:
NT4/Exchange 5.5 to 2003 Server Exchange 2003 |
|
|
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
|
|
Jonathan Norris
Guest
|
| Posted:
Tue Dec 20, 2005 5:58 pm Post subject:
RE: NT4/Exchange 5.5 to 2003 Server Exchange 2003 |
|
|
UPROMOTE it. I have used this in the past for reasons you have described.
Its a good product for these situations.
--
No Warrenties Implied
"Nex-Tech Support Staff" wrote:
| Quote: | 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
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in