Installing .NET Framework 3.5 with MDT

You could use a DISM command line to install .net Framework 3.5 using something like:

DISM.exe /online /enable-feature /featurename:NetFX3 /All/Source:”%deployroot%\Operating Systems\Windows 8.1 x64 Enterprise\Sources\SXS” /LimitAccess

But since you have already imported the OS into MDT you may as well use the media that MDT already has and specify the source instead of using online sources.

In the State restore add a step to set the WindowsSource Path
The Windows Source will be located within the Operating Systems folder on your Deployment Share

  1. Add a Set Task Sequence Variable step
    1. Type Task Sequence Variable: WindowsSource
    2. Type Value for your source files: %deployroot%\Operating Systems\Windows 8.1 x64 Enterprise VL\Sources\SXS

  1. Add a Install Roles and Features step
    1. Select your Operating System within the step
    2. Mark .NET Framework 3.5 (Includes .NET 2.0 and 3.0)

At this point, you could also remove the Skip roles from  CustomSettings.ini using: SkipRoles=YES


No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

MDT – Joining a Computer to a Domain Using PowerShell

Using PowerShell scripts within a task sequence provides more flexibility than using the CustomSettings.ini file to join a computer to a domain. The parameters of the CustomSettings.ini file are common to any deployment you perform. That’s why creating a custom PowerShell script to join your domain will be customize to …

Task Sequence Tasks Explained

This document explains the tasks that you will find in standard task sequence. Initialization > Gather local only – gathers deployment configuration settings from local sources that apply to the target computer [ZTIGather.wsf] Validation > Validate – verifies that the target computer meets the specified deployment requirement conditions. Such as …

How MDT uses XML to install Applications

Have you ever thought about what actually happens when you import applications into your MDT environment? How does the task sequence know what application to install? How does it know what command-line arguments to specify during the application install process? Technically, as a user, all that is required of us …