Forum Replies Created
-
Posts
-
I tested the new firmware 9.1.6 and it seemed to fix the lease time but they didn’t fix the thin client getting its name from dhcp option 12 tag.
I tested the new firmware 9.1.6 and it seemed to fix the lease time but they didn’t fix the thin client getting its name from dhcp option 12 tag.
I uploaded some logs from 9.1.4 and 9.1.5 for Dell and they have not said a lot I’m afraid. I did some more trouble shooting and here is what if found. It only happens on my lab switches in our environment which are cisco catalyst 3560CG series and 3560CG poe. Also it doesn’t happen on the wireless for us either. I’ll let you know if I hear something which I hope will be pretty soon.
I’m not sure of your environment but in mine the with software encrypted thumb drives 2016 XenApp can not see them in session but can see hardware encrypted thumb drives. We use Win10 XenDesktop too so the software encrypted thumb drive work on those.
Hi,
I opened a ticket with Dell regarding this and got this back:
I told them that my service properties window don’t even look the same and I’m waiting for a response but it does mention upgrading the MongoDB so maybe that will help you. I’m still unsure what version the mongo database is and even asked them so but considering its a brand new install of 3.5.2 and not an upgrade why would it need to be upgraded.
I put in a ticket for this with Dell and it has been pretty quite about it. In my case though I’m seeing it happen on a certain switch in my test lab the Cisco catalyst 3560-cg series. On this switch the 9.1.5 software am getting a 1 hour ip lease if I roll back the software to 9.1.4 I get a 12 lease and also with all 8.6 thinos. Look at your lease time in the event log but just so you know that pop up will come up every time your device renews the lease and will also stop you from typing and forcing you to click on the screen to make it go in the back ground.
On our normal switches I get a 12 hour lease and it doesn’t matter what thinos I use.
I don’t know if its the best way but I can tell you what I’m currently doing. I have WMS 2.o installed on our prod server which won’t let me upgrade so I created a new WMS server 3.5.2 and created all the same groups as the prod server. Then I’m going to use this line in the advanced area of each different group.
CCMEnable=yes CCMServer=https://WYSE2.xxx.org:443 GroupPrefix=defa GroupKey= Xxxxxxx!1 MQTTServer=WYSE2.xxx.org:1883 AdvancedConfig=yes Override=yes
Just put your new server in the bolded area and the correct group key want the thin clients to migrate too. Make sure you spell and get everything right because in my tests where I didn’t the thin client kept its config but was unreachable by either the old or new WMS server and would have to be touched. To test I just made exceptions to my test thin clients and plopped the line in the advanced area. I ended up making all the lines so I couldn’t mess it up.
Another thing in found in my case is that it reboots everything in that group so I’m going to need my Citrix team to probably fix any Citrix storms that happen do them all hitting citrix at once on reboot. Some of my OUs have 1300 or more thin clients. I did ask Dell if there was a way to stop it but I haven’t heard back yet. If you have any more question just ask.
If you are using DHCP option tag 12 to name the thin clients that is currently broke in 9.1.4 and 9.1.5. I have a ticket open with Dell about it and have even tested a beta firmware Dell gave me that didn’t work. I don’t think anyone reported it before me.
You can turn Enrollement Validation off till you’re done migrating. The setting is under Portal Administration > Other Settings and just uncheck it. I’m doing the same thing because I can’t seem to get the server upgraded without the server hard drive filling up.
No the settings get erased in all of my testing and usage because of the software upgrade. Sorry I didn’t understand.
I’m sorry I was reading fast and was thinking you meant will it automatically autologin with 9.1. You need to set up the config first before upgrading. Select the group you want to upgrade and then edit the policy ThinOS 9.x.
Yes in the tests that I’ve done they do. I’ve not moved over to 9.x yet in my organization because every time I test I find something not working correctly. I was hopeful for 9.1.5 but I found the DHCP was broken and was even broken in 9.1.4.
This is what I’m currently using to migrate to a new WMS server because I can’t get out prod server upgraded. I just use this in the advanced line on the old WMS server. I also used the same line to migrate from WDM.
CCMEnable=yes CCMServer=https://newwms.server.org:443 GroupPrefix=defa GroupKey= groupkeyfornewservergroup MQTTServer=serveryourmovingtoo:1883 AdvancedConfig=yes Override=yes
I just wanted to update you that Dells escalation team reproduced my issue while I was on the phone with them.
I had the same thing happen and since I took a snap shot beforehand I deleted the big files. I did have one other thing go wrong though, I was able to login but I got an error when I clicked the Setup button at the bottom of the portal administration page. I don’t think deleting the files had anything to do with error though. Just for fun I tried to update again to 3.3 and after an hour of backing up the database I reverted back to the original snapshot.
