7.0

Table Of Contents
n
Provisioning error occurred on Pool Desktop_ID because available free disk space is reserved
for linked clones
n
Provisioning error occurred on Pool Desktop_ID because of a resource problem
Cause
You do not have permission to access the selected datastore, or the datastore being used for the pool is out
of disk space.
Solution
n
Verify that you have sufficient permissions to access the selected datastore.
n
Verify whether the disk on which the datastore is configured is full.
n
If the disk is full or the space is reserved, free up space on the disk, rebalance the available datastores,
or migrate the datastore to a larger disk.
Pool Provisioning Fails Due to vCenter Server Being Overloaded
If vCenter Server is overloaded with requests, provisioning of a desktop pool can fail.
Problem
Provisioning of a desktop pool fails, and you see the following error message in the event database.
Provisioning error occurred on Pool Desktop_ID because of a timeout while customizing
Cause
vCenter is overloaded with requests.
Solution
n
In View Administrator, reduce the maximum number of concurrent provisioning and power operations
for vCenter Server.
n
Configure additional vCenter Server instances.
For more information about configuring vCenter Server, see the View Installation document.
Virtual Machines Are Stuck in the Provisioning State
After being cloned, virtual machines are stuck in the Provisioning state.
Problem
Virtual machines are stuck in the Provisioning state.
Cause
The most likely cause of this problem is that you restarted the View Connection Server instance during a
cloning operation.
Solution
u
Delete the virtual machines and clone them again.
Virtual Machines Are Stuck in the Customizing State
After being cloned, virtual machines are stuck in the Customizing state.
Problem
Virtual machines are stuck in the Customizing state.
Setting Up Desktop and Application Pools in View
332 VMware, Inc.