All available desktop sources for this desktop are currently busy

[swerly01]

We are doing a pilot on several thin clients. The problem is that we have 7 Windows Embeded WYSE devices, they are working wonderfully. But we also have 3 WYSE V10L thin OS devices. When a user is already logged into a desktop and they try to log into a thin client device they recive a "all available desktop sources for this desktop are currently busy" error. This only happnes the first time they hit enter while the desktop is disconnecting. If they hit enter again they are able to log in directly. My question is there a way to fix this so the user never gets an error or if it can wait a second for the disconnect or something. Any help would be appreciated.

Thanks,

Tom Bryan

[mikebarnett]

Hi Tom,

Are these desktops in a Disconnected state when the users attempt to log in or are they in a Connected state?

If it's Connected where is the other session connected from?

What firmware version are your Wyse V10L thin clients running?

Mike

[swerly01]

The desktops are connected on another thin client. They are in the connected state. Once you try to log in and get the error it disconnects the session on the other thin client.

Thin Client Versions are 6.3.0_12

[mikebarnett]

I have a V10L that I have been testing with and I tried this very thing last week and it disconnected from my active session and connected to the new one with no error. I don't have access to the Thin Client today but I will test this out again for you and let you know my results.

Mike

[kopper27]

I had/have the same issue. Mine was this...VMs were being deployed you know installing updates, doing some stuff on them using Administrator user. This was using the Vcenter (you know console to the VM)

So there were some people doing these admin activities and they usually just closed the console and never log out so when a normal user tried to log in using a V10L client they could not override the administrator session that was still open and connected and got that all All available desktop sources... message

So basically they were said (admins) when you finish the admin activities close/log out the session.

so we fixed it that way but as the person who open this thread. Is there a way to override or close that active session even if it is an Administrator session?

Firmware issue?

Thanks a lot

[mikebarnett]

The easiest way is to give users the ability to reset their desktops. This will restart the machine but will do what they need.

Are you using View Composer and linked clones? If so, may I ask why updates and other operations are being done on each individual machine and not with a snapshot/recompose operation?

Mike

[kopper27]

no individual desktops that is the issue someone else setup the View enviroment. Composer was installed but individual desktops is being used. At this point I don't know if I can move from individual to automated...

when you say let users reset their desktops that would be at thin client level right?

[mikebarnett · Accepted solution]

Yes, it would be at the client level. That would allow them to just reset.

And thanks for letting me know about the individual desktop thing too. If you can switch over to linked clone desktops at some point it would make maintenance a lot easier as well!

Mike

[kopper27]

sorry for bothering you again

so there is a feature in the V10L client to let users reset the other sesion that on open?

is tha what you mean right?

[mikebarnett]

I'll have to check for the V10L. I know that it can be done from a thick client or the web client though.

I will check on this and get back to you.

Mike

[kopper27]

thanks a lot

will be waiting :smileygrin:

[mikebarnett]

OK, so I tested this today using a V10L with the 6.0.1_04 version of the firmware installed. I opened my session on another machine and then connected from the Wyse client. It took a few seconds while my first client disconnected and the Wyse terminal took over but it did not error out.

I also tried connecting to the Wyse terminal first and then opening my other client and connecting from there with the same result.

I am going to upgrade the firmware of the Wyse terminal and try again.

Mike

[swerly01]

thats strange, i wounder if when u upgrade the fw if it'll do the same thing mine does.... wounder what else is diffrent in our environment for you to not get the error and have to hit enter twice.

What version of VDI are u using ?

[mikebarnett]

Currently I am connecting to View 3.1.1.

Mike