Click to Rate and Give Feedback
MSDN
MSDN Library
Visual Studio 2008
Visual Studio
 Deployment Guide for Administrators
.NET Framework 3.5 Deployment Guide for Administrators

The Microsoft .NET Framework 3.5 offers two ways to deploy to field clients:

  • Administrator mode setup   This option enables IT administrators to deploy the .NET Framework through Microsoft Systems Management Server (SMS) or other software distribution tools. The IT administrator runs the .NET Framework setup in silent mode. If errors occur, setup quits silently and logs an error code.

  • Active Directory deployment   In this option, the administrator must add individual .msi files from the .NET Framework version 3.5 installation package into the group policy in the order in which the .msi files should be deployed. After the group policy is enabled, any clients that are part of this group policy will automatically install the components when they boot and reconnect to the network. If errors occur, setup quits silently and logs an error code.

The software referenced in this document, including without limitation, the .NET Framework 3.5 and Active Directory, are each subject to license terms and conditions. These instructions assume that such license terms and conditions have been reviewed and accepted by the appropriate licensees of the software. These instructions do not waive any of the terms and conditions of such license agreements.

For Windows XP, Windows 2000, and Windows Server 2003, Windows Installer 3.1 must be installed on the computer. You can download Windows Installer 3.1 from the Windows Installer 3.1 Redistributable page on the Microsoft Download Center Web site.

The following deployment steps apply to Windows Server 2003, Windows XP, Windows Vista, and Windows Server 2008.

Running Administrator Mode Setup

Step 1: Check the Prerequisites

Before you run this phase of administrator setup, make sure that the target computer meets the software and hardware prerequisites. Windows Installer 3.1 is a prerequisite for all installations. The following is a list of components required for the .NET Framework version 3.5. Unattended setup will fail if the prerequisites are not met.

  • On Windows Server 2003, Service Pack 1 (SP1) is required.

  • On Windows XP Home Edition and Windows XP Professional, Service Pack 2 (SP2) is required.

  • On all platforms, Microsoft Internet Explorer 6.0 Service Pack 1 is required.

Step 2: Create a Network Image

  1. Create a folder on the server, such as drive:\NETFX35.

  2. Download the .NET Framework 3.5 standalone redistributable package from the Web and save it in the folder you created in step 1. You can download the package from the Microsoft Download Center.

    This standalone redistributable package contains all the components that are needed to deploy the .NET Framework 3.5 on x86, x64, and ia64 platforms on all supporting operating systems. Language packs are not included in this package.

Step 3: Run Setup

  1. Verify that the .NET Framework 3.5 redistributable package is available on the network.

  2. In the Windows Start menu, choose Run.

  3. Type the following:

    \\computer\share\dotnetfx35.exe /q /norestart

Installation Maintenance

You can run setup again on a computer that already has an existing installation in order to access setup maintenance features. Both users and administrators should run setup from Add or Remove Programs in the Windows Control Panel. To run setup in maintenance mode, users must have administrative permissions on the target computer.

The following deployment steps apply to Windows XP (SP2), Windows Server 2003, Windows Vista, and Windows Server 2008.

Prerequisites for Deploying the .NET Framework 3.5

Network administrators must verify that all client computers have the system components required for installing the .NET Framework 3.5. Installation will fail if the prerequisites are not met.

Cc160717.alert_note(en-us,VS.90).gifNote:

You must deploy the required components in the order that they are listed. The component installation setup will fail if they are deployed in a different order. For example, the .NET Framework 2.0 Service Pack 1 requires that you install Windows Installer 3.1 first; therefore, Windows Installer is listed before the .NET Framework 2.0 Service Pack 1. The components without an asterisk (*) are located in the WCU folder of the NET Framework 3.5 setup package. For information about how to deploy these components, see How to: Deploy the .NET Framework by Using Active Directory.

The following are the prerequisites for deploying the .NET Framework 3.5 on Windows Server 2003:

  • Microsoft Windows Server 2003 Service Pack 1

  • Microsoft .NET Framework 2.0 Service Pack 1

  • Microsoft .NET Framework 3.0 Service Pack 1

  • Microsoft Core XML Services (MSXML) 6.0. To download this component, go to the Microsoft Core XML Services (MSXML) 6.0 page on the Microsoft Download Center Web site.

  • Windows Imaging Component

  • XML Paper Specification Shared Components Pack 1.0

  • Software rasterizer for the Microsoft DirectX 9.0 Software Development Kit (SDK)

