none
Enable .net3 / .net3.5 via group policy

    Question

  • We have DC on windows 2012 R2, and have clients of windows 7, 8, 8.1, 10, 2008, 2008 R2, 2012 & 2012 R2 in our domain.

    We have a s/w deployed by GPO and is successfully deployed, BUT it requires .net framework 3/3.5 to run.

    My que is how to deploy it to all m/c without going to it. Our users also don't have admin permissions on their computers.

    i will make this gpo (http://www.askvg.com/fix-cant-install-microsoft-net-framework-3-5-in-windows-8-and-later/) to not to go to windows update source but how to turn windows feature on & off for .net via GPO


    Thanks, Rishi Pandit.

    Friday, August 12, 2016 7:46 AM

Answers

  • ..my users dont have admin rights so can i pass dism command in powershell script (along with source) for them and if yes, how will it work?

    i understand i can share sxs folder and give permissions to domain computers group but what about account running dism running command.

    If you use a logon script, this runs as the user account logged on, and so the user would require admin rights.

    If you use a Startup script, this runs as the computer account, and so is therefore fully privileged on the local machine.
    In the case of Startup script, running as computer account, ensure that the sources (WinSxS) folder is shared for computer accounts access (i.e. share to Domain Computers or Authenticated Users)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, August 24, 2016 9:48 PM

All replies

  • Am 12.08.2016 um 09:46 schrieb Rishi Pandit:
    > [...] how to turn windows feature on & off for .net via GPO
     
    There is no native GP technic to handle Windows Features.
     
    Integrate .net in your Softwaredeployment Solution.
     
    Mark
    --
    Mark Heitbrink - MVP Group Policy - Cloud and Datacenter Management
     
    Homepage:  http://www.gruppenrichtlinien.de - deutsch
     
    Friday, August 12, 2016 9:21 AM
  • gpo startup script?

    maybe this:

    https://social.technet.microsoft.com/Forums/windows/en-US/418aa719-8079-4594-873a-62045e9814dc/gpo-enable-net-framework-35-in-windows-8?forum=w7itproinstall


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, August 13, 2016 7:56 AM
  • Hi,

    Please check if the steps mentioned in the following article is helpful to you:

    Deploy .Net 3.5 Using Group Policy

    http://www.lukebrowning.com/sysadmin/windows/deploy-net-35-using-group-policy/

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 15, 2016 5:46 AM
    Moderator
  • but deploying package would not cover windows 10 / 2012

    Thanks, Rishi Pandit.

    Wednesday, August 17, 2016 10:35 AM
  • on Windows7 and later, and also WS2008R2 and later, the .NET FW 3.5 is an Operating System component.
    So you need to use the OS component management (DISM or equivalent) to add this feature.

    The link provided by Alvin is not applicable to Win7 or later.


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, August 17, 2016 8:54 PM
  • Hi Rishi,

    Sorry for my mistake, add to DonPick's suggestion, you may refer to the following articles:

    .NET Framework 3.5 Deployment Guide for Administrators

    https://msdn.microsoft.com/en-US/library/cc160717(v=vs.90).aspx

    Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM)

    https://technet.microsoft.com/en-us/library/dn482069.aspx

    Best Regards,

    Alvin Wang 


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 18, 2016 2:28 AM
    Moderator
  • Yes i saw it before posting and mentioned the link (stating same) in question itself.

    After you suggestion question comes that my users dont have admin rights so can i pass dism command in powershell script (along with source) for them and if yes, how will it work?

    i understand i can share sxs folder and give permissions to domain computers group but what about account running dism running command.


    Thanks, Rishi Pandit.

    Tuesday, August 23, 2016 3:50 PM
  • Hello,

    You can just run a startup script like this one :

    Install-WindowsFeature Net-Framework-Core -source \\network\share\sxs

    Regards.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, August 23, 2016 5:28 PM
  • ..my users dont have admin rights so can i pass dism command in powershell script (along with source) for them and if yes, how will it work?

    i understand i can share sxs folder and give permissions to domain computers group but what about account running dism running command.

    If you use a logon script, this runs as the user account logged on, and so the user would require admin rights.

    If you use a Startup script, this runs as the computer account, and so is therefore fully privileged on the local machine.
    In the case of Startup script, running as computer account, ensure that the sources (WinSxS) folder is shared for computer accounts access (i.e. share to Domain Computers or Authenticated Users)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, August 24, 2016 9:48 PM