V10L

  • This topic is empty.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #633
    Avatarephesians52
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Hi, I’m having problems getting my V10L recognizing ftp://server/wyse/wnos/wnos.ini. I put the ini file with all the recommended folders and it’s like the V10L never saw the ini. the V10L is DHCP and recognizes the Server path, rapport server. The ultimate goal is to create a environment where i can have the ini contain the VDI broker, along with the restricted rights settings. Support could deploy the wysebox without having to configure it.

    #10307
    ConfGenConfGen
    Keymaster
    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    When you look at the V10L settings for the Fileserver, what does it say there?

    ConfGen

    #10315
    Avatarephesians52
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    162.30.48.101/WNOS

    #10317
    ConfGenConfGen
    Keymaster
    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    Hi ephesians52,

    then you have to put your wnos.ini in a folder ftproot/wnos/wnos/, cause the last folder wnos is always added by default by the unit.

    ConfGen

    #10318
    Avatarephesians52
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    I’ve done that but it still doesn’t see it. I grabbed a S10 and tried it but that doesn’t recognize it either. My wnos.ini looks like

    Privilege=None Lockdown=no
    DesktopColorDepth=32
    Resolution=1024×768 Refresh=75
    DeskColor=”0 0 255″

    I figure at least with this it’ll change the desktop background to blue and i’ll know the ini is working.

    #10319
    ConfGenConfGen
    Keymaster
    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    So the desktop color is changing but nothing else?

    Look at the eventlog on the V10L. Does it say “Cannot access system profile”?

    ConfGen

    #10321
    Avatarephesians52
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    no the desktopcolor isn’t changing. I was just using that is a quick visual reference the ini was working. I’ll post the log from the wyse box monday morning. thank you for the help so far though! this is a great site. I’ve shared it with some work buddies.

    #10325
    Avatarephesians52
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    I’ll hopefully be doing a conference call with a wyse rep / tech today. I’ll post the result if we come up with it. It’s probably something stupid i’m doing but i know i was able to do it before.

    #10345
    Avatarephesians52
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Emails that resolved my issues from the bottom up.

    Kevin – if it’s grayed out then you either have option tag 161 setup on DHCP OR you have Wyse Device Manager setup (I believe you do..) and it is enabled to hand out the path. To disable this on WDM, go into the Configuration ManagerPreferences tabBlazer and uncheck the box that says ‘Return FTP path’ or something to this effect.

    See if this helps.

    The path on the device can’t be changed. It’s greyed out. I was also hoping to set it up so that support does not have to make changes to the device. They can just plug them in oob and it works.
    Thanks,
    Kevin

    Change path to-
    ftp://162.30.48.101/wyse/wnos/wnos.ini

    Then on the device under network tab enter- 162.30.48.101/wyse

    It will automatically look for wnos.ini under wyse/wnos

    Let me know..

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