The following are the prerequisites for deploying the .NET Framework 3.5 on Windows XP:

  • Microsoft Windows XP Service Pack 2

  • Microsoft Internet Explorer 6.0 Service Pack 1

  • Microsoft Windows Installer 3.1

  • Microsoft .NET Framework 2.0 Service Pack 1

  • Microsoft .NET Framework 3.0 Service Pack 1

  • Windows Imaging Component

  • XML Paper Specification Shared Components Pack 1.0

  • Software rasterizer for the Microsoft DirectX 9.0 Software Development Kit (SDK)

The following are the prerequisites for deploying the .NET Framework 3.5 on Windows Vista. Obtain these updates through Windows Update before deploying the .NET Framework 3.5.

  • Microsoft .NET Framework 2.0 Cumulative Update 1

  • Microsoft .NET Framework 3.0 Cumulative Update 1

There are no prerequisites for deploying on Windows Server 2008 or Vista Service Pack 1. The Microsoft .NET Framework 2.0 and 3.0 Cumulative Updates 1 are included in Windows Server 2008 and Vista Service Pack 1.

The above components are subject to their own license agreements.

Deploying a Component Using Active Directory

This section describes how to use Active Directory to deploy the Windows Installer setup package for a specific component across a network. To deploy components that require file extraction, you must have administrator privileges on the target computers.

Before you can deploy applications using Active Directory, you must extract individual files from the .exe redistributable package. The Windows Installer file must be extracted from the .exe file. You might need to extract additional files as well. For example, to deploy the .NET Framework 3.5 component, the vs_setup.msi file must be extracted from the .exe file to be used for deployment.

Before you deploy the .NET Framework, make sure that target computers meet the minimum configuration requirements. For details, see the Deploying & Configuring Applications page on the Microsoft .NET Framework Developer Center.

The Windows Imaging Component and the XML Paper Specification Shared Components Pack 1.0 use the Package Installer (formerly Update.exe). Update.msi is not provided for these two components. Microsoft recommends that you use the command-line option to deploy these Windows components.

The following tables show the list of components that can be deployed using Active Directory.

Table 1 Components that can be deployed using Active Directory (x86)

Component

OS

.exe or .msi file location

Directory

Component command

File extraction required

Microsoft Core XML Services (MSXML) 6.0

XP, W2K3

wcu\dotNetFramework\dotNetFX30\x86\msxml6.msi

msxml6

msiexec /qb /a msxml6.msi TARGETDIR=c:\msxml6

No

Software Rasterizer for the Microsoft DirectX 9.0 Software Development Kit (SDK)

XP, W2K3

wcu\dotNetFramework\dotNetFX30\RGB9RAST_x86.msi

rgbrast

msiexec /qb /a RGB9RAST_x86.msi REBOOT=ReallySuppress TARGETDIR=c:\RGBRAST

No

.NET Framework 2.0 SP1

XP, W2K3

wcu\dotNetFramework\dotNetFX20

the appropriate MSI and MSP

dotNetFX20

msiexec /a netfx20a_x86.msi /update ASPNET.msp;CLR.msp;CRT.msp;NetFX_CA.msp;NetFX_Core.msp;NetFX_Other.msp;PreXP.msp;WinForms.msp;DW.msp USING_EXUIH=1 REBOOT=ReallySuppress TARGETDIR=c:\dotNetFX20

No

.NET Framework 3.0 SP1

XP, W2K3

wcu\dotNetFramework\dotNetFX30

the appropriate MSI and MSP

dotNetFX30

msiexec /a netfx30a_x86.msi /update WCF.msp;WCS.msp;WF.msp;WPF1.msp;WPF2.msp;WPF_Other.msp;XPS.msp;WF_32.msp;WPF2_32.msp;WPF_Other_32.msp USING_EXUIH=1 REBOOT=ReallySuppress /l* %WORKFOLDER%\logs\netfx30_x86.log TARGETDIR=%WORKFOLDER%\AIP\NETFX30

No

.NET Framework 3.5

XP, W2K, Vista, W2K8

wcu\dotNetFramework\dotNetFX35\x86\netfx35_x86.exe

dotNetFX35

msiexec /qb /a vs_setup.msi USING_EXUIH=1 REBOOT=reallySuppress TARGETDIR=c:\dotNetFX35

Yes

