Part VSteps of Complex Create Task Sequence WizardScenarioThe example scenario in this topic describes the decisions made by Aaron, the lead Configuration Manager administrator at FourthCoffee. Aaron has decided to use Configuration Manager to deploy Windows 8.1 Enterprise x64 to the existing Windows devices on the FourthCoffee enterprise network. In this scenario, Aaron has already created the boot media required in order to provide new devices connectivity to the Configuration Manager environment, and will now create a task sequence to deploy the operating system for existing managed systems which are designated to be refreshed with Windows 8.1 Enterprise 64-bit.

PrerequisitesIn order for FourthCoffee to use Configuration Manager to image new systems, Aaron must have completed configuration of all items in the project requirements.

Create more advanced task sequence wizardIn order to start the job of refreshing FourthCoffee corporation systems with Windows 8.1, Aaron needs to create a task sequence more suited for existing Configuration Manager clients. Before the task sequence that is created is ready to deploy, Aaron will have some additional editing to do with the task sequence in order to add the steps required for some of the more complex scenarios he wants to implement.

NOTE: After the Create Task Sequence Wizard has completed, all properties and settings specified in the wizard can be adjusted as necessary. Simply locate the task sequence in the console and select Edit from the ribbon to change the task sequence steps as needed.

ContentsScenario..........................................................................................................................................................................................1

Prerequisites...................................................................................................................................................................................1

Create more advanced task sequence wizard................................................................................................................................1

Step 1: Create Task Sequence Wizard.............................................................................................................................................4

What It Does...........................................................................................................................................................................4

Implications............................................................................................................................................................................4

Best Practices..........................................................................................................................................................................4

Step 2: Task Sequence Information............................................................................................................................................6

What It Does...........................................................................................................................................................................6

Implications............................................................................................................................................................................6

Best Practices..........................................................................................................................................................................7

Step 3: Install Windows..............................................................................................................................................................9

What It Does...........................................................................................................................................................................9

Implications..........................................................................................................................................................................10

Best Practices........................................................................................................................................................................11

Step 4: Configure Network........................................................................................................................................................13

What It Does.........................................................................................................................................................................13

Implications..........................................................................................................................................................................14

Best Practices........................................................................................................................................................................14

Step 5: Install Configuration Manager......................................................................................................................................15

What It Does.........................................................................................................................................................................15

Implications..........................................................................................................................................................................15

Best Practices........................................................................................................................................................................16

Step 6: State Migration.............................................................................................................................................................17

What It Does.........................................................................................................................................................................17

Implications..........................................................................................................................................................................17

Best Practices........................................................................................................................................................................19

Step 7: Include Updates............................................................................................................................................................20

What It Does.........................................................................................................................................................................20

Implications..........................................................................................................................................................................20

Best Practices........................................................................................................................................................................21

Step 8: Install Applications........................................................................................................................................................22

What It Does.........................................................................................................................................................................22

Implications..........................................................................................................................................................................23

Best Practices........................................................................................................................................................................23

Step 9: Summary.......................................................................................................................................................................25

What It Does.........................................................................................................................................................................25

Implications..........................................................................................................................................................................25

Best Practices........................................................................................................................................................................25

Step 10: Completing the Wizard...............................................................................................................................................26

What It Does.........................................................................................................................................................................26

Implications..........................................................................................................................................................................26

Best Practices........................................................................................................................................................................26

Step 1: Create Task Sequence WizardThe wizard opens when the user is at the Task Sequence node and clicks Create Task Sequence from the Create group on the Home tab.

Figure 1 - Create New Task Sequence Wizard

What It DoesUsers select the type of task sequence to create. The wizard displays only the relevant pages for the selection.

ImplicationsA different type of task sequence is created by the wizard, depending on which option is selected. Each option acts as a template to create a task sequence, which can be edited later as needs evolve.

Best PracticesSelect the option that meets the requirements for the task sequence you need to create.

Install an existing image is used to create a basic task sequence. This includes options to select a pre-existing operating system image, optionally select to migrate user and system state data, install applications, etc.

Build and capture a reference operating system image is used to create a single task sequence. This allows users to install an operating system and all applications specified, and then perform an image capture of this reference operating system in order to produce an operating system image. The task sequence created here will conduct an unattended install of Windows, all specified applications, and will then generalize the operating system to prepare for an image capture, before capturing the image to a shared location of your preference.

