{"description":"Windows Nano Technical Preview 3","short_description":"Windows Nano Technical Preview 3","name":"mwrock/WindowsNano","versions":[{"version":"0.7.0","status":"active","description_html":"
Cleanup updates and shring down ~200MB.
\n","description_markdown":"Cleanup updates and shring down ~200MB.","providers":[{"name":"virtualbox","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.7.0/providers/virtualbox/unknown/vagrant.box"},{"name":"hyperv","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.7.0/providers/hyperv/unknown/vagrant.box"}]},{"version":"0.6.0","status":"active","description_html":"Install updates
\n","description_markdown":"Install updates","providers":[{"name":"virtualbox","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.6.0/providers/virtualbox/unknown/vagrant.box"},{"name":"hyperv","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.6.0/providers/hyperv/unknown/vagrant.box"}]},{"version":"0.5.0","status":"active","description_html":"Updated to RTM. Fixes bluescreen on first boot in hyper-v
\n","description_markdown":"Updated to RTM. Fixes bluescreen on first boot in hyper-v","providers":[{"name":"virtualbox","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.5.0/providers/virtualbox/unknown/vagrant.box"},{"name":"hyperv","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.5.0/providers/hyperv/unknown/vagrant.box"}]},{"version":"0.3.0","status":"active","description_html":"Built with Technical Preview 5
\n\nThere is a known issue on the Hyper-V provider where it blue screens on first boot. This goes away after a reboot.
\n","description_markdown":"Built with Technical Preview 5\r\n\r\nThere is a known issue on the Hyper-V provider where it blue screens on first boot. This goes away after a reboot.","providers":[{"name":"hyperv","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.3.0/providers/hyperv/unknown/vagrant.box"},{"name":"virtualbox","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.3.0/providers/virtualbox/unknown/vagrant.box"}]},{"version":"0.2.0","status":"active","description_html":"Updates to Technical Preview 4
\n","description_markdown":"Updates to Technical Preview 4","providers":[{"name":"hyperv","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.2.0/providers/hyperv/unknown/vagrant.box"},{"name":"virtualbox","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.2.0/providers/virtualbox/unknown/vagrant.box"}]},{"version":"0.1.1","status":"active","description_html":"Edits the vagrant user so its password never expires.
\n","description_markdown":"Edits the vagrant user so its password never expires.","providers":[{"name":"hyperv","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.1.1/providers/hyperv/unknown/vagrant.box"},{"name":"virtualbox","checksum":null,"checksum_type":null,"url":"https://vagrantcloud.com/mwrock/boxes/WindowsNano/versions/0.1.1/providers/virtualbox/unknown/vagrant.box"}]},{"version":"0.1.0","status":"active","description_html":"This is a Windows Nano Technical Preview 3 box.
\n\nThe WinRM service in Nano currently only accepts requests set to the UTF-8 code page 65001. However, the WinRM Gem used by Vagrant sets the codepage to 437. This prevents vagrant from establishing WinRM connections with the nano box.
\n\nHowever, Vagrant is able to create and destroy the box and one can connect via via windows Powershell Remoting.
\n\nThe very first boot on Hyper-V will blue screen. However it will recover. How it recovers depends on the type of switch used:
\n\nYou can connect via powershell remoting using port 55985 on VirtualBox and the normal WinRM ports using Hyper-V.
\n\nMore instructions to come
\n\nThis box was created using the template located at https://github.com/mwrock/packer-templates/blob/master/vbox-nano.json The build was identical for VirtualBox and Hyper-V with the exception of the drivers used to create the initial nano image. Hyper-V used the -GuestDrivers
option and VirtualBox used -OEMDrivers
.