HP Matrix Operating Environment Software - Manual (Page 158)

Server reservation and allocation fail even though servers exist in the assigned pool
Server reservation and allocation fail with the following messages, even though servers exist in the
assigned pool that satisfy the template requirements. Issue
•
Reservation failed for logical server . Unable to find a
physical server with the following requirements: There are no valid
available targets to provision the service. Check if the targets in
the selected pools are in maintenance.
•
Unable to allocate servers and networks in the same Virtual Connect
Domain Group. Either more available servers are required, or could
not match existing servers against memory size, disk space and
processor count requirements.
Matrix infrastructure orchestration's Resource Manager has marked servers as “invalid” during
resource discovery because of a communication error between LSA and OA. Possible cause
Check the status of server blades within the enclosures. Action
1. In the infrastructure orchestration console, select the Servers tab and look at the Enclosures
column. This identifies the C-Class enclosures within the environment.
2. Find each enclosure in the Systems Insight Manager All Enclosures collection. The page for each
enclosure includes a link to the Onboard Administrator (OA).
3. Login to the OA; under Enclosure Information, click Device Bays and resolve any status errors
or warnings.
TIP: In some cases, status errors may be cleared by a reset of the active OA.
Create request fails, but the service is still listed in the Service tab in “Reserved” state, and no
resources are allocated
A Create request fails, but the service is still listed in the Service tab in “Reserved” state, and no
resources are allocated. Issue
A data migration attempt occurred while the Create request was waiting for approval. Possible cause
Do not attempt data migration when a service request is waiting for approval. Either approve or
reject the Create request and allow the request to complete before migrating data. Action
Virtual service creation
Password is blank for Windows 2008 R2 and higher provisioned VMs
If a VM is provisioned with Windows 2008 R2 OS 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 higher (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 higher operating system, 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.
158 Troubleshooting