Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We recently had to upgrade our servers from Win 2008 R2 Standard to Enterprise. The upgrade method was DISM. After the upgrade, a lot of weird things started to happen.

Though Windows says it's been properly activated, we lost 1) RDP settings (disappeared from the Remote Setting tab of Properties of My Computer) 2) The option to join a domain is grayed out 3) The server had to 2 physical processors 12 cores each. Now, task manager or windows sees only 1 processor (or only 12 cores) 4) the amount of physical ram on this sever is 32 GB (Windows reports only 4 GB are usable)

Has anyone encountered this before ? Thanks Ravi

share|improve this question does this apply – tony roth Feb 27 '12 at 0:34
Yeah I have heard of this before, on this very site. I just can't find the link to it! – Mark Henderson Feb 27 '12 at 3:17
@tonyroth I will follow the steps for MS kb you provided and let know – Ravi Feb 27 '12 at 7:37
up vote -1 down vote accepted

This KB will take you through resolving your issue:

The issue is that your current install is tied to KMS and not MAK. Use the relevant KMS key from and then use slmgr.vbs to set your key once the Transmog is done.

"Remember to activiate your server, or stuff like Remote Desktop will be disabled."

The above quote is incorrect all features work just fine you just get a black desktop.

share|improve this answer
FrontPage? Is that the correct KB in your link? Perfect example of why a single-link-only answer isn't really desirable here. – jscott Feb 27 '12 at 1:08
@jscott (and other downvoters) It's obviously a typo in the link, he has the correct link in the comment he posted above. Still, a description of what the link is to would be a good idea. – Ward Feb 27 '12 at 7:00
fwiw, I've not down voted the answer. I had hope a comment would prompt the poster to add information to their answer. – jscott Feb 27 '12 at 11:13

It sounds like you never re-activated Windows after the upgrade. Make sure you change the installed product key to one for Enterprise and you run through activation again.

share|improve this answer
We did activate Windows after the upgrade, by changing the key and going through the procedure. Windows even says it's activated. I wonder if we have to do this via command line also (…) last comment – Ravi Feb 27 '12 at 6:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.