Contents of this Article
Microsoft announced the release of System Center 2019 under Long-Term Servicing Channel (LTSC). LTSC provides 5 years of standard and 5 years of extended support. Subsequent the release of System Center 2019, the suite will continue to accrue value through the Update Rollup releases every six months over the mainstream support window of 5 years. Microsoft has dropped Semi-Annual Channel (SAC) releases, but new features before the next Long-Term Servicing Channel (LTSC) release will be delivered through Update Rollups. You can read about the announcement on Windows Sever Blog. You can download the media from the Volume Licensing Service Center (VLSC), or you can download the evaluation bits from the following link.
There are a lot of improvements and new features were introduced in this release.
In System Center 2019 Virtual Machine Manager, Microsoft added several new features as follows:
- Nested Virtualization – Run Hyper-V inside a Hyper-V virtual machine
- Performance Improvements to Host refresher
- Manage VMware Esxi 6.5 hosts
- Migrate VMware VM (EFI firmware-based VM) to Hyper-V
- Enhanced console session for VMs
- Prevent CSVs from getting full by setting a threshold for warning or auto migrating VHDs across CSVs in a cluster
- Monitor storage health and operation status
- Ability to choose CSV during the creation of new VHD
- Improvements to VMM Storage QoS
- Upgrade and patching of S2D clusters
- Encrypted VM Networks
- Layer 2 Network Information for Hosts (LLDP)
- Convert SET switch to Logical Switch
- Configure SLB VIPs through VMM Service Templates
- Configuration of guest clusters in SDN environments
- Support for Static MAC address on VMs deployed on a VMM cloud
- Configure Layer 3 Forwarding Gateway
- New RBAC Role – VM Administrator
- Support for ‘Group Managed Service Account (gMSA)’ as VMM service account
- Linux Shielded VM support
- Integration with Azure Update Management
In this post, I will show you how to install SCVMM 2019 on top of Windows Server 2019 and SQL Server 2017. In a follow-up blog post, I will dive into the new features and improvements.
Prepare VMM 2019 Installation
The following prerequisites and components should be installed on the server, before you install VMM:
- The Deployment Tools feature from the Windows® Assessment and Deployment Kit for Windows Server 2019 must be installed on this computer to run Microsoft System Center 2019 – Virtual Machine Manager. To download the Windows® Assessment and Deployment Kit, go to: Windows Assessment and Deployment Kit (ADK).
- The Windows Preinstallation Environment feature. Starting with Windows 10, version 1809, ADK does not include Windows PE by default. It’s a separate add-on download Download the Windows PE add-on for the ADK.
- PowerShell 5.0 or later.
- .NET 4.6 or later.
- Ensure that a domain controller for the Active Directory domain is available.
- Ensure that the domain account used for VMM service is a member of the Administrators group on the local VMM server.
Install VMM 2019 on Windows Server 2019 and SQL Server 2017
The installation of VMM is straightforward using the graphical user interface (GUI). In this article, I will show you how to automate the installation of System Center 2019 Virtual Machine Manager and SQL Server 2017 on top of Windows Server 2019. The same steps will also apply to Windows Server 2016.
Automate Windows Assessment and Deployment Kit Installation
Open an elevated command prompt window, then navigate to the adksetup.exe location, and then run the following command on a single line to install Windows ADK in silent mode:
adksetup.exe /quiet /installpath D:\ADK /features OptionId.DeploymentTools
Automate Windows PE Installation
Open an elevated command prompt window, then navigate to the adkwinpesetup.exe location, and then run the following command on a single line to install Windows PE in silent mode. This command will also restart the machine:
adkwinpesetup.exe /quiet /installpath D:\ADK /features OptionId.WindowsPreinstallationEnvironment /forcerestart
Automate SQL Server 2017 Installation
Please note that System Center 2019 Virtual Machine Manager supports local and remote SQL Instance. You can disregard this step if you already have SQL server deployed locally or on another server in your environment.
Mount SQL Server 2017 Standard media and then open an elevated command prompt window, then navigate to the SQL Server 2017 media, and run the following command on a single line:
Make sure to update the domain name, SQL service accounts and passwords according to your environment. As a side note, you can also use a parameter (configuration) file and pass it to the setup for SQL instead of typing the long CLI below, either way will work. For more information on how to install SQL Server using a configuration file, please check the following article. To specify the configuration file at the command prompt, use the following syntax: Setup.exe /ConfigurationFile=”D:\MyConfigFile.ini”
Setup.exe /Q /ACTION=install /IACCEPTSQLSERVERLICENSETERMS /FEATURES=SQLEngine /INSTANCENAME=VMM2019 /INSTANCEDIR="D:\Program Files\Microsoft SQL Server" /INSTALLSHAREDWOWDIR="D:\Program Files (x86)\Microsoft SQL Server" /INSTALLSHAREDDIR="D:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="domain\username" /SQLSVCPASSWORD="vmm2019##" /SQLSYSADMINACCOUNTS="domain\username" /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /AGTSVCSTARTUPTYPE="Automatic" /SECURITYMODE=SQL /SAPWD="vmm2019##" /SQLTEMPDBDIR="D:\Program Files\Microsoft SQL Server\TempDB\\" /SQLUSERDBDIR="D:\Program Files\Microsoft SQL Server\SQLData\\" /SQLUSERDBLOGDIR="D:\Program Files\Microsoft SQL Server\SQLLog\\"
After short period of time, the installation will complete as shown in the next screenshot without error:
Starting from SQL 2016 onward, SQL Server Management Studio (SSMS) is now packaged and installed separately with only a web link to each download page within the SQL Server Installation Center. At the time of writing, SSMS version 17.9.1 is the current General Availability (GA) which you can download it from here.
Within the same command prompt window, type the following command to install SQL Server Management Studio (SSMS) in silent mode:
SSMS-Setup-ENU.exe /install /quiet /norestart /log log.txt
Once you install SSMS package, open SQL Server Management Studio (SSMS) and verify you are able to connect to the SQL instance name that you specified in the previous step.
Now we are ready to install VMM 2019.
Automate VMM 2019 Installation
Now before we install VMM, we need to add the domain account for the VMM service as a member of the local Administrators group on the VMM server. Open Windows PowerShell and type the following command (make sure to update the domain name and account):
Net localgroup Administrators VIRT\vmmsvc /add Get-LocalGroupMember Administrators
Copy the following details into Notepad and save it on the VMM server as VMServer.ini.
You can use the same script below whether the SQL Server instance is installed on the VMM server or on a remote server.
When creating the VMServer.ini, replace the text inside < > with values from your own environment.
You can find a sample of the VMServer.ini in the installation media of VMM under the following path: D:\System Center 2019 Virtual Machine Manager\amd64\Setup
[OPTIONS] ProductKey=<xxxxx-xxxxx-xxxxx-xxxxx-xxxxx> UserName=<User Name> CompanyName=<Organization Name> ProgramFiles=<VMM Server Installation Path> CreateNewSqlDatabase=1 SqlInstanceName=<SQL Instance Name> SqlDatabaseName=<VMM Database Name> RemoteDatabaseImpersonation=1 SqlMachineName=<SQL Server Machine Name> IndigoTcpPort=8100 IndigoHTTPSPort=8101 IndigoNETTCPPort=8102 IndigoHTTPPort=8103 WSManTcpPort=5985 BitsTcpPort=4443 CreateNewLibraryShare=1 LibraryShareName=MSSCVMMLibrary LibrarySharePath=<Library Share Path> LibraryShareDescription=Virtual Machine Manager Library Files SQMOptIn=0 MUOptIn=0 VmmServiceLocalAccount=0 TopContainerName=<Container for Distributed Key Management (DKM); for example: CN=VMMDKM,OU=SysCtr MGT,OU=VIRT LAB,DC=VIRT,DC=LAB> HighlyAvailable=0 VmmServerName=<VMM Server Name> # VMMStaticIPAddress = <comma-separated-ip-for-HAVMM>
Here is a real example of the VMServer.ini file that I will use in this example:
After you edit the file, open an elevated command prompt and run setup.exe with the parameters below. For example, to use a VMServer.ini file that is stored in C:\Temp with a SQL Server administrator account of VIRT\vmmadmin and password, VMM service account of VIRT\vmmsvc and password, use the following command:
Setup.exe /server /i /f C:\Temp\VMServer.ini /SqlDBAdminDomain VIRT /SqlDBAdminName vmmadmin /SqlDBAdminPassword vmm2019+1 /VmmServiceDomain VIRT /VmmServiceUserName vmmsvc /VmmServiceUserPassword vmmsvc /IACCEPTSCEULA
Sit back and relax… after 10 minutes VMM will be installed automatically as shown in the following screenshot:
You can also validate that the VirtualManagerDB is created successfully in SQL Server Management Studio.
That’s it there you have it!
Thank you for reading my blog.
If you have any questions or feedback, please leave a comment.