Help with big mess!

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #4557
    uselessuser
    Member
    • Total Post: 2
    • Newbie

    Hi

    I have walked into a odd situation…

    250 small branches with no infrastructure in place, just a router giving out DHCP and 3 or 4 WYSE clients.

    The clients range from a 8440, to a 9450, to V90L’s (All have some kind of Windows OS on, either NT or XPe)

    The problem is none of these are being centrally manged or asseted etc…

    Some have been imaged using a 4.5.2 WDM server which has now been destroyed (And it had an IP in a range no longer in use – yep this gets better)…

    Anyways I have had enough of this so I have decided to do something about it…

    After a bit of reading…The plan is to install 4.7.2 Workgroup on a new server and do the following…

    At each branch router giving dhcp configure dhcp option 43 to point back to the WDM server so we can push installs

    Configure option 186 to point back to our WDM server so that the HAgent’s come back to the new WDM server so we have some initial visibility… Which will necessitate reboots of the client but that is not an issue if I configure a branch at a time I can warn them!

    Now for the questions!

    Any problems with the above??!!

    Firstly this option 186, does it work? I have seen various references stating it is ignored by XPe?? I have also set up a test environment and it does not appear to do anything? I have it set as a IP address type does it need to be something else? Also does the client actually need to be able to see the WDM server at the time of getting the address to do the three reboots? I do not believe I need 187 or 192 etc as I am running standard WDM on port 80…

    As the 8440’s, and 9450 devices are no longer supported by WDM, do they not appear in the console at all, or will they appear but be unmanageable (Looking for an easy way to get numbers in order to replace with V90L’s)

    Also does anyone know in a technical sense what the find devices method is? Does it walk all IP’s poking a specific port on the client?? It just does not seem to work???

    #16561
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Wyse is working on this but currently OT 186 is still not working as expected with Xpe devices.
    So you would have to reconfigure each device manually or recreate a WDM with the old IP and then push a package to change the WDM server IP on the clients agent.

    CG

    #16563
    uselessuser
    Member
    • Total Post: 2
    • Newbie

    Hi,

    I thought this might be the case… (sigh)

    And the number one issue I have with this is that if I can recreate a new WDM server with the old IP address, all units across all branches that have that address are going to at some point reboot which is going to be entirely out of my control…

    This also does not help with the devices that were USB imaged and have no details in the Rapport/WDM control panel icon…

    God damnit WYSE this is useless…

    Do you have some kind of insight into WYSE tech that would give any indication of what is wrong and when it will be resolved?

    #16564
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    My contacts told me that this should have been solved in the latest agent but it isn’t. So I guess it will be in the next.
    Let’s keep the fingers cross.

    CG

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