understanding and troubleshooting evaluation windows version and activation failures on azure vms

Hi ,

when I was working on Azure, I got below scenario.
I have created a VM by using LCS, which was demo env. hence the licensing and all were evaluation.
this URL ( Click Here )says more on demo env license.

so this env gives a period, in my case of 90 days for OS.
so you must activate this or reamr to extend this to a grace period.
 to get grace period follow below.

ReArm, get grace period of 180 days
there are some standard scripts given inside VM to do so under C:\DemoFiles\StartupScripts\Rearm. open command prompt as Admin. then run
rearm.cmd and then activate.cmd . make sure your VM connected to internet.

else run below command in elevated command prompt

slmgr.vbs /rearm

now restart your VM.

now activate it
slmgr.vbs /ato
slmgr.vbs /dlv

if you have any error while doTroubleshooting Windows activation failures on Azure VMsing so, please follow below link....
http://blogs.msdn.com/b/mast/archive/2014/12/23/troubleshooting-windows-activation-failures-on-azure-vms.aspx

you can also activate to MSDN key

MSDN Key
this is very simple, you need to have the respective MSDN version key with you.
to get the version you can run below command in elevated command prompt or power shell
DISM.exe /Online /Get-TargetEditions
this result will help to know, to which edition you can activate.
in my caseI got below, mine is ServerDatacenter

PS C:\Users\Administrator> DISM.exe /Online /Get-TargetEditions Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Image Version: 6.3.9600.17031 Editions that can be upgraded to: Target Edition : ServerDatacenter The operation completed successfully

you can get the current version with command DISM.exe /Online /Get-CurrentEdition

not you get your MSDN data center key and run below command
DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

 

this should show a success message and will ask you for restart and enter Y (make sure you have saved your work)

I got below result

PS C:\Users\Administrator> DISM /online /Set-Edition:ServerDatacenter /ProductKey: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX/AcceptEula   Deployment Image Servicing and Management tool Version: 6.3.9600.17031   Image Version: 6.3.9600.17031   Starting to update components... Starting to install product key... Finished installing product key.   Removing package Microsoft-Windows-ServerDatacenterEvalEdition~31bf3856ad364e35~amd64~~6.3.9600.16384 [==========================100.0%==========================] 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) Y

Hope this will help someone.

 

Regards,

Sudhanshu 

 

Azure number of VMs, more than you subscribed, 1 domain names are needed for this configuration, but only 0 domain names (of 20) remain in your subscription.Request an increase

while working in azure, I was trying to create a vm and got below error
in new portal
Azure number of VMs, more than you subscribed, 1 domain names are needed for this configuration, but only 0 domain names (of 20) remain in your subscription.Request an increase

in old portal

this means, that you have exceeded the maximum number of VMs you can create under your subscription. this is good has been done from MS side, that there is an alert in a certain range.

so to get this you need to request to MS to increase the max number of VMs you can have, check if this has any relation with the number of cores that you can have.
cause the initial assigned cores you might not have used for all 20 VMs.

hope this will help.

Regards,
Yes.Sudhanshu

A Membership Provider has not been configured correctly. Check the web.config settings for this web application. FBA configuration AX dynamics 2012

while configuring claim base login for dynamics ax 2012 with sharepoint 2013, I configured everything, but while going to Site Settings > FBA User Management , I got the below error

"A Membership Provider has not been configured correctly. Check the web.config settings for this web application."

but I thoroughly checked all my configs are correct, including the membership and permissions in DB as well.

finally I found that my app pools ( Ep site and STS site) were running in different accounts. hence causing this issue.
finally I make them all same and all were OK.

Regards,
Yes.Sudhanshu

WARNING: No deployment found in service: in Windows Azure

hi while setting a static IP to one of my Azure VM, I got the below warning message.
"WARNING: No deployment found in service: <service name>"
however I was able to do so earlier.
then I realise that I have multiple subscriptions in same login.
so this is issue of subscription.
so before you use the command you must set your subscription for which you wan to work.
get the list of subscriptions you have
Get-AzureSubscription | Select SubscriptionName

now set to the desired subscription
Select-AzureSubscription -SubscriptionName "<Your-Desired-Subscription-Name-Here>"
then use your command.

Regards,
yes.sudhanshu

How to change the authentication (Multifactor authentication) mode setting in Azure

initially I had MFA call to mobile, when I set the MFA.
then I tot when I will travel, I need to hv the app. so this is how you can change to other options...

login to you azure subscription.
on the top right corner and select "Additional security verification" and that will drive you another screen as below as select as highlighted..

after this click Configure and then it will as you to scan the bar code, before that you must install the Multi-factor App (make sure you download the correct one from MS), then follow the steps in the screen. then you are done.

 

same way you can change to other options...

hope this will help surely...

 

Regards,

Yes.Sudhanshu

 

This runbook is deprecated. Please use OrgID credential auth .

while creating automate process , I was authenticating and for the below warning....

WARNING: This runbook is deprecated. Please use OrgID credential auth to connect to Azure, instead of certificate auth using this runbook. You can learn more about using credential auth with Azure here: http://aka.ms/Sspv1l

so the new Azure AD authentication has been implemented and the old one (cert) will be deprecated.
follow the link http://aka.ms/Sspv1l to get the details of Azure AD authentication.
regards,
yes.sudhanshu