T10 WDM Workgroup, DNS queries

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

    Hi first time poster, i have a couple queries with our recently purchased t10.

    Firstly on our WDM server (4.9.1) i can see the WTOS device though any commands i.e shutdown/reboot/WOL will not work. I tried looking to apply an updated agent though i couldn’t see the option for hagent….do you need to do this with the t10?

    Secondly i have configured ftp access and the t10 pulls the wnos.ini file, applying the configuration changes though when i look at the event log it states

    Contacting File Server
    Accessing system profile
    open ini error: Login failed

    Any idea reagrding this?? And also when you reboot or start up the device it hangs while “Contacting WDM Server” for roughly 20 seconds, is it normal?

    Lastly after assigning a hostname to the device and entering the correct DNS entry under the “Named Servers” dialog box it does not create an A host dns record, thus i cannot ping the hostname.

    Just a few queries

    Thanks
    Mark

    #23771
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    1. you do not need WDM, nor do you have to update any agent. The WDM agent (of HAgent) is part of the OS image.
    2. post your wnos.ini
    3. on the client, go to Central Configuration – WDM and disable all discovery options.

    CG

    #23780
    MrMarkT
    Member
    • Total Post: 5
    • Newbie

    The reason i am using the WDM server is for management and remote shadowing if need be.

    Appreciate the reply

    #23781
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    2. post your wnos.ini

    Get your hands on the WDM 4.9.1 hotfix. This will eliminate the 20 sec delay.

    CG

    #23786
    MrMarkT
    Member
    • Total Post: 5
    • Newbie

    Thanks ConfGen, i appreciate the reply.

    For the ini file i fixed the issue that was causing that error. i had changed the default path in which the client was searching.

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