View Connection Error message returning too quickly

[krismcewan]

We are doing a little test before going live with Vmware View and Sunrays, View Client and The web client.

So far if we have a pool of desktops and make all that are needed available

there is no problem.

But to have them powered off and then turned on when required we get an error

from the client (The desktop has failed to open (xptest). All available desktop

sources for this desktop are currently busy. Please try connecting to this

desktop again later, or contact your system administrator.)

Now we have this error appearing almost instantaneously and on the VC

you can see a new machine being powered on and after about 20-30 seconds if you

try again success.

What we are looking for is the connection client to wait the 30

or so seconds until the machine is switched on and then connecting. I.e. a nice

Waiting message.

Anyone had anything similar or any ideas?

[admin]

Please check the name resolution and or client Windows firewalls.

Blog: http://communities.vmware.com/blogs/dommermuth

[krismcewan]

name resolution or firewall are not the issue.

the error comes as the machines are being provisioned and powered up.

Once they are up and running we have no problems. We were expecting a message saying "Please wait" instead of a flat denial.

The Test XP build i am using has nothing on it apart from a base build and takes 20 seconds to power up and about 35 to clone and powerup. Its during this 20-35 seconds.

[lbourque]

Try going to Desktop Sources in the View Manager. It will indict when the VM is ready and completed customization. The error is technically correct since the VM is not ready and the service isn't available (the error comes from RDP technically).

[krismcewan]

this doesnt help us. We know the machines are being provisioned. we havnt hit or limits.

What we would really like is a settign somewhere to change the time that a client machine will be told there is no machines available. We dont get the Preparing Desktop Message which we are expecting .

As i say if all the machines are provisioned and provisioned there is no problems. But we dont want 400 virtual machines constantly on.

[lbourque]

A few settings you could do (without knowing all the details of the environment):

• create a "buffer" of available machines (e.g., if you know you'll usually have 50 people on any given day and up to 25 more people, then provision 50 and create available machines of 25 -- this is in the advanced option when selecting pool size

• put them into suspend when not in use (setting on the pool) rather than Always Leave On. Suspend has a shorter time to start up and I believe, IIRC, the error is different. The user will be told to wait while the VM is made available.

[krismcewan]

we already have explored the buffers setting them to half of the requirement in the test lab.All works fine untill you get to that buffer and even if you have an available count eventually you hit the error as the machines are still trying to boot/unsuspend.

ven with the vm in suspend mode the error comes back within 2 seconds not even giving time for the VM to unsuspend and be available.

I had expected a message saying "provisioning your desktop" and it waiting for so long to let the machine become available.

I think the quick return of the error is the main issue.

[lbourque]

Then I would suggest putting in a feature request or opening up an SR that is a feature request (list it at a level 2-3). You can file the feature request here: http://www.vmware.com/contact/contactus.html?department=feature-request

[lbourque]

Oops.. sorry. Duplicate because of a crashed Firefox.

[krismcewan]

I may put in a Support request as it could be a Bug.

[krismcewan]

UPDATE

reported this issue to VMWare and they are aware of this issue and will be releasing an Upgrade soon that will resolve this issue

[krismcewan]

Still heard nothing on this yet.

could be August before there is a update

VCP, VTSP4, VSP4 and anything else I can learn