1. I upgraded an installed and running windows 2008r2 standard server (x64) to enterprise with the dism - tool. it worked fine. 2. I activated this server with the mak-key from technet plus... The activation was successful. 3. The server showed 54 GB of RAM. 4. I rebooted the server. The server showed only 4 GB of RAM and was (of course) completely slow. 5. I removed the activation key and rebooted the server again: The server showed 54 GB of RAM. The server was not activated (of course). But it was perfectly running. 6. After re-installing the mak - key I've got the problems as described in step 4. What can I do ? mcg michael

Hi, are you setting the pkey on the dism commandline? http://social.technet.microsoft.com/forums/en-us/windowsserver2008r2general/thread/CE1A80C6-AC89-442B-8680-0CC11E3CAEC2Don

Hi, How about to activate the server online with the MAK key? Best Regards, Vincent Hu

I finally solved it : For the upgrade with dism I used the generic 489J6-VHDMP-X63PK-3K798-CPX3Y KSM Product Key because my MAK Key was not working. When I later tried to install my MAK Key on the converted server (enterprise) something of the KSM Key sticked to the system making it impossible to get a valid activation. I found the anser in the following post: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/e0083b53-5721-42d8-b676-5bbb1ac76816 These are the steps. 1. Open the command prompt and change working directory to System32 directory 2. Type in slmgr.vbs -ckms (this clears and KMS entry you may have) 3. Type slmgr.vbs -upk (this removes any product key installed) 4. Type slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where the x’s is the new product key you want to use ) 5. Type slmgr.vbs -ato (this activates the server) Thank you, Don for the solution. It works great !! mcg michael

Hello, This is only an issue if you are using a MAK key and doing a DISM upgrade. Activating after the upgrade and installing the MAK should be all that is needed. MAK keys are not edition specific ( same MAK key can be used for Standard and Enterprise which is why you have to use the generic KMS key to go from standard to enterprise. Then you switch back to the MAK key, not everything is updated properly until you activate again after installing the MAK key.)Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

I finally solved it : For the upgrade with dism I used the generic 489J6-VHDMP-X63PK-3K798-CPX3Y KSM Product Key because my MAK Key was not working. When I later tried to install my MAK Key on the converted server (enterprise) something of the KSM Key sticked to the system making it impossible to get a valid activation. I found the anser in the following post: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/e0083b53-5721-42d8-b676-5bbb1ac76816 These are the steps. 1. Open the command prompt and change working directory to System32 directory 2. Type in slmgr.vbs -ckms (this clears and KMS entry you may have) 3. Type slmgr.vbs -upk (this removes any product key installed) 4. Type slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where the x’s is the new product key you want to use ) 5. Type slmgr.vbs -ato (this activates the server) Thank you, Don for the solution. It works great !! mcg michael

Hello, This is only an issue if you are using a MAK key and doing a DISM upgrade. Activating after the upgrade and installing the MAK should be all that is needed. MAK keys are not edition specific ( same MAK key can be used for Standard and Enterprise which is why you have to use the generic KMS key to go from standard to enterprise. Then you switch back to the MAK key, not everything is updated properly until you activate again after installing the MAK key.)Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hello, This is only an issue if you are using a MAK key and doing a DISM upgrade. Activating after the upgrade and installing the MAK should be all that is needed. MAK keys are not edition specific ( same MAK key can be used for Standard and Enterprise which is why you have to use the generic KMS key to go from standard to enterprise. Then you switch back to the MAK key, not everything is updated properly until you activate again after installing the MAK key.) Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en Hello, we had the same problem as described above. But our server was already activated after upgrading to Enterprise. After first reboot of the machine we got the same issue. After follow instructions of Michael server survive 5 reboots until now. Best Sebastian

Hello You reactivated the machine with the MAK key and restarted? Can you make the application event log available for download?Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hi Darrell, Log is around 2 MB. Can i send you the file or a Link more privat as the public forum? Sebastian

Hello, Can you compress it any? You can send to my first name, last initial at microsoft.comThanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en