Identifying Software That Impacts Image-based Installations

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Several types of software can affect the way you perform an image-based installation. Some applications cannot be installed and configured on a disk image; they must be installed after the disk image is copied onto a destination computer. Some applications can only be installed on portable computers and cannot be installed on desktop computers, which can force you to create separate disk images for portable and desktop computers. To determine whether your software impacts your image-based installation, identify which of the following types of software you need to install.

Core applications

Identify the core applications that you want installed on every client and server computer. For client computers, this typically includes an office productivity suite, which includes such applications as an e-mail client, a spreadsheet, and a word processor. For server computers, this typically includes tools for maintenance and operations, such as performance-monitoring applications, remote management programs, and backup programs. Virus-detection programs are also core applications because they are usually installed on all computers.

Core applications are typically installed and configured on the disk image. If there are any computers that you do not want to install core applications onto, or any computers require different configuration settings for the core applications, note this in your software inventory.

Line-of-business applications

Identify all of the line-of-business applications that are used in your organization, and identify which groups use them. Accounting programs, specialized database programs, and investment modeling programs are examples of line-of-business applications. You might want to create a separate disk image for certain groups if they use line-of-business applications that require substantial configuration or take a long time to install.

Applications that depend on Active Directory

Identify all applications that are dependent on Active Directory. These applications cannot be installed and configured on a disk image: you must install and configure these applications after the disk image is copied onto a destination computer. An application is dependent on Active Directory if it uses any data from Active Directory or writes any data to Active Directory when the application is installed or when the application is run. You do not need to identify applications that are built into the operating system, such as snap-ins, optional components, or system tools.

Third-party tools

Identify all third-party tools that are specific to a certain computer or hardware configuration. For example, many computer manufacturers have a suite of diagnostic tools that are designed for their specific computers. Likewise, portable computers commonly have a suite of hardware-specific tools that let you configure power options and other features. You might need to install these tools after the disk image is copied onto destination computers, or you might want to create a separate disk image for the computers that require these tools.

Service packs, hotfixes, and other software updates

Identify all service packs, hotfixes, and other software updates that are installed in your organization. Be sure you record the revision number and the revision date of the service pack, hotfix, or other software update.

Having this information in your software inventory makes subsequent design steps easier for you to perform. If you do not have a software inventory, or you need to update your software inventory, keep these tips in mind:

  • Be sure to allow plenty of time for preparing your software inventory. Customer data shows that you and your administrative staff might spend considerably more time identifying the software that is used in your organization than you estimate.

  • Do not rely on end-user feedback to create a software inventory. End users often do not know what programs they use, because some programs do not have a user interface and some programs start without end-user interaction.

  • Create a database for your software inventory and keep the database updated. You can use the database to plan, design, and track rollouts of service packs, hotfixes, and other software updates.