wnos.ini – Is there Better way to plan dual screens?

  • This topic is empty.
Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #7867
    AvatarWayne
    Member
    • Total Post: 5
    • Newbie

    I have 400 users with dualscreens and 400 users single screen.

    Is there a better way for me to do this without setting up 400 seperate ini files by mac address?

    #23877
    AvataraLiE
    Participant
    • Total Post: 320
    • Jacked into The Matrix
    • ★★★★★★

    Is there a reason why you want to force the dual screen option in the wnos.ini ?

    Depending on the client hardware this can be auto detected, i thought the R10L is the only one for now.

    #23879
    ConfGenConfGen
    Keymaster
    • Total Post: 9812
    • Jedi Master
    • ★★★★★★★

    aLIE is correct. Currently it only works with R10L. But with the upcoming firmware version 8, it will also work with the other models.

    CG

    #23892
    AvatarWayne
    Member
    • Total Post: 5
    • Newbie

    I currently have V10L’s and I am testing some Xenith and T10 clients.

    From what I gather when plugged in they auto dual screen but the resolution on the second screen isnt the same as the first screen. I think they also default to mirror and not span.

    I am using a DVI to DVI/VGA splitter also.

    Ideas?

    #23909
    AvatarMrCentral
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    This will only work if modifying the naming convention of the terminals is an option available to you, but here’s what I’m doing to determine which terminals get which RDP connection profiles:

    Add a prefix or a suffix to all terminal names denoting whether they are single monitor or dual monitor. For example, if your terminals are named EastBranch01, Warehouse04, etc., you could add a two-letter suffix and make them EastBranch01dm and Warehouse04sm. Then put this line at the end of wnos.ini instead of specifying display settings:

    Include=&Right($TN,2).ini

    and inside the wnosinc folder, create two files: sm.ini for the single-monitor settings, and dm.ini for the dual-monitor settings.

    You could do it as a prefix using &Left instead of &Right, and it could be longer (or even one character if you like). It still involves the work of adding that information to each terminal name, but unlike creating separate mac.ini files for each machine, it scales well. Future effort is reduced to naming the client correctly.

    #23910
    AvatarWayne
    Member
    • Total Post: 5
    • Newbie

    Thanks that is quite helpful I will give it a go.

    #23930
    AvatarMrCentral
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    Glad it’s helpful!

    I’ll mention a couple other things just to head off potential frustrations:

    1. I’m guessing you’re using new-ish clients, but just FYI you can’t Include= based on terminal name on versions prior to 5.something. I know for sure that 4.4 won’t do it so I have a legacy solution for our oldest clients.

    2. Make sure that those two display settings files (sm.ini and dm.ini in the example I gave) *actually* have a .ini file extension. Since extensions for known file types are hidden by default in Windows 7, it was easy for me to forget and just create a text file. Easiest thing is just to make the files in Configuration Generator, or to make copies of your wnos.ini and then replace their content with the settings you want and rename them.

    That probably seems incredibly obvious but it threw me for a loop when I was doing initial testing.

    #23944
    Avataramiss
    Participant
    • Total Post: 42
    • Frequent Flyer
    • ★★★

    So I have a question on this:

    Say my terminals were named:
    wyse-trm

    with this include in the .ini file:
    Include=$TN.ini

    And this file located on our FTP server:
    wyse-trm.ini

    If I wanted to use these &Left and &Right parameters and rename the terminals to something like:
    wyse-trmxp

    With this include:
    Include=&Right($TN,2).ini

    would I need to change the terminal name .ini files from wyse-trm.ini -> wyse-trmxp.ini AND also create the xp.ini file, or do I just need to create the xp.ini file and the Include will snip however many (in this case, 2) characters off the end so it’s still looking for wyse-trm.ini instead of wyse-trmxp.ini?

    #23946
    AvatarMrCentral
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    I’m not sure if this will answer your question (“would I need to change x or y?”) because I don’t know what you’re trying to accomplish, or what the different files are supposed to do.

    The offsets (&Right, &Left) are confusing because they sound like they’re trimming off the specified amount of characters; actually the number you specify determines how many characters it reads.

    Using your example, if you have a client called wyse-trmxp, when you say
    Include=&Right($TN,2).ini
    you are ultimately asking the client to look in the wnosinc folder for a file named xp.ini
    If it finds one, the settings will be applied; the same will be true of any clients whose terminal names end with “xp.”

    – $xx obviously tells it which variable to use ($TN is the most flexible since you have control over its value, but you can use any of them and $MAC is quite useful)
    – &Right tells it to read from right to left
    – &Left tells it to read from left to right
    – and the number after the comma tells it how many characters to read.

    Does that make more sense? If that doesn’t answer the question, tell me how you’d like the clients to be organized (what groups get what settings, etc.).

    #23947
    Avataramiss
    Participant
    • Total Post: 42
    • Frequent Flyer
    • ★★★

    That does. What I was trying to do would be have the specific terminal configurations in the wyse-trm.ini file (such as the resolution, the mouse speed, etc., etc.) and in the xp.ini file there would be a XenApp connection to an XP desktop

    I don’t know how to best explain the question; I did some quick testing using both:
    Include=$TN.ini
    Include=&Right($TN,2).ini

    with terminal name:
    wyse-trmxp

    and .ini files:
    wnos.ini
    wyse-trm.ini
    wyse-trmxp.ini
    xp.ini

    The wnos.ini would always load

    the wyse-trm.ini, wyse-trmxp.ini, and xp.ini files all contain Exit=all at the end of them, so it would include the first .ini file but on the second. I didn’t test without exit

    BUT the important thing I answered:
    using Include=&Right($TN,2).ini WILL NOT include both the wyse-trmxp.ini (or the wyse-trm.ini) and xp.ini file, it will only include the xp.ini file.

    So, if you use &right or &left, it will only include the truncated file (in my case, xp.ini). you would have to use a separate include file (such as Include=$TN.ini) to include the normal terminal name file

    #23948
    AvatarMrCentral
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    That is correct. When you use &Right or &Left, it reads however many characters from the direction specified and looks for only that file. It will not deal with partial matches.

    So here’s how I have these set up. We have about ten locations and a few different usage profiles within them. All the locations have three-letter codes, so I use those and use three more characters to differentiate the profiles. So I end up with 4-7 profiles per location, all using six letters. Those profile names are the beginning of all the terminal names. Then I do an include from the left with the first six characters. I have another include statement for nine characters because one location is large and has several large departments.
    The clients from that larger location still see and try to run the include statement for six characters, so they look for the location and department codes. But since I don’t have a .ini file named precisely that, it doesn’t cause any issues.

    So you can definitely use two include statements (the two you tested), one looking for the .ini matching the last two characters and one looking for the whole-name match. But if your goal with the whole-name match is to apply a few settings only to one machine, another option would be:

    Include=&Right($MAC,6).ini

    This looks for a file matching the last six characters of the MAC address, which will obviously be unique. That’s how I’m keeping the device-specific .inis more separate in the inc folder from my area-profile ones.

    As to the Exit=All, you only need that statement in the included .ini if you want that .ini to be the last thing processed. For example, I have the display settings at the very end of wnos.ini, with an Include=($MAC,6).ini right before it. If I want to use the $MAC.ini for alternative display settings and not have the defaults in wnos.ini be processed, then I use Exit=All. But earlier Include statements aren’t looking for settings to replace a contradictory default, they’re just adding settings in. So there’s no Exit=All and processing continues where it left off.

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.