Hello, everyone!
This post will show you how to resolve VM publishing failures caused by VM renaming failures.
Fault type
VM renaming failure
Keyword: VM renaming failure
Applicable version: FusionAccess V100R005C10
Description
1. During the VM provision, onsite engineers enter ITOU on FusionAccess. However, the correct one in the AD is VMOU/ITOU.
2. Renaming VMs fails when VMs are assigned.
Alarm information
None
Analysis
1. The error information is displayed in the ITA log, as shown in the following figure:
2015-04-21 17:45:56,036 [31] INFO filePath:C:/ITA/tomcat/vDesktop/WEB-INF/script/xd5/renameByNetdom.ps1, parameters:$vmIp="10.153.7.1";$password="******";$user="vd\ITAServiceUser";$cmdString="******"; 2015-04-21 17:45:58,965 [5] INFO execute result:Active code page: 437 Active code page: 437 The network path was not found. The command failed to complete successfully.
2. The OU configuration is incorrect. The OU must be configured according to the OU configuration format in Domain/OU.
3. It is found that the address is incorrectly resolved after the AD domain name is pinged on the ITA server.
Solution
Enter the correct OU information based on the OU layer.
Summary and suggestion
None
This is my solution, how about yours? Go ahead and share it with us!