Install and existing image package to a virtual hard disk is used to create a fully functional operating system environment inside a Virtual Hard Drive (VHD) to be used directly in Hyper-V. The VHD can be placed in a shared location to be used by System Center 2012 R2 Virtual Machine Manager.

Create a new custom task sequence is used to create a blank task sequence to be edited later for any use required by the Configuration Manager administrator.

Step 2: Task Sequence InformationEnter the task sequence name, any description of the task sequence, and the boot image associated with the task sequence.

Figure 2 - Task Sequence Information

What It DoesThe Task Sequence Information task sequence creation wizard step configures the properties of the task sequence that is displayed in the Configuration Manager console. After the wizard completes, users can right-click to see the properties of the task sequence and configure additional options.

This Task Sequence Name setting allows users to provide a name for the task sequence. This is how the task sequence is displayed in the Configuration Manager console. The Description setting is used to provide a note in context to the task sequence. The Boot image selected here is associated with the task sequence.

ImplicationsThe Task Sequence Name is a required property (which can be changed later), and is displayed in the Configuration Manager console. Names do not have to be unique in any part of the folder structure created under the Task Sequences node.

The Description setting is optional.

The Boot image selection is required. Select a boot image architecture which matches your Operating System architecture you are going to deploy.

Best PracticesThe Task Sequence Name is generally used to describe the Operating System to be deployed and the target scenario. In this case, Aaron has chosen to use the name of “FourthCoffee New Computer”. This name might not fully describe the Operating System to be deployed, however it does describe the scenario for which this task sequence should be used - new systems, or those that would be considered “bare metal”. Bare metal systems will generally not be configured with an operating system on the hard drive, and so are not capable of being used by the end user until an operating system has been installed. Specifying the processor architecture (address width) is also recommended as a part of the task sequence name in most cases. This is so that it is easy to differentiate task sequences that deliver a 32-bit operating system from one that delivers a 64-bit operating system. At this point in the wizard, since Aaron already knew he would be installing Windows 8.1 Enterprise x64 edition, he might have called the task sequence “Windows 8.1 Enterprise x64 - New Computer” in order to be more descriptive.

In the Description field, Aaron identified himself as the author of this task sequence. For easy identification of task sequence specifics, a best practice is to include contact information, the task sequence version number, which boot image is required, and possibly a link to an internal website for further documentation. Note: the description settingis limited to 127 characters. All of this documentation can be placed on an internal web site.

The Boot image selected here is associated with this task sequence. This boot image should be used in the boot media employed to start the task sequence. For example, if Aaron wants to start the imaging process by using PXE-enabled distribution points, this boot image will need to be deployable from the PXE-enabled distribution point.

Figure 3 - Data Source Tab of Boot Image Properties

Otherwise, if Aaron is using a bootable media, he will need to ensure he specifies this boot image in the boot media creation wizard.

Always ensure the task sequence boot image matches the boot image used in the boot media. If a different boot image other than the one that selected in the Task Sequence is used to create the boot media, then when the Task Sequence is started from the boot media, it will need to download the correct boot image from the nearest distribution point, stage it on the local hard drive, and then the computer will reboot into the staged boot image from the local hard drive. This is true even for

different versions/revisions of the same boot image. After ensuring the boot image from the properties of the task sequence match, the task sequence engine will begin to process the task sequence steps. This introduces a delay in task sequence execution and may confuse users and administrators.

Step 3: Install WindowsSelects which Operating System image and image index is used, which (if any) product key to use, how the device is licensed, and how to handle the local Administrator password.

Figure 4 - Install Windows

What It DoesThe Install Windows task sequence creation wizard step will configure the Apply Operating System and Apply Windows Settings task sequence steps with data in the final task sequence.

The Specify the Windows operating system image and installation information section selects which image package and image to use. WIM files can contain several indexes and when you import a WIM as an operating system image, all images inside the WIM file are incorporated. Windows 8.1 Enterprise x64 contains only a single image in the WIM, so there is only one choice to select under the Image drop-down. Click Browse to select the operating system image previously imported into Configuration Manager. Change the Image drop-down if required in order to enable the specific image that will be deployed in this task sequence.

