none
boot.wim has reached 4.5 GB deployment stuck RRS feed

  • Question

  • Hello there,
    recently the deployment of nodes got stuck and  we determined the cause to be the interruption of the boot.wim file transfer.
    The boot.wim is currently larger than 4.5 GB and it hits some limit there while being transferred.

    I tried to replace the boot.wim with a standard win2008 x64 boot.wim from another server, but now everything after the boot.wim stops.

    So my basic questions are:

    1. How can I force the hpc2008 cluster to rebuild its WDS like deployment. Just adding new OS images didn't do the trick.
    2. Is there anything special about the HPC2008 boot.wim in contrast to ordinary WDS boot.wim ? It was my impression that every setting is provided by config files and that the boot.wim is rather generic.
    3. How can I look inside a boot wim to see what goes on  with the 4.5 GB Monster. S.th. more intuitive than imagex would be great!
    Thanks in advance

    JH
    Thursday, March 4, 2010 10:06 AM

Answers