Table 2 Components that can be deployed using Active Directory (x64)

Component

OS

.exe or .msi file location

Directory

Component command

Microsoft Core XML Services (MSXML) 6.0

XP, W2K3

wcu\dotNetFramework\dotNetFX30\x64\msxml6.msi

msxml6

msiexec /qb /a msxml6.msi TARGETDIR=c:\msxml6

 No

Software Rasterizer for the Microsoft DirectX 9.0 Software Development Kit (SDK)

XP, W2K3

wcu\dotNetFramework\dotNetFX30\RGB9RAST_x64.msi

rgbrast

msiexec /qb /a RGB9RAST_x64.msi REBOOT=ReallySuppress TARGETDIR=c:\RGBRAST

 No

.NET Framework 2.0 SP1

XP, W2K3

wcu\dotNetFramework\dotNetFX20

the appropriate MSI and MSP

dotNetFX20

msiexec /a Netfx20a_x64.msi /update ASPNET_64.msp;CLR_64.msp;CRT_64.msp;DW_64.msp;NetFX_Core_64.msp;NetFX_Other_64.msp;WinForms_64.msp;ASPNET.msp;CLR.msp;CRT.msp;NetFX_CA.msp;NetFX_Core.msp;NetFX_Other.msp;PreXP.msp;WinForms.msp;DW.msp USING_EXUIH=1 REBOOT=ReallySuppress TARGETDIR=c:\dotNetFX20

No

.NET Framework 3.0 SP1

XP, W2K3

wcu\dotNetFramework\dotNetFX30

the appropriate MSI and MSP

dotNetFX30

msiexec /a netfx30a_x64.msi /update WCF.msp;WCS.msp;WF.msp;WPF1.msp;WPF2.msp;WPF_Other.msp;XPS.msp;WCF_64.msp;WCS_64.msp;WF_64.msp;WPF1_64.msp;WPF2_64.msp;WPF_Other_64.msp USING_EXUIH=1 REBOOT=ReallySuppress TARGETDIR=c:\dotNetFX30

No

.NET Framework 3.5

XP, W2K, Vista, W2K8

wcu\dotNetFramework\dotNetFX35\x86\netfx35_x64.exe

dotNetFX35

msiexec /qb /a vs_setup.msi USING_EXUIH=1 REBOOT=reallySuppress TARGETDIR=c:\dotNetFX35

 Yes

You can enable logging for each component by adding /l*v logfile to the msiexec command. For example, to include a log file for the .NET Framework 3.5 component deployment, use the following command:

msiexec /qb /l*v netfx35_x86.log /a vs_setup.msi USING_EXUIH=1 REBOOT=reallySuppress TARGETDIR=c:\dotNetFX35

Step 1: Create the Administrator Install Point

Cc160717.alert_note(en-us,VS.90).gifNote:

  To see a sample script that shows how to create the install point, see the Appendix of this document.

  1. Create a folder to hold the redistributable package.

  2. Download the .NET Framework 3.5 redistributable package from the Microsoft Download Center Web site and save it in the folder that you created in step 1.

  3. Extract files from the .NET Framework 3.5 redistributable .exe file to find the component files listed below. To extract files, run the following command:

    dotnetfx35.exe /x:<ExtractionDestination>

    For example:

    dotnetfx35.exe /x:C:\NETFX35

  4. Copy the component's .exe file or .msi file to the root directory of the C:\ drive on your local computer. (For the location of components, see Table 1.)

  5. In the Windows Start menu, click Run and then type cmd to open a Command window.

  6. Change the directory to the root directory of the C: drive.

  7. Type the following command to create a directory in which to copy the .exe file:

    mkdir directoryName
    
  8. Type the corresponding component command (see Table 1) to create the install point in the directory.

  9. Close the Command window.

  10. Open Windows Explorer and navigate to C:\directoryName to verify that the files were extracted.

  11. Move the folder and all its contents to the network share that you intend to use for deployment.

