multiple .ini files

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #8134
    Klokos
    Member
    • Total Post: 3
    • Newbie

    Hello and thanks for this great forum!!

    I would like to manage Xenith clients that are in different countries / time-zones. To do that I need to deploy various .ini files.

    As a test I created one .ini file and added DHCP-ID tag:

    option 161 string http://wyse.domain.com

    My .ini file is located on IIS server here C:inetpubWYSE Managementwysewnos

    And it works perfectly well!!

    Now… My solution for multiple .ini files would be:

    Create sub-folders in C:inetpubWYSE Management

    location1wysewnos

    location2wysewnos

    location3wysewnos

    And then create DHCP-IDs on each site:

    option 161 string http://wyse.domain.com/location1

    option 161 string http://wyse.domain.com/location2

    option 161 string http://wyse.domain.com/location3

    Is this correct way to go on?

    I’m using Juniper firewalls that runs DHCP.

    #24599
    ConfGen
    Keymaster
    • Total Post: 10692
    • Jedi Master
    • ★★★★★★★

    No, you have to use OT 162 instead.
    OT 161 is just the fileserver, whereas OT 162 gives you the path.
    But instead of that, your way is correct.

    CG

    #24628
    Klokos
    Member
    • Total Post: 3
    • Newbie

    So the correct style is:

    option 161 string http://wyse.domain.com

    option 162 string location1

    or

    option 162 string /location1

    #24633
    ConfGen
    Keymaster
    • Total Post: 10692
    • Jedi Master
    • ★★★★★★★

    Just “location1”.

    CG

    #24636
    Klokos
    Member
    • Total Post: 3
    • Newbie

    And the structure under “location1” should be:

    location1wysewnosxen.ini

    OK?

    #24647
    ConfGen
    Keymaster
    • Total Post: 10692
    • Jedi Master
    • ★★★★★★★

    Yes

    CG

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