azure-virtual-machine

问题 I have an Azure Virtual Machine. When I log in through RDP I can see only black screen and CMD console is opened. Is it possibile that there is no explorer? VM OS spec: Operating system: Windows Publisher: MicrosoftWindowsServer Offer: WindowsServerSemiAnnual SKU: Datacenter-Core-1803-with-Containers-smalldisk Version: latest I have tried multiple things: Connect RDP through 3 different apps (Windows Remote Desktop Connection, Windows Remote Desktop Connection Manager, Remote Desktop Manager)

问题 I'm able to run puppet bolt command in powershell. In powershell, I got output as below Started on winrm://remotemachine Finished on winrm://remotemachine STDOUT: RemoteMachineHostName Successful on 1 target Run on 1 tartget in 3.2 sec My C# is as below PowerShell ps = PowerShell.Create(); ps.AddScript("C:\\User1\\GetRemoteAzureVMHostName.ps1"); Collection<PSObject> results = ps.Invoke(); // in results, I'm getting value as 0. foreach (PSObject result in results) { //Do something } I tried

问题 I'm trying to run below puppet bolt command for remote Azure VM through powershell . bolt command run ipconfig --targets winrm://158.28.0.546 --no-ssl -user testuser123 -password test@84p getting below error for above command in powershell Failed on 192.168.0.140: Timeout after 10 seconds connecting to 192.168.0.140 Failed on 1 target: 192.168.0.140 How to resolve above issue Update 1: WinRM enabled on remote Azure Virtual Machine . Even Firewall is disabled on Azure VM for public networks.

问题 I'm trying to run below puppet bolt command for remote Azure VM through powershell . bolt command run ipconfig --targets winrm://158.28.0.546 --no-ssl -user testuser123 -password test@84p getting below error for above command in powershell Failed on 192.168.0.140: Timeout after 10 seconds connecting to 192.168.0.140 Failed on 1 target: 192.168.0.140 How to resolve above issue Update 1: WinRM enabled on remote Azure Virtual Machine . Even Firewall is disabled on Azure VM for public networks.

问题 I tried with below script in local machine to run remote powershell script which is located in remote azure vm . I'm able to connect to azure remote vm through powershell pssession , but Invoke-Command is not returning anything. Unable to run remote powershell script . I tried as below aswell But -FilePath trying to look into local machine D: drive instead of remote azure vm D: drive. How to run remote azure vm powershell script which is located in remote azure vm D: drive 回答1: My guess is

问题 In case I have 2 VM with premium disk how can I make one to be a cold back. The VM will have SQL server using Premium disks and in case of a failure of one VM I need the other VM to have the last data inserted into SQL server. How can this be done with Cold backup with Azure and assured me zero data loss? 回答1: I dont think there is a way to do this with zero RPO. Both Azure Backup and Azure Site recovery do not offer such RPO. you might be able to use some third party solution, but I dont

问题 I have a VM in azure, and via the portal have selected its Disk, and created a snapshot of it. How do I now revert back to that snapshot for the Disk (via portal or CLI)? I'm not looking to create new disks or VMs from the snapshot, just revert back. 回答1: How do I now revert back to that snapshot for the Disk (via portal or CLI)? Do you mean you want to use this snapshot to rollback your system? Unfortunately, for now Azure does not support this, we can't use snapshot to revert back. In Azure

问题 I've couple of VMs under same subnet in Azure without any availability set attached to any of the vm. When I try to use load balancer (public),it shows two options to load balance VMs Availability set Single VM Is it necessary to use availability set to implement load balancer between VMs and they should be under same availability set? Also ,if above it true, what is the purpose of single vm option where vm is visible to add under load balancer without any availability set? 回答1: Yes, it is.

问题 I would like to keep each VM in separate resource group for ease for lifecycle management. I have a cluster containing n VLMs. So I create one resource group for common things like public IP, load balancer and put availabilitySet declaration into it because is also must be shared between VMs. Then I create VM in separate resource group and reference to availabilitySet with "availabilitySet": { "id": "[resourceId('Microsoft.Compute/availabilitySets',variables('availabilitySetName'))]" }, Of

问题 I'm using command1.ps1 script to install Azure Custom Script Extension on the target VM and execute command2.ps1. command2.ps1 is supposed to run a script (that is inside ScriptBlock) as domain administrator (hence -Credential $Credentials ). When I run command2.ps1 manually and input $domainAdminName and $domainAdminPassword it works, but when running it through command1.ps1 it doesn't work. Maybe the problem is cause by Azure Custom Script Extension running command2.ps1 as System account?