We’ve been receiving support ticket from users having Remote Access issues connecting to the Windows Server 2012, 2016, and 2019 systems, or other situations where they may lose network connectivity internally to the space or to the Internet. In these situations rebooting the system, or resetting the network interface may solve the problem for a period of time.
While working with VMware Support on this issue, it was found on Windows Server 2012, Windows Server 2016, and Windows Server 2019, VMware will set the interfaces to the E1000 interface by default (which is not recommended for theses OS’s). There is no way to specify a different interface when being deployed thru their API in CONS3RT.
VMware Support recommended interface for use with Window Servers 2012, 2016, and 2019 is the VMXNET3 interface type. In order to use the VMXNET3 interfaces on new deployment runs, you can use the following templates:
- Windows Server 2012 R2 [NICS]
- Windows Server 2016 [NICS]
- Windows Server 2019 [NICS]
These three templates come with the cons3rt-net and user-net interfaces pre-added to the systems using the VMXNET3 interfaces. If you need additional interfaces added, please put in a support ticket and we can add any additional network interfaces to your run for networks in your spaces.
If you have any older runs that have been experiencing interfaces going offline, and you are unable to redeploy them, you can put in a support ticket and we can coordinate swapping the network interfaces drivers with you. We also have a work around using this asset that can reset the network interfaces without rebooting the system via a scheduled task: https://app.arcus-cloud.io/ui/#/software/90886/help