Step 2: Add a Setup Package to an Active Directory Group Policy

  1. In the Windows Start menu, click All Programs, click Administrative Tools, and then click Component Services.

  2. Expand Active Directory Users and Computers.

    The Active Directory Users and Computers tree is displayed.

  3. Right-click the domain node and then click Properties.

  4. In the Properties dialog box, click the Group Policy tab.

  5. In the Group Policy Objects Links dialog box, click the Group Policy tab.

  6. If you intend to set policies that apply to computers regardless of who logs on to them, expand Computer Configuration\Software Settings.

    Cc160717.alert_note(en-us,VS.90).gifNote:

    Make sure that you map to the shared location on the Active Directory server. Otherwise, it will not let you create a package for installation.

  7. Right-click Software installation, click New, and then click Package.

  8. In the Open dialog box, browse to the location where you copied the deployment folder and then select the .msi file.

  9. In the Deploy Software dialog box, click Assigned and then click OK.

  10. Click Auto Install to install the software automatically on every computer in the domain.

  11. Click OK and then close the Component Services console.

Step 3: Set the Elevated Privileges Using Group Policy

Because most packages allow only local administrators of the computer to install the package, you should use elevated privileges to advertise the package per-computer in Group Policy. Network administrators can create policies for one user, one computer, or a group of users. For more information about how to create special policy profiles, see the System Policy Editor Help. For more information about how to configure policies, see Help in the Group Policy snap-in.

  1. In the Windows Start menu, click All Programs, click Administrative Tools, and then click Component Services.

  2. Expand Active Directory Users and Computers.

    The Active Directory Users and Computers tree is displayed.

  3. Right-click the domain node and then click Properties.

  4. In the Properties dialog box, click the Group Policy tab.

  5. In the Group Policy Objects Links box, select a Group Policy object, and then click Edit.

  6. Open the Computer Configuration\Administrative Templates\Windows Components\Windows Installer folder.

  7. In the details pane, double-click Always install with elevated privileges.

  8. In the Properties dialog box, select the Enabled option to turn the setting on, and then click OK.

  9. Open the User Configuration\Administrative Templates\Windows Components\Windows Installer folder and repeat steps 7 and 8.

    Cc160717.alert_note(en-us,VS.90).gifNote:

    You can use the System Policy Editor and Windows Installer policy to set the Always install with elevated privileges policy. You must set the policy for the computer and for each user. If you choose not to use the Group Policy Editor or the System Policy Editor, you can specify the same setting on each computer by changing a value in the Windows registry.

Step 4: Verify that the Package is Ready to be Assigned to Computers

  1. In the Component Name - English Properties dialog box, click the Deployment tab.

  2. Under Deployment type, click Assigned.

  3. Under Deployment options, select the options for when and how to deploy the component.

  4. Browse the other tabs and set options as necessary. For details, see Group Policy Help, which is available in the dialog box.

Step 5: Deploy Other Required Components

To deploy other .NET Framework 3.5 components, repeat step 1 and add the .msi and .msp files to the designated Active Directory Group Policy.

Redeploying a Package

In some cases you might want to redeploy a software package. For example, this might be required if you upgrade or modify the package.

  1. Start the Active Directory Users and Computers console. To do this, in the Windows Start menu, select Administrative Tools, and then click Active Directory Users and Computers.

  2. In the console tree, right-click the domain node and then click Properties.

  3. Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.

  4. Expand the Software Settings container that contains the software installation item that you used to deploy the package.

  5. Click the software installation container that contains the package.

  6. In the right pane of the Group Policy Object Editor, right-click the program, select All Tasks, and then click Redeploy application.

    You will see the following message:

    Redeploying this application will reinstall the application everywhere it is already installed. Do you want to continue?

  7. Click Yes.

  8. Close the Group Policy Object Editor console, click OK, and then close the Active Directory Users and Computers snap-in.

Removing a Package

You can remove a published or assigned package if it is no longer needed.

  1. Start the Active Directory Users and Computers snap-in. To do this, in the Windows Start menu, click Administrative Tools, and then click Active Directory Users and Computers.

  2. In the console tree, right-click the domain name, and then click Properties.

  3. Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.

  4. Expand the Software Settings container that contains the software installation item that you used to deploy the package.

  5. Click the software installation container that contains the package.

  6. In the right pane of the Group Policy Object Editor, right-click the program, select All Tasks, and then click Remove.

  7. Do one of the following:

    1. Click Immediately uninstall the software from users and computers, and then click OK.

    2. Click Allow users to continue to use the software, but prevent new installations, and then click OK.

  8. Close the Group Policy Object Editor console, click OK, and then close the Active Directory Users and Computers console.

For information about known installation issues, see the Microsoft .NET Framework 3.5 Release Notes.

Microsoft .NET Framework 3.5 Log File Locations

