MDT 2013 : Who knows the value name for .NET Framework feature in the OSFeatures property? RRS feed

  • Question

  • Hi,

    Who knows the value name for .NET Framework feature in the OSFeatures property of the CustomSettings.ini?

    I've tried:

    - NET-Framework
    - NET-Framework-Core
    - NET-Framework-Features

    Nothing seems to work: .NET Framework 3.5 (includes .NET 2.0 and 3.0) value is not preselected under Roles and Features step.

    Friday, November 8, 2013 1:23 PM

All replies

  • Have a look at this link: Installing the .NET Framework 3.5 on Windows 8 or 8.1

    The actual command is:

    Your computer is not connected to the Internet. Please connect, and then retry the operation.

    If you cannot connect to the Internet, you can enable the .NET Framework 3.5 by using the Deployment Image Servicing and Management (DISM) command-line tool and specifying the installation media (ISO image or DVD) you installed Windows 8 from.

    1. In Windows 8 or Windows Server 2012, open a Command Prompt window with administrative credentials (that is, choose Run as administrator).

    2. To install the .NET Framework 3.5 from installation media located in the D:\sources\sxs directory, use the following command:

      DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs

    If this post is helpful please click "Mark for answer", thanks! Kind regards

    • Proposed as answer by Keith GarnerMVP, Moderator Friday, November 8, 2013 8:02 PM
    • Marked as answer by AcetiK Monday, November 11, 2013 9:55 AM
    • Unmarked as answer by AcetiK Monday, November 11, 2013 9:56 AM
    Friday, November 8, 2013 7:02 PM
  • Thank you.

    But I meant in the CustomSettings file:



    • Edited by AcetiK Monday, November 11, 2013 9:57 AM changed
    Monday, November 11, 2013 9:56 AM
  • AcetiK,

    What I don't understand is, you can enable it with command line + DISM.

    You can enable with 'Add Roles and Features' through Windows 8, Server 2008 and Server 2012 (see the link:MDT 2012 Update 1: Roles and Features improvements) why make it yourself any harder and do this with the customsettings.ini?

    If this post is helpful please click "Mark for answer", thanks! Kind regards

    Monday, November 11, 2013 10:12 AM
  • I'll take this option if there is no other solution.

    But MDT 2013 seems to allow to install this feature in the natural deployment process without this script.

    Monday, November 11, 2013 12:07 PM
    Monday, November 11, 2013 12:41 PM
  • Best bet is to use the Install Roles and Features step in the Task Sequence.

    If you want to enable/disable these OSRoles/OSFeatures in the cs.ini, you would *first* simulate the desired roles in the MDT Console UI. Then go to the deployment share and open the file

          <step type="BDD_InstallRoles" name="Install Roles and Features" description="" disable="false" continueOnError="false" runIn="WinPEandFullOS" successCodeList="0 3010">
              <variable name="OSRoleIndex" property="OSRoleIndex">10</variable>
              <variable name="OSRoles" property="OSRoles"></variable>
              <variable name="OSRoleServices" property="OSRoleServices"></variable>
              <variable name="OSFeatures" property="OSFeatures">NetFx3,NetFx4-AdvSrvs,DirectPlay,Microsoft-Hyper-V-All,Microsoft-Hyper-V-Tools-All,Microsoft-Hyper-V-Management-Clients,Microsoft-Hyper-V-Management-PowerShell,Internet-Explorer-Optional-amd64,MediaPlayback,WindowsMediaPlayer,Microsoft-Windows-MobilePC-Client-Premium-Package-net,MicrosoftWindowsPowerShellV2Root,MicrosoftWindowsPowerShellV2,SearchEngine-Client-Package,Printing-XPSServices-Features,Xps-Foundation-Xps-Viewer</variable>
            <action>cscript.exe "%SCRIPTROOT%\ZTIOSRole.wsf"</action>

    You can then remove the entries for OSRoles, OSRoleServices, OSFeatures, and put them in your CS.ini file.

    Note that the OSRoleIndex value is OS Specific.

    If any value is placed in the CustomSettings.ini file it will override this local TS.XML value.


    Keith Garner -

    Monday, November 11, 2013 5:26 PM