\n<\/em><\/p>\n
Step 1 – Make Folders<\/h2>\n
Create three folders on a computer with a fast disk. Note that I\u2019ll use C: but maybe you should use a D: or something.<\/p>\n
- \n
- C:\\Nano<\/li>\n
- C:\\Nano\\Base<\/li>\n
- C:\\Scripts<\/li>\n<\/ul>\n
Step 2 – Copy Scripts<\/h2>\n
Mount the WS2016 ISO – let\u2019s assume that it mounts as E:. Copy two scripts from E:\\NanoServer from the ISO to C:\\Scripts:<\/p>\n
- \n
- new-nanoserverimage.ps1<\/li>\n
- convert-windowsimage.ps1<\/li>\n<\/ul>\n
Step 3 – Dot The Scripts<\/h2>\n
Note that I missed out on this step because I had never encountered this sort of thing before – I\u2019m an advocate of PowerShell but I\u2019m no guru! If you do not run this step, New-NanoServerImage.ps1 will do nothing at all and wreck your head for 3 hours (it did for me!).<\/p>\n
Open a PowerShell window with elevated privileges. Navigate to C:\\Scripts. Run the following:<\/p>\n
. .\\convert-windowsimage.ps1<\/pre>\n
I know – it looks funny. Enter it exactly as above. This appears to load the contained script as a cmdlet that can later be executed.<\/p>\n
Do the same again for New-NanoServerVHD.ps1:<\/p>\n
. .\\new-nanoserverimage.ps1<\/pre>\n
Now we can build a new VHD with Nano Server pre-installed.<\/p>\n
Step 4 – Create a VHD<\/h2>\n
You can now run New-NanoServerImage. Here\u2019s what I ran:<\/p>\n
New-NanoServerImage -MediaPath e:\\ -BasePath C:\\Nano\\Base -TargetPath C:\\Nano\\Nano1 -GuestDrivers -ComputerName \"Nano1\" -DomainName \"prev.internal\" -EnableIPDisplayOnBoot -AdministratorPassword (convertto-securestring -string \"AVerySecurePassPhrase\" -asplaintext -force) -EnableRemoteManagementPort -Language EN-US\r\n<\/pre>\n
The above will prep a VHD with a VM called Nano1. I have configured the VM to join the prev.internal domain – note that this will require me to have suitable domain creds – a computer account is created in the domain. I enabled the Hyper-V<\/a> guest drivers and allowed the IP of the VM to appear on the console. The VHD will be stored in C:\\Nano\\Nano1. Note that if this folder exists then the process will abort:<\/p>\n
WARNING: The target directory already exists. If you want to rebuild this image, delete the directory first.
\nWARNING: Terminating due to an error. See log file at:
\nC:\\Users\\ADMINI~1.LAB\\AppData\\Local\\Temp\\2\\New-NanoServerImage.log<\/p><\/blockquote>\nNote that I had to specify EN-US because, at this time, my default region of EN-IE was not available:<\/p>\n
WARNING: The ‘en-ie’ directory does not exist in the ‘Packages’ directory (‘g:\\NanoServer\\Packages’).
\nWARNING: Terminating due to an error. See log file at:
\nC:\\Users\\ADMINI~1.LAB\\AppData\\Local\\Temp\\2\\New-NanoServerImage.log<\/p><\/blockquote>\nI could have added other roles\/packages to the VHD such as:<\/p>\n
- \n
- -Storage: For a SOFS cluster.<\/li>\n
- -Compute: To enable Hyper-V \u2026 useful when TPv4 (we guess) introduces guest virtualization.<\/li>\n
- -Clustering: To enable failover clustering in the VM.<\/li>\n
- -Defender: Adding security to the guest OS.<\/li>\n<\/ul>\n
A minute or so later, a 439 MB was created in the newly created C:\\Nano\\Nano1.<\/p>\n
Recreating a Nano Server VM<\/h3>\n
If you\u2019re playing with Nano Server in a lab then you\u2019ll create VMs with name reuse. If you do this with domain join then you might encounter a failure:<\/p>\n
WARNING: Failed with 2224.
\nWARNING: Terminating due to an error. See log file at:
\nC:\\Users\\ADMINI~1.LAB\\AppData\\Local\\Temp\\2\\New-NanoServerImage.log<\/p><\/blockquote>\nOpen the log and you\u2019ll find:<\/p>\n
Provisioning the computer…<\/p>\n
Failed to provision [Nano1] in the domain [prev.internal]: 0x8b0.<\/p>\n
It may be necessary to specify \/REUSE when running<\/p>\n
djoin.exe again with the same machine name.<\/p>\n
Computer provisioning failed: 0x8b0.<\/p>\n
The account already exists.<\/p><\/blockquote>\n
That\u2019s one of those \u201cding-ding-ding aha!\u201d moments. The computer account already exists in AD so delete the account and start over.<\/p>\n
Creating Additional VMs<\/h3>\n
Once you have run the above process, C:\\Nano\\Base will be populated with files from the ISO (\\NanoServer). This means that you can drop the -MediaPath flag and eject the ISO.<\/p>\n
New-NanoServerImage -BasePath C:\\Nano\\Base -TargetPath C:\\Nano\\Nano2 -GuestDrivers -ComputerName \"Nano2\" -DomainName \"prev.internal\" -EnableIPDisplayOnBoot -AdministratorPassword (convertto-securestring -string \"AVerySecurePassPhrase\" -asplaintext -force) -EnableRemoteManagementPort -Language EN-US<\/pre>\n
Step 5 – Move the Computer Account<\/h2>\n
In AD, move the computer account for the new Nano server to the required OU so it get\u2019s any requierd policies on the first boot – remember that this sucker has no UI so GPO and stuff like Desired State Configuration (DSC) will eventually be the best way to configure Nano Server.<\/p>\n
Step 6 – Create a VM<\/h2>\n
The above process prepare a VHD for a Generation 1 virtual machine. Create a Generation 1 VM, and attach the VHD to the boot device. Connect to the VM and power it up. A couple of seconds will pass and a log in screen will appear:<\/p>\n
![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2015\/10\/image_thumb45.png\" "\\"image\\"")
<\/a><\/p>\nLog in with your local admin or domain credentials and you\u2019ll be greeted with the console. Note that I enabled the IP address to be displayed during the setup:<\/p>\n
![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2015\/10\/image_thumb46.png\" "\\"image\\"")
<\/a><\/p>\nStep 7 – Manage the Nano Server VM<\/h2>\n
If you want to do some management work then you\u2019ll need to:<\/p>\n
- \n
- Wait for the eventual remote management console that was quickly shown at Ignite 2015.<\/li>\n
- Use PowerShell remoting.<\/li>\n
- Use PowerShell Direct (new in WS2016).<\/li>\n<\/ul>\n
If you have network access to the VM then you can use remoting:<\/p>\n
Enter-PSSession -ComputerName Nano1 -Credential prev\\administrator<\/pre>\n
Troubleshooting network issues with Nano Server can be a dog because there is no console that you can log into. However \u2026 you can use PowerShell Direct with no network access to the VM, via the Hyper-V guest OS integration components:<\/p>\n
Enter-PSSession -VMName Nano1 -Credential prev\\administrator<\/pre>\n
Tip: Most AD veterans start network troubleshooting with DNS – it\u2019s nearly always the cause. In my lab, I have 3 domains, so 3 sets of DNS. My DHCP scope sets up on domain\u2019s DNS server as the primary, and that can cause issues. Some PowerShell Direct to the VM with some Set-DnsClientServerAddress<\/a> sorted things out.<\/p>\n
Technorati Tags: Hyper-V<\/a>,Windows Server 2016<\/a>,Deployment<\/a>,PowerShell<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"Setting up a Nano Server VM requires running some PowerShell. The instructions that I found out there aren\u2019t that clear for a non-PowerShell guru , are wrong, or are incomplete. So let me clear up everything by showing you exactly what I am using to deploy Nano Server as a Windows Server 2016 (TPv3\/Technical Preview … Continue reading “Create a WS2016 Nano Server Hyper-V VM”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":19270,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[20],"tags":[174,181,87,137],"class_list":["post-19267","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hyper-v","tag-deployment","tag-hyper-v","tag-powershell","tag-windows-server-2016"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t