Newly Install of WDM 4.7.2 Enterprise Edition

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #5505
    Mangelsdorff
    Member
    • Total Post: 23
    • Regular Joe
    • β˜…β˜…

    Hello,

    since now we use WDM just for setting up the devices (941GXL, V90L, V90LE) in an isolated network and then putting the devices in our internal network.

    Since conficker virus in march/april 2009 all devices were newly installed with actual image with own settings (and patches πŸ™‚ ) extracted under WDM 4.7.0 and then put to the devices with Wyse Simple Imager.

    This was quite a lot of work and finally I received my money to implement WDM Enterprise on network πŸ˜€

    Now I have some open questions about implementing the WDM and the effects when installing the WDM on network.

    The devices (941GXL, V90L, V90LE) are on different subnets.

    1)
    Is the WDM searching the Network for devices right after the setup ?
    As they are XPe devices, they should restart once to write back the WDM IP (as stated in the documentation). Is the time is to be estimated when it will happen ?

    2)
    We have a pxe-server for enteo OSD at work.
    Does the WDM work with this or how should we solve this ?
    Do we have to put DHCP Option Tag 186 or do we have to do something special with IP Helpers (we do have active IP Helpers) ?

    3)
    Can we alternatively use HTTP-Imaging with the HAgent Version 5.1.0.15 which is now on all devices, or do we have to re-image the devices for this ?

    Thanks for answers in advance πŸ˜€

    #17105
    ConfGen
    Keymaster
    • Total Post: 11424
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Hi,

    1. No, you would have to do a search within WDM. But do it on a IP Range base and not on Subnet base as subnet searches are done via UDP broadcast which is normally blocked from the routers.

    2. Only on PXE server can exist in a subnet. Either shutdown Enteo while imaging your Wyse units or make sure Enteo is just answering his dedicated PCs/Servers. WDM will always only answer known clients in his database.
    OT 186 is not needed but IP helpers have to be set. Even if you already have some in place, you can always add more. Point them directly to the WDM server.

    3. HTTP imaging does not solve your issue. Non-PXE imaging would solve it. But to get this running you would have to have a Non-PXE boot agent on the unit which can only be achieved by reimaging the unit. And, btw, Non-PXE bootagents are only available currently for some selected devices.

    CG

    #17109
    Mangelsdorff
    Member
    • Total Post: 23
    • Regular Joe
    • β˜…β˜…

    to 1)
    OK, seems to be clear.

    to 2)
    I will contact Enteo if they support mac filtering.
    If so, it would be possible to filter 008064* out (this are our thin clients).

    IP Helpers are already set as networker mentioned to me before.
    Right now the IP Helper should point to DHCP Server i think.

    What do you mean that they can add more ?
    I think you mean that one IP Helper shows to the WDM-Server too (additionally to the one that points to the DHCP-Server) ?

    to 3)
    To understand right –>
    PXE is just needed to reimage the device, right ?
    To distribute software this is not necessary, right ?

    Which selected devices are currently supported ?
    How to image them with these Non-PXE-Bootagents ?

    Thanks for patience. πŸ˜€

    #17116
    ConfGen
    Keymaster
    • Total Post: 11424
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    2. Filtering 008064* would work perfectly.
    IP Helper should point to the DHCP server AND WDM server. So implement at least 2 IP helper.
    3.

    PXE is just needed to reimage the device, right ?

    Yes

    To distribute software this is not necessary, right ?

    Yes

    Which selected devices are currently supported ?

    V, VL, VLE and RL, RLE, RLW and RLEW – class units.

    How to image them with these Non-PXE-Bootagents ?

    You would have to completly reimge the unit as the BA resides on a second partition.

    CG

    #17117
    Mangelsdorff
    Member
    • Total Post: 23
    • Regular Joe
    • β˜…β˜…

    As it seems the mac filtering is not possible.
    We will proof this through a specialist further, but I thin this will take some time.

    We will now set up a test scenario where we test the option tag 186 togehter with the ip-helper pointing to the dhcp server.
    As my colleagues are saying this should work then.
    … we will see …

    So our 941GXL are not “Non-PXE-Bootable”
    and our V90L/V90LE are “Non-PXE-Bootable”.

    My question is how to set up a non-pxe-bootagent ?
    How do i set them up this way ?

    #17119
    ConfGen
    Keymaster
    • Total Post: 11424
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    You cannot easily setup this Non-PXE BA yourself. Although possible it require quite a lot of work.
    Contact Wyse or wait until Non-PXE images are posted on Wyse.com.

    CG

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