Professional Documents
Culture Documents
Microsoft .Net 3.5 Deployment Considerations
Microsoft .Net 3.5 Deployment Considerations
5
Deployment Considerations
September 28, 2012
Abstract
Disclaimer: This document is provided as-is. Information and views expressed in this document, including
URL and other Internet website references, may change without notice. Some information relates to prereleased product which may be substantially modified before its commercially released. Microsoft makes no
warranties, express or implied, with respect to the information provided here. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or
connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft
product. You may copy and use this document for your internal, reference purposes.
2012 Microsoft. All rights reserved.
Document History
Date
Chan
ge
September 28,
2012
June 13, 2012
Contents
Introduction........................................................................................ 3
Configure Features on Demand and Feature Store Repair Group
Policy............................................................................................... 3
Requirements............................................................................... 4
Servicing updates........................................................................5
Multilingual images......................................................................5
Modify an image prior to deployment.............................................5
Requirements............................................................................... 5
For an online reference image that can access Windows Update 5
For an offline reference image.....................................................6
Multilingual images......................................................................6
Use the Deployment Image Servicing and Management (DISM)
command line tool..........................................................................7
Requirements............................................................................... 7
Steps............................................................................................ 7
Enable Windows .NET Framework 3.5 using PowerShell..................7
Requirements............................................................................... 8
Steps............................................................................................ 8
Turn Windows Features on or off from Control Panel (Windows 8
only)................................................................................................ 8
Requirements............................................................................... 8
Steps............................................................................................ 9
Add feature using the Add Roles and Features Wizard (Windows
Server 2012 only)............................................................................9
Requirements............................................................................... 9
Steps............................................................................................ 9
Upgrading from Windows 7 or Windows Server 2008 R2..............10
Windows Server Update Services (WSUS) is not supported as a
source for Features on Demand or feature file store repair...........10
Summary....................................................................................... 10
Appendix A: Common Errors and Resolution Steps...........................11
Introduction
This paper provides recommendations and guidance on how to
acquire and enable .NET Framework 3.5 in Windows 8 or Windows
Server 2012. The .NET Framework 4.5 is an integral Windows
component that supports building and running the next generation
of applications and web services and is included by default in
Windows 8 and Windows Server 2012. The .NET Framework 4.5
provides a subset of managed types that you can use to create
Windows Store apps for Windows using C# or Visual Basic, for more
information see the .NET Framework Developer Center.
When a user runs a legacy application requiring .NET Framework 3.5,
the Windows 8 application compatibility feature detects this
condition (via a compatibility shim) and prompts the user to
download and install the necessary .NET Framework 3.5 files from
Windows Update using a new feature called Features on Demand
(FoD). This process requires internet access. Only the metadata
required to enable the .NET Framework 3.5 is contained in the
default Windows image (\sources\install.wim) but the actual binaries
are not in the image - this feature state is called disabled with
payload removed. The .NET Framework 3.5 payload files can only be
acquired either from Windows Update or from the installation media
in the \sources\sxs folder. For more information, see the Installing the
.NET Framework 3.5 on Demand topic on Microsoft Developers
Network (MSDN). Once the .NET Framework 3.5 feature is enabled on
a PC, the files are serviced just like other operating system files from
Windows Update.
Administrators can either enable .NET Framework 3.5 installation
using the FoD group policy or include the .NET Framework 3.5 files in
their default image. FoD allows administrators to create smaller
images and speed up initialization times. For more information see
Features on Demand topic of Windows Server Installation Options.
By default, Windows 8 automatically fixes conditions that may
prevent users from installing updates by resolving inconsistencies in
file data and/or registry. For administrators, the FoD group policy also
configures feature store repair behavior. For more information, see
Configure a Windows Repair Source topic of the Deployment Image
Servicing and Management (DISM) Reference.
Requirements
Figure 1: Group Policy Setting for Features on Demand and feature store repair
Servicing updates
Keep any repair source current with the latest servicing updates. If
you are using an image from a WIM file for Feature on Demand, you
can use the DISM tool to service the image. For more information,
see How to Mount and Modify an Image. If you are using an online
Windows installation shared on your local network as a repair image,
make sure that the computer has access to Windows Update.
Multilingual images
You must include all relevant language packs with your repair source
files for the locales that your image supports. If you restore a feature
without all localization files that the Windows installation requires for
that feature, installation fails. You can install additional language
packs after a feature is restored.
Requirements
Internet Connection
Installation media
Multilingual images
For images that will support more than one language, you must
add .NET Framework 3.5 binaries before adding any language packs.
This order ensures that .NET Framework 3.5 language resources are
installed correctly within the reference image and available to users
and applications.
Requirements
Installation media
Steps
1. Open a command prompt with administrator user rights (that
is, Run as Administrator) in Windows 8 or Windows Server
2012.
2. To install .NET Framework 3.5 from installation media located
on the D:\ drive, use the following command
Requirements
Installation media
Steps
1. Start PowerShell in the Administrator Command Prompt by
typing
September 28, 2012
2012 Microsoft. All rights reserved.
powershell
Requirements
Internet Connection
Steps
1. On the Start Screen type turn on windows features, select
Settings in the search pane and click on Turn Windows
features on or of.
2. Under Turn Windows features on or of, click .Net
Framework 3.5 (includes .NET 2.0 and 3.0)
3. The wizard will search for required files and then prompt you
to download files Windows Update.
4. Select Download files from Windows Update.
5. After the wizard completes, click Finish.
Add feature using the Add Roles and Features Wizard (Windows Server
2012 only)
Server Manager can be used to enable .NET Framework 3.5 for a
local or remote installation Windows Server 2012.
Requirements
Installation media
Steps
1. In Server Manager, click Manage, then select Add Roles
and Features to launch the Add Roles and Features Wizard.
2. Click Next at the Before you begin screen.
3. At the Select installation type screen, select Role-based or
feature-based installation and click Next.
4. On the Select destination server screen, select the target
server and click Next.
5. On the Select server roles screen, click Next.
6. On the Select features screen, check the box next to .Net
Framework 3.5 Features and click Next.
7. On the Confirm installation selections screen, a warning will be
displayed asking "Do you need to specify an alternate source
path?...". If the target machine does not have access to
Windows Update, click the Specify an alternate source path
link to specify the path to the \sources\sxs folder on the
installation media and click OK. After you have specified the
September 28, 2012
2012 Microsoft. All rights reserved.
Summary
Windows 8 and Windows Server 2012 include .NET Framework 4.5
which is required to create Windows Store apps with Visual C# or
Visual Basic. .NET Framework 3.5 is not included by default, but for
legacy application compatibility purposes can be downloaded from
Windows Update using Features on Demand. For environments
where Windows Update cannot be used as a source, IT Professionals
Windows 8 IT Pro
Windows Server 8
Name
Description
Resolution Steps
0x80
0F08
1F
CBS_E_SOURCE
_MISSING
http://go.microsoft.com
/fwlink/?LinkId=243077.
0x80
0F09
06
0x80
0F09
07
CBS_E_DOWNL
OAD_FAILURE
CBS_E_GROUPP
OLICY_DISALLO
WED
c:\mount\windows)
for an image
mounted to c:\mount.
Verify that the
computer or server
has connectivity to
Windows Update, and
that you are able to
browse to
http://update.microso
ft.com
If WSUS is used to
manage updates for
this computer, verify
that the Group Policy
setting Contact
Windows Update
directly to
download repair
content instead of
Windows Server
Update Services
(WSUS) is enabled.
Contact your network
administrator for
assistance with the
Specify settings
for optional
component
installation and
component repair
group policy.