With VMM 1807, you can now choose any location to place the new disc. You can manage this disc easily, based on the storage availability of CSVs. For more information, see Add a virtual hard disk to a virtual machine.
What’s new in System Center Virtual Machine Manager 1807
When you deploy a virtual machine, you might want to run a post-deployment script on the guest operating system to configure virtual network adapters. Previously, this was difficult because there wasn't an easy way to distinguish different virtual network adapters during deployment. Now, for generation 2 virtual machines deployed on Hyper-V hosts running Windows Server 2016, you can name the virtual network adapter in a virtual machine template. This is similar to using consistent device naming (CDN) for a physical network adapter.
One of the common issues faced by customers in a VMM deployment is a Cluster Shared Volume (CSV) getting full. When the CSV becomes full, the virtual machines with virtual hardware disks (VHDs) on that CSV are stopped, leading to disruption of service. A nifty little change in VMM 1807 now enables administrators to avoid running into this situation. When you add a virtual disk to an existing virtual machine, VMM now enables you to pick the CSV where you would like to place the VHD. The CSV that you choose to place the VHD on can be different from the CSV in which other VHDs of that VM reside. Prior to VMM 1807, a new VHD of an existing virtual machine would be placed in the same CSV as the other VHDs, aggravating the problem if the CSV was already running high on utilized storage.
VMM 1807 has improvements in networking over the previous release. Using the Link Layer Discovery Protocol (LLDP), VMM now provides physical network connectivity details for the Hyper-V hosts. We have heard from customers that they need visibility into physical network connectivity to troubleshoot the connectivity of virtual machines. VMM 1807 now provides switch port ID, VLAN, chassis ID, management address of the switch, and other details.
When you add a new VHD to the existing VM, you can now define CSV path (a new volume) for that disk to eliminate problems with storage space. Prior to VMM 1807, a new VHD of an existing virtual machine would be placed in the same CSV as the other VHDs, aggravating the problem if the CSV was already running high on utilized storage.
Where can I download virtual machine manager 1807 non-eval copy? I looked at my volume license service site and I cannot find it. I was told we have a license for it, I just cannot figure out where to download it?
Kevin, the official doco for 1801/1807 ( -us/system-center/scom/system-requirements?view=sc-om-1807#microsoft-monitoring-agent-operating-system) suggests there is no agent support for Windows Server 2019, but there is for SCOM 2016 and SCOM 2019. Do you know if this is going to change?
After banging on the door for several hours using different hammers and axes, and even trying to talk nicely to the door in all the languages and dialects the knights could muster, they went about searching for an answer on the spy network better known as scroogle search. That only provided garbage and ample ads for armor-itch ointments. They went on to kidnap a gremlin from the blue window in hope that he could provide answers. He demanded a special key for access and that the knights signed a scroll of license. Furthermore they had to agree to random spies in the cookie-jar. At least the gremlins were forthcoming about this in contrast to the sneaky creatures of scroogle. Anyways, the gremlins blamed the SPN setup. But the SPN setup was verified, and everything worked just peachy until the restart of the VMM server! After some digging around in old technet forum posts, the knights came across this: -us/c3e5fd36-5de2-413f-87b8-538411d8dc6d/virtual-machine-manager-error-1604. It did not provide a direct solution, but the honorable DavyPierson mentioned going in to the depths of AD and looking for a key. A keyword to be exact, that had to include the name of the service account running VMM. We did not change the service account, but we chose to check it out anyway. The service account was OK as expected, but to our horror we found a pile of garbage where the SPNs should have been defined as a keyword: 2ff7e9595c