Deployment Solution

 View Only

Why does the Windows @OSFlavorName not get filled in with non-Default unattend.xmls in DS 8.0?

  • 1.  Why does the Windows @OSFlavorName not get filled in with non-Default unattend.xmls in DS 8.0?

    Posted Jan 24, 2017 05:05 PM

    Dear All,

    I am trying to get DS 8.0 HF5 working with installing Windows 10 Professional. The Default Unattend answer file (same as the 2016 file) works, but the computer does not auto-login to complete the final (and tediously-slow) installation after the user logs in.

    So as to fix this, I have copied out the Default Unattend.xml from the SOI/AnswerFiles folder and edited this to add an Auto-Login section for 1 time to get Windows to finalise the installation on its own (and probably auto-reboot?)

    When I make this change to the Unattend.xml, I find that the selection for which OS to install appears and the setup.exe hangs there. When I look at the Unattend.xml, I see that the XML file has not been edited by DS to change the @OSFlavorName variable to "1", which is the correct value, but stays as "@OSFlavorName" in the XML file. When I edit the file itself in the custom folder and manually replace @OSFlavorName with 1 and re-run the installation task, the setup.exe again hangs in the same place (however, if I press "Next", it does go through to completion). When I again look at the Unattend.XML file, the @OSFlavorName value is back!

    What is going on?!?!?

    Kindest regards,

    QuietLeni