Jump to content

Recommended Posts

Posted

By default Windows 10 does not install Net Framework 3.5, so I am trying to find step by step instructions of how to automatically install Net Framwork 3.5 on machines during deployment without much luck.

 

I am using the latest Win 10 1703 image and MDT and was hoping their would be an easy way of installing it via MDT, but the only instructions I can find involve using SCCM which I do not have.

 

If anyone else has managed to do this, I would really appreciate a step by step instruction of how you managed to do it.

 

At the moment I am logging on to each machine after building and installing manually and its a pain.

Posted

Back when we moved from 7 to 8/8.1 I put the dism command in the SCCM TS

Today on W10 I only have a few machines that need 3.5 so I push it with pdq deploy with the program that needs it.

 

I've not used MDT for a while now, but here is what I'd do.

1. evaluate if you still need 3.5, I'm guessing you have already done this since your going through the trouble to install it.

2. Create a bat file with the dism command to run as an app install.

OR

3. Modify the wim to have net 3.5 enabled.

 

The command you want is something like this.

 

Dism /online /enable-feature /featurename:NetFX3

Posted
Not using MDT, but enabling it before image capture works absolutely fine.

 

As I have never had to do this (using MDT) with Windows 7 in the past, is there any step by step guides or videos on how to do this (using image capture) with Windows 10?

Posted
I can't look now but if you good it there is a DISM command to do it. Just share the Win10 media somewhere and point DISM at it to install

 

I have been manually installing it using DISM but thats a pain having to manually install it after deployment. It also has to be run in a elevated command prompt. I did try creating a batch file but when I right hand click on any .BAT file and choose run as administrator a screen flashes and closes and the .BAT file does not run. I am not sure if there is another bug or issue in Windows 10 Pro causing this to happpen.

 

If it can be installed using DISM using MDT then I really need to have a step by step of where to put the task sequences and what to put in them, rather than trying to get it to work with trial and error.

Posted
Back when we moved from 7 to 8/8.1 I put the dism command in the SCCM TS

Today on W10 I only have a few machines that need 3.5 so I push it with pdq deploy with the program that needs it.

 

I've not used MDT for a while now, but here is what I'd do.

1. evaluate if you still need 3.5, I'm guessing you have already done this since your going through the trouble to install it.

2. Create a bat file with the dism command to run as an app install.

OR

3. Modify the wim to have net 3.5 enabled.

 

The command you want is something like this.

 

Dism /online /enable-feature /featurename:NetFX3

 

Just trying to work out exactly how I would implement this in MDT and where I would need to put task sequences and what they would need to be and what would need to be in them. I understand the theory but putting it in to practice I really need a step by step as I only know the basics of MDT and I am not an expert with it.

Posted
As I have never had to do this (using MDT) with Windows 7 in the past, is there any step by step guides or videos on how to do this (using image capture) with Windows 10?

 

You enable it (.NET 3.5) manually, run Sysprep and then capture using your imaging tool.

 

Likewise with Windows 7, you may choose to install .NET 4.5, 4.6 or maybe 4.7, run Sysprep and then capture using your imaging tool.

Posted

In Windows 10 I've just added an appropriate Install Roles and Features step to the task sequence. I saw no need to manually set up the WindowsSource variable.

 

Mind you, I've retired now. Maybe I left the whole thing in a mess.

Posted
with mdt just add it as a package and it installs with 0 interference as long as you dont have anything else set to limit what packages install
Posted
You enable it (.NET 3.5) manually, run Sysprep and then capture using your imaging tool.

 

Likewise with Windows 7, you may choose to install .NET 4.5, 4.6 or maybe 4.7, run Sysprep and then capture using your imaging tool.

 

 

I never did it that way for other .Net Frameworks (exxcept 4.7 which I have actually disabled as it breaks too much and tried to come down through WSUS anyway). I used a .BAT file in netlogon copying the text file across with a silent install at the logon screen (mod of the office installation .BAT file). What imaging tool do you use? Like I say never had any need to use Sysprep for Windows 7 (although I vaguely recall I may have used it for Windows XP deployments), but with updates was trying to get it onto already built machines and also works with .BAT file on rebuilding machines.

Posted
I think that this is what you need: https://blog.thomasmarcussen.com/installing-net-framework-3-5-with-mdt-2013-the-simple-way/

 

This is how I do it [emoji3]

 

Edit: article written for win 8 but method the same.

 

Thank you. I also found https://blog.thomasmarcussen.com/installing-net-framework-3-5-with-mdt-2013-the-simple-way/ which I was going to try if OS|DC: MDT 2013 U1: How to Install .Net Framework 3.5 on Windows 10 did not work. After spending ages on this it looks like there may be two easy ways of doing this.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...