Partition and format the target computer before installing the operating system will format the hard drives on the system according to specific conditions. Once the task sequence creation wizard has completed, the next section will examine these options more closely. This option is used here ONLY when there is no user data present on the system already.

Configure task sequence for use with BitLocker will ensure that the hard drive schema created by the task sequence when it executes is ready for BitLocker. This will create one or more additional partition(s) without assigned drive letter(s) in full Operating System depending on which hardware profile is being used.

In the Specify the licensing information for the Windows installation section, a decision about entering the product key here will be required. Options for Server licensing mode are “Do not specify”, “Per server”, and “Per seat”.

In the “Administrator password” section (this section is not named, but is simply referred to by this phrase since the radio buttons only contain options related to the local Administrator account password on the system to be imaged), the task sequence will choose to create a random complex password, or to specify a known password for the local Administrator account.

Implications Specify the Windows operating system image and installation information

Aaron has selected Windows 8.1 Enterprise en-US as the image he wants to deploy with this task sequence. This designation means that the original source media from which Aaron has copied the Install.wim source image is the Windows 8.1 Enterprise x64 version, intended for distribution through the United States in the English language. Other language packs may be added to this image as needed later in order to satisfy any regional language requirements for systems Aaron will image. This image has only a single image index contained in the Windows Image Manifest (WIM) file. Had Aaron browsed and selected a different operating system image here, such as Windows 8.1 Pro or Windows Server 2012 R2, there would several options from which to choose in the Image drop down.

Partition and format the target computer before installing the operating systemThis option adds two steps to the task sequence which prepare hard drive 0 with a partitioning scheme appropriate to the BIOS/UEFI found on the device being imaged. This option can be destructive for any volumes already present on hard drive 0. If this option and Configure task sequence for use with BitLocker are BOTH not checked, then no steps are inserted into the task sequence which partition and format the hard drive on the system. Since Aaron needs to prepare hard drives which do not already have an operating system or partition structure present, then this is the proper option to select so that the hard drive will be partitioned and formatted.

Configure task sequence for use with BitLockerIf this option is NOT selected, BitLocker steps are NOT inserted into the task sequence. The hard drive partitioning and formatting will be compatible with BitLocker if the Partition and format the target computer before installing the operating system option is enabled. BitLocker will be enabled at a later time after the operating system has been deployed, however no additional task sequence steps are added when this option is not enabled. If this options IS enabled, three steps are added to the task sequence:

o Disable BitLockerThis option executes first and only if the task sequence is started in full Operating System before any other task sequence steps are executed. In order to ensure that the volume on which Windows is installed, or another other named volume, is ready to be encrypted. This step is not executed in the typical bare metal scenario because Windows will not be installed yet.

o Pre-provision BitLockerThis step will prepare the system to use BitLocker on the specified formatted partition. This step is skipped if the system does not have a Trusted Platform Module (TPM) or if TPM is not enabled on the device.

o Enable BitLockerThis step will enable BitLocker on the selected volume in a number of modes: TPM only, Startup Key on USB only, TPM and Startup Key on USB, or TPM and PIN. You can also select whether you wish to create a recovery key in Active Directory or not, as well as selecting to wait until BitLocker has encrypted the entire volume or not before continuing. The task sequence wizard sets this as the final step in the task sequence.

Specify the licensing information for the Windows installation

For Product key, either the Multiple Activation Key (MAK) key type or standard Product ID (PID) key are valid for this field. Per default Windows can be installed without a product key. If installing an Volume-Licensed or “Enterprise” version of the operating system, a KMS key can be used here or left blank. The Volume Activation Guide has a list of KMS Client keys you can use if needed (KMS Client Setup Keys). A task sequence variable, machine variable, or collection variable are also valid to use here, so long as they contain a value equal to one of the key types.

Administrator passwordFor the Administrator password section, you can choose to allow Configuration Manager to generate a random password for the local Administrator account, or to specify your own password. A random generated password is a security best practice but can be an issue in case of troubleshooting a failed deployment, because it will be known to no one. On the other hand it is a poor security practice to assign a password which is known by the Configuration Manager Administrator and possibly others. If you use a custom password consider group policies to change the local administrator’s password after a successful deployment.

Best PracticesAaron has determined that FourthCoffee does in fact have the Key Management Service (KMS) enabled for Active Directory. Therefore, all Windows 8.1 Enterprise clients will successfully activate with this configuration. Aaron is using the best practice for the Windows Product Key setting.

