- This topic has 41 replies, 5 voices, and was last updated 4 years ago by
.
-
Posts
-
Ok so the beta drop is working, seems like an issue with the prod release, I have to laugh at that.
Have you tried to enter the WMS URL with leading https and without :443 at the end?
CG
I did.
I’m rolling back again to 8.6_206 and then upgrading to 8.6_303 and then i’ll try the prod version of WTOS 9. I don’t remember reading anything about needed to be on a specific version of 8.6 to then upgrade to production, but when WTOS 9 was dropped, 8.6_206 was all that was out.
Thank you again for all your help and feedback ConfGen. I was very happy to see you in the beta forum as well so I knew this forum would be well prepared for the major release of WTOS 9.
So by default WTOS 9 has Proxy enabled, even if I do a WTOS 9 factory reset the proxy is enabled and has to be manually disabled. Other observations
- The default URL for the WMS check-in is incorrect I had to change it from us1-pns.wysemanagementsuite.com (the MQTT URL) to https://us1.wysemanagementsuite.com (the WMS URL)
- WTOS cannot check-in to WMS due to the proxy being enabled by default in WTOS 9
- After the proxy is disabled, WMS check-in is available and the policy can be applied to the 3040
Hello Guys!
I’m having similar issues with ThinOS 9. everything is fine with 8.6 but as soon as I update a client to 9.0 the client won’t ever connect back to the WMS server.
(I have set up the thinos 9.0 config already)
I have already tried the WMS server URL in every possible combination and on the proxy page, in the network settings, every field is empty.
Should I see an other enable/diable proxy option somewhere else?
(wyse 3040 devices)
Thanks a lot!
I have actually managed to make it connect by manually entering the MQTT server address on the client from the admin policy settings however it seems to randomly revert back to “us1-pns.wysemanagementsuite.com” and when that happens the client isn’t connecting to our local WMS server.
Also even if the client is finally connected to our WMS server login to the citrix environment isn’t working. It shows “Starting broker sign-on…” No matter how I enter our storefront address and which store I chose.
(certificates are successfully arriving to the client from the WMS)
The enable/disable proxy has to be done locally on the device using the local admin policy tool under Network Configuration and then Proxy. After a factory reset or after the upgrade from 8.6-9.0 this needs to manually be done for 3040’s.
I did test the 5070/5470 and that upgrades without issue so the issue is only in the A10Q package not the X10.
That indeed did the trick, thanks a lot! Now the connection to the storefront is okay, I can even log in and see all the apps, however none of them is launching.
Event log simply says “Vdimgr:connecting to “ica: the applications name” but seemingly nothing ever happens.
The connection doesn’t show up in the Citrix director at all, like there wasn’t even a try.
Was just going to say the same, sounds like the Citrix package isn’t installed.
It seemed like the Citrix Workspace was already on the ThinOS but I might have missed something obvious 😀
My experience with ThinOS and ThinOS light was pretty much plug and play when it came to accessing citrix. Of course it required some tweaking with the INI config lines if we wanted anything specific but I never had to install any package before.
I’ll get the package on the device and give it another go, thanks a lot for the help! 🙂
Yeah, it has changed from ThinOS 8 to 9. Now a lot more components are distributed as packages.
There are a lot more to come with 9.1.CG
I can confirm, it does work after installing the citrix package 🙂
Is there an estimated release date for 9.1? I think I read somewhere that there will be a new thinos 9 update this July, is that correct?
I have the same problem here, and i have testet alot, 1 thing is that https:// is ignored at the web interface, so when i use DHCP options it some times work, but as the unit register into WMS it cant login agian to WMS since its get config without https. I think Dell have a few bugs in this v9 software. Another think is WMS server is constantly changed back to Dell default when you edit the policy, making it hard to setup correctly. Hope to see a new release from Dell soon.
- You must be logged in to reply to this topic.