The following log files are generated during the .NET Framework 3.5 setup process:

  • dd_dotnetfx35error.txt

  • dd_dotnetfx35install.txt

For non-English installations, the following log files are also generated:

  • dd_dotnetfx35error_lp.txt

  • dd_dotnetfx35install_lp.txt

Each component in the .NET Framework also creates its own log, including the following:

  • RGB Rasterizer: dd_RGB9Rast_*.txt

  • MSXML6.0: dd_msxml6_*.txt

  • WIC: dd_wic*.txt

  • .NET Framework 2.0 SP1: dd_net_framework20*.txt

  • .NET Framework 3.0 SP1: dd_net_framework30*.txt

  • .NET Framework 3.5 MSI: dd_net_framework35*.txt

During the .NET Framework 3.5 setup process, the log files are located in the %temp% directory.

For Active Directory deployment, specify the /lv logfile option as noted in How to: Deploy the .NET Framework by Using Active Directory to create the log file for each component deployment.

Windows Installer Error Codes

For a list of error codes, see the Windows Installer Error Codes page on the MSDN Web site.

Below is a sample script that you can use to create the administrator installation point.

set WORKFOLDER=d:\deploy
set dotNetFX35build=%WORKFOLDER%\dotnetfx35.exe
echo Creating Admin Install points for NETFX3 %PROCESSOR_ARCHITECTURE%
 
REM Create folders where work will be done
md %WORKFOLDER%\ext
md %WORKFOLDER%\AIP
md %WORKFOLDER%\logs
pushd %WORKFOLDER%
 
REM Extract the files from the NETFX35 redist SFX
call dotnetfx35.exe /q /x:%WORKFOLDER%\ext

REM ------------------------------------------------------------
REM create the MSXML6 x86 admin install point
md %WORKFOLDER%\AIP\MSXML6_x86
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\x86\msxml6.msi /qb /l*v %WORKFOLDER%\logs\MSXML6_x86.log Targetdir=%WORKFOLDER%\AIP\MSXML6_x86

REM create the MSXML6 x64 admin install point
md %WORKFOLDER%\AIP\MSXML6_x64
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\x64\msxml6.msi /qb /l*v %WORKFOLDER%\logs\MSXML6_x64.log Targetdir=%WORKFOLDER%\AIP\MSXML6_x64

REM ------------------------------------------------------------
REM create the RGBRAST x86 admin install point
md %WORKFOLDER%\AIP\RGBRAST_x86
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\RGB9RAST_x86.msi /qb /l*v %WORKFOLDER%\logs\RGBRAST_x86.log REBOOT=ReallySuppress Targetdir=%WORKFOLDER%\AIP\RGBRAST_x86

REM create the RGBRAST x64 admin install point
md %WORKFOLDER%\AIP\RGBRAST_x64
call msiexec /a %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\RGB9RAST_x64.msi /qb /l*v %WORKFOLDER%\logs\RGBRAST_x64.log REBOOT=ReallySuppress Targetdir=%WORKFOLDER%\AIP\RGBRAST_x64
 
REM ------------------------------------------------------------
REM Extract NETFX 35 x86 components 
md %WORKFOLDER%\ext\netfx35_x86
call %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX35\x86\netfx35_x86.exe /q /x: %WORKFOLDER%\ext\netfx35_x86

REM Extract NETFX 35 x64 components 
md %WORKFOLDER%\ext\netfx35_x64
call %WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX35\x64\netfx35_x64.exe /q /x: %WORKFOLDER%\ext\netfx35_x64

REM ------------------------------------------------------------
REM create the NETFX35 x86 admin install point
md %WORKFOLDER%\AIP\netfx35_x86
call msiexec /qb /a %WORKFOLDER%\ext\netfx35_x86\vs_setup.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx35_x86.log TARGETDIR=%WORKFOLDER%\AIP\netfx35_x86
 
REM create the NETFX35 x64 admin install point
md %WORKFOLDER%\AIP\netfx35_x64
call msiexec /qb /a %WORKFOLDER%\ext\netfx35_x64\vs_setup.msi USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx35_x64.log TARGETDIR=%WORKFOLDER%\AIP\netfx35_x64


REM ------------------------------------------------------------
REM create the NETFX20 x86 SP1 admin install point

