Licensing Server 2012 MAK
We had purchased Server 2012 DataCenter MAK licensing, and while it was being shipped we downloaded the DataCenter evaluation edition of Server 2012.
When trying to apply it now, it will not accept it. It says it can not be used for this edition of windows.
Since the editions are the same, DC and DC, I assume it may be because it is a MAK license.
Is there a way to fix this?
When trying to apply it now, it will not accept it. It says it can not be used for this edition of windows.
Since the editions are the same, DC and DC, I assume it may be because it is a MAK license.
Is there a way to fix this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
cgaliher, both are for 2012 R2 DC edition.
Jackie, So is there no way for someone to try out Server 2012 DC (evaluation) and then decide to buy a volume license?
This seems crazy. MS use to have many different DLs for each product type, but it seems like now unless you buy you get two options: Standard or DataCenter,
Jackie, So is there no way for someone to try out Server 2012 DC (evaluation) and then decide to buy a volume license?
This seems crazy. MS use to have many different DLs for each product type, but it seems like now unless you buy you get two options: Standard or DataCenter,
ASKER
Also, If I try to use the eval ISO it accepts the MAK. It is only the ones already installed with the eval License code that won't convert.
So it surely isn't an issue with the ISO used to install.
So it surely isn't an issue with the ISO used to install.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That command appears to work, but it still isn't activated. I tried a few reboots and to force it via Control Panel as suggested in the article. Below is what happens if I use /GetEula and another command. I replaced out Key here of course,
Any ideas from here?
C:\Windows\system32>DISM /online /Get-CurrentEdition
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Current edition is:
Current Edition : ServerDatacenter
The operation completed successfully.
C:\Windows\system32>DISM /online /Set-Edition:ServerDatacen
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Error: 50
This Windows image cannot upgrade to the edition of Windows that was specified.
The upgrade cannot proceed.
Run the /Get-TargetEditions option to see what edition of Windows you can upgrad
e to.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.
C:\Windows\system32>DISM /online /Get-TargetEditions
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Editions that can be upgraded to:
(The current edition cannot be upgraded to any target editions.)
The operation completed successfully.
Any ideas from here?
C:\Windows\system32>DISM /online /Get-CurrentEdition
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Current edition is:
Current Edition : ServerDatacenter
The operation completed successfully.
C:\Windows\system32>DISM /online /Set-Edition:ServerDatacen
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Error: 50
This Windows image cannot upgrade to the edition of Windows that was specified.
The upgrade cannot proceed.
Run the /Get-TargetEditions option to see what edition of Windows you can upgrad
e to.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.
C:\Windows\system32>DISM /online /Get-TargetEditions
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Editions that can be upgraded to:
(The current edition cannot be upgraded to any target editions.)
The operation completed successfully.
ASKER
This is what it looks like when it seems to work:
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Starting to update components...
Starting to install product key...
Finished installing product key.
Removing package Microsoft-Windows-ServerDa
amd64~~6.3.9600.16384
[=========================
Finished updating components.
Starting to apply edition-specific settings...
Finished applying edition-specific settings.
The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now? (Y/N)
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
Starting to update components...
Starting to install product key...
Finished installing product key.
Removing package Microsoft-Windows-ServerDa
amd64~~6.3.9600.16384
[=========================
Finished updating components.
Starting to apply edition-specific settings...
Finished applying edition-specific settings.
The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now? (Y/N)
ASKER
Support case open with MS. If you try that same command after it reboots it says it can't upgrade...
ASKER
MS couldn't resolve the issue.
We however did. We found the issue to be that the 2012 servers were not getting the proper proxy settings. This is because they no longer use the same GPO item to determine these settings. Instead, they look to the Group Policy Preferences for the settings.
Resolving the proxy issues resolved the other issues.
We however did. We found the issue to be that the 2012 servers were not getting the proper proxy settings. This is because they no longer use the same GPO item to determine these settings. Instead, they look to the Group Policy Preferences for the settings.
Resolving the proxy issues resolved the other issues.
You need to re-install the server 2012 using the ISO file downloaded from the MS Volume Licensing Centre.
https://www.microsoft.com/Licensing/servicecenter/default.aspx
You shall sign up a Microsoft account with your email address which your vendor should have informed MS that it is the email address of the administrator of the MAK licence.
Contact your vendor immediately regarding the volume licence.