Views: 31.9k  |  Created: 09/06/2009

Average Rating: 0
.NET Framework has 8 inventory records, 16 Questions, 4 Blogs and 5 links. Please help add to this by sharing more!

Deployment Tips (13)

Most Common Setup Type
Windows Installer (MSI)
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 4 ratings
Most Commonly Reported Deployment Method
Windows Installer Command Line (No MST)

Deployment Tip Summary

.NET Framework Deployment Guide for Administrators -> http://msdn.microsoft.com/en-us/library/ee390831.aspx
or cancel
28
Command Line
We run this to install it:

dotNetFx40_Full_x86_x64.exe /q /norestart /log %temp%\dotNetFx40.log

If you run dotNetFx40_Full_x86_x64.exe /?, it will extract the setup files into a temporary directory and then display help text reproduced below. However, setup.exe can't be run directly and will just give you an error message, so the text below appears to be misleading.

---------------------------
Microsoft .NET Framework 4 Setup
---------------------------
Usage: Setup [switches]
All switches are optional.

/CEIPconsent - Optionally send anonymous feedback to improve the customer experience.
/chainingpackage <name> - Optionally record the name of a package chaining this one.
/createlayout <full path> - Download all files and associated resources to the specified location. Perform no other action. * Disabled *
/lcid - Set the display language to be used by this program, if possible. Example: /lcid 1031
/log <file | folder> - Location of the log file. Default is the process temporary folder with a name based on the package.
/msioptions - Specify options to be passed for .msi and .msp items. Example: /msioptions "PROPERTY1='Value'"
/norestart - If the operation requires a reboot to complete, Setup should neither prompt nor cause a reboot.
/passive - Shows progress bar advancing but requires no user interaction.
/showfinalerror - Passive mode only: shows final page if the install is not successful.
/pipe <name> - Optionally create a communication channel to allow a chaining package to get progress.
/promptrestart - If the operation requires a reboot to complete, Setup should prompt, and trigger it if the user agrees.
/q - Quiet mode, no user input required or output shown.
/repair - Repair the payloads.
/serialdownload - Force install operation to happen only after all the payload is downloaded.
/uninstall - Uninstall the payloads.
/parameterfolder <full path> - Specifies the path to the Setup’s configuration and data files.
/NoSetupVersionCheck - Do not check ParameterInfo.xml for setup version conflicts.
/uninstallpatch {patch code} - Removes update for all products the patch has been applied to.
/? - Display this help.

Examples:

Silently install the package and create log file SP123.htm in the temp folder: Setup /q /log %temp%\SP123.htm
Install with no user interaction unless reboot is needed to complete the operation: Setup /passive /promptrestart
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
26
Note

The above post about "Blocking Issues" when running the setup.exe from the extracted files is respectfully, incorrect. You must add an extra switch, either "/x86" or "/x64" in addition to the options you select.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
23
Command Line
We run this to install it:

dotNetFx40_Full_x86_x64.exe /q /norestart /log %temp%\dotNetFx40.log

If you run dotNetFx40_Full_x86_x64.exe /?, it will extract the setup files into a temporary directory and then display help text reproduced below. However, setup.exe can't be run directly and will just give you an error message, so the text below appears to be misleading.

---------------------------
Microsoft .NET Framework 4 Setup
---------------------------
Usage: Setup [switches]
All switches are optional.

/CEIPconsent - Optionally send anonymous feedback to improve the customer experience.
/chainingpackage <name> - Optionally record the name of a package chaining this one.
/createlayout <full path> - Download all files and associated resources to the specified location. Perform no other action. * Disabled *
/lcid - Set the display language to be used by this program, if possible. Example: /lcid 1031
/log <file | folder> - Location of the log file. Default is the process temporary folder with a name based on the package.
/msioptions - Specify options to be passed for .msi and .msp items. Example: /msioptions "PROPERTY1='Value'"
/norestart - If the operation requires a reboot to complete, Setup should neither prompt nor cause a reboot.
/passive - Shows progress bar advancing but requires no user interaction.
/showfinalerror - Passive mode only: shows final page if the install is not successful.
/pipe <name> - Optionally create a communication channel to allow a chaining package to get progress.
/promptrestart - If the operation requires a reboot to complete, Setup should prompt, and trigger it if the user agrees.
/q - Quiet mode, no user input required or output shown.
/repair - Repair the payloads.
/serialdownload - Force install operation to happen only after all the payload is downloaded.
/uninstall - Uninstall the payloads.
/parameterfolder <full path> - Specifies the path to the Setup’s configuration and data files.
/NoSetupVersionCheck - Do not check ParameterInfo.xml for setup version conflicts.
/uninstallpatch {patch code} - Removes update for all products the patch has been applied to.
/? - Display this help.