REM 2.0 SP1 files location
Set fx20=%WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX20\
md %WORKFOLDER%\AIP\NETFX20_x86
call msiexec /a %fx20%netfx20a_x86.msi /update %fx20%ASPNET.msp;%fx20%CLR.msp;%fx20%CRT.msp;%fx20%NetFX_CA.msp;%fx20%NetFX_Core.msp;%fx20%NetFX_Other.msp;%fx20%PreXP.msp;%fx20%WinForms.msp;%fx20%DW.msp USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx20_x86.log TARGETDIR=%WORKFOLDER%\AIP\NETFX20

REM create the NETFX20 x64 SP1 admin install point
md %WORKFOLDER%\AIP\NETFX20_x64
call msiexec /a %fx20%Netfx20a_x64.msi /update %fx20%ASPNET_64.msp;%fx20%CLR_64.msp;%fx20%CRT_64.msp;%fx20%DW_64.msp;%fx20%NetFX_Core_64.msp;%fx20%NetFX_Other_64.msp;%fx20%WinForms_64.msp;%fx20%ASPNET.msp;%fx20%CLR.msp;%fx20%CRT.msp;%fx20%NetFX_CA.msp;%fx20%NetFX_Core.msp;%fx20%NetFX_Other.msp;%fx20%PreXP.msp;%fx20%WinForms.msp;%fx20%DW.msp USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx20_x64.log TARGETDIR=%WORKFOLDER%\AIP\NETFX20_x64


REM ------------------------------------------------------------
REM create the NETFX30 SP1 x86 admin install point

REM 3.0 SP1 files location
Set fx30=%WORKFOLDER%\ext\wcu\dotNetFramework\dotNetFX30\
md %WORKFOLDER%\AIP\NETFX30_x86
call msiexec /a %fx30%netfx30a_x86.msi /update %fx30%WCF.msp;%fx30%WCS.msp;%fx30%WF.msp;%fx30%WPF1.msp;%fx30%WPF2.msp;%fx30%WPF_Other.msp;%fx30%XPS.msp;%fx30%WF_32.msp;%fx30%WPF2_32.msp;%fx30%WPF_Other_32.msp USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx30_x86.log TARGETDIR=%WORKFOLDER%\AIP\NETFX30_x64

REM create the NETFX30 SP1 x64 admin install point
md %WORKFOLDER%\AIP\NETFX30_x64
call msiexec /a %fx30%netfx30a_x64.msi /update %fx30%WCF.msp;%fx30%WCS.msp;%fx30%WF.msp;%fx30%WPF1.msp;%fx30%WPF2.msp;%fx30%WPF_Other.msp;%fx30%XPS.msp;%fx30%WCF_64.msp;%fx30%WCS_64.msp;%fx30%WF_64.msp;%fx30%WPF1_64.msp;%fx30%WPF2_64.msp;%fx30%WPF_Other_64.msp USING_EXUIH=1 REBOOT=ReallySuppress /l*v %WORKFOLDER%\logs\netfx30_x64.log TARGETDIR=%WORKFOLDER%\AIP\NETFX30_x64
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
The setup fails and the package is incomplete      mabra ... Noelle Mallory - MSFT   |   Edit   |  
This is really the plain horror. What admins need is a COMPLETE autonomous package to install without internet connection!
Poor!      GHeaver ... Thomas Lee   |   Edit   |  
This document is terrible! It doesn't work at all for group policy deployment!
Incomplete!      CesarAD ... Thomas Lee   |   Edit   |  

- I absolutely agree with Noelle: this guide doesn't explain how to avoid the installer to download anything from the internet.
- Even the complete package tries to connect to the internet to check if there's a new version of the bootstraper so, unless we are isolated from the internet, there's no way to be sure that the Framework 3.5 will be installed as expected.
- We certainly need a way to ensure that a given procedure to install the Framework will allways work in the same way. There are many scenarios where this kind of validation is a must!

See Aaron Stebners Blog      Amazone   |   Edit   |  

http://blogs.msdn.com/astebner/archive/2008/01/21/7191582.aspx

Following the hints in this blog worked for me. I was able to build an installation package with language packs which does not need an internet connection at runtime.

Tags What's this?: Add a tag
Flag as ContentBug
Am I missing something?      Rashad Rivera ... Thomas Lee   |   Edit   |  

When I run the script I keep getting "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer pachage". An ideas?

[tfl] - You are probablay better off asking this question on the MSDN Forums at http://forums.microsoft.com/msdn. You will likely get a quicker response through the forum than through the Community Content.

Flag as