Switching dynamic IP to static in VMM

Creating a VM from virtual disk or existing virtual machine is a basic task in every VMM infrastructure. What if you want to assign IP from static pool instead of dynamic which is just the one option by default for such deployments? Well,doing this in wizard, will end by receiving a warning:“You cannot customize IP settings for a stored virtual machine or a virtual hard disk. You can only customize IP settings if you use a VM template” and static IP pool will be grayed out.

vmm static ip pool greyed out

If you don’t want to create VM template for some reason, PowerShell will help you to fix this behavior. Just start VM creation wizard, edit hardware and other settings and leave Dynamic IP for network adapter. Then don’t run VM and execute the following PowerShell script:

#Get VM
$vm=Get-SCVirtualMachine -Name "rl-srv-01.demolab.com"

#Get static pool which you are going to use with that VM (here I'm filtering pool by address range)
$pool=Get-SCStaticIPAddressPool|? {$_.IPAddressRangeStart -eq "10.10.25.1"}

#Grant changes
Grant-SCIPAddress -GrantToObjectType "VirtualNetworkAdapter" -GrantToObjectID $vm.VirtualNetworkAdapters[0].ID -StaticIPAddressPool $pool

#Update network adapter settings
Set-SCVirtualNetworkAdapter -VirtualNetworkAdapter $vm.VirtualNetworkAdapters[0] -IPv4AddressType static

Go back to the VM settings and check changes that script has successfully made:

vmm dynamic to static ip pool result

Nano Server future and Windows Server servicing channels

Nano Server has been presenting as an ideal Windows Server option for general infrastructure roles including Hyper-V and Storage since the RTM release. It’s been changed. Nano Server won’t be supported as an image for infrastructure-related roles deployed on physical/virtual machines and can be used only as container image.  So, now we need to step back and use Server Core again for roles like Hyper-V or Storage Spaces Direct.

It was confirmed yesterday by Erin Chapple, General Manager of Windows Server:

This next release will focus on making Nano Server the very best container image possible. From these changes, customers will now see the Nano Server images shrink in size by more than 50 percent, further decreasing startup times and improving container density. As part of this effort to focus on containers, we will be removing the functionality for infrastructure-related roles. Instead of using Nano Server for these scenarios, we recommend deploying the Server Core installation option, which includes all the roles and features you would need.

There are also some changes in the servicing model for Windows Server and System Center. There will be two primary release channels available to Windows Server customers, the Long-term Servicing Channel, and the new Semi-annual Channel in order to align with similar release and servicing models for Windows 10 and Office 365 ProPlus

In Long-term Servicing model, where a new major version of Windows Server is released every 2-3 years, users are entitled to 5 years of mainstream support, 5 years of extended support, and optionally 6 more years with Premium Assurance. This channel is appropriate for systems that require a longer servicing option and functional stability.

The new Semi-annual channel for Windows Server, Server Core and System Center will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release. Most of the features introduced in the Semi-annual Channel will be rolled up into the next Long-term Servicing Channel release of Windows Server. The editions, functionality, and supporting content might vary from release to release depending on customer feedback.

The Semi-annual Channel will be available to volume-licensed customers with Software Assurance, as well as via the Azure Marketplace or other cloud/hosting service providers and loyalty programs such as MSDN.

Both the Long-term Servicing Channel and the Semi-annual Channel releases will be supported with security updates and non-security updates distributed by servicing tools like WU, WSUS or SCCM

windows server servicing models

Windows Server has also become a member of Windows Insider Program. Pre-release builds of Windows Server will be available for download via the Windows Insider Program and the Windows Insider Program for Business. To join this program follow these steps