- This topic has 3 replies, 3 voices, and was last updated 6 years ago by
.
-
Posts
-
Sorry for the long post…
Initial dive into WMS and I’m running into a quirky issue with how policies cascade on down. Trying to figure out if it’s my understanding of how it’s supposed to work that’s off, or if there might be a bug in how WMS applies certain settings.
Our current WDM device deployment scenario is that we have a couple of different classes of WTOS devices. What I mean about classes is that they’re all 7010s (D10D), they just differ in how we deploy them.
Some of the devices are set to auto logon to AD on start up. With WDM we do this by using the include=$tn.ini statement in the wnos.ini and then have the defaultuser= password= and domain= statements in that device specific INI.
In WMS I have set up a Default Policy Group policy. This has all the global settings for any WTOS device. Included in the policy is the time server and time zone information that are part of the General Settings node. Also part of this node are the Sign-On settings which, for the most part, I leave blank except for the domain fields.
I then have a couple of settings in the ThinOS Clients policy. But nothing in the General Settings node that would override what comes down from Default.
I added a specific group under ThinOS Clients and added policy items for that group. And, again, nothing different in the General Settings node.
By now, I would expect that since nothing additive was added to General Settings, that it would cascade on down from the top group.
Finally, and based on a response I received the other day from Thomas, I added a device level exception policy to a WTOS client in the lowest level group. This policy includes the username, password and domain info and these items were added to the General Settings node.
At this point, I expected that these settings would apply and that the device would use them to auto logon.
What I’m finding, however, is that the device just sits at the login screen.
When I look at the WMS.ini on the device, I see that the username, password and domain info are listed twice. Once at the very top of the file with values filled in and then again in the middle of the file with all the fields blank.
It seems as though the exception policy is being overridden by the top level policy. Or, it’s not applying in the order I would expect it to – meaning as last policy that overrides any settings that come down from above.
As an alternate, I took out the General Settings items from the device exception policy and, instead, added the items to the Advanced section as numbered line items. This way it seems to work. The device auto logs on. When I look at the WMS.ini, those settings are now reflected at the bottom of the file.
So, after all that, wondering if I’m doing something wrong (either with the policy set up or with my assumption of how the policies are applied), if there’s a bug with WMS and/or if anyone else has run into this issue?
WMS version = 1.2 (Standard)
Firmware = 8.5_012
Logically you are 100% correct.
This should not happen at all.For me it looks like (again) WMS is pushing down even non-configured parameter which then conflict with other group or local settings.
Please open a ticket for that on techdirect.dell.com
CG
Hello, I can confirm, I had the same problem.
You can try this :In “remote connection (8.5+)” > “Citrix Broker” > activate the policy but don’t configure anything, or just one thing if you want.
You will see that “username=” and “password=” are sent, empty.
I had the problem because I wanted the thin clients to remember the last used login, and it disappeared after each reboot. When I deactivate this policy, no problem, when I activate it the parameters are sent.
That’s a real problem with WMS… non-configured parameters are sent just by activating a policy, even if just 1 parameter is set.
Sorry for my english.
- You must be logged in to reply to this topic.