Upgrading from developer version of exchange

[RogerWilliamson]

I am currently running a Small business server with a Development copy of exchange server--obtained via MSDN.

Now that I've left the development phase of my project, I want to use the exchange server as a real exchange server, but my license will not allow that.

What I would like to know is: can I upgrade to a full version--like the one that comes standard with SBS--without losing all the work I performed setting up exchange in the first place?

 

[TechSoEasyMVP]

You can't "upgrade" a separate Exchange Server with the SBS version because the SBS version MUST be installed on the same machine as SBS.

Normally this is installed during the initial installation and configuration of your server... so I wonder if it's properly deployed to begin with.



Jeffrey B. Kane
TechSoEasy

http://www.techsoeasy.com

 

[RogerWilliamson]

There has got to be a better way.

I'm in this position because Microsoft sent us the wrong media--server 2003, and I made promises to have the exchange server operational for development by a certain day, so installed our Visual Studio version of Exchange.

Now we are dependent on that Exchange server for testing and need to expand it to an enterprise solution with no downtime... which is impossible, according to you.

 

[TechSoEasyMVP]

I'm sorry, but it doesn't appear that you're in this situation because Microsoft sent you the wrong media.

I say that because the entire scenario you describe doesn't make any sense at all... either you have mixed up the proper terminology when attempting to describe the situation, or you don't really have a full understanding of Small Business Server. So, let's try to straighten out what we're talking about so we know if it's possible or not to achieve what you are attempting to do.

First, please be careful with your usage of "Enterprise" solution. I think what you are saying by that is a NON-MSDN license, or a "Production Environment". But the term "Enterprise" in Microsoft Licensing designates a specific class of Windows Servers -- which normally wouldn't be combined with a Small Business Server.

Correct me if I'm wrong, but to summarize what I understand that you are trying to do is move your customized configurations from a "Development" environment to a "Production" environment.

So then, please clarify this for me...

I am currently running a Small business server with a Development copy of exchange server

Are you saying that you are running Exchange on a SEPARATE box from SBS? Or was your SBS an MSDN license as well?






Jeffrey B. Kane
TechSoEasy

http://www.techsoeasy.com

Blog:

http://techsoeasy.spaces.live.com

 

[TechSoEasyMVP]

Okay... I almost understand, but you missed something very important in your explanation...

So, I decided that I would install Server 2003, hoping that the License I purchased would be valid for Server 2003. The installation of the Server went through perfectly

Can you please clarify what that really means?


Jeffrey B. Kane
TechSoEasy

http://www.techsoeasy.com

Blog:

http://techsoeasy.spaces.live.com

 

[RogerWilliamson]

I ordered one SBS license and one set of SBS install CDs--media. The CDs I got were for vanilla Server 2003, and not SBS.

I went ahead with the install anyway, and used the product key I purchased for SBS during the Server 2003 installation. I was amazed and relieved that Server 2003 installed with a SBS license. Unfortunately, I'm in a bizarre situation, since I currently have Server 2003 running under a SBS license.

Of course, I'm only in this situation because somewhere along the way, my order for the SBS media got mixed up and I received Server 2003 media instead.

 

[TechSoEasyMVP]

So, you still haven't clarified for me... is the Exchange server installed on this same box?

And, I don't want to try and cast blame... but you certainly are not in this situation JUST because your order for the SBS media got mixed up. You're in this situation because you knew you got the wrong product and installed it anyhow.

The fact that the key worked is rather curious too... but it really doesn't matter. Had you waited a few days more for them to fix the problem and get you the right media (which I've known them to send out next-day if there is a mixup like that) then the issue wouldn't even exist.

So... assuming that you have installed the Exchange server on the same box then what you need to do is MIGRATE to a NEW SBS Installation. This can actually be done on the same machine if that's what you have, but in order to preserve existing settings and data without having any down time, I'd suggest that you use the SwingIT Migration method from

http://www.sbsmigration.com.

Their kit runs about $200, but will be well worth it because you'll have full guidance on how to proceed.



Jeffrey B. Kane
TechSoEasy

http://www.techsoeasy.com

Blog:

http://techsoeasy.spaces.live.com