14

We ran into a little issue where Windows Server Standard only supports 32 GB of memory, which is depressing to find out when your server was recently upgraded to 48 awesome GB of memory.

Is it possible to do an in-place upgrade from Windows Server Standard (max 32 GB memory support) to Windows Server Enterprise or Datacenter (max 2TB memory support)?

I tried kicking off the Windows Server 2008 setup.exe from within the OS, which gives me an "upgrade" option.. but when I get to the "Where do you want to install Windows" part of the process, it tells me

The partition you selected might contain files from a previous Windows installation. If it does, these files and folders will be moved to a folder named Windows.old. You will be able to access the information in Windows.old, but you will not be able to use your previous versions of Windows

That's... not... what I had in mind when I clicked "upgrade"!

I really don't want to deal with a clean OS install on our production database sever, and would much rather do an upgrade install if at all possible!

chmeee
  • 7,370
  • 3
  • 30
  • 43
Jeff Atwood
  • 13,104
  • 20
  • 75
  • 92

6 Answers6

17

I know this question was originally regarding Server 2008, but I thought I'd post an easier answer that applies to Server 2008 R2 (and Win7 for that matter). I got the original info from TechNet Server Core blog post.

Starting with Windows 7 and 2008 R2, it's possible to upgrade editions in-place with the dism utility. You can only go upwards in edition (i.e. Standard to Enterprise) and you can't reverse the change. You'll also need the associated KMS Client Setup Key for the version you're going to. Here's a link to the list of KMS Client Setup Keys

To determine the installed edition, run:
DISM /online /Get-CurrentEdition

To check the possible target editions, run:
DISM /online /Get-TargetEditions

Finally, to initiate an upgrade, run:
DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

For example, to upgrade to Enterprise from a downlevel version, run:
DISM /online /Set-Edition:ServerEnterprise /ProductKey:489J6-VHDMP-X63PK-3K798-CPX3Y

Ryan Bolger
  • 16,755
  • 4
  • 42
  • 64
  • has anyone been able to upgrade to Server 2k8 R2 SP1 after doing this? I've been unable to. see: http://serverfault.com/questions/239366/error-when-installing-server-2008-r2-sp1 – TodK Feb 23 '11 at 18:49
  • KMS Client Keys (required for KMS-activated OS instances' Product Key in the DISM command): http://technet.microsoft.com/en-us/library/ff793421 – aharden Jul 18 '12 at 13:25
13

I fired up a VM with Windows 2008 Standard on it, and then upgraded it to Enterprise. At first I couldn't because I didn't have enough disk space available on the C drive. It appears that 15-20 Gigs of free space is required. Once I made the C drive larger it upgraded without issue.

When there wasn't enough space it wouldn't upgrade and would require that I install a new OS much like you said you saw.

After I clicked upgrade, the installer confirmed that I wanted to upgrade then it started the upgrade. It's still running at the moment, but I'm sure it'll finish eventually.

mrdenny
  • 27,174
  • 4
  • 41
  • 69
  • My upgrade finished without a problem. The only thing I can think of is that maybe your C drive didn't have enough space on it to do the actual upgrade. – mrdenny Jul 02 '09 at 06:37
  • 1
    In fact, I was able to upgrade one of our "spare" servers 100% remotely. And it WORKED! Rebooted and remoted back into a Windows Server 2008 Enterprise server. Pretty impressive.. – Jeff Atwood Jul 02 '09 at 08:06
  • +1 for spinning up a VM and testing it! I had to get to bed, so I couldn't... *smile* – Evan Anderson Jul 02 '09 at 12:10
  • Huzzah for the tireless pursuit of knowledge. – Kara Marfia Jul 02 '09 at 13:13
5

Microsoft seems to say so: http://technet.microsoft.com/en-us/library/cc755199(WS.10).aspx

This discussion seems to indicate that it's a matter of starting SETUP.EXE from inside the existing OS, as you did: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/a9fb29a1-9cad-4d01-9e65-ce9b2b88232b

I'd say spin up a scratch box and give it a try... (or start a community IT support site and wait for some poor addicted fool to do it and report back on whether or not it works... >smile<)

Evan Anderson
  • 141,881
  • 20
  • 196
  • 331
1

The message you get makes sense in the context, that this upgrade procedure is the same one for upgrading Windows Server 2003 to 2008. It's a warning that the old version - in your case the 2008 Standard Edition - cannot be used after the upgrade.

During the upgrade process all files, folders and applications associated with the previously installed Windows version are relocated to a windows.old folder and all user settings stored.

Once this task was completed, a clean installation of the new Windows version is performed and all saved user settings will be migrated to the new environment. A successful upgrade will include all applications, settings and user files from the previous operating system installation - in your case from Windows Server 2008 Standard.

Good luck!

splattne
  • 28,508
  • 20
  • 98
  • 148
  • I think I just made a mistake and clicked the wrong button [upgrade/install] in the dialog the 1st time, because now it's definitely doing an UPGRADE. Not getting the warning. – Jeff Atwood Jul 02 '09 at 06:44
1

As the answer is already here, I just thought I'd be the boring guy by stating that the general opinion on doing upgrades on Windows is that this is a feature reserved for home use and even then as a last resort only.

Wipe and redeploy. There are too many things that can go awry during an upgrade that are not immediately apparent.

But good thing it seems to work, I guess ;p

Oskar Duveborn
  • 10,760
  • 3
  • 33
  • 48
  • Well, in case of stuff like Win2008 Standard to Enterprise it's not really an upgrade, it's just adding some more features, as they are essentially the exact same operating system. Of course, exception is stuff like "Non-Service Pack installation CD on a SP1 System". – Michael Stum Jul 02 '09 at 18:17
  • Yeah sure, it might be as little as changing a registry value to gain access to enterprise features and limits I guess... but still ^^ – Oskar Duveborn Jul 02 '09 at 19:03
0

I ran into some problems when trying to upgrade to Enterprise from Standard because our Product keys worked for both editions. Found the reason in this blog. The blog also recommended to use a MS client setup key to do the upgrade. The keys can be found here.

knurmia
  • 11
  • 3
  • Enterprise keys work for Standard Edition too. You do not need to enter a key during installation (applies to Server 2008 or Vista and newer OSes only). – Chris S May 31 '11 at 19:38