- This topic is empty.
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Could somebody tell me what mechanism is responsible for setting up the restrictions for the built-in User account on Wyse Windows Embedded units? I am trying to configure a screen saver app that runs a batch file after a certain period of inactivity, and while it runs fine in the Administrator account it errors out in the User account, seemingly because of a restriction on the ‘Run’ command/app that it calls. If I could edit those restrictions it would be a big help, but I can’t find out how it’s configured (doesn’t seem to be local group policy).
In case it inspires a better solution, the main issue we’re running into for the C90LEWs and the D90D7s is that we’re using the Citrix Receiver application which temporarily stores the user’s Citrix username and password once logged in. They first sign in, then it populates the desktop with their assigned Citrix published applications (such as the Desktop we’re pushing out to them), however once they log out of said desktop they also need to manually log off the Citrix Receiver app or log off as a user entirely or else the apps remain on the desktop with their cached credentials, which is a big security risk if they forget to log off a second time at the end of the day. I’ve been scrambling to find a solution that can either close that program automatically after a period of inactivity or, as a last resort, log off the user (which would create a loop of repeating logoffs depending on the inactivity timer, which is not ideal). Any advice you could lend us would be most helpful.
All restrictions are done in the registry.
Check “Policy Registry Information” under Products – WES on this site.
CG
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |