VMware provides a set of pre-packaged VMs that are ready to deploy.

VMware provides a curated Microsoft software repository with the following OVF packages for your use:
  • Windows Server 2022
  • Windows Server 2019 Datacenter
  • Windows Server 2016 Datacenter
  • Windows Server Datacenter (provides Microsoft Semi-Annual Channel Release)
  • Windows Server 2019 Datacenter with SQL Server 2019 Enterprise
The following SQL Server features are pre-configured in the OVA:
  • Database Engine services
  • Client tools connectivity
  • Client tools backwards compatbility
SQL Server services are configured as follows:
  • SQL Service Agent: Automatic
  • SQL Server Database Engine: Automatic
  • SQL Server Browser: Manual
The following configuration was applied to the default SQL Server instance:
  • "Grant perform Volume Management Tool" is enabled
  • Min Server Memory: 0 MB
  • Max Server Memory: 5940 MB
  • Authentication mode: "Windows Authentication"
  • SQ Server Administrator Role: "BUILTIN\Administrators (Administrators)"
Note: If you need to add features to the installed instance, use the SQL Server ISO image provided in the same Content Library. See Create a VM Using a Microsoft ISO for more information on using the ISO images.
Note: Windows Firewall is enabled in all VMware-provided OVAs.
The OVF packages have the following configuration:
  • Hardware compatibility: ESXi 7.0 and later (Hardware Version 17).
  • 4 CPUs
  • 8 GB memory
  • Network adapter: VMXNET3
  • single 90GB VMDK attached to VMware Paravirtual vSCSI (PVSCSI) controller
Note: Access to the VMware-curated Microsoft software repository should be used only for deploying Microsoft binaries for use on VMware Cloud on AWS.

Procedure

  1. Subscribe to the VMware-curated Microsoft software repository by creating a subscribed Content Library using the following URL: https://vmc-microsoft-templates.s3-us-west-2.amazonaws.com/Images/lib.json
    For more information on creating Content Libraries, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A0F1C13-7336-45CE-B211-610D39A6E1F4.html.
  2. Deploy the desired OVF into your environment.
    For more information on deploying OVFs from Content Libraries, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3C02B3FC-5DE6-48AA-9AD3-7F0D1C7EC4B6.html.
  3. Make any necessary modifications to the VM, such as adding vCPUs, adding disks, or changing network settings.
    For more information on configuring VMs, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html.
  4. Configure the compute gateway firewall using the VMware Cloud Console to allow outbound HTTP and HTTPS access to the internet.
    This is required for initial activation of the Windows server image. For more information about firewall configuration, see https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-A5114A98-C885-4244-809B-151068D6A7D7.html.
  5. Power on the VM.
  6. Configure a Windows Server password to secure the VM according to your corporate security policy.
  7. (Optional) Convert the VM into a template for re-use.
    You might need to reactivate VMs cloned from the template.

What to do next

  • Update your VM with the latest patches and security updates. Although VMware supplies current versions of Microsoft products, it is your responsibility to apply the latest maintenance updates and security patches to ensure that the products run in a secure environment. Follow your enterprise recommendations on updating any binaries that you import into your SDDC.
  • Update firewall rules. The activation and patch update process requires that the VM have internet access. Follow your enterprise guidelines on whether these firewall rules should be modified after activation.