Hot answers tagged

3

DS-series VMs are capable of using Premium disks for either OS or Data (or both). But the performance will ultimately depend on which type of disk you use. If you use a standard disk, it will perform just like a D-series. In your case, since you created your OS disk as a standard storage VHD, it will have all the performance characteristics of standard ...


3

As you correctly state, all Azure disk storage (except for temporary disks) are replicated 3 times in the same DC, and if you use geo replication than another 3 times in another DC, so realistically disk failure is an unlikely cause. There are a few reasons I could think of that might explain this: As HopelesNoob mention, it could be data corruption, if ...


2

The problem was due to the machine being cloned. Remote Desktop has a certificate associated with it. That certificate has the machine name within it. If the machine name in the certificate does not match the current machine name, Remote Desktop will not run. To solve this problem: Run the Certificate Manager ( certlm.msc ). Navigate to Remote Desktop -> ...


2

You can switch to another console, log in to a new session, and then kill the ping process running in the first console. To switch consoles, just press Alt while pressing the left or right arrow keys. This take me through 6 different consoles.


2

Well there is still no option in the GUI, but Samir Farhat has written a powershell script which can be used to change the AS of existing VM in ARM mode. AFAIK, this feature may be addressed by the end of this year. It's a big challenge for the MS team to allow such operation. Changing the availability Set requires a review of the VM mobility ...


1

I raised a ticket with Microsoft and they confirmed that the SQL Express version number caused the problem. Their response was: the product team has confirmed that the "SQL Server 2014 SP1 Express on Windows Server 2012 R2" image was wrongly built by an internal builds (12.0.4193.9). I am not sure when they will have it fixed. As a workaround I ...


1

This isn't really an Azure question, its a "how do I do SQL clustering question". You can't just share a SQL database between two VM's and it magically work, you would need to setup your VM's in a cluster to share the SQL workload between them. Clustering in Azure is slightly different than on premises as you can't use shared disk storage for clustering ...


1

Your Classic VMs and ARM VM's can't share the same VNET, they need v1 and v2 VNETs respectively. You could join the two VNETs togther using a VNET to VNET connection, but this document states: A cloud service or a load balancing endpoint CANNOT span across virtual networks, even if they are connected together. This goes for the ARM load balancer as ...


1

In order to be in an same availability set the VMs need to be in the same region.


1

The obvious way is to run a login script (either GPO or local policy) to map the drive. Obviously the downside to this is that your storage credentials will be stored in plain text in the login script, you can do some encryption with PowerShell or similar but this still doesn't stop someone walking away with the login script and using it elsewhere. Which I ...


1

In a general sense I suspect MTU (frame size) is the root of the problem. I have a few reasons and a few suggestions. First, this behavior varies by L2 (it only happens with the wired traffic as opposed to wireless). That in itself is suspicious and suggests that there is a problem at the interface level. Second, packet fragmentation is a symptom of MTU ...


1

I want to sync files from serverA to serverB, but there's no direct connection between them, but I have serverC that can access both serverA and serverB. what worked for me is: on serverC: ssh user@serverA 'rsync -avP -e "ssh -ax user@serverC ssh " /source/files user@serverB:/des/tination'



Only top voted, non community-wiki answers of a minimum length are eligible