locked
Getting error messages when deploying WIndows 2016 via MDT RRS feed

  • Question

  • Getting error messages: ZTIOSRolePS.ps1 

    ArgumentNotValid: The role, role service, or feature name is not valid: 'Web-DAV-Publishin'.  The name was not found.

    This same error happens with Web-Http-Error, 

    When I checked Windows 2016 Roles/Features, these names are not correct.

    Where do I go to modify the roles for Windows 2016?  Version 8443 is said to be compatible with Windows 2016: MDT https://blogs.technet.microsoft.com/msdeployment/2016/11/14/microsoft-deployment-toolkit-8443-now-available/


    Consultant

    Thursday, March 14, 2019 5:20 PM

All replies

  • There are 3 typos in the ServerManager.xml file.  I reported these to Microsoft years ago, but MDT v8450 & v8456 still have the errors.

    To fix the errors, you'll need to edit the Scripts\ServerManager.xml file in your deployment share.

    "Web-DAV-Publishing"

    Change both instances of this (for MDT 8443, it is lines 2314 & 2616):

    <RoleService DisplayName='WebDAV Publishing' Id='Web-DAV-Publishin' />

    to:

    <RoleService DisplayName='WebDAV Publishing' Id='Web-DAV-Publishing' />

    "Web-HTTP-Errors"

    Change both instances of this (for MDT 8443, it is lines 2311 & 2613):

    <RoleService DisplayName='HTTP Errors' Id='Web-HTTP-Error' />

    to:

    <RoleService DisplayName='HTTP Errors' Id='Web-HTTP-Errors' />

    "Fax Server"

    Change this one instance (for MDT 8443, it is line 2265) from:

    <RoleService DisplayName='Fax Server' Id='DNS' />

    to:

    <RoleService DisplayName='Fax Server' Id='Fax' />

    You should also copy the updated file to the Bin and Templates\Distribution\Scripts folders on the computers where you've installed the Toolkit.


    -Tony

    • Edited by Tony MCP Saturday, March 16, 2019 8:18 AM
    • Proposed as answer by Tony MCP Friday, April 5, 2019 7:32 AM
    Saturday, March 16, 2019 7:18 AM
  • Thanks Tony, that did the trick !!!

    Consultant

    Monday, April 1, 2019 3:22 PM
  • I can confirm that this is still a bug in  MDT 8456.
    although I never ran into those issues yet, but I have corrected it !

    Thursday, April 4, 2019 12:48 PM
  • Thanks Tony, that did the trick !!!

    Consultant


    Please mark my reply as the answer.  Thank you.

    -Tony

    Friday, April 5, 2019 7:32 AM