Amerist

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 45 total)
  • Author
    Posts
  • in reply to: Reconfigure wnos.ini while DHCP 161 and 162 are set #42249
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    In our environment we use a WNOS.INI file that has Include = $MAC.ini as the very first line.

    This allows us to make special configurations that completely bypass the standard config.

    At the end of each MAC.INI we either include the EXIT to return back to the WNOS.INI and pick up additional default configuration settings or EXIT ALL to ignore the WNOS.INI completely.

    We use this approach to have several thin clients set up as kiosks and all that’s required to add another kiosk is to copy the existing MAC.INI from another Kiosk and change the MAC address on the file to point at the new winterm.

    Hopefully that made sense.

    in reply to: HELP !!!!! with configuration. #25474
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    Miles,

    I would highly recommend you seek out the individual responsible for creating and maintaining the DHCP for your office where these thin clients are deployed and ask them to add a couple of option tags for your DHCP scope. This only takes a couple of minutes for a qualified administrator. Once these are set up you do all the configuration from your FTP server.

    If your department has already spent the money on servers and licenses, its clear to me that the business deems this a necessary project, so if you need some help really don’t be shy about asking for two minutes of admin time to get the project complete the right way. DNS entry or the DHCP option tags are necessary for zero-touch deployment.

    Secondly, I see you are struggling with the wnos.ini file. I started with thin OS devices knowing nothing about how to configure them and when I started I wish someone had offered me this advice. Start with the Configuration Generator software and make your first INI file using that tool. Don’t select too many options at first, just the bare minimum to show you that the configuration is loading. Move on from there to add settings that are critical to delivering what you need. Once you have a working INI file then go in and make another one that’s more advanced. (the nice-to-haves)

    I would strongly encourage the use of MAC.INI files for testing. The way I have mine set up is the very first line of the WNOS.INI file is:

    Include=$MAC.ini

    Then at the end of my 008064XXXXXX.ini file I have this as the last line:

    Exit=All

    What this is going to do for you is that your users (production environment) can continue using your WNOS.INI file while you experiment with settings on your own terminal using your own “copy” of the WNOS.INI that’s actually called 008064XXXXXX.ini where the XXes are the rest of your MAC address on your test terminal.

    Finally, I would recommend you download a copy of the Wyse ThinOS INI Files Reference Guide as it will explain most of the settings that appear in your WNOS.INI file. It seems from your questions that you’ve asked (particularly about disabling the search for the WDM server) that you haven’t read this guide yet. FWIW, I use these settings:

    RapportDisable=yes
    Service=WDM disable=yes

    😉

    in reply to: Connect to a Macintosh? #25473
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    Thanks. What if I already have ARD installed? What’s the next step?

    in reply to: Is there an OS/hack/firmware that will work? #25472
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    @Veloslave wrote:

    @Amerist wrote:

    How many students concurrently and what’s your budget?

    I run around 600 units, NEVER that many concurrently but that is how many deployed.

    I just got a P25 from Dell to try out and I am pretty impressed so far… had to tell it where the connection server was due to older WYSE WDM software but BAM… smooth streaming A/V!!!

    I am shooting for next years budget… haven’t sprung the whole thing on the CBO yet, fingers crossed

    What kind of servers are you using? We use 2008 R2 with XenApp with Dell Wyse T10 terminals and have been very pleased. The P25 may more than you need.

    in reply to: PNagent and log off #25414
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    @oleschmi wrote:

    Another issue is that we have some shared devices that require that a user logs on, locks his desktop. Then another user want to log on but not log off the first users.
    Just like Citrix Storfront that have a X minutes inactivit on the web site before the user is logged off Storefront but not logged off the Citrix session.

    Is this possible?

    I realize this is an old post but I saw your question was unanswered. You should be able to set your Citrix servers to disconnect the session when idle for X minutes without logging off the session. The session can stay idle while in a disconnected state.

    As an example, in our environment, we use XenApp 6.5 and no storefront, but we use PNAgent. We have a 20 minute window of idle time before the screen locks. After 2 hours total idle time, the session disconnects. After 8 hours total idle time, the session logs off. Anytime after two hours but before the 8 hours is up, the user can log back in and reconnect with their disconnected session. All windows and apps are just as the user left it. We do this to reduce the number of logons and logoffs because these are hardest on server performance. (it’s less work for the server to have five idle sessions than one person logging in)

    in reply to: Is there an OS/hack/firmware that will work? #25413
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    How many students concurrently and what’s your budget?

    in reply to: “Connection reset by peer” #25412
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    This same message happened to us when we migrated DHCP role from existing server to a new server. We forgot to shorten the lease times a few days in advance, and we think this may have caused some address conflicts on the network. Some Wyse ThinOS devices exhibited this message as well as a disconnect symptom. In all cases, the users were able to get reconnected with their XenApp 6.5 sessions.

    in reply to: C10LE and Internal Wireless #24264
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    Also if your C10LE is wireless capable it will come with an antenna in the package that you can screw on the back. Just pull off the black rubber plug to expose the threads.

    in reply to: WTOS winterms time out connecting to XA 6.5 farm apps #23142
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    I just checked and we have two Web interface servers. One listed the farm name as XenApp65 and the other WI server listed the farm name as XA65. I corrected this so they both say XA65 and now everything is working normally.

    in reply to: Resetting expired passwords #22980
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    make sure there is no other “signon=” in your WNOS.INI and make sure that if you need an EXIT=ALL at the end of your MAC.INI file that you have one there.

    in reply to: C10LE Xenapp6 Dual Monitor Spanning #22979
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    This may be a red herring, but I though it might be worth a try. I had a similar problem with full-screen desktops on a dual-monitor PC.

    I had two problems that were somehow connected. When launching full screen sessions on a Dual-monitor PC running Receiver for Enterprise 3.2 with a XenApp 6.5 published desktop, the citrix menu (AKA “connection bar”, “desktop viewer”) did not appear. The second problem was that the taskbar was stretched across two monitors, and maximized windows would span both monitors.

    When I tried the solution for the first problem, it magically fixed the second!

    http://support.citrix.com/article/CTX122544

    By default the “desktop viewer” is only enabled for XenDesktop, but we had grown accustomed to using it because it appeared all on its own with our old XenApp 4.5 farm.

    I added the desktopviewer=1 line to the webinterface.conf of my PNAgent site on the Web Interface server and added ConnectionBar=1 to the [application] section of the default.ica file.

    Like I said, I wasn’t expecting that one would have anything to do with the other but it worked for me. By the way, this connection bar only appears on Citrix Receiver so it won’t affect your Winterms.

    in reply to: C10LE SCREENSAVER #22953
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    Example floating logo screensaver. Add this line to your wnos.ini or %mac%.ini and use your own bitmap, placed in the path that ConfGen gave you.

    ScreenSaver=30 SoftSaver=no LockTerminal=yes Type=2 Image=AGM_wb_499x170.bmp

    in reply to: R10L – Latest and list of released firmware? #22952
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    R10LE 7.1_122 has a bug in it that you can’t get into the BIOS with the included PS2 keyboard. You would need to use a USB keyboard.

    in reply to: Wyse Software maintenance #22830
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    I’ve had some success using Wyse Simple Imager to first flash a unit to the right firmware then the USB firmware utility to “PULL” an image of the upgraded unit to have it on thumb drive. Then I can use that thumb drive to push the firmware to other units of the same model.

    in reply to: WNOS.INI issues please help #22561
    Amerist
    Participant
    • Total Post: 58
    • Back Stage Pass
    • ★★★★

    Do you have this line at the end of each of your {MAC}.INI files?

    Exit=all

Viewing 15 posts - 1 through 15 (of 45 total)