I have a Windows Instance running in Google Cloud with two disks (ie boot disk and empty drive).
I manually logged into the machine and copied boot data into empty drive. I removed the boot and tried to spin up the VM with the empty drive and it was successful.
However, instead of showing RDP connect button now it is showing SSH. Any idea on why this is happening or how to solve the issue?
Which version of Windows are you installing?
Some new versions of Windows Server like "Core" versions only have access by SSH, the procedure that you have performed seems a little bit strange.
My suggestion is to redeploy your VM and check your attached disk looking for everything that is right on the boot disk.
Related
I cannot access the ssh console at all. Is there a way for me to download the disk inside the cloud platform?
You should be able to get onto the VM through a serial console:
https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-using-serial-console
Alternatively, mount the disk on another, VM revert the change and then put it back on the original VM.
I have changed some rdp settings to the windows server. I can see the screenshot but I cannot able to connect to the instance. What are the other methods to connect to the instance? I dont have snapshots. How to fix this?
Create an AMI of your server before doing anything below.
You will not be able to connect to the instance using RDP if you have messed up RDP thru any other tool. You might be able to repair your settings by attaching the root EBS volume on another Windows instance and repairing.
This document will show you how to attach the Windows volume to another server. Just skip the stuff about resetting the password.
Resetting the Windows Administrator Password
If the changes to RDP were made in the registry, you can also attach the registry on the other Windows instance. Then undo / repair your changes.
Just make sure that you are using the same Windows versions for everything above.
Load or Unload Registry Hives
Edit another Windows install's registry
I have a Windows Server 2012 instance running on Gcloud Compute Engine. Just yesterday I was installing an antivirus and the program installation stopped.
I aborted the installation and rebooted the instance, but I was unable to access again to the instance. I can't figure out any way to access this instance any more.
It doesn't appear there is a console. Is there a way to force Windows into safe mode during boot time from gcloud? Any suggestions?
Thanks,
Jeremy
I have one instance of a Windows Server 12 R2 VM on google cloud that's working properly and I have connected to it successfully using RDP. I have tried to replicate it by creating a snapshot out of it and creating an instance from the snapshot. According to the platform the instance was created, but i can't seem to connect to it or to get a password. When I click "Get windows password" I get this:
forever. When i try to connect to it, I get
I have no idea what to do, any help would be appreciated.Thanks
The password creation tool from the console only works for images builted from the official image repo. In this case your source is a previous VM through a snapshot. In that case, and also in migrations all the previous credentials are kept in the new VM. You can download the GCP RDP agent here and access using the credential you used to have in your source VM.
Connecting to a Windows Instance
https://cloud.google.com/compute/docs/instances/windows/connecting-to-windows-instance
-----------Update----------------
In the case you can not get to enter the VM, it seems to be a firewall rules issue. By default the port tcp:3389(RDP access) is open to all VM at the default network, check your VM is in that network or check if the firewall rule has a tag to be applied.
If not, apply a tag to your new machine and create a firewall rule tobe applied to that tag.
Hope it help. Keep us posted!
For testing of automated OS deploy on a hardware cluster, I need Vagrant to create few VMs without OS installed, with just network boot enabled.
I succesfully created base box image and configured boot order with Vagrant.
Problem is that Vagrant dies after waiting for VM to boot (which it doesn't, because it has nothing to boot), trying to set up ssh forwarding, shared folders etc.
Is there any way I can tell Vagrant to just power on the machine and not try to configure or boot it?
Vagrant's idea is to manage already installed boxes. It has some requirements for them. SSH or other login access is a fundamental one.
If you just want to spin up a VirtualBox VM, you can call VBoxManage etc. directly.