Forum Replies Created
-
Posts
-
Found the culprit. That was a “service” motherboard changed previously. In the BIOS, there is a “maintenance” section where the SKU was set to “default” instead of “ThinOS”.
The trick is that to be able to edit that setup, a bootable USB imaging stick must be plugged (but not booted with) when entering the BIOS
RDP direct connection is fine though
We have a crash case when cascading w/ a Citrix workspace connexion inside the VM.
Note that we’re still on ThinOS 8.6 for the majority of clients (~100) because every single AVD release has been aving “glitchs” so far. No UDP yet, which is flabbergasting.
The only improvement we’ve seen w/ ThinOS 9 is Zoom plugin for offloading cpu and network.
BTW, what was wrong with 9.x.x numbering so to add a parallel quarterly numbering. ?
This is insane. There are now two flavors or ThinOS 2311 : 9.4.4106 and 9.4.4123
Hi,
Looks like you can create a fake connection that people can edit prior to launch.
Looks fixed to me…
ThinOS 2303 / 9.4.1141
AVD 2.0.2102
BIOS 1.21
(BTW, We don’t have pro support and Dell accept our support requests submitted through TechDirect..)
for the record
The “direct connection” is not available with the current PCoIP client. Only “broker” type connection.
The workaround is therefore to specify the host as the broker and it works.
The limitation it that only one PCoIP host is possible because only one broker can be specified.I’ve been able to obtain trial licenses, after all.
I’ve installed the latest PCoIP host agent (23.04) in a Windows 11 host and activated it.
Connexion from a Windows PCoIP client is OK.
Connexio from a Wyse, either ThinOS 8 or 9 is NOT OK. “This Desktop has no source available”
No clue why in the Wyse log.
Any idea ?
Turns out the device was not PCoIP capable.
I’ve upgraded another one who was and it’s OK.Well sort of… The device can’t connect to the VM. This is a W11 where I have installed the PCoIP standard agent.
Any clue ?
Solved by re-instating the previous http server (alias to the new one) and then disabling local copies.
+1.
Letting the user decide which scale factor fits better for her/him should be the default.
(One of the reason we’re still on ThinOS 8…)
DELL support told to make an enhancement request through our DELL sales contact. You should probably do the same.
Freeware NAPS2 works well is I set “old DSM” flavor of twain…
Hi,
I have plugged a Kodak i940 to a Wyse 5070 / ThinOS 8.6.
I installed the Kodak drivers (TWAIN, WIA and ISIS)
Redirection is done out-of the box and the scanner appears well in the host as a “local” device.
Kodak OneTouch is not working. Says that the scanner is not ready
Kodak SVT validation tools is working..
Freeware NAPS2 works (almost) using twain. Won’t work using WIA.
I can scan a document but the software then wait forever for some twain “closure”
Any hints ?
Apparently this has to do with MirrorFileServer option which is flawed :
I now set it to NO.
Reset the Wyse to factory
Start the Wyse —> It fetchs wnos.ini and <@MAC>.ini —-> OK
Stop the http server.
Restart the Wyse —> It can’t fetch ini files . BUT previous connections are there (w/ a star and no custom icons) although they shouldn’t. They can’t be deleted.
So, for some reason, some Wyses and displaying both downloaded ini files and previously cached ones…
Extra entries have a star and the custom icon is no set.
