HP Matrix Operating Environment Software - Manual (Page 180)

Virtual service creation
Password is blank for Windows 2008 R2 and later provisioned VMs
If a VM is provisioned with Windows 2008 R2 OS or above from infrastructure orchestration without
setting any password in the Sysprep file, the following occurs: Issue
• VM deployed on ESX and ESXi hosts boot up and can be logged in with a blank password.
•
VM deployed on Hyper-V boot up to prompt the user to set a password.
Microsoft removed the option “password never expires” in Windows 2008 R2 and later (as part
of Sysprep). Possible cause
VMware overrides the option “prompt for a password on the next boot.”
Action • Specify an explicit password in the Sysprep.ini file for any deployment of a VM that has a
Windows 2008 R2 or later operating system. The password can be in either cleartext or encrypted
format. Or,
•
Specify an empty string “” password in the Sysprep.ini file, which results in the “prompt for
a password on the next boot” from VMware.
Error deploying logical server: Copy virtual machine failed: Unable to access file
vmware-template-name.vmdk
Error deploying logical server from _ls realized by
vm:///vmfs/volumes/....vmx/. Copy virtual
Failure message
machine failed: Unable to access file
[inactive-datastore-name]vmware-template-name/vmware-template-name.vmdk.
In the message above, “/.../” represents the datastore allocated for the VM;
[inactive-datastore-name
]” represents the datastore on which the template resides.
The template selected for provisioning an ESX VM resides on an inactive datastore. Possible cause
Do one of the following: Action
•
Activate the datastore on which the selected VMware template resides.
• In infrastructure orchestration designer, select a different VMware template for provisioning the
ESX VM.
Start function on virtual machine failed: there are not enough licenses installed to perform the
operation
The start function on virtual machine failed: There
are not enough licenses installed to perform the operation.
Failure message
ESX host not licensed. Possible cause
Use vCenter to apply a full ESX license to the host. Action
Select or create an empty folder as the target destination
Select or create an empty folder as the target destination. Failure message
The directory that infrastructure orchestration is attempting to deploy to is not empty, probably due
to a previous failed provisioning which was not cleaned up completely. Possible cause
When infrastructure orchestration deploys a virtual machine, it creates a directory structure into
which the virtual machine is provisioned. The directory that is created follows the pattern: Action
Volume>\\ . This folder contains all the folders and files
corresponding to the virtual logical servers. Delete this folder and all its contents.
180 Troubleshooting