KineticNetworking
asked on
Can dot net 3.5 be included in a WSUS server
I have setup a Windows deployment system (please see Spec below). In my deployment I add the feature .net 3.5. The whole network points to my WSUS server for updates. Most of the time the .net 3.5 feature fails to install and when I also try to add the feature to non Windows MDT deployed computers it also fails. I have found a work around by adding a registry key that will bypass my wsus server and get the files from windows update. but is there a way to add the files needed to my WSUS server so I don't have to do the registry key patch.
Deployment Servers Spec
Windows Server 2012R2 with WDS /MDT (2013 Update 2)
Windows Server 2012R2 with WSUS
Windows Server 2012R2 with KMS
Deployment Servers Spec
Windows Server 2012R2 with WDS /MDT (2013 Update 2)
Windows Server 2012R2 with WSUS
Windows Server 2012R2 with KMS
ASKER
Sorry for the confusion. My main question is when we try to add .net3.5 as a feature on any client machine, it errors out and Windows wants to look for the source files to finish the install. Can the .net 3.5 source files be added to my WSUS server so when we want to add .net 3.5, it can get them from the WSUS server and not look for the local CD or windows update website?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Instead of adding the files to the WSUS you will need to create a shared folder with read access to enable a distribution point for the source files needed by the operative system to add the .NET 3.5 feature.
You will have to plan a specific folder for each operative system version (7/2008/2008R2/8/8.1/2012/
You can obtain the SXS files from the C:\Windows\WinSXS folder on a computer with the .NET already installed, or you can extract the files from a good WIM file.
You will have to plan a specific folder for each operative system version (7/2008/2008R2/8/8.1/2012/
You can obtain the SXS files from the C:\Windows\WinSXS folder on a computer with the .NET already installed, or you can extract the files from a good WIM file.
I have found another article about this on Microsoft site.
ASKER
Thank You I will look into this.
To prepare the image you need to install a temporary machine with the operative system you want to clone, add all feature you need, install all baseline programs, then run SYSPREP and reboot, then boot with PXE and pick up the option to Capture Image. Microsoft Windows Deployment Guide is a good document to start reading.