Recommendations and Processes for Preinstalling Applications (Standard 7 SP1)

7/8/2014

As part of your Windows Embedded Standard 7 installation process, you will probably be installing additional applications and device drivers during Windows Setup. The following sections detail some of the methods that we recommend for preinstalling applications.

Recommendations for Preinstalling Applications

The following sections include recommendations and guidelines for preinstalling applications, based on the size and classification of your.

General Preinstallation Considerations

Review the following considerations before determining when and how you intend to install applications during an unattended installation.

• You should not preinstall your applications by using the RunSynchronous setting in the specialize configuration pass, as not all services are running during that phase of Windows Setup.

• Ensure that all application prerequisites are met. For example, many applications require the latest version of the .NET framework.

• Many application installation technologies include a "silent" option. A silent installation does not prompt a user-interface page during installation. This makes it ideal for scripted, automated, installations. In addition, some installation technologies provide macros that can automate some of the user-interface prompts during installation.

  Note

  If the application cannot be installed through a “silent” option, you should talk to the vendor who created the application. In some cases, the vendor might have two versions of an application, one that is intended for the public, and another that is intended for the OEMs, which can be installed silently.

• Applications should be written to the default user profile during the preinstallation process, due to the potential for severe issues. One such issue is overwriting the profile information, which can occur if the installation writes to a specific user profile. If you intend to install an application during the auditUser configuration pass, you should use the CopyProfile setting to replicate your changes to the default user profile.

  Note

  For more information about CopyProfile setting, see CopyProfile.

• Applications must not store Windows Installer files (.msi) in any of the %TEMP% locations of the downlevel operating system. Any Windows installer files that are stored in the %TEMP% directory, such as in the C:\Users\<USERNAME>\AppData\Local\Temp\ directory, will not be migrated during the operating system upgrade process, and might cause the application to no longer work, or to provide a suboptimal user experience.

• If an application requires changes to the Boot Configuration Data (BCD) file, it must occur after running Sysprep, during the first boot process. Sysprep automatically removes customizations made to the BCD file. Therefore, any modifications you make will be undone prior to running Sysprep during the first boot process.

• If you intend to run the Sysprep command-line tool with the /generalize option to create a reference Windows image, you must test your applications after running sysprep /generalize. You must verify that no changes occurred during the generalize process that would affect your applications. For example, verify that the drive lettering did not change, because this could affect an application that relies on a specific volume or drive to function.

  Important

  The generalize configuration pass removes system-specific information, which includes the unique security ID (SID) and other hardware-specific settings, from the image. In some cases, the generalize configuration pass can cause a preinstalled application to behave unexpectedly. For example, if you preinstall an application that grants its license to the system volume, and then you copy that image by using a file-based program, such as ImageX, the license might be removed. This would result in the application not functioning properly because creating a new system volume by copying an image would overwrite the original license.

Preinstallation Recommendations for OEMs and System Builders

Depending on your manufacturing environment, you can preinstall applications in one of two ways:

• Install applications to the reference Windows image.
  In this scenario, you install your applications to the baseline Windows image, and then capture that image to use on all of the computers in your environment. By installing applications to the reference Windows image, you can ensure that all of your computers will include the application.
• Install applications to the Windows image you intend to ship to a customer.
  In this scenario, you install your applications directly to a computer that will be shipped to a customer. This installation process enables you to customize a computer with the specific applications selected by a customer. You can also customize a computer for the specific computer model.

We recommend that OEMs and system builders preinstall applications in audit mode. In audit mode, you automatically log on as the built-in administrator account and have elevated user privileges. You can access a network, run scripts, configure applications to be installed by using the RunSynchronous commands in an answer file, and test the validity of the Windows installation. Audit mode does not require Windows Welcome settings to be applied, such as creating a user account or creating a computer name.

Preinstallation Recommendations for IT Professionals

We recommend that IT Professionals and enterprise organizations preinstall their applications while in audit mode, or after completing Windows Welcome. Completing Windows Welcome enables you to preconfigure the time-zone and language settings for your end users. Preinstalling your applications during audit mode requires an end user to configure the time-zone and language settings through the Windows Welcome process.

Preinstallation Processes

There are several ways in which you can make applications available to be installed during an unattended installation:

• In networked environments, you can create a distribution share. Distribution shares are Universal Naming Convention (UNC) paths that are located on a network drive, which can be accessed by a destination computer during Windows Setup. When you create your answer file, you must specify the UNC paths of the applications and drivers you want to install from the distribution share. The benefit of using a distribution share is that you can create a single location that includes the latest applications and driver versions. However, for this strategy to work, you must ensure that you have network connectivity with the destination computers and that you can potentially troubleshoot networking and authentication issues.

  Note

  You can save hard drive space by not copying the source files of the application to the destination computer.

• In non-networked environments, or in environments where you need only a subset of the content located on a distribution share, you can create a configuration set. A configuration set copies all of the applications and drivers referenced by a distribution share to media, such as a USB flash drive (UFD). The benefit of using a configuration set is that it is ideal for field offices, or locations that do not have access to a central server. However, you must verify that you have network adaptor driver support and you must review your application redistribution rights with the application vendor.

  Important

  To verify that your network card is supported, you must boot into the Windows Preinstallation Environment (Windows PE) 3.0, and then at the command prompt, type netcfg -v -s n to return a verbose list of the supported network cards.

• Create a data .wim file that contains all of the applications, drivers, and other resources that you want to make available on the destination computer. During unattended installation, you can configure the data .wim file to be applied to the Windows installation. However, you must review your application redistribution rights with the application vendor.

Preinstalling Device Driver Application Packages

Not all device drivers are available as individual .inf files. Some driver packages are not available outside of an application installation. In addition, some devices might require additional application support required for end users. For example, many video drivers include custom applications that provide additional functionality and capability.

We recommend that you install driver applications during audit mode. This enables you to quickly boot to the desktop, install the driver application as a RunSynchronous command, and then test the functionality of the device.