Sign in with
Sign up | Sign in
Your question

Server 2003 to 2012 Questions

Tags:
  • Exchange Server
  • Business Computing
  • Servers
Last response: in Business Computing
Share
January 16, 2014 2:58:18 PM

Hey everyone. I am just looking into how to upgrade our 2003 test server to a 2012 server. From what I have read, you can upgrade server 2003 into the server 2008 and bring up a lot of the roles and programs up with it. From there, upgrade 2008 to 2012. A few questions come into mind before we try this:
1) Will things follow the upgrade path (we're not really running anything on the 2003 server, just a few programs we can reinstall if need and exchange server 2003).
2) Will user accounts follow with the upgrade?
3) Will exchange cals follow or will I have to buy a new exchange server?
4) What cost will there be in doing something like this? Like, do I have to buy a 2008 or can I just use a iso and upgrade. Same for exchange server.. I know we might have to buy 2010 in the end.


Still kind of new to this, so it's just a test computer with a few users. Trying to see how this will work in a real environment.

More about : server 2003 2012 questions

January 19, 2014 8:20:06 AM

The potential issue with your upgrade path is that 32bit installs (which your 2003 server probably is) cannot be upgraded to 64bit installs (which is the only flavour 2012 comes in).

Regarding user accounts, is this server a domain controller? Is it the only domain controller?

Exchange CALs like server CALs are specific to the version of the server software. You would need to purchase both to be compliant.

Regarding costs, aside from the CALs I just mentioned, you should just need to purchase the final version. If you purchase via volume licensing, you are entitled to use any previous versions as needed.

My personal feelings are that you should not attempt to directly upgrade your server. I would get hold of a spare PC, install 2012 on it, promote it to a DC, install Exchange 2010/13, transfer the exchange databases to it, then wipe your proper test server clean, install, promote, transfer back to it.

Also take an image of all volumes on your test server before you start - if you get into trouble, just restore from the back up and it is like it never happened.
m
0
l
!