- This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
I have a little bit of a problem with a linked clone pool and need some expert advice. There are users in the pool that do not like the resolution that they are receiving and because of that I am creating a mac.ini for the WYSE device to change the resolution for a handful of users. In the wlx.ini file I have INCLUDE=$MAC.ini at the end of the file to call on the ini file associated with the client. In the mac.ini file I have the changes to the resolution for both screens that the user has. With my test client that I have setup I am successful in getting the resolution to change but the VIEW connection that was setup via the wlx.ini file is not showing up on the client. I am only prompted with a username screen instead of a VIEW connection screen. I can enter the username “Admin” and the password that we have changed via the wlx.ini file and I can enter the Connection Manager, so that tells me that the client is reading the section to change the passwords and is keeping it. If I remove the INCLUDE=$MAC.ini from the wlx.ini and reboot the client everything works fine with the exception of the resolution that some of the users do not like.
Below is what I have in the MAC.ini….
DisplaySettings=MON1 rotate-normal 800×600 MON2 rotate-normal on-right 800×600
Exit=all
Thank you for your help!
Have you tried adding anything else in the MAC.ini and see if that’s being read as well? Maybe Like a different connection to an intranet site or something?
also, I think your display settings line needs to be surrounded by quotes and have a semi-colon separating the two monitors. I’ve seen in my ini’s instances where if something is off, the rest of the ini just stops being looked at completely.
It’s very nice, support
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. |