Examples:

Silently install the package and create log file SP123.htm in the temp folder: Setup /q /log %temp%\SP123.htm
Install with no user interaction unless reboot is needed to complete the operation: Setup /passive /promptrestart
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
15
Note
If you like the MSI approach:

- This example is for x86 machines, I assume you can use the same method for x64 systems (not tested)
- Please note that your system meets the right Prerequisites, like OS service pack, windows installer version, WIC .. (For Win XP SP2 you need MS Installer 3.1 + wic_x86_enu.exe)

0 - Download the full package "dotNetFx40_Full_x86_x64.exe"
1 - Use 7Zip or commandline (/x:ExtractionDestination
) to extract the "dotNetFx40_Full_x86_x64.exe" content
2 - Install in the following order:
a) RGB9Rast_x86.msi (No props needed, this package is not mandatory)
b) netfx_Core_x86.msi (See 3)
c) netfx_Extended_x86.msi (See 3)
3 - Use MST or commandline to add the following property’s:
A) "EXTUI"="1" --> making solo MSI install possible
B) "UserLanguageID"="%####%" --> Choose LANG code, example 1043 (this is not mandatory)
C) "SystemLanguageID"="%####%" --> Choose LANG code, example 1043 (this is not mandatory)
D) "REBOOT"="ReallySuppress"
E) "ROOTDRIVE"="C:\" (this is not mandatory, but best practise)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
15
Note
If you like the MSI approach:

- This example is for x86 machines, I assume you can use the same method for x64 systems (not tested)
- Please note that your system meets the right Prerequisites, like OS service pack, windows installer version, WIC .. (For Win XP SP2 you need MS Installer 3.1 + wic_x86_enu.exe)

0 - Download the full package "dotNetFx40_Full_x86_x64.exe"
1 - Use 7Zip or commandline (/x:ExtractionDestination
) to extract the "dotNetFx40_Full_x86_x64.exe" content
2 - Install in the following order:
a) RGB9Rast_x86.msi (No props needed, this package is not mandatory)
b) netfx_Core_x86.msi (See 3)
c) netfx_Extended_x86.msi (See 3)
3 - Use MST or commandline to add the following property’s:
A) "EXTUI"="1" --> making solo MSI install possible
B) "UserLanguageID"="%####%" --> Choose LANG code, example 1043 (this is not mandatory)
C) "SystemLanguageID"="%####%" --> Choose LANG code, example 1043 (this is not mandatory)
D) "REBOOT"="ReallySuppress"
E) "ROOTDRIVE"="C:\" (this is not mandatory, but best practise)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
13
Command Line

With a simple dotNetFx40_Full_x86_x64.exe /q /norestart it installs silently. The help dialog does not prompt :)

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • I used this, but it didn't seem to work until i added /x64 to it.
Please log in to comment
3
Command Line
  All switches are optional.

/CEIPconsent ‐ Optionally send anonymous feedback to improve the customer
experience.
/chainingpackage <name> ‐ Optionally record the name of a package chaining
this one.
/createlayout <full path> ‐ Download all files and associated resources to the
specified location. Perform no other action. * Disabled *
/lcid ‐ Set the display language to be used by this program, if possible. Example:
/lcid 1031
/log <file | folder> ‐ Location of the log file. Default is the process temporary
folder with a name based on the package.
/msioptions ‐ Specify options to be passed for .msi and .msp items. Example:
/msioptions "PROPERTY1='Value'"
/norestart ‐ If the operation requires a reboot to complete, Setup should neither
prompt nor cause a reboot.
/passive ‐ Shows progress bar advancing but requires no user interaction.
/showfinalerror ‐ Passive mode only: shows final page if the install is not
successful.
/pipe <name> ‐ Optionally create a communication channel to allow a chaining
package to get progress.
/promptrestart ‐ If the operation requires a reboot to complete, Setup should
prompt, and trigger it if the user agrees.
/q ‐ Quiet mode, no user input required or output shown.
/repair ‐ Repair the payloads.
/serialdownload ‐ Force install operation to happen only after all the payload is
downloaded.
/uninstall ‐ Uninstall the payloads.
/parameterfolder <full path> ‐ Specifies the path to the Setup’s configuration and
data files.
/NoSetupVersionCheck ‐ Do not check ParameterInfo.xml for setup version
conflicts.
/uninstallpatch {patch code} ‐ Removes update for all products the patch has
been applied to.
/? ‐ Display this help.

Examples:

Silently install the package and create log file SP123.htm in the temp folder:
Setup /q /log %temp%\SP123.htm
Install with no user interaction unless reboot is needed to complete the operation:
Setup /passive /promptrestart

