installig framework 3.5 role does not work on wsus client
i have a server 2012 R2 running.
this server gets his updates from a wsus server in the local lan.
now i want to add the client a new role and feature.
.framework 3.5
this always fail, because the source files are missing.
any help?
this server gets his updates from a wsus server in the local lan.
now i want to add the client a new role and feature.
.framework 3.5
this always fail, because the source files are missing.
any help?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
After doing this try to reinstall the .Net 3.5 framework
You are being restricted by your Domain GPOs. Use your local computer Group Policy Editor to manage this for that local computer/users
If you do have domain admin access, I'd suggest modifying the GPOs related to your update configurations to allow for this if your WSUS server is not download/distributing properly...you will probably find that you have a BUNCH of updates that haven't been pulled down in a while...
You are being restricted by your Domain GPOs. Use your local computer Group Policy Editor to manage this for that local computer/users
If you do have domain admin access, I'd suggest modifying the GPOs related to your update configurations to allow for this if your WSUS server is not download/distributing properly...you will probably find that you have a BUNCH of updates that haven't been pulled down in a while...
As Hector2016 pointed out above, you need Windows Server 2012 OS installation files on a dvd or on local drive and specify Alternate Source Path during Add roles and features wizard.
Microsoft's Technet page:
"For environments that use Active Directory and Group Policy, the Feature on Demand (FoD) policy setting option provides the most flexibility for the installation of .NET Framework 3.5. This Group Policy setting specifies the network locations to use to enable optional features that have had their payload files removed, and for file data and registry repair operations from failed update installations. If you disable or do not configure this setting, or if the required files cannot be found at the locations that are specified in this policy setting, the files are downloaded from Windows Update (if this is allowed by the policy settings for the computer). The Group Policy setting Specify settings for optional component installation and component repair is located at Computer Configuration\Administrati
Deploy .NET Framework 3.5 by using Group Policy Feature on Demand setting
-----
https://technet.microsoft.
"For environments that use Active Directory and Group Policy, the Feature on Demand (FoD) policy setting option provides the most flexibility for the installation of .NET Framework 3.5. This Group Policy setting specifies the network locations to use to enable optional features that have had their payload files removed, and for file data and registry repair operations from failed update installations. If you disable or do not configure this setting, or if the required files cannot be found at the locations that are specified in this policy setting, the files are downloaded from Windows Update (if this is allowed by the policy settings for the computer). The Group Policy setting Specify settings for optional component installation and component repair is located at Computer Configuration\Administrati
Deploy .NET Framework 3.5 by using Group Policy Feature on Demand setting
-----
https://technet.microsoft.
There is a hotfix that fixes that.
Explanation: https://support.microsoft.com/en-ca/kb/3002547
Hotfix 3005628: https://support.microsoft.com/en-ca/kb/3005628
Explanation: https://support.microsoft.com/en-ca/kb/3002547
Hotfix 3005628: https://support.microsoft.com/en-ca/kb/3005628
I'm glad to hear that I was able to help
In this case WSUS won't help you , because .NET needs to be installed as a feature, not as an update.