By working with FourthCoffee’s Active Directory team, and reviewing Backing Up BitLocker and TPM Recovery Information to AD DS, Aaron has also determined that Active Directory at FourthCoffee can support backing up BitLocker recovery keys. Aaron wants the computing devices to be as secure as possible at FourthCoffee, so determines that devices which match specific criteria should receive BitLocker configurations. This indicates that Aaron is using the best practice for this task sequence. In order to make this process as easy as possible, Aaron selects the Configure task sequence for use with BitLocker option, so that the three steps which configure BitLocker are added to the task sequence.

The hard drive partitioning and formatting will be compatible with BitLocker if the Partition and format the target computer before installing the operating system option is enabled. Enabling this setting will add three steps to the task sequence:

o Disable BitLocker

This step executes in the task sequence immediately after the state capture steps (if state migration is enabled), in order to ensure that the volume on which Windows is installed (or another other named volume) is ready to be encrypted. This step is only executed in full Operating System and will not run in a typical bare metal scenario because Windows will not be installed yet. Disable BitLocker just suspends BitLocker and does not decrypt the drive.

o Pre-provision BitLocker

This step will prepare the computer to use BitLocker. Only the used drive space of the volume is encrypted which speeds up the end-to-end drive encryption process. This step is skipped if the computer does not have a Trusted Platform Module (TPM) or if TPM is not enabled on the device.

o Enable BitLocker

This still will enable BitLocker on the selected volume in a number of modes: TPM only, Startup Key on USB only, TPM and Startup Key on USB, or TPM and PIN. Selections are available to determine whether to create a recovery key in Active Directory, as well as selecting to wait until BitLocker has encrypted the entire volume before continuing. The task sequence wizard sets this as the final step in the task sequence.

It is a security best practice to enable the BitLocker option where the hardware supports this option. Beware, that with this option enabled, the task sequence will signal a failure on the Enable BitLocker step when executing on hardware that does not support a TPM chip. Additionally you should verify the system’s TPM chip is enabled which can be done in the Systems BIOS. Some 3rd party vendors offer tools to automate this operation. In order to use this same task sequence on hardware that supports the BitLocker functionality as well as on hardware that does not, place a condition on the Options tab of the Pre-provision BitLocker and the Enable BitLocker task sequence steps that filters out the hardware models which do not support

BitLocker. For example, add the following condition to task sequence steps in order to skip the step on systems which are Hyper-V guests:

Figure 5 - Adding Condition to Filter Virtual Machines from BitLocker configuration

For the Administrator password section, Aaron has implemented the security best practice. Using this option, a password is randomly created at runtime of the task sequence that is complex and different for each machine that has been imaged with this task sequence.

Step 4: Configure NetworkThe Configure Network task sequence creation wizard step provides the capability to determine whether the computer being imaged will remain in the named workgroup, whether it will join a domain and if so what Organizational Unit (OU) path the system account will be created inside, and which security principal will be used in order to join the domain.

.

Figure 6 - Configure Network

What It DoesThe Configure Network task sequence creation wizard step configures the workgroup or domain location configured for devices imaged with this task sequence which can be found in “Apply Network Settings” in the new created task sequence.

The radio buttons Join a workgroup and Join a domain are mutually exclusive.

If selecting Join a workgroup, the workgroup name must be provided. The name must comply with NetBIOS naming standards, and be 15 alphanumeric characters or less. Joining a workgroup does not require a security principal in order to successfully complete this action.

If selecting Join a domain, the domain name specified must be provided. The domain can be in either NetBIOS format, with a single name of 15 alpha-numeric characters or less; or, the domain can be in Fully Qualified Domain Name (FQDN) format.

The name can be entered in free-text format by user input, or click clicking the Browse button to select the proper domain from the list provided.

It is optional to specify the Domain Organizational Unity (OU) location if joining a domain. If typing in free text into this field, it must be entered manually in Active Directory Distinguished Name (DN) syntax, such as LDAP://OU=Test,DC=FourthCoffee,DC=com. Click Browse to view a tree control where you can manually select the Active Directory OU in which you wish to place the system account. When browsing and selecting the proper OU, the Domain OU path will be populated with the correct DN syntax for the object selected.

