UAG 3.3, UAG 3.4
UAG appliances deployed on Hyper-V using the deployment PowerShell script do not set the vCPU correctly, even when specifying in the deploymentOptions parameter.
Note: Customers can still log into the Hyper-V console and add the processor.
A current workaround is to add the following PowerShell script in the uagdeployhv.ps1 file before the #Start:
Set-VMProcessor –VMName $VMName –count $vCPU
The following image is an example:
Our product team has been engaged and is actively working to resolve the issue.
Other Languages: 日本語