- This topic has 1 reply, 2 voices, and was last updated 3 years, 9 months ago by .
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.
I wanted to update a registry key to enable TLS 1.2 on WES7 devices. I exported the registry key that I want to use to modify other devices. I placed the exported registry key on the WMS 1.4 repo under Thin Client Apps. I created an App Policy and selected the registry Key file as the application to use, the OS subtype was WES7 and I also selected the Platform Filter. I did not entered any parameters as I thought that WMS will know how to execute the file. The job was executed the Wyse device rebooted as expected to disable the write filter, it booted up and I saw the Typical message the administrator is performing changes, the job completed and the Wyse rebooted. Unfortunately, the registry key didn’t get updated. Any thoughts or suggestions.
You cannot just push the regfile.
Create a batch or similar to trigger regedit to import your regfile.
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. |