If joining a domain, a user account will need to be specified which has the domain join user right associated with it in Active Directory. To configure the domain join account, click Set, and enter the options to indicate the proper username and password. The user account must be in the DOMAIN\User format. Note that the User Principal Name (UPN, similar to Aaron@FourthCoffee.com) format is not accepted. Note: never use the container Computer in the root of your active directory domain as it is not an Organizational Unit and will cause your domain join to fail.

ImplicationsThe results from this task sequence creation wizard step will configure the Apply Network Settings task sequence step to carry out actions against the system as it is being imaged. This will either add the system account to a workgroup or to the domain specified, in the OU path specified (if any). If joining the domain, the user security principal specified will be used to add the system account to Active Directory. Note: If the Systems account already exists in your Active Directory Domain it will be reused which means Windows Setup will not move the existing object to another Organizational Unit specified.

Best PracticesAaron has determined to implement Dynamic Variables in this task sequence, and will determine the Domain OU location based on certain criteria for the systems as they execute the task sequence. Joining devices to the domain and optionally placing the device account in a specific named OU are best practices for enterprise devices. Devices added to Active Directory will be able to back up their BitLocker keys, and be subject to other group policies designed to provide security and reliability for FourthCoffee computing devices and users. This practice is examined more closely in the next section.

Step 5: Install Configuration ManagerThis step provides the path to the Configuration Manager Client installation package. Optional Installation properties can also be specified here.

Figure 7 - Install Configuration Manager Client

What It DoesThe Install the Configuration Manager client task sequence creation wizard step allows you to specify which Configuration Manager client installation package to use in order to continue the second half of the task sequence. If you want to change the associated package afterwards you can do this in the “Setup Windows and Configuration Manager” task sequence step.

ImplicationsThis step is required in order to successfully complete the task sequence. Devices will not be managed if they do not download the Configuration Manager client installation package. The task sequence will also stop executing if steps are encountered which require components of the Configuration Manager client and find that these components are not present.

Best PracticesEach Configuration Manager environment will contain at least one Configuration Manager Client Package instance. At a minimum, the best practice for this setting is to stipulate a Fallback Status Point (FSP) for your environment. In a single primary site Configuration Manager environment, this is the Primary site server if the site role is configured. In a Configuration Manager hierarchy, with a Central Administrative Site (CAS) and one or more Primary site servers, the primary site where the clients are assigned is the FSP to specify in this setting. Ensure the FQDN referenced in the setting is resolvable in DNS by the clients in potentially remote locations. Additionally it may be helpful to increase log file size and history or change the default cache size of the client. Most Client Installation properties can be used except SITECODE which is determined by the task sequence engine internally. Refer to http://technet.microsoft.com/en-us/library/gg699356.aspx for any additional client installation properties.

Step 6: State MigrationConfigure user state migration of settings and files, network settings, and Microsoft Windows settings in this step.

Figure 8 - State Migration

What It DoesThe Configure state migration task sequence creation wizard step provides options to configure user data and state migration from the old operating system to the new operating system. In addition to user data, the existing system and network settings can be migrated from the old operating system to the new operating system. The settings depicted in Figure 8 - State Migration are the default settings.

ImplicationsIf any of the three main options (each represented by a checkbox) are selected, then groups are added to the task sequence at the beginning and at the end. The group at the beginning of the task sequence will be called Capture Files and Settings. Activities that take place in this group are related to capturing user or system state data. Steps in this group only run if the current operating system is not Windows PE; that is to say, if the task sequence starts running inside a full Windows Operating System. The group at the end of the task sequence that is created when selecting the Capture user settings and files option is

called Restore User Files and Settings. Activities that take place in this group are related to restoring user state data. In either case, several task steps are added to each group.

Capture user settings and files

Selecting this option creates a group at the beginning of the task sequence that only runs in the full Windows OS. If options to capture network and Windows settings are also selected, an inner group is created with three steps:

Request User State StorageThis step allocates a secure state store on the state migration point, and indicates the intention to capture state from the computer.

Capture User Files and SettingsRuns the USMT package tool, ScanState.exe with configuration files to collect user data and application settings.

Release User State StorageReleases control of the state store on the state migration point.

Save user settings and files on a State Migration PointMutual exclusion with “local files” option. Sets options to save user profile data on state migration point.

