[Keyword] FusionAccess, creating VMs, and failed to rename VMs
[Applicable version] All versions of FusionAccess V100R005
[Alarm information] None
[Description] All tasks fail when the user uses FusionAccess portal to batch provision test VMs. In the task center, the error is reported as "Failed to rename newly created VMs. Please check that the network environment is normal, and create VMs again."
- The naming rule is incorrect. The names of provisioned VMs are test01, test02, and test03, all of which comply with the naming rule.
- Check whether same names have existed in the same OU.
The desktops are provisioned to one user and added to users test01 and test02 in the users group.
Log in to the AD server and find that user names test01 and test02 have existed in the same OU, as shown in the following figure.
The error is reported during desktop provisioning because username in one OU must be unique.
[Solution] Name hosts with names different from names in the OU. Modify host names to names excluding test01, test02, and test03. If the desktops are provisioned to user test01, they can be successfully provisioned.
[Summary and suggestion] None
