How to avoid "This Size is not available in zone. . ."
Hi, Anybody has found the optimal solution to avoiding the following text, when selecting the VM on Azure: This size is not available in zone 2. Zones '1' are supported. Of course the zone numbers can be mixing. I tried to use the Get-AzComputeResourceSku CMDlet, but did not got any smarter: PS C:\> Get-AzComputeResourceSku -Location "westeurope" | Where-Object { $_.name -EQ "Standard_D4_v5" } ResourceType Name Location Zones RestrictionInfo ------------ ---- -------- ----- --------------- virtualMachines Standard_D4_v5 westeurope {1, 2, 3} type: Zone, locations: westeurope, zones: 2, 3 Basically Zones says, this should be available, but when trying to select that on portal or run PS. PowerShell gives the following error: New-AzVM: The requested size for resource '/subscriptions/.../virtualMachines/myVM' is currently not available in location 'westeurope' zones '2' for subscription '111.....111'. Please try another size or deploy to a different location or zones. ErrorCode: SkuNotAvailable ErrorTarget: StatusCode: 409 ReasonPhrase: Conflict The funny thing is, this speaks about "subscription" and if I choose a different subscription this VM size is available on the same zone. So I'm interest to hear what others are using for listing available VM sizes, to see how to choose similar VMs on all zones? I have tested with different sizes, and seems to be the case a bit randomly.
Connection was denied because the user account is not authorised for remote log in
Hi experts, ... there was a restart of the server that is running as VM in azure... and since then, I've been experiencing some issues that are seriously affecting the company. When I want to RDP with a required account (lets call it "azvmuser") to the server, I get the message that I'm not authorized. With Administrator account, I can connect with no issues... The only way I could fix it was by adding the "azvmuser" via "User Accounts" -> "Give other users access to this computer" .... This works for a while however at some point the issue returns and when I check the Users Accounts again, the "azvmuser" is missing there again and have to add it again... There is a task created in "Task Scheduler" that runs for that user and due to the issue above, the task is failing... When I add the user to "Give other users access...", the Task runs fine... Any idea how to fix it? ... for now, I just manually check the VM and add the user "azvmuser" when I get the error message... It is happening for a business critical VM..... other 3 VMs we have in Azure are working fine 😕
Azure, Hypher-V machine getting out to the internet
Hello there, I would like to ask a question: In Azure, I have created a Virtual Machine with Windows 2016. This machine has connectivity to the internet ( 10.0.0.4 , gateway 10.0.0.1 , and DNS itselft (10.0.0.4) because it is a Domain Controler ) In that Virtual Machine I have installed the Hyper-V feature. Inside Hyper-V I have created a Virtual machine. This virtual machine is domain-joined ( 10.0.0.5 , Gateway: 10.0.0.1 , DNS: 10.0.0.4 ) This virtual machine is attached to a Hyper-V virtual switch set as external. In that scenario, why does the virtual machine inside Hyper-V cannot reach 8.8.8.8 through ping ? I tried to set "IP Forwarding" to the network nic attached to the Hypher-V host , so that the machine inside Hyper-V could get to the internet, but it hasn't worked. I don't get much information throught "tracert 8.8.8.8" , all it says is "not reachable" but it doesn't even reach 10.0.0.1 , maybe because that IP is Azure-managed ( the gateway ) Any thoughts on this? , thanks in advance!
