Hello everyone.

So, my organization has some issues. My primary focus is ramping up security, and one thing sticking out like a sore thumb is our legacy Windows 2003 Server x64 running Exchange 2007. Spiceworks has identified known threats probing this server on three separate instances in the past 4 weeks.

Our exchange server, again, is currently operating on Windows Server 2003 x64 SP2 with Exchange 2007.
The goal would ultimately be Windows 2012 R2 with Exchange 2013.

The specs of the server are as follows:
Supermicro / X7DB8
8 x Intel Pentium III Xeon
16GB RAM

I know that the migration process from Server 2003 is not exactly painless. I was considering purchasing a new SSD drive, placing the drive into one of our unused workstations, doing a full install and configuration, performing a live test on the network during the weekend and then, upon success, swapping out with the primary drive on the server. I will obviously have the drivers on hand, but I am still wondering if there would be an easier way to go about doing this?

Also, does anyone have any suggestions or detailed links to the steps I can take for this migration? I have experience working with Server, but not so much when it comes to the Exchange end. The videos I have watched look pretty straight forward with the setup and Powershell procedures... just wanted to know if this would be something I could try or will we inevitably be better off forking out a massive chunk to acquire outside assistance?

You can't in-place upgrade or do a swap of any kind with Exchange.

I am also not sure where you have got the idea that migrations off Windows 2003 are difficult, because they are not.

If you want to upgrade the same hardware then you are going to need another machine to use as a staging post. That will allow you to install Exchange 2013 on to it, move all the data, so you can then remove Exchange 2007 and rebuild the box.

Anything else is high risk.

You also don't want to rush the migration. You haven't said how many users you have, but trying to do it in a weekend is asking for problems.

An external consultancy would probably help you a lot, but you will still need an additional machine to use an interim point. You cannot avoid that.

Simon.

I don't know that upgrading an OS on an existing Exchange server is supported.  And I wouldn't do that anyway.  I would just bite the bullet and transition to Exchange 2013, remove Exchange 2007 and decommission the Windows 2003 server entirely.

Thanks, Simon.

I figured an interim point was required. Our Exchange server currently has just over 200 users.

But using a workstation as the interim point to transition all of the data and settings to a clean Server 2012 R2 install and then replacing the drive or imaging it onto the existing server is out of the question? I'm trying to formulate the most cost effective AND low risk scenario.

Imaging introduces risk that can be avoided. If you are moving to a different server (which would be a workstation) then you are also introducing hardware driver compatibility issues.

Or you could just build a new server with Windows 2012 R2, do the Exchange 2013 migration on to it, then remove Exchange 2007 from the old server. What you do with the hard disks in the machine is completely irrelevant.

I wouldn't suggest taking the disks from the temporary system and putting them in to the old server, for the same reasons as taking an image is a bad idea.

Don't try to shortcut a migration, it will only come to bite you later on.

Simon.

Thanks for the advice, Simon. I certainly see your point that this is not an area to be cutting corners.

Just thought I'd join in and try help out a bit. Having 200 users on a single point of failure which is also quite old hardware gives you some leverage to push for funding for new hardware (ideally two new servers). Once you have this or at least one of these then you can migrate to Server 2012 R2/Exchange 2013.

Thanks.