azure-virtual-machine

问题 I am trying to access an azure vm via powershell remoting from azure automation. All our vms inside the subscription do not have public ips (only private ip). I have tried to access by New-Pssession (as below) , but no luck. Could you please let me know what are the other ways to achive this? $connectionName = "AzureRunAsConnection" $SPC = Get-AutomationConnection -Name $connectionName Write-Output $SPC Add-AzureRmAccount -ServicePrincipal -TenantId $SPC.TenantId -ApplicationId $SPC

问题 I created a Azure VM (windows sever 2016) using azure portal. It has .net 4.6.2 installed on it. Now I want to roll out latest available .net framework (4.7/ 4.7.1) on it. One option is to download required framework and install it on the VM. I am sure there should be some other better way to roll out .net framework on Azure VMs using Azure portal or ARM template. Please help me with the option available for the same. 回答1: Like the other answer says, you could use Azure Powershell DSC

问题 I created a Azure VM (windows sever 2016) using azure portal. It has .net 4.6.2 installed on it. Now I want to roll out latest available .net framework (4.7/ 4.7.1) on it. One option is to download required framework and install it on the VM. I am sure there should be some other better way to roll out .net framework on Azure VMs using Azure portal or ARM template. Please help me with the option available for the same. 回答1: Like the other answer says, you could use Azure Powershell DSC

问题 I have deleted some Key Vaults from my resource manager after assuming that they are not used anywhere in my configuration and that those were some leftovers from my testing. Now I can't start my virtual machines and this error message appears. Failed to start virtual machine 'xxxx'. Error: The Key Vault secret referenced with the URL 'xxxx' does not exist. Could you please advise me how to put my virtual machines back on track since I can't afford the time building them again? Thanks a lot.

问题 I have deleted some Key Vaults from my resource manager after assuming that they are not used anywhere in my configuration and that those were some leftovers from my testing. Now I can't start my virtual machines and this error message appears. Failed to start virtual machine 'xxxx'. Error: The Key Vault secret referenced with the URL 'xxxx' does not exist. Could you please advise me how to put my virtual machines back on track since I can't afford the time building them again? Thanks a lot.

问题 I have deleted some Key Vaults from my resource manager after assuming that they are not used anywhere in my configuration and that those were some leftovers from my testing. Now I can't start my virtual machines and this error message appears. Failed to start virtual machine 'xxxx'. Error: The Key Vault secret referenced with the URL 'xxxx' does not exist. Could you please advise me how to put my virtual machines back on track since I can't afford the time building them again? Thanks a lot.

问题 I have deleted some Key Vaults from my resource manager after assuming that they are not used anywhere in my configuration and that those were some leftovers from my testing. Now I can't start my virtual machines and this error message appears. Failed to start virtual machine 'xxxx'. Error: The Key Vault secret referenced with the URL 'xxxx' does not exist. Could you please advise me how to put my virtual machines back on track since I can't afford the time building them again? Thanks a lot.

问题 I am very new to the AZURE, and was trying to connect two VM (same network, separate Subset). I have enabled RDP on both the VM, So I can ping from VM-1 to VM-2 like this: PS C:\Users\AzureUser> Test-NetConnection 10.0.1.4 -port 3389 ComputerName : 10.0.1.4 RemoteAddress : 10.0.1.4 RemotePort : 3389 InterfaceAlias : Ethernet SourceAddress : 10.0.0.4 TcpTestSucceeded : True I guess this is because this port 3389 is used for RDP. Now in Inbound port rules I have added port 8080 but not able to

问题 My (dotNET) application is built (using a Windows Hosted agent), from a build pipeline, and in the subsequent Release pipeline, I provision a 16GB-Win2016 VM (enabling RDP, HTTP, HTTPS, WinRM and SSH), into which I RDP manually (there is a Manual Intervention task here), and configure WinRM (following this article: https://docs.microsoft.com/en-us/azure/marketplace/cloud-partner-portal/virtual-machine/cpp-configure-winrm-after-vm-creation#configure-vm-to-enable-winrm). Everything is fine

问题 Hi I have a azure vm on which I want to configure port forwarding so that I can redirect traffic to 1100 port, I have created a public loadbalancer and in NAT rule I have configured the ports, but seems that I cant RDP onto the VM using my port 1100, can anyone suggest me some documents where I can get this thing done? Or point me in the right direction? 回答1: As I understand, you want to RDP your Azure VM through the front port 1100 of Load Balancer. So you need to add your VM into the