<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtual-Machine on Anything About IT</title><link>https://www.verboon.info/tags/virtual-machine/</link><description>Recent content in Virtual-Machine on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Apr 2015 22:52:41 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/virtual-machine/index.xml" rel="self" type="application/rss+xml"/><item><title>How to troubleshoot a Windows-based Azure Virtual Machine</title><link>https://www.verboon.info/2015/04/how-to-troubleshoot-a-windows-based-azure-virtual-machine/</link><pubDate>Sun, 05 Apr 2015 22:52:41 +0000</pubDate><guid>https://www.verboon.info/2015/04/how-to-troubleshoot-a-windows-based-azure-virtual-machine/</guid><description>&lt;p&gt;When a physical device running Windows has problems, you have all sorts of possibilities to fix it, when virtual machine hosted within your on-premise virtualization infrastructure runs into issues, you still have all options to fix it. But the first time when a virtual machine hosted in Azure gets into trouble you might feel a little bit lost. But there’s hope. When I ran into an issue myself recently I found the following article “&lt;a href="http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-troubleshoot-remote-desktop-connections/"&gt;Troubleshoot Remote Desktop connections to a Windows-based Azure Virtual Machine&lt;/a&gt;”&lt;/p&gt;</description></item></channel></rss>