Fixed issues in 1912 LTSR CU3

In the Citrix Provisioning console, attempts to copy and paste target device properties by using a mouse might fail.

In large VMware deployments, the Export Devices Wizard might take longer than expected to filter the compatible devices.

VDAs fail to start in scenarios where DNS name resolution and BDM are used with Infoblox DNS and DHCP.

Changes to scheduled updates you make through vDisk Update Management do not take effect until you restart the Citrix PVS Soap Server service.

The Citrix Provisioning virtual disk might be forced to reconnect intermittently by the server.

After upgrading Citrix Provisioning Services from version 7.15 LTSR to version 1912 LTSR CU2, the available network interfaces might be missing from the TFTP configuration tool (Tftpcpl.cpl).

Attempts to merge the vDisk versions to a base image might fail causing this error message to appear:

The parameter is incorrect. Error number 0xE00000057.

In large VMware deployments, the Export Devices Wizard might take longer than expected to filter the compatible devices.

The PVS Device Service (BNDevice.exe) might consume a high percentage of CPU usage.

When you configure UEFI PXE with DHCP Option 17 through a custom port, a target device might fail to start.

Enabling Asynchronous I/O for a vDisk might cause the target device failover to fail.

When you upgrade or install the Provisioning Services target drivers into a platform layer, the Script value under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\Scripts\Startup might be incorrectly set to C:\Program Files\Citrix\Provisioning Services\CPVOfficeActivation.cmd. As a workaround, you must manually run the command c:\windows\setup\scripts\kmsdir\gposetup.cmd.

With this fix, multiple partitions from multiple hard disks can be combined to create a vDisk in a BIOS VM.