January 30, 2019 at 1:10 am #48957aaronsParticipant
- Total Post: 2
Hello, we’re testing out Wyse Converter for PC and have issue were after each setting change / publish the device loses it’s WIFI and we have to reconnect and enter passcode again.
This is on Windows 7 Enterprise version.
Wanted to use this on laptop devices that the end user would be able to take home and connect to their home wifi or even travel with. I do see that profiles can be made using DWirelessProfileEditor.exe, but this wouldn’t help us for each users home network as it would quickly become impossible to make a profile for each of their networks.
Is there a way to keep it from dropping the wifi connections each time and store the user entered wifi?February 3, 2019 at 12:27 pm #48988ConfGenKeymaster
- Total Post: 10692
- Jedi Master
DWirelessProfileEditor.exe is the way to go.
Is the WriteFilter enabled on the device? You can try to disable it then, enter the information and enable it again. This should store the settings permanently.
CGFebruary 3, 2019 at 8:44 pm #48990aaronsParticipant
- Total Post: 2
Thanks for replying CG,
Sounds like there is not a great way for the end user to administer their own WIFI connections. That’s unfortunate.May 15, 2019 at 10:01 pm #49811
We’re having the same issue with Wyse Converter for PC’s 2.0 and WMS 1.3 Pro Cloud. The wifi settings were being retained find before we had the clients reporting connecting to WMS. Now that they are connecting to WMS the wifi settings are getting wiped on logout/reboot. All the documentation points to a UWF/DWF write filter but none of these filter utilities are available/exist on our laptops after Wyse Converter 2.0 is installed. What’s the deal @ConfGen ? I’ve disabled netxclean service to rule out whether it was the culprit of the wifi settings getting lost but they are still getting wiped.May 16, 2019 at 4:31 pm #49813ConfGenKeymaster
- Total Post: 10692
- Jedi Master
Sounds like the WMS policy is “overwriting” the local settings. Anything configured in the WMS policy in regarding of Wifi?
CGMay 16, 2019 at 4:45 pm #49819
No I made sure that all network configuration settings were omitted in the WMS policy.
In regards to the write filter, just found the release notes for the converter software and it looks like the DWF is only applicable to Win7 systems and the UWF is only applicable to Win10 Enterprise systems. We’re using Win10 Pro so does that mean we’re not utilizing a write filter at all and just relying on netxclean? A RAMDisk does get configured after the software is installed so I would think that there is some kind of redirection of writes occurring.July 23, 2019 at 9:11 pm #50406HayesEParticipant
- Total Post: 1
ConfGen, I too am having these exact same issues with the Wyse Converter for PC and have traced the problem to a bug in the cloud version of WMS 1.4 – I have a case open with Dell and it has been escalated (and unfortunately stalled) to their developer group.
In short; the bug does not allow a client to save its wireless config, despite employing the correct, documented whitelisting procedures per Dell and Microsoft (as well as your instructions on here). WMS enforces a default behavior that will always wipe a previously-set wireless config upon reboot despite not enabling any of the restrictive wireless policies set in place within WMS.
The project we are using the Wyse Converters are for a fleet of telework laptops, and there are currently three workarounds for the bug, all of which are unacceptable to the goals of our software thin client project;
1) Disable the universal write filter.
2) Operate the converted PC without WMS management.
3) Set wireless policies within WMS to allow approved WiFi networks via the XML importing feature with DWirelessProfileEditor.exe – for a fleet of hundreds of teleworker laptops with hundreds of different individual wireless networks, this is a practical impossibility.
The response from WMS development was a dismissive statement to the effect that what is being requested is an “enhancement”, not a bug. This is despite written documentation from Dell that explicitly states persistent WiFi settings for Wyse Converter are supported.
It’s very frustrating getting any traction on this and was wondering if there is anything you can help with or share. We have already escalated this past enterprise support directly to development and also have escalated via our sales representatives.July 23, 2019 at 9:49 pm #50408
Meanwhile this is the last correspondence I received from the support engineer on the case I opened for this issue:
We finally got an answer back from engineering about this issue
It appears that the clearing of manually input WIFI information upon rebooting once the device is attached to WMS is by design.
If we need this to be addressed, we’ll need to submit it as an Enhancement Request with your Pre-Sales Engineer. Do you know who your Account Representative or Systems Engineer might be? Please contact them and request That manually input WIFI information be retained when the device is rebooted, while it’s registered to WMS.”
Sounds like internally they don’t even know what the expected behavior is supposed to be. It should be called Wyse Converter 0.1 Beta honestly. This is not a 2.0 product Dell.July 23, 2019 at 9:56 pm #50410
Yes, they’ve been contacted and I haven’t heard back, same as the previous “enhancment request” I filed with them for them to work on having the ThinLinux 2.0 3040/5070 to automatically reconnect to a VMware Horizon session after an extended network disconnect to the client. Right now there’s manual keyboard/VNC intervention required to re-establish the session. We’re trying to find alternatives to Teradici PCoIP clients but there’s honestly nothing out there that has the basic features we’ve grown accustomed to on the Teradici P20/25’s.
- You must be logged in to reply to this topic.