Some command line switches are disabled for this package: create layout
(c) Microsoft Corporation. All Rights Reserved.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
2
Note
This relates to Windows XP:

If you do have only .NET 2 installed on your target machines, the package wants to install the RGB9Rast_x86.msi as it prepares the installer for later versions of .NET installations.

You may recive an error like:
"MSI (E:\073b39cc3bdd7647a3baf06ef854a959\RGB9Rast_x86.msi) Installation failed"

PerformOperation returned 1603 (translates to HRESULT = 0x80070643"
This means fatal error during installation of the RGB9Rast_x86.msi

Simply extract the RGB9Rast_x86.msi from the package and install it before the .NET 4 package like:
RGB9Rast_x86.msi /qn /norestart ALLUSERS=2
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
2
Command Line
  All switches are optional.

/CEIPconsent ‐ Optionally send anonymous feedback to improve the customer
experience.
/chainingpackage <name> ‐ Optionally record the name of a package chaining
this one.
/createlayout <full path> ‐ Download all files and associated resources to the
specified location. Perform no other action. * Disabled *
/lcid ‐ Set the display language to be used by this program, if possible. Example:
/lcid 1031
/log <file | folder> ‐ Location of the log file. Default is the process temporary
folder with a name based on the package.
/msioptions ‐ Specify options to be passed for .msi and .msp items. Example:
/msioptions "PROPERTY1='Value'"
/norestart ‐ If the operation requires a reboot to complete, Setup should neither
prompt nor cause a reboot.
/passive ‐ Shows progress bar advancing but requires no user interaction.
/showfinalerror ‐ Passive mode only: shows final page if the install is not
successful.
/pipe <name> ‐ Optionally create a communication channel to allow a chaining
package to get progress.
/promptrestart ‐ If the operation requires a reboot to complete, Setup should
prompt, and trigger it if the user agrees.
/q ‐ Quiet mode, no user input required or output shown.
/repair ‐ Repair the payloads.
/serialdownload ‐ Force install operation to happen only after all the payload is
downloaded.
/uninstall ‐ Uninstall the payloads.
/parameterfolder <full path> ‐ Specifies the path to the Setup’s configuration and
data files.
/NoSetupVersionCheck ‐ Do not check ParameterInfo.xml for setup version
conflicts.
/uninstallpatch {patch code} ‐ Removes update for all products the patch has
been applied to.
/? ‐ Display this help.

Examples:

Silently install the package and create log file SP123.htm in the temp folder:
Setup /q /log %temp%\SP123.htm
Install with no user interaction unless reboot is needed to complete the operation:
Setup /passive /promptrestart

Some command line switches are disabled for this package: create layout
(c) Microsoft Corporation. All Rights Reserved.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
2
Command Line

Doing some lab testing for ConfigMgr 2012.  I wanted to install App-V 5.0 Beta but it needed the .NET Framework 4 Full as a prereq.  So, created the .NET Framework 4 Full application with the following command line:

dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage "SCCM 2012"

Gathered info from:  http://msdn.microsoft.com/en-us/library/ee942965.aspx

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Doing some lab testing for ConfigMgr 2012. I wanted to install App-V 5.0 Beta but it needed the .NET Framework 4 Full as a prereq. So, created the .NET Framework 4 Full application with the following command line:

    dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage "SCCM 2012"

    Gathered info from: http://msdn.microsoft.com/en-us/library/ee942965.aspx
Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.
0
Note

You can deploy .NET 3.5 on Windows 8 machines by calling DISM in two ways an online option

  DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

OR a source media option

 DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Should be moved to version 3.x instead of 4.x, imho.
Please log in to comment
0
Command Line

dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT

 

Download the full package at this link -> http://www.microsoft.com/fr-fr/download/details.aspx?id=17718

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
-13
Note
With this package, you cannot extract the files out by running dotNetFx40_Full_x86_x64.exe and then looking for the setup.exe where the files were extracted. If you just run setup.exe, you'll get the following error message:

Blocking Issues:
You cannot use this setup program to install the .NET Framework.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (8)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

.NET Framework

Version

4.0.30319

Readme

http://go.microsoft.com/fwlink/?LinkId=164156

Uninstall String

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\Setup.exe /repair /x86 /parameterfolder Client C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\Setup.exe /repair /x86 /x64 /parameterfolder Client E:\Windows\Microsoft.NET\F

Questions & Answers (16)

Questions & Answers related to Microsoft .NET Framework

3
ANSWERED
0
ANSWERS
6
ANSWERS
2
ANSWERS
3
ANSWERS
2
ANSWERS
2
ANSWERS
6
ANSWERED

Blogs (4)

Blog posts related to Microsoft .NET Framework

Reviews (0)

Reviews related to Microsoft .NET Framework