- #Inno script studio check .net 3.5 how to#
- #Inno script studio check .net 3.5 install#
- #Inno script studio check .net 3.5 update#
\sxs\19xx -NoRestart -LimitAccessĮnable-WindowsOptionalFeature -Online -FeatureName ‘NetFx3’ -Source.
Set-ItemProperty -Path “HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU” -Name “UseWUServer” -Value $currentWUĮnable-WindowsOptionalFeature -Online -FeatureName ‘NetFx3’ -Source.
Set-ItemProperty -Path “HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU” -Name “UseWUServer” -Value 0Įnable-WindowsOptionalFeature -Online -FeatureName ‘NetFx3’ -Source.
$WinVer = (Get-WmiObject -class Win32_OperatingSystem).Version $currentWU = Get-ItemProperty -Path “HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU” -Name “UseWUServer” | select -ExpandProperty UseWUServer I modified the script and now works like a charm! Get the cab file on the corresponding ISO. I was getting some issue depending of the OS version. Net 3.5 cab-files if you want to use local source installation and be able to take advantage of Delivery Optimization otherwise \sxs\ -NoRestart -LimitAccessĮnable-WindowsOptionalFeature -Online -FeatureName 'NetFx3' -NoRestartĭisable-WindowsOptionalFeature -Online -FeatureName 'NetFx3' -Remove -NoRestartĬreate a new folder called dotnet35 and copy in the script Install.ps1 and also include the SXS folder with the. \sxs\Microsoft-Windows-NetFx3-OnDemand-Package*.cab)Įnable-WindowsOptionalFeature -Online -FeatureName 'NetFx3' -Source. More info about DISM here –dism–command-line-options
#Inno script studio check .net 3.5 update#
If the files and folder does’t exist it will run Enable-WindowsOptionalFeature withouth the /source parameter which means that the computer will go to Windows update and get the files needed. Net content already exist in the Win32 app package, if the folder sxs exist and inside at least one NetFx3 cab-file is present it will run the DISM command and point to that source. Im also including logic In the script to check if the.
#Inno script studio check .net 3.5 install#
This will make us be able to both do Install and uninstall with Intune. Here’s the powershell Installation script we will use, this will invoke the installation or uninstall depending on what we parameter we call the script. The next step is to start putting it all togheter. Mount the Win10 ISO and navigate to sources\sxs and copy the 2 files that contains netfx3 in the name. Instead of adding the source files to the installation package we can also just let each machine get the content directly from Microsoft. We will be using the Enable-WindowsOptionalFeature powershell cmdlet and we can either specify a source path for the. Net 3.5 content to the client In this scenario. Net 3.5 then we need a custom Installation script which is provided below and then we need to convert it to a. To make this all happen we have few things, first of all. Net in all of our applications that requires it. Net as a dependency so we no longer have to include. Togehter with the new feature in Intune to set dependencies on Win32 apps we are now able toĭeploy. Net to our Windows devices but the most frequent one I encounter is that there’s still a lot of applications requiring version 3.5 and Windows 10 does not come with that pre-installed. There could be many reason for why we want to deploy any version of.
#Inno script studio check .net 3.5 how to#
Welcome back to another blog post and today I will cover how to deploy.