Have current exchange server...getting new exchange server soon.
Hello experts-
I'd like any advice on moving exchange to a new server....
I have a 2003 windows standard edition server with exchange 2003. This is all this server does...email. Everything works great, but we are running low on disk space and we will be getting a new server in the next few weeks. The new server will be just hardware, no software (OS or exchange). My plan was to use the Windows Server 2003 license and exchange software that is currently on the old server. After the migration the old server will be demoted to a desktop computer for some user, and reformatted and loaded with XP. So i'm trying not to just 'throw away' a 2003 server license by not buying one with the new server, since after the migration the windows 2003 server edition license will NOT be used by the old server anymore.
1) I was wondering if i'm going to hit any walls trying to do this (since technically there will be two microsoft windows 2003 product keys on the same domain temporarily until i move the exchange data). *I thought i read with XP at least that two license's can't be on the same domain, which is perfectly understandable. Is this the same with server editions? If it is, how do you get around not 'throwing away' a license?
Thanks in advance.
I'd like any advice on moving exchange to a new server....
I have a 2003 windows standard edition server with exchange 2003. This is all this server does...email. Everything works great, but we are running low on disk space and we will be getting a new server in the next few weeks. The new server will be just hardware, no software (OS or exchange). My plan was to use the Windows Server 2003 license and exchange software that is currently on the old server. After the migration the old server will be demoted to a desktop computer for some user, and reformatted and loaded with XP. So i'm trying not to just 'throw away' a 2003 server license by not buying one with the new server, since after the migration the windows 2003 server edition license will NOT be used by the old server anymore.
1) I was wondering if i'm going to hit any walls trying to do this (since technically there will be two microsoft windows 2003 product keys on the same domain temporarily until i move the exchange data). *I thought i read with XP at least that two license's can't be on the same domain, which is perfectly understandable. Is this the same with server editions? If it is, how do you get around not 'throwing away' a license?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
MCPJoe
Correct me if I'm wrong, but even if its OEM software, once you get the license (even if bundled with hardware) does not "tie" it to that hardware. A license is a license. You should be able to use the CD Key that you have for Server 2003, and setup your new server box. Then install Exchange and migrate to the new box. You can then de-commission the old server and remove windows on that box. I don't believe that Microsoft is so "hard". In my experience I've done this with volume license media and keys, so it could be slightly different if you have a retail version of the software. But worst case scenario, you can still install everything and if any activation is required, then call Microsoft and explain the situation, I'm sure they will be able to help you.
ASKER
Thanks for the advice guys, I'm think I will end up calling micro$oft today or tomorrow. I was unaware licensing questions were free of charge. I do have an OEM (Dell) version of windows server 2003 that's in question and that's why I'm a bit leary.
I've heard before that they are tied to hardware, but I don't think it's entirely true either (or not true in every case)...I had a new desktop from Dell that had OEM Dell XP version with it, but one of the programs we used at this company wasn't compatible yet with XP at the time, so i uninstalled XP from that computer, put on a version of windows 2000...then took that XP version and installed it on another computer. Everything worked fine.
I'll let you know what i find out though.
BTW.... Haha, I should hope it doesn't take me 2 years, a weekend maybe. ;)
I've heard before that they are tied to hardware, but I don't think it's entirely true either (or not true in every case)...I had a new desktop from Dell that had OEM Dell XP version with it, but one of the programs we used at this company wasn't compatible yet with XP at the time, so i uninstalled XP from that computer, put on a version of windows 2000...then took that XP version and installed it on another computer. Everything worked fine.
I'll let you know what i find out though.
BTW.... Haha, I should hope it doesn't take me 2 years, a weekend maybe. ;)
Sure MCPJoe, you're wrong :)
I only know because I went through this recently with MS (and HP doing stupid things with my order...) while you *could* do it, you *could* also download a version... Also, don't confuse OEM and VLK, they are totally different.
But hey, it may have changed in the last 3 months, as much as I doubt it.
Also, taking a version of XP and installing it somewhere else is a breach of the license - even if you have 2000 installed on the XP licensed machine instead (at that point, you are technically using the XP downgrade rights)
Anyway, calling MS was the best idea in this thread - Sembee says it best, when it comes to licensing, get 3 different people advice (one being MS) - and the most expensive will be correct.
The move will take you at least a week - don't rush it.
-red
I only know because I went through this recently with MS (and HP doing stupid things with my order...) while you *could* do it, you *could* also download a version... Also, don't confuse OEM and VLK, they are totally different.
But hey, it may have changed in the last 3 months, as much as I doubt it.
Also, taking a version of XP and installing it somewhere else is a breach of the license - even if you have 2000 installed on the XP licensed machine instead (at that point, you are technically using the XP downgrade rights)
Anyway, calling MS was the best idea in this thread - Sembee says it best, when it comes to licensing, get 3 different people advice (one being MS) - and the most expensive will be correct.
The move will take you at least a week - don't rush it.
-red
ASKER
<<Also, taking a version of XP and installing it somewhere else is a breach of the license - even if you have 2000 installed on the XP licensed machine instead (at that point, you are technically using the XP downgrade rights).
Just so there's no misconstruded assumptions...The windows 2000 had it's own seperate legitimate license key. The XP also had it's own seperate legitimate license. Not a downgraded license situation. Are you still saying this would be a breach of license?
Just so there's no misconstruded assumptions...The windows 2000 had it's own seperate legitimate license key. The XP also had it's own seperate legitimate license. Not a downgraded license situation. Are you still saying this would be a breach of license?
OK, I thought you had installed 2000 on the XP machine without a license (which I am pretty sure you can do, dont quote me though)
But moving an OEM license is still a breach last I checked.
In fact, it is, and it is worse than I thought.
If you purchased a new motherboard for your PC, by the EULA, that is now a new PC and will need a new license;
http://www.michaelstevenstech.com/oemeula.htm
I appreciate that is not an MS site, but he is an MVP, and it is a copy of the OEM EULA.
-red
But moving an OEM license is still a breach last I checked.
In fact, it is, and it is worse than I thought.
If you purchased a new motherboard for your PC, by the EULA, that is now a new PC and will need a new license;
http://www.michaelstevenstech.com/oemeula.htm
I appreciate that is not an MS site, but he is an MVP, and it is a copy of the OEM EULA.
-red
ASKER
Bummer... :(
I called Micro$oft just to verify and red is correct. OEM licenses are tied to the computer (pretty much the motherboard).
Seams like such a waste to me, $800 for an OEM windows server 2003 edition.....down the tube. I'll be going the retail versions route from now on, they really aren't that much more money, and are transferable. :)
I called Micro$oft just to verify and red is correct. OEM licenses are tied to the computer (pretty much the motherboard).
Seams like such a waste to me, $800 for an OEM windows server 2003 edition.....down the tube. I'll be going the retail versions route from now on, they really aren't that much more money, and are transferable. :)
ASKER
Thanks for the guidance gentlemen and have a good weekend!
>>Seams like such a waste to me, $800 for an OEM windows server 2003 edition.....down the tube.
You're preaching to the choir man :)
What I usually do is use these machines for mail gateways, or print servers, or whatever
Thanks
-red
You're preaching to the choir man :)
What I usually do is use these machines for mail gateways, or print servers, or whatever
Thanks
-red