Advanced IT Peeps: Exchange 2000
#1
Hi,
Just need to pick some brains/be pointed to some faq's...
I have two domains, domainnt and domain2k.
domainnt is our old domain, this is be discarded
domain2k is our new domain, which i want to have exchange2000 running also.
domainnt
* PDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a with Exchange 5.5 SP4 installed.
domain2k
* Main forest running windows2000 sp2
* windows2000 sp2
I want to migrate exchange 5.5 to exchange2000 on the new server in the new domain.
I thought an ideal solution would be to :
domainnt
* PDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a with Exchange 5.5 SP4 installed.
* windows2000 sp2 running exchange 5.5 SP4
domain2k
* Main forest running windows2000 sp2
The windows2000 machine becomes part of the exchange, i then move all mailboxes from the nt4server to the win2k server. I then take it out of the domain, back into work group, then move it into the domain2k.
Once the win2k machine is in domain2k, go to the services and change the account to point to domain2k\exservice instead of domainnt\exservice . Restart the services, fire up exchange, change the logon details manually for each email account, so mine i would change to point to domain2k\christian instead of domainnt\christian
Is there a better way? Basically I want to migrate the mailboxes form the exchange5.5 machine to the exchange2000 machine, which is in a different domain, and thus will have different user accounts etc.
Just need to pick some brains/be pointed to some faq's...
I have two domains, domainnt and domain2k.
domainnt is our old domain, this is be discarded
domain2k is our new domain, which i want to have exchange2000 running also.
domainnt
* PDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a with Exchange 5.5 SP4 installed.
domain2k
* Main forest running windows2000 sp2
* windows2000 sp2
I want to migrate exchange 5.5 to exchange2000 on the new server in the new domain.
I thought an ideal solution would be to :
domainnt
* PDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a file/print sharing
* BDC Running NT4 Server SP6a with Exchange 5.5 SP4 installed.
* windows2000 sp2 running exchange 5.5 SP4
domain2k
* Main forest running windows2000 sp2
The windows2000 machine becomes part of the exchange, i then move all mailboxes from the nt4server to the win2k server. I then take it out of the domain, back into work group, then move it into the domain2k.
Once the win2k machine is in domain2k, go to the services and change the account to point to domain2k\exservice instead of domainnt\exservice . Restart the services, fire up exchange, change the logon details manually for each email account, so mine i would change to point to domain2k\christian instead of domainnt\christian
Is there a better way? Basically I want to migrate the mailboxes form the exchange5.5 machine to the exchange2000 machine, which is in a different domain, and thus will have different user accounts etc.
#2
That wont work as the Exchange DIR will have permissioning/SIDS relative to the old domain..
What about setting up the ADC between domains and syncing the whole lot up and slowly migrate the mailboxes across..
Cheerio
What about setting up the ADC between domains and syncing the whole lot up and slowly migrate the mailboxes across..
Cheerio
#4
What you need to do is a pretty straightforward migration reqiurement, best to goto www.microsoft.com/exchange and hit the whitepapers - there will be plenty of advice on there on how to do it..
cheerio
cheerio
#5
Off Topic slightly - I think I'm right in thinking exchange is a true pop3 / smtp mail server (and more), but can it be configured to dialup the internet and download company emails from an ISP's pop3 server ?
#6
yes you can, but that isn't really the point of exchange, and you will need purchasing of external software to get it to work properly.
What would be a better option, is purchase a domain name, and have them to setup the mx record to point to your fixed public ip address. This ip address would then be assigned to your firewall, which would forward it on to your exchange box.
What would be a better option, is purchase a domain name, and have them to setup the mx record to point to your fixed public ip address. This ip address would then be assigned to your firewall, which would forward it on to your exchange box.
#7
Scooby Regular
I'll have a look at my notes at work tomorrow, although what Ga22ar is saying is right enough. Incidentally, how many mailboxes are you talking about?
As part of our W2K migration, we are configuring the ADCs (one in Aberdeen, the other in our HQ in Houston) this week and then when that is done will start to move all 30,000 Exchange 5.5 mailboxes to Exchange 2000, carrying it out on a site by site basis
As part of our W2K migration, we are configuring the ADCs (one in Aberdeen, the other in our HQ in Houston) this week and then when that is done will start to move all 30,000 Exchange 5.5 mailboxes to Exchange 2000, carrying it out on a site by site basis
Trending Topics
#8
Scooby Regular
Join Date: Feb 2001
Location: Hemel Hempstead
Posts: 7,953
Likes: 0
Received 0 Likes
on
0 Posts
Depending on the number of mailboxes...... could you not;
1. export mailboxes to .pst files
2. deploy the mailserver onto the new domain, install EX2000
3. manualy re-create the mailboxes
4. import the .pst files to the new mailboxes.
Nice simple solution, however this is dependent of the number of mailboxes, if you have 30,000, this is not really an option 10 or so would be fine....
P
1. export mailboxes to .pst files
2. deploy the mailserver onto the new domain, install EX2000
3. manualy re-create the mailboxes
4. import the .pst files to the new mailboxes.
Nice simple solution, however this is dependent of the number of mailboxes, if you have 30,000, this is not really an option 10 or so would be fine....
P
#9
Scooby Regular
I've had a look, basically what I would do is (think this would work). This is all from memory cos the folder from a course I did 6 months ago that I thought was here at my desk has walked off:
+Bring up E2K box running in mixed mode (different to AD mixed mode) in your Ex5.5 site.
+Move mailboxes across to Ex2K box.
+Retire Ex5.5 box.
+Kick Ex2K box into native mode.
+Bring up other Ex2K box in your W2K domain.
+Move all mailboxes to the Ex2K box in the W2K domain.
Links wise, look at:
Migrating Exchange 5.5 to Exchange 2000
Windows 2000 Magazine Migration Guide
[Edited by Miles - 5/21/2002 12:34:29 PM]
+Bring up E2K box running in mixed mode (different to AD mixed mode) in your Ex5.5 site.
+Move mailboxes across to Ex2K box.
+Retire Ex5.5 box.
+Kick Ex2K box into native mode.
+Bring up other Ex2K box in your W2K domain.
+Move all mailboxes to the Ex2K box in the W2K domain.
Links wise, look at:
Migrating Exchange 5.5 to Exchange 2000
Windows 2000 Magazine Migration Guide
[Edited by Miles - 5/21/2002 12:34:29 PM]
#11
Scooby Regular
From the MS site:
"Moving Exchange 2000 Mailboxes
Exchange Server 5.5 mailboxes are Exchange Server directory objects. In Exchange 2000, Active Directory (AD) user objects' attributes point to mailboxes, and you use the Microsoft Management Console (MMC) Active Directory Users and Computers snap-in to move Exchange 2000 mailboxes.
To relocate Exchange 2000 mailboxes, simply select the mailboxes you want to move, right-click them, and select Exchange Tasks, Move Mailbox. The resulting dialog box lets you choose the selected mailboxes' destination server and mailbox store. Although Exchange Task Wizard's Move Mailbox function can't move mailboxes between Exchange Server organizations, it can easily move Exchange 2000 mailboxes between administrative groups.
Like Exchange Server 5.5's Move Mailbox, Exchange Task Wizard's Move Mailbox process is transparent to clients. However, Exchange Task Wizard's Move Mailbox doesn't
suffer from the bottlenecks that Exchange Server 5.5's Move Mailbox does. Exchange Task Wizard's Move Mailbox transmits mailbox data directly from the source server to the target server."
"Moving Exchange 2000 Mailboxes
Exchange Server 5.5 mailboxes are Exchange Server directory objects. In Exchange 2000, Active Directory (AD) user objects' attributes point to mailboxes, and you use the Microsoft Management Console (MMC) Active Directory Users and Computers snap-in to move Exchange 2000 mailboxes.
To relocate Exchange 2000 mailboxes, simply select the mailboxes you want to move, right-click them, and select Exchange Tasks, Move Mailbox. The resulting dialog box lets you choose the selected mailboxes' destination server and mailbox store. Although Exchange Task Wizard's Move Mailbox function can't move mailboxes between Exchange Server organizations, it can easily move Exchange 2000 mailboxes between administrative groups.
Like Exchange Server 5.5's Move Mailbox, Exchange Task Wizard's Move Mailbox process is transparent to clients. However, Exchange Task Wizard's Move Mailbox doesn't
suffer from the bottlenecks that Exchange Server 5.5's Move Mailbox does. Exchange Task Wizard's Move Mailbox transmits mailbox data directly from the source server to the target server."
#13
Miles :: Slight problem with your theory.. The 1st x2k box that you migrate the x55 mailboxes from in your plan is in the same domain as the x55 box.. Tell me how do you install x2k into a domain that doesnt have AD ?
You wouldnt wanf to do a .pst migration even on a few large mailsboxes as you'll lose Single Instance and wind up with an much large Information Store on the x2k server..
Only practical way is ADC between the two Exchange orgs, sync objects and then migrate the mailboxes..
Cheerio
You wouldnt wanf to do a .pst migration even on a few large mailsboxes as you'll lose Single Instance and wind up with an much large Information Store on the x2k server..
Only practical way is ADC between the two Exchange orgs, sync objects and then migrate the mailboxes..
Cheerio
#14
Daz,
As Christian says it is possible with Exchange but it maybe overkill. Bog standard Ex 5.5 won't collect from POP3 mailboxes. MS did offer a POP3 collector for BackOffice SBS 4.5 but this only installs on SBS versions.
I can't remember if Ex 2000 will collect POP3 on it's own.
If you want a free and no frills collector try PopRoute. I've run it for a while on systems and works a treat when you use the NT / 2000 Task Scheduled to call it.
Plenty of cheaper and easier to manage alternatives though.
Chris.
As Christian says it is possible with Exchange but it maybe overkill. Bog standard Ex 5.5 won't collect from POP3 mailboxes. MS did offer a POP3 collector for BackOffice SBS 4.5 but this only installs on SBS versions.
I can't remember if Ex 2000 will collect POP3 on it's own.
If you want a free and no frills collector try PopRoute. I've run it for a while on systems and works a treat when you use the NT / 2000 Task Scheduled to call it.
Plenty of cheaper and easier to manage alternatives though.
Chris.
#15
Scooby Regular
Ga22ar, that's a very good point . Confusion was reining in my head and indeed when I typed that in I wondered at the time. That cleared up coupled with me finding my notes leads me to agree with you 100%
Thread
Thread Starter
Forum
Replies
Last Post