.Net Framework 3.5 - how to deploy globally

[cdwyer]

Hi all,

 

.Net framework 3.5 is not installed on our machines but there is an option in 'turn on windows features' for it, is there a way I can enable this setting globally so that .net 3.5 downloads automatically?

 

Thank you!

[mavhc]

What OS version?

[cdwyer]

What OS version?

 

Windows 10 1607 Anniversary Edition.

[ZeroHour]

You would have to use a DISM command I think, deploying it could be a little quirky though.

Dism.exe /online /enable-feature /featurename:NetFX3 /All

[mavhc]

I like to use https://msdn.microsoft.com/en-gb/windows/hardware/commercialize/manufacture/desktop/deploy-net-framework-35-by-using-deployment-image-servicing-and-management--dism#nointerent

 

Put sources file on the network, saves every client downloading it.

 

I run it as a script as part of my unattend.xml file, you can run it as a startup script via gpo too

[AliG]

You can now also use WSUS as the source using features on demand

[cdwyer]

Thanks everyone I'll give these a try Monday.

[CHiLL]

I'm deploying it as part of the SCCM Task Sequence and these are the steps I took (originally from a guide I found online, but I can't remember which it was).

 

1) Copy 'microsoft-windows-netfx3-ondemand-package.cab' from the 'Sources\sxs' folder of the Windows 10 installation media/ISO to an appropriate folder on your SCCM Sources$ share, such as \\sccmserver\sources$\Apps\NET 3.5.

2) In the same location that you have now copied the NetFx3 cab to, create a new powershell script containing:

$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All

3) In SCCM, create a new application package and select 'This package contains source files'. Select the path you have saved the NetFx3 cab to.

4) Click Next and select 'Do not create a program'.

5) Distribute the package to your distribution point.

6) Edit your Task Seqeunce and add a new step for Add > General > Run Powershell Script

7) Browse for the package you have created

8) Enter the script name in the 'Script name' box

9) Set the PowerShell execution policy to 'Bypass' in the drop down list

 

I don't know why, but I had issues deploying this as an application, but it works through the task sequence.

[Fazza]

We run a DISM command to do this via an SCCM Task Sequence when we deploy a software build via PXE etc. so it could easily be pushed out to clients as well - assuming you have SCCM that is?

[cdwyer]

Hi all,

 

We tried a few things and it turned out to be more trouble than it was worth, the build we had completed hadn't been deployed yet so we just installed it using programs and features and sysprepped it again, this seems to have worked. Thank you all for your comments.