This desktop currently has no desktop sources available

[GCIC]

Evaluating VMWare View Manager. When logging in via browser or client everything goes normally and shows VM's available. When I click on a pool, I get an error.

"The desktop has failed to open (poolname). This desktop currently has no desktop sources available. Please try connecting to this desktop again later, or contact your system administrator. "

The VM's are domain member and available easily via Virtual Center they just will not go to the client.

What am I missing here?

[TomHowarth]

Welcome to the forums,

Firstly I have moved it to the VMware View Manager forum

secondly have you entitled the Desktop pool to any users?

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[GCIC]

Yes, The pool is active and entitled. I get the same result no matter how large or small the pool is.

[TomHowarth]

Login to your vCenter and verify that your guests in the pool have been provisioned and finished customisation

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[GCIC]

View Manager shows waiting for agent. I don't have sysprep installed so I had to customize the VM's manually. The Virtual Center shows the VMs operating normally and waiting at the login prompt. If I log into either machine the VM functions normally on the domain with no issues. VMs were created as designed by the ViewManager. All of this is in a closed environment , on the same subnet with minimal overhead. The domain is uncluttered and to aid troubleshooting, firewalls have been disabled on all servers and clients. The switches are in dumb mode and there is no filtering.

All hosts are properly addressed and network is pingable via short name, FQDN and IP. The ESX hosts are Version 3.5 and the Virtual Center is currently running on a laptop. This is the only thing that isn't "working" as designed. VMotion, HA and DRS have no issues. There are no affinity rules to affect DRS issues. VM's and workstations are DHCP. All other infrastructure is static IP's. The AD, DNS and View Manager servers are also on a Win2K3 VM. AD is hosted on a separate ESX server (3.0.2) not part of the VM cluster.

Thanks for taking the time to work through this with me.

[TomHowarth · Accepted solution]

have you installed the View Agent on the Desktops it need to be in the template so it is deployed with each machine

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[GCIC]

The View agent is installed in all templates and VM's in the pool. The Client is installed on the workstations. I also checked from a different workstation using View Portal and had the very same results. The activeX control installed automatically as it should but it wouldn't serve up the VM and gave the exact same error.

BTW I'm also not using View Composer.

[GCIC]

Thank You for pointing me along the correct path. The issue seems to have been some combination of registering the VMs in DNS and Remote Destop settings. I'm still figuring out where I can put my security settings back into place without breaking the system again. Fortunately, it's not a production system so breaking it is just a learning process.

[Urbanb]

Hi run into the same problem...so perhaps I can help. Fixed it.

I installed a complete new XP SP2 and after this the vmware tools plus the viewagent. : Reboot

Now added the VM into the ViewManager.

After this the problem mentioned occurs..

The XP is still a workgroup member, no domain member.

= So I entered the correct DNS Server for my envrionment, and a second thing was to disable the Firewall (okok that was the fasted one;), than reading the manual and figgure out that port used)

[mattyche]

Same problem here. Any resolution yet?

[TomHowarth]

is your VC at 2.5 U3 and are your ESX hosts at 3.5U3

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[ITRC_Architect]

Same problem here also... I have the VMWare tools and VDM agent installed, it is connected to the domain, nslookup is showing the correct address, it is provisioned, there is no firewall, and so forth... I have rebooted a few times just for good measure.

Status is "Waiting for agent."

This problem seems to be centered around individual desktops.

We could use any help in resolving this.

[ITRC_Architect]

The issue seems to have resolved.

Our problem was that we were rebooting the client VM Guests after installing the agent. We should have simply rebooted the VDM / View server after installing the agent on the guests.

We rebooted the View Server and all the client VM Guests changed to the status "ready."

[shanfont]

I'm having the same problem. Rebooting didn't do anything for me. Desktop sources still unavailable and pooled vm's show status of "customizing" after three hours so far. My vm's show up in DNS with no issues although in view manager the pool don't have dns name or IP address listed probably because it's still customizing. This is version 3.0 of view manager by the way.

Shane,

[dpomeroy]

I'm just starting to play around with View and I'm seeing this problem, anyone have any updates?

I have a VM that is perpetually in "Waiting for Agent" status. Everything else (with install and config) seemed to work fine up till this point. Reboots don't help. The VM in question seems to function normally, the Agent installed and the View Agent services are running.

Don Pomeroy

VMware Communities User Moderator

[GCIC]

My original issue ended up being a combination of DNS and permissions.

I logged into each of the VM's with the appropriate account and ensured the DNS settings weren't changed by the sysprep. I then ran ipconfig /registerdns from the cmd prompt. Ensure your client can ping via FQDN to the VM you are logging into. I also ended up putting a hosts file on each of my machines to ensure DNS wasn't a holdup in the future. My situation was very non-standard and your results may vary. I also updated my template to ensure the authorized accounts had profiles present on the VMs.

BTW, I noticed an marked improvement in performance with the hosts file in place on the Virtual Center and View Connection Manager systems.

[shanfont]

My issue was solved by uninstalling the agent off of my vm's and then reinstalling and doing a re-boot. After that they showed up in VDM as 'Ready'. Hope this helps you but it sounds like your having a different message on yours.

[dpomeroy]

Thanks guys, I tried host files on the VM and CS server, and removing and reinstalling the View Agent on the VM (and rebooting everything), but still no luck. I opened a SR with VMware, they can figure it out

Don Pomeroy

VMware Communities User Moderator

[altapowder]

Any luck on this yet? I am setting up an evaluation of View 3.0 and have run into this same issue and can not move forward with convincing my boss to let me buy this solution. Everything else seems to be working well I just can't log onto any of the VM's through the view client and I get the exact same error "This desktop currently has no desktop sources available".

[dpomeroy]

Not yet, but I have an SR open, so once I get a resolution from that I'll post it here, although it will probably end up being something in our environment and not View itself. I'm waiting for VMware support to move beyond rebooting, re-installing, and checking DNS as resolutions.

Don Pomeroy

VMware Communities User Moderator