I cannot currently rdp to my Azure server. After checking the RDP endpoints were open I looked at the Boot Diagnostics and a Settings window was displayed.
Is this significant, if so how do I correct it.
Note: I created another VM based on a previous image of the problematic server and the same thing happened.
Thanks
Phil
According to your description, I had test in my lab, follow this article I had create image, and it works. Maybe there are some points need to consider:
1.run sysprep.exe, in Shutdown Options, select Shutdown. After sysprep.exe was running, we will disconnect this VM, but it does not mean this VM was stopped.
We should confirm the status of this VM, we can via portal to check the status:
2.After this VM's status is stopped, then we can click the VM and select the virtual machine you want to capture.
3.Then we can use this image to create a new VM.
You should re-capture this image.
Note:Prior to caputuring an image of an Azure virtual machine, it is recommended the target virtual machine be backed up
Related
The Azure Monitoring Agent is a service that runs on a virtual machine and sends logs and metrics to Azure Analytics. This agent can be installed via multiple ways, for example:
by selecting the option while creating the VMSS, for example in the Azure portal
with an "Enable" button in the monitoring section of a VMSS in case it was not installed while the VMSS was created
by installing the the correct "extension" for all machines in the VMSS
manually or automated as a software installation inside the virtual machine, for example via ansible or actually by hand
There might be more options, but in any case the agent needs to know to which Analytics Workspace it should send its data, and this value is a user input during the installation of the agent.
Now, once installed, how can I change the destination Analytics Workspace for an entire VMSS?
There is no option to change the workspace. for the Virtual machines scale sets this support is limited as of now.
I use Azure- windows VM for running some services, the services are very stable(after testing).
The server run one day and after that he has fallen and i get this message.
**
Diagnose and solve problems
In Activity log
Resource health
Solved
The problem was in 'Auto-shutdown' it was enabled to 'Scheduled shutdown'. you can find it under - HOME --> VM --> Auto-shutdown(under the title Operations).
From the Activity Log, we can see the Azure Lab Service initiated the VM deallocation.
When you create a Lab Service in Azure, there is an option for you to automatically shut down virtual machines when users disconnect. It's probably the reason. This could help save costs.
It's the same Lab policy when you create template VMs in the lab Account or change it later.
Does Azure deallocate end user's VM's at its own discretion?
I was using an Azure VM for a clean build and then the remote connection was dropped, I tried to reconnect by RDP and found out the machine was deallocated.
The info from Microsoft was:
Connect is disabled because this virtual machine is deallocated.
I did not know that Azure took machines away like that?
I would be hesitant to use Azure VM's in the future for build work.
Azure does not de-allocate your VM. There are numerous reasons you VM might be de-allocated while you are using it, below are a few;
Like #david mentioned in comment, you ran out of credit
Shared subscription, someone that also has access to you subscription shutdown VM
Automation, VM is set to shutdown at a certain time
These a just a few reason why you vm might have de-allocated while you are using it. If you can't determine on your own why it shutdown you can file a support ticket with Azure support.
Hope this helps.
Check if your appropriate resource group is enabled:
Open Azure portal.
Navigate to the Subscriptions.
Search for the necessary subscription group. enable it.
By default, there is a scheduled shutdown on Azure. If you go to operations settings in the left panel of the Azure VM portal, there is an auto-shutdown. You need to disable it so that your VM won't shutdown at the scheduled time.
Azure VM machine might be in stopped mode so it is saying that error message, please check the Azure VM list and see the status, accordingly start the VM, it will work
normally when you create your VM, you will see that there is a parameter that it will stop at 7pm or something like that. So After 7pm it will stop you VM. Which is good I think, because we tend to forget our VMs and then we pay for nothing. So no worries, just start your vm and you are all good to go :)
I have a azure VM. I setup the Backup in the Recovery Service vaults. Installed Windows Azure Guest Agent on VM (WindowsAzureVmAgent.2.7.1198.778.rd_art_stable.160617-1120.fre.msi), update GuestAgentStatus based on https://blogs.msdn.microsoft.com/mast/2014/04/07/install-the-vm-agent-on-an-existing-azure-vm/ . Now if I check GuestAgentStatus, I can see ProvisionGuestAgent has value.
However, once I setup backup, run it, it always failed. The error message is:
The VM Agent is not in Running State.
The recommended action is:
This is mostly because of older version of VM agent. Please update the VM agent as mentioned in the troubleshooting guide at http://go.microsoft.com/fwlink/?LinkId=800034
It also has another link: https://azure.microsoft.com/en-us/documentation/articles/backup-azure-vms-troubleshoot/
However, they do not provide solution for the same error. There is a similar error:
Could not communicate with the VM agent for snapshot status. - Ensure that VM has internet access. Also, update the VM agent as mentioned in the troubleshooting guide at http://go.microsoft.com/fwlink/?LinkId=800034
The VM agent is the latest, also, I can use its DNS RDP to the VM, there is no problem to browser website like google, etc., and no Network Security Group.
Anyone has any ideas why the backup failed? How do I check whether the VM agent is running?
Thanks
See if restarting the VM post updating the agent is solving the issue. VM agent will be listed under services running inside a Windows machine.
I have a program that I run only 1-2 hours a day. Is there a way to suspend the Azure server so I don't pay for it, then resume it later? How fast is it to suspend and then resume?
To clarify here, Azure no longer charges for stopped VMs. The billing change was announced in 2013 on Scott Guthrie's blog: No Charge for Stopped VMs.
This means you can use the portal or APIs to stop a VM without deallocating the resource - and avoid charges at the same time.
Not sure if you are asking for Window Azure Cloud Services or for Windows Azure Virtual Machines but you sure can stop/start these Azure Virtual Machines directly on Windows Portal or using Powershell or REST based Service Management API. The Windows Azure Portal does not provide a way to schedule stop/restart so you will have to manually do it by yourself or use some 3rd party service i.e. AzureWatch etc to do it.
Note: Even if you shutdown the Virtual Machine or Cloud Service, you will still pay for if you want to do it for cost saving, then you would need to delete the service or VM. Reboot/Restart does not take long as VM is already configured and ready to run so it is just the time to turn on a pre-configured VM.
If you want to use REST API in your own application to stop/start here is some help:
Virtual Machines: http://msdn.microsoft.com/en-us/library/windowsazure/jj157206.aspx
Cloud Service: http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx
If you want to use Powershell to stop/Start Azure VM look for "Start-AzureVM" and "Stop-AzureVM" cmdlet below:
http://msdn.microsoft.com/en-us/library/windowsazure/jj152841.aspx
To save money, I did Remote Desktop to my Azure Windows VM, and clicked shutdown.
Then, at my Azure dashboard (https://manage.windowsazure.com) > VIRTUAL MACHINES > STATUS it changed from Running to Stopped.
But then I read this doesn't stop the billing.
So I went to Microsoft Azure > Virtual machines (classic) >
and saw the status was Stopped. But this doesn't mean billing stopped.
I clicked the "stop" command, and it changed to Stopped (deallocated) which means no (or near 0) billing.
The screenshot says it all... so only a "deallocated" VM won't be billed!
One more thing to add. As opposed to a deleted VM, a deallocated VM still has virtual disks attached to it which consume storage space and therefor creates costs.
If you mean the "suspended" state you can achieve with your computer I don't think is available today on Azure.
Google Cloud for example has just released that feature on beta https://cloud.google.com/compute/docs/instances/suspending-an-instance