Save user settings and files locally Mutual exclusion with “state migration point” option; enables the use of USMT for migrating user data via file copy to the state store in a local protected path. Allocates the state store on the local hard drive.

Capture locally by using links instead of by copying filesUSMT for migrating user data via local file copy to the state store in a local protected path. Allocates the state sore on the local hard drive.

Capture network settings

If this option is selected, domain/workgroup membership and network adapter settings are collected and migrated to the new operating system. If domain membership is migrated, you must specify a domain join account in the Apply Network Settings task sequence step that can be used to rejoin the CAPTURED domain. Values for what is collected are stored in task sequence variables. This step is not related to USMT and does not require User State Migration Tools to be in place.

Capture Microsoft Windows settings

If this option is selected, the computer name, registered user and user’s organization names, and time zone data are migrated to the new operating system. Values for what is collected are stored in task sequence variables. This step is not related to USMT and does not require User State Migration Tools to be in place.

Figure 9 - Capture Files and Settings Options Selected

Best PracticesConsideration should be given to the user state data: if it is present on the system, it should be migrated to the new operating system being installed on the computer. Since USMT cannot anticipate all file types and locations, it does not migrate everything. Consequently, this may require custom configuration files to match the custom application and environmental needs. What USMT migrates can be found at http://technet.microsoft.com/en-us/library/dd560792(v=ws.10).aspx. Note: System Center 2012 R2 Configuration Manager uses migapp.xml and migdocs.xml by design. In order to specify additional locations and more file types for user state data migration, read how to customize the USMT XML files at http://technet.microsoft.com/en-us/library/dd560793(v=WS.10).aspx and http://technet.microsoft.com/en-us/library/dd560778(v=ws.10).aspx for more information and guidance.

When planning user state and data migration, keep in mind that user state and files from a 32-bit operating system can migrate to a 64-bit operating system successfully. However, a user state and files from 64-bit operating system cannot successfully be migrated to a 32-bit operating system.

USMT included with the Windows Assessment and Deployment Kit (ADK) and used in System Center 2012 R2 Configuration Manager does not support any of the following Operating Systems:

Windows Server operating systems Microsoft Windows 2000 Windows XP Any of the starter editions for Windows 7, Windows Vista, or Windows XP.

In order to migrate user state and data from Windows XP directly to Windows 8.1, review the techniques described at http://blogs.technet.com/b/configmgrteam/archive/2013/09/12/how-to-migrate-user-data-from-win-xp-to-win-8-1-with-system-center-2012-r2-configmgr.aspx

Hard link user state migration is useful only for computer-refresh scenarios. Data is not moved off the local machine, and is best used when bandwidth between the computer and the state migration point is the primary concern, or if disk space on the state migration point is limited. It is the fastest option for state migration. If bandwidth is not the primary concern, the use of State Migration Points is a helpful option. Keep in mind that disk space of the State Migration Point is limited. As a best practice you might want to “Calculate Disk Space Requirements using the ScanState Tool” before migration.

Step 7: Include UpdatesConfigure options for installing software updates as a part of the task sequence deployment.

Figure 10 - Include Updates

What It DoesThe Include Updates task sequence creation wizard step determines if the resulting task sequence contains a step entitled Install Updates. If Mandatory software updates or All software updates are selected, then the Install Updates task sequence step is created near the end of the resulting task sequence. If the Do not install any software updates option is selected in this wizard step, then no Install Updates step is inserted into the task sequence for software updates.

ImplicationsThere is one main implication to this setting, which must be satisfied in order for this setting to be successful. Whether using the Mandatory software updates option, or the All software updates option, there must be a software updates deployment targeting the same collection that the Task Sequence is targeted to, so that the computer running the task sequence has an authorized updates deployment list.

Best PracticesAaron has selected the option which represents the best practice in using this setting. The task sequence step Install Updates will be created near the end of the task sequence by default. This step will install any applicable updates which have been deployed to the collection targeted by the task sequence as a part of the task sequence execution.

There are no negative consequences to configuring this step to be included in the task sequence if there are no software updates deployments targeting the collection. If a system executing a task sequence runs this task sequence step, and there are no software updates deployed to it, or there are no software updates that would be applicable for the system, then the system will perform the scan and continue to the next step. In short, it never hurts to have this step, even if there are no applicable software updates deployed for the system.

