So, here is the list of updated MP’s for Windows Server 2016, not all seems to be done but Kevin Holman has a nice list with URL’s for those that have been released so far.
Check this site for more info:
Prior to deployment on production I wanted to test new Windows Server 2016 Hyper V Cluster. On paper it seems it didn’t change much from Windows Server 2012 R2 but still there is fear of unknown. My goal was to test all of it on my desktop workstation since it is quite good even after 3 years of service it is still capable of doing some serious business. Main new feature that will enable me to do this is called Nested Virtualization.
Well now after everything I must say I am impressed what I was capable to achieve and this will be series of articles and step by step instructions if you are interested in doing similar setup at your home or just part of it for fun.
First things comes first 🙂
In all possible scenarios planing and preparation is half work done right there, because of that we need detail plan of our future Hyper V cluster environment and all of it parts and envision our test case.
Well after quite a few deployments of new Server I noticed that Windows update will throw warring and notification “Your device is scheduled to restart outside of active hours” even do you set it not to do so – it is set do DownloadOnly.
It seems that this is a known bug in the Windows Update Settings UI in which the text does not correctly reflect the configuration of your Windows Update settings. MS Server Team will make fix soon but for now if you don’t want your server to automatically restart this is what you need to check and configure :
Validate your current Update settings using SCONFIG
To determine what updates your machine has already installed, follow these steps:
- Open a command prompt with Admin permissions.
Type sconfig and press Enter.
NOTE: There may be a short pause as the tool inspects your system.
Option #5 shows the current configuration of your Windows Update settings.
This is procedure how to add Nano Server to domain. Basic idea behind this is to do offline join to domain. Before you venture to adding Nano Server to domain you must set network address and adequate DNS record on your DNS server.
Nano server is a headless server which you cant RDP or not a command prompt. For Nano Server management we have to use PowerShell or RSAT tools. So as a first step is to login to other server which stays in the same network and run the PowerShell and execute the following commands.
First add the server to TrustedHost List
Set-Item WSMan:\localhost\Client\TrustedHosts "192.168.2.95" -Concatenate
Check the virtual machine configuration versions
- On the Windows desktop, click the Start button and type any part of the name Windows PowerShell.
- Right-click Windows PowerShell and select Run as Administrator.
- Use the Get-VM cmdlet. Run the following command to get the versions of your virtual machines.
PowerShell1Get-VM * | Format-Table Name, Version
You can also see the configuration version in Hyper-V Manager by selecting the virtual machine and looking at the Summary tab.
Upgrade the virtual machine configuration version
- Shut down the virtual machine in Hyper-V Manager.
- Select Action > Upgrade Configuration Version. If this option isn’t available for the virtual machine, then it’s already at the highest configuration version supported by the Hyper-V host.