I´m having a VMware image with Windows Server 2012 installed which I´m trying to import and convert to Amazon EC2.
I´m doing it from command line, and import process to Amazon S3 is successfully, but the conversion into an EC2 instance is failing. The error message I get is unsupported Windows version (Windows Server 2012 Server Standard), which is pretty strange because that OS version seems to be supported in Amazon EC2.
Someone who has experience about this?
While you can run an Amazon provided Windows 2012 image. It is not supported by the import tools.
You can import VMware ESX and VMware Workstation VMDK images, Citrix
Xen VHD images and Microsoft Hyper-V VHD images for Windows Server
2003, Windows Server 2003 R2, Windows Server 2008 and Windows Server
2008 R2. You can export previously imported EC2 instances to VMware
ESX VMDK, VMware ESX OVA, Microsoft Hyper-V VHD or Citrix Xen VHD file
formats. We plan to support import for additional operating systems,
versions and virtualization infrastructure products in the future.
Windows Server 2012 is not supported by Amazon VM import.
Still if you are not tied to AWS by an already created infrastructure, you could try other clouds like ElasticHost, CloudSigma or Windows Azure.
Related
I am new to Hyper-V and Server Core but I am stumped as to how to install a guest OS from an ISO using only PowerShell.
I have downloaded the Hyper-V Server ISO and installed it on my server. It only installs Server Core and does not give me the option for a full GUI option. I configured its network settings, etc and all looks ok. So Server Core installed properly and Hyper-V feature is enabled. I can use PowerShell to create a VM with VHDX and link my Guest OS ISO to it. When I start the VM there is no console UI to install the OS.
How are you supposed to install a guest OS with no console interface to setup the OS?
Note, there is no option under this configuration to enable the OS GUI as some posts have suggested.
First, please don't confuse "Server Core" with "Hyper-V Server". "Server Core" is an installation mode of Windows. Among other things, it can be converted to GUI mode, which is why people keep telling you to just turn the GUI on. Hyper-V Server looks like Server Core but it is not Server Core.
For your actual problem, you're not going to find a simple out-of-the-box solution. You could work up a complete unattended installation process. You could set up a Windows Deployment Services server and have it install via PXE boot. I think some of the third-party Hyper-V management solutions allow you to connect to the console of a VM from within the local Hyper-V Server.
Hyper-V Server was designed with headless operation in mind. It was expected that you would use it to configure and perform maintenance on the management operating system and, if desired, the virtual machines as containers. The guest operating systems themselves were not really meant to be managed from within Hyper-V Server. What it's expected that you'll do is use a full GUI, whether another copy of Windows Server or a Windows desktop operating system running Remote Server Administration Tools to remotely connect to Hyper-V Server and manage its VMs.
I am trying to put windows server 2003 from disk to a bootable USB. I have downloaded the software WinToFlash and it has worked, now my USB is bootable with windows 2003.
My only problem is, ow do I install disk 2 of windows server 2003? Do I create another bootable USB of it and connect it to the server?
If anyone has any information it would be greatly appreciated.
Disk 2 is not needed for installation, so you can install Windows from USB and then copy all files from Disk2 to machine to install addtional applications and services (OS will ask location of this files when needed).
I have a single Windows 2012 Server and trying to configure it for 2 independent purposes:
(1) DB Server MSSQL-2012
(2) VDI for about 5 clients.
I understand more or less how everything works but I'm little uncertain how the VM's should be nested into a single server. Should the Base Server manage the VDI Pools OR should a separate VM be created to manage VDI??
Base Install -- Windows 2012 Server with Hyper-V Role Enabled
(VM) - Windows 2012 Server with MSSQL
(VM) - Windows 2012 Server to Manage VDI Pool
(VM) Client VDI
(VM) Client VDI
(VM) Client VDI
The best thing to do is review Microsoft's LAB setups for various (and clearly defined) VDI scenarios. VDI QuickStart
I have a vhd file, I need to enable networking and remote connection on it. On the vhd is installed Windows Server 2008 R2 and SharePoint development platform, VS 2010 ...
My laptop runs Windows 8 x64 Hyper-v. I can run the vhd into the hyper-v and works great, no problem. But I have no idea about hyper-v configuration and settings.
I want to desktop remote connect (from Windows 8) to the vhd file running Windows Server 2008 R2 (domain contoso.com) but I don't know how to configure the hyper-v to allow the network connection ... if I start the remote desktop connect on my Windows 8 and type the server name or domain\server ... it doen't work.
Any idea how to configure the hyper-v so I can have internet access in the VHD and connect to it using remote desktop connection?
I am guessing you are using a Wi-Fi connection on your laptop. Hyper-V does not automatically use wi-fi connections, since it's a server technology and all.
But there are ways - here's an article from a MS dude explaining how to use a switch to bridge your wi-fi.
http://blog.credera.com/topic/technology-solutions/microsoft-solutions/using-your-windows-8-wireless-connection-inside-hyper-v/
I'd like to import a real Windows Server 2008 server as a Hyper-V Virtual Server on another Windows Server 2008 instance.
Anyone have any idea how to do this?
I'm looking at the System Center Virtual Machine Manager 2008 but it doesn't seem to import Windows Server 2008 - nor is it free.
Is there some other workaround (i.e. import the image into VMWare first, then convert to Hyper-V)?
Please help.
Regards,
Randall
while testing disaster recovery, iwas pleasantly surprised
(and impressed) that the builtin windows server backup
restored to hyper-v without a hitch.
this was on production hardware, with hw raid 5 and such -
so i expect it would work with slightly less exotic stuff as well.
I know from personal experience that using VMware's converter works to take an image of the system. You can then use Hyper V to import the VMware image you created.
When I was testing the the beta version of Hyper-V this was the only reliable method I found to import a physical system into a Hyper-V environment.
It's seems crazy to doubled convert something, but it worked!