Forum Replies Created
-
Posts
-
Has anyone had any success with this? Dell will only allow to open a support case via phone and no one I’ve talked at Dell knows anything about this KB article.
Hi Jim,
Do you know the reason this isn’t publicly available? Why is it hidden behind having to open a support case with Dell?
Thank you.
The VM has moved between ESX hosts (vMotion) before due to host maintenance, yes.
I will send you an email directly as you mentioned above.
Thanks.
Yes, I am able to upgrade WMS_Hotfix_3.8.0.182.exe successfully. Next upgrade after that to 4.0.0.526 is when it fails.
Thanks
Because of this failure, I did revert my snapshot and start over with doing step-up upgrades and I get the exact same failure message when going from 3.8 to 4.0.0.526. So at the moment, I cannot advance the update beyond 3.8 without receiving a failure message “failed to migrate lockbox configuration while upgrade.”
Thanks.
Sorry for the delay but I wanted to follow up… the issue was the fact that when the cert expired, it was only replaced in the storefront servers and they forgot to replace it in the netscalers. I had wondered this, and tried to change the configuration to not use the public storefront virtual IP but instead try and connect directly to one of the servers URL from the wyse but this resulted in failure to login every time.
Should a similar situation arise; is there a way to bypass the netscalers and instead use the URL of one of the storefront servers directly?
Thank you.
I’m still having trouble with this… any ideas of what I’m missing?
Thanks.
I believe I have it right. I have the following in WMS :
And the text file looks like :
“Citrix”=”Citrix Universal Printer”
And the Wyse terminal looks like :
Port:LPT1
Printer Name: Citrix
Printer Identification: Citrix
Printer Class: PCL5
Enable Printer Device = Checked
I added the printer mapping to WMS. My printer.txt is set for :
“Citrix”=”Citrix Universal Printer”
I changed the Printer Name and Printer ID in ThinOS to Citrix
This is just a test to see that it should actually change the driver but it doesn’t work. It still shows in Citrix with the wrong driver and yellow exclamation. The driver in printer.txt matches exactly the driver name I have in Citrix but it won’t change.
What else am I missing?
Thanks.
Thank you for the help… that did fix my problem.
I have to say, I don’t find the WMS as intuitive as I’d like. And the Admin Guide leaves a little to be desired.
But once again, thanks everyone for your help!
It is under ‘Visual Experience.’ Thank you so much for your help folks. I still have the last question of how can I stop the clients from trying to contact the file server? I haven’t configured it in WMS as I don’t need it but every time the Wyse client starts up it pauses for a couple of seconds.
So… that’s exactly what I tried; I did have a Custom Name on my storefront name in WMS and it keeps appending that name to the address so it obviously fails. I removed it and it logs in without issues now.
The only thing I am trying to find now, is in WDM, I was able to set the Wyse to shutdown when people logged off,but I can’t find that option in WMS. Just a scheduled Shutdown/Reboot. Is that option gone now or did I overlook it?
