Windows on linode

[only-cliches]

No description provided.

[EugeneKay]

This guide uses a VirtualBox donor VM, which is overly complex IMO. The only benefit of performing a KVM-migrated install(my original approach) was the use of Paravirtualization drivers, required for the KVM Beta. The alternate Full Virt mode is slightly slower, but does not require jumping through quite so many hoops to get running.

Quick HowTo:

1. Download a Windows ISO installer image and license key.
2. Burn the ISO to a USB sitck. I like to use Rufus
3. Create a new Linode. Create two Disk Images of type Raw: System(must be at least minimum size to install Windows, will be your C:\ drive) and Installer(as large as the USB stick). Wait until later to create any additional disks(D:)
4. Launch Rescue mode with the Installer disk attached as sdb. Enable SSH & set a password for root.
5. Plug the USB stick into a Linux machine. Copy it to the Rescue mode system: dd if=/dev/sdX bs=1M | pv -s 8G | ssh root@12.34.56.78 dd of=/dev/sdb bs=1M
6. Create a new Configuration Profile. Full-virtualization mode. Kernel: direct disk boot. System as sda; Installer as sdb. Root device as sdb(temporarily). Disable all boot helpers.
7. Boot into the new Profile. Connect using Glish in the Remote Access tab. The installer will boot, follow the prompts. Make sure that you pick the System disk(no partitions) for install location!
8. When the Windows Installer is ready to Reboot for the first time, you must Shut Down the Linode from the Dashboard.
9. Edit the Configuration Profile and change the Root Device to sda(System). Disconnect sdb(Installer); it is no longer needed.
10. Boot the Linode and reconnect to Glish. The Windows installation will boot.
11. Disable IPv6 Privacy Extensions (optional)
12. Create any additional Disk Images you want to use, attach them to the config profile, and reboot to use. You will need to use Windows tools(diskmgmt or PowerShell) to format the new drive as NTFS and mount it.
13. Enjoy!

Suggested reading

[pbzona]

Hi @ClickSimply

While this is a cool concept (and one we get asked about more often than you might think), the logistics of testing and updating a Windows guide regularly would make it very difficult to maintain. Additionally, we're unable to provide support for Windows, and generally stay away from publishing guides on proprietary OSes.

Thank you for your submission, but I'm going to have to close this PR. If you're interested in doing a different topic in the future please feel free to reach out. Even though we can't take this guide, it's very well written and you've clearly got some interesting ideas!

[dawesi]

"generally stay away from publishing guides on proprietary OSes." #really it's almost like you don't want to take people's money. #hostingfail