Forum Replies Created
-
Posts
-
Thanks ConfGen
I’ve tried with and without all of those things and nothing has changed. I’m going to reach out to Dell. This isn’t urgent but I figured I’d like to test as a home worker since I am a home worker now for the next couple months.
The same device I can roll back to 8.6_206 and register with the same group token and it has no issue, then when i flip the firmware from 8.6_206 to 9.0_011.36 after it updates it doesn’t know how to check in.
Should I not have the same group registration token name inn my 9.x WMS policy as I do in the 8.6 WMS policy? Meaning in the WTOS 9 policy you have to set a group registration token and I have it the same as the 8.6 token.
Are you USB force redirecting the PID VID? The below change will also allow for the finger print reader to work in Citrix through the thin client.
On your Windows machine make this change
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\GenericUSB
EnableBloombergHID changed from 0 to 1
DeviceRules key added the following:
ALLOW:vid=1188 pid=9525 # Bloomberg
ALLOW:vid=1188 pid=9535 # Bloomberg
ALLOW:vid=1188 pid=9545 # Bloomberg
ALLOW:vid=1188 pid=03e9 # Bloomberg
ALLOW:vid=1188 pid=03ef # BloombergOn your thin client policy make this advanced line config change or make it an INI file:
#Bloomberg keyboard force redirect
Device=vusb ForceRedirect=0x1188,0x9525,0x03,0x01,0x01
Device=vusb ForceRedirect=0x1188,0x9535,0x03,0x00,0x01
Device=vusb ForceRedirect=0x1188,0x9545,0x03,0x00,0x01
Device=vusb ForceRedirect=0x1188,0x03e9,0x03,0x00,0x01
Device=vusb ForceRedirect=0x1188,0x03ef,0x03,0x00,0x01I even set my thin clients IP manually in my router and put that IP in the router DMZ which I should not be necessary for a home setup and its still giving the same message. You should be able to key in a group registration token with an OOB factory reset experience but that doesn’t seem to be the case.
I’ll likely open a case with Dell tomorrow.
Great news. I have to force redirect Bloomberg keyboard fingerprint readers by PID VID for Citrix and, though I don’t do RDP, made me think your situation might be similar.
You might have to force redirect the PID:VID of the camera for it to get picked up.
Are you testing the camera default in ThinOS before you start the RDP session or the camera isn’t passing through the RDP session but the camera default is recognized in the ThinOS environment?
Assuming you’ve checked the event logs on the machine you’re connecting to? Policy refresh? Service crashing? Any indicator on the remote machine at that time that could be causing the issue?
Its an RDP specific message so I would think the Windows event logs would give some more clues
We have a similar issue with video/audio and also screen dragging across multiple monitors. We corrected this with a Citrix policy for Video Codec Compression
https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/graphics/thinwire.html
where we saw the issue specific to thin clients was using “For the entire screen” and it was corrected by changing it to “For actively changing regions”.
I strongly believe this is a limitation with the ThinOS Citrix Receiver version that is a Dell modified version of a several year old Citrix Receiver not keeping up with Citrix’s new capabilities. See if that graphics policy change on the Citrix side helps.
I did remedy this with Sleep=0. The previous behavior was the monitor going to sleep before the 5470 was introduced. Additionally, the Shut Down, Restart, Sign Out screen on the thin client includes a Sleep option on the 5070 and 5470 but does not include that option on the 3040. This definitely seems to be introduced at the time the 5470 and 5070 started sharing the X10_wnos file as an all-in-one firmware.
It will not, there is a Windows 7 Citrix resolution limitation of 4094 pixels in any dimension. In testing with the 5070 with 3×24 inch monitors are clocking a spanned resolution of 5760×1200 (1920×1200 for each) and 3×22 inch monitors clock at 5760×1080 (1920×1080 for each)
If you unplug a DisplayPort cable it will span 2 monitors at 3840×1200 or 3840×1080 which is under the 4094 pixel limitation.
https://support.citrix.com/article/CTX201696
Desktop OS VDAs (Virtual Desktops / XenDesktop)Windows 7 – Supports up to 8 monitors. Display resolution is limited to 4094 pixels in any dimension. The VDA must have sufficient memory allocated to support the desired configuration. Refer to CTX200257 – Screen Issues Connecting to 4K Resolution Monitors for additional information.
I see two sections in my WMS.ini that may address what you’re looking for: possibly the ExpireTime parameter in the first section and as you already stated you have lock terminal set to 0
SignOn=Yes ExpireTime=0 RequireSmartCard=No SCRemovalBehavior=0 IconGroupStyle=Default DisableGuest=No
ScreenSaver=20 LockTerminal=0 Type=2 Image=”” PictureTimer=6 PictureOrder=Default PictureCheck=Default PictureLayout=center Sleep=60 Unit=No
In the WMS 1.4.1 Release Notes for Known Issues: The quarantine verbiage is throwing me off, but sounds similar to your issue.
- WMS141-375 – Occasionally, when a device is registered through DNS and DHCP
discovery method to quarantine group for the first time, the device
restarts continuously – There is no workaround in this release.
https://topics-cdn.dell.com/pdf/wyse-wms_release-notes21_en-us.pdf
- WMS141-375 – Occasionally, when a device is registered through DNS and DHCP
