The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Making a case for migrating from Exchange 2000 to 2003.
Artoria
Registered User regular
Registered User regular
I was asked to look into getting Blackberries for a few highly mobile users. So I did some research got the price for the black berry software, a small server, phones, service ect.. and gave it to my boss. A couple of weeks go by and I find out that they were nto too thrilled about he service chage or having to add yet another server into the mix. I was then asked to look into the AT&T tilt phone. I was told that it could be used without an additional push server etc...
So I go looking into it and I find that in order to use Microsoft Push technology you have to be using Exchange 2003 SP2. Well right now we are using Exchange 2000 on Server 2000. So I do the research on upgrading exchange, getting a new exchange server etc.. and talk to my boss about it. She is not thrilled at all she said “I promise you this we are not getting a new exchange server”
Her suggestion (that I don’t agree with) is to do the following.
1. transfer all the users in Houston to the main Exchange server in SF
2. Install Server 2003 then Exchange 2003 on that server.
3. then transfer all the users from SF to Hou
4. upgrade the server in SF to Windows and Exchange 2003
5. Transfer back the SF users
A drawn version. (yes I know about the typos)
Now there are several reasons I don’t think this is such a good idea and migration is the best way to go. Those being that every place I worked at had a similar set up to this and every one of them migrated to new servers even though the servers they had were not that old. The “old” exchange servers were always made into something else. Also the MX record is in SF and I think it would be easier to migrate that to a new server as opposed to trying to recreate it on a new installation. Also if there are issues with the exchange server I have time to test those and fall back if necessary.
Also upgrade in place is not an option since Microsoft Push (the whole reason for this fiasco) will not work on Server 2000.
Can someone here confirm that I am right and maybe provide me with a compelling case (in the form of links) as to why this suggestion will not work? Or if this idea does work explain to me how it does and how to make it as painless as possible?
So I go looking into it and I find that in order to use Microsoft Push technology you have to be using Exchange 2003 SP2. Well right now we are using Exchange 2000 on Server 2000. So I do the research on upgrading exchange, getting a new exchange server etc.. and talk to my boss about it. She is not thrilled at all she said “I promise you this we are not getting a new exchange server”
Her suggestion (that I don’t agree with) is to do the following.
1. transfer all the users in Houston to the main Exchange server in SF
2. Install Server 2003 then Exchange 2003 on that server.
3. then transfer all the users from SF to Hou
4. upgrade the server in SF to Windows and Exchange 2003
5. Transfer back the SF users
A drawn version. (yes I know about the typos)
Now there are several reasons I don’t think this is such a good idea and migration is the best way to go. Those being that every place I worked at had a similar set up to this and every one of them migrated to new servers even though the servers they had were not that old. The “old” exchange servers were always made into something else. Also the MX record is in SF and I think it would be easier to migrate that to a new server as opposed to trying to recreate it on a new installation. Also if there are issues with the exchange server I have time to test those and fall back if necessary.
Also upgrade in place is not an option since Microsoft Push (the whole reason for this fiasco) will not work on Server 2000.
Can someone here confirm that I am right and maybe provide me with a compelling case (in the form of links) as to why this suggestion will not work? Or if this idea does work explain to me how it does and how to make it as painless as possible?
Artoria on
0
Posts
Anyway, Her suggestion would work, but I wouldn't do it. I don't see the need, unless the win2k OS is all crapped up with junk. If the server is stable, and there are win2k3 drivers, I'd do (and did) an in-place upgrade over a weekend.
The only 'trick' is you have to do it in the correct order. First MSEX 2k -> MSEX 2k3 then Win2k -> Win2k3. Apply patches, drink heavily. http://www.msexchange.org/tutorials/Upgrade_Exchange_2000_to_2003.html
Second - the 'push'. You mean OMA? http://technet.microsoft.com/en-us/library/aa998981(EXCHG.65).aspx
We're running it. You'll need to have HTTP access to your exchange box from the internet. For us, that's an exchange front end in a DMZ. You don't mention that, so I thought I would...