Step 8: Install ApplicationsA single Install Applications step will allow up to nine Applications and their dependencies to install as a single task sequence step.

Figure 11 - Install Applications

What It DoesThe Install Applications and Install Package task sequence steps install applications and package/programs on systems executing the task sequence. For the Install Applications step, all application requirements are evaluated at runtime in the task sequence. This differs slightly from standard application deployments, in that in a task sequence the requirement conditions are evaluated when the task sequence step is executing. Application Deployment Type dependencies are then evaluated for compliance prior to execution, and once all conditions and requirements are satisfied, the first applicable deployment type is selected and executed. Once the deployment type completes, the next application in the list is evaluated. If the optional checkbox, If an application installation fails, continue installing other applications in the list is selected, then a failing application in the middle of the list will not cause the remaining applications to be skipped in the single step. A maximum of nine applications can be used in a single Install Applications step. Use additional Install Applications steps to

increase the total amount of Applications installed. The Install Package task sequence step (not shown), by contrast, only allows a single package and program to be selected to install.

ImplicationsUsing this method, administrators can control the order in which applications are installed. For example, some applications may require a specific platform runtime be installed prior, or may share components with an application suite. In these cases, Configuration Manager Administrators will create a series of Install Applications steps so that they represent a custom installation order.

Content for all deployment types in the applications listed in the Install Applications step need to be configured to allow for completely silent installation, which does not require any user input. The application property Allow this application to be installed from the Install Application task sequence action without being deployed must also be selected so that the application can be listed in the Install Applications task sequence action.

All content for all deployment types must also be available to clients, given their location and relationship to a boundary and boundary group.

Given the capability to use dynamic application variables for the task sequence step, a large grouping of applications may be installed in sequence. Many Configuration Manager Administrators will use this method to create groups of line-of-business applications, and allow the task sequence to determine which Install Applications step to execute depending on values of task sequence variables.

Condition checks can be placed on the Options tab of the Install Applications step such that the step is skipped if the conditions are not satisfied. In a previous step, placing a condition to filter Virtual Machines was demonstrated. The same principle may apply to the use of this task sequence step: if specific conditions apply then process an application list, otherwise skip to the next task sequence step. For example: Install Applications if Variable Department has a value of “Finance”

Best PracticesFor applications that do not change often, and will get installed every single time, the best practice is to install the applications into a reference machine and then capture the image of the reference machine. Refer to http://technet.microsoft.com/en-us/library/hh397285#BKMK_CreateCaptureMedia to get started in capturing operating system images.

In cases where it is proper to control the order that applications are installed on the systems, it may be best to keep the type of application installation as a single step with multiple applications in it, as shown in Figure 11 - Install Applications. Alternatively, a single Install Applications step can be used for each application to install on devices, however, this can quickly lead to a large number of steps in the task sequence. The best practice is to group related applications together, or those that form some level of dependency, into a single step.

In any case, applications will need to be installed with task sequences. Aaron organized the applications he wanted to install in the task sequence to execute in a specific order. It is a best practice to install the Office Suite prior to additional applications like Visio or Project. Applications which share similar usage scenarios are perfect candidates to list in a “stack” in a single Install Applications step.

Figure 12 - Sample Condition for Install Applications if Department is Finance

Step 9: SummarySummary of all options selected from the Create Task Sequence Wizard steps.

Figure 13 - Summary

What It DoesThis step in the Create Task Sequence Wizard allows Configuration Manager Administrators the ability to review their selections BEFORE the task sequence is created.

ImplicationsCarefully review the options selected in prior steps of the wizard.

Best PracticesAlways review the summary text displayed during this step for correctness in order to ensure the final product is created as intended. Otherwise, complex task sequence edits may be required later to fix mistakes.

Step 10: Completing the WizardDetails are displayed which indicate the success in the overall action and the individual parts.

Figure 14 - Create Task Sequence Wizard Completed

What It DoesDisplays success/failure for each of the different steps represented by the Create Task Sequence Wizard.

ImplicationsIf any mistakes were made by the user as a part of the Create Task Sequence Wizard, they will be summarized and displayed here. If the wizard cannot successfully create the task sequence overall, or if the wizard encounters an error adding any of the configured steps to the task sequence, the error will be displayed here.

Best PracticesReview the success/failure indicators for all of the task sequence summary information displayed and take corrective action where required.