In some cases, when some applications are installed together they need to be installed in a certain order. You can do this in Application Migration by adding the applications that have specific installation order constraints to the Application installation sequence.

On this page:

Introduction

In previous versions of Application Migration, the order in which applications were installed was not set. In some cases, if certain applications are installed together, they must be installed in a particular order or sequence. This requirement may also apply when multiple versions of the same application are to be installed side-by-side.

In the case where migration rules or role-based applications result in multiple versions of the same application to be installed, Application Migration will automatically install these in order of ascending version. In the case where certain different applications need to be installed in a certain order, users can now define a sequence in which applications should be installed.

For example, a new computer needs setting up with Visual Studio and .Net Framework. In previous versions of Application Migration if it attempted to install Visual Studio before .Net Framework, the installation would fail. On the Install Sequence screen, users can now define that .Net Framework should be installed before Visual Studio.

Install sequence is different from application dependency:

  • Install sequence - means that if applicable migration rules or role-based application sets result in these identified applications being installed together, they will be installed in the defined order or sequence
  • Application dependency - means that every time a certain application is installed, one or more other applications must be installed first. Application dependencies must be defined on the Application or Program in Configuration Manager, independent of Application Migration.

Install Sequence Screen

Using Install Sequence Screen

Users can add, remove or reorder applications on the install sequence screen.

Adding an application

To add an application:

  1. Click on the Add button to open the Add Application popup.
  2. On the Add Application popup, fill the Vendor, Title, Version and Edition fields then click Add to save.

    When adding an application for installation sequencing, be sure to define the Vendor, Title, Version and Edition exactly as defined in the migration rule or role-based application set that will install the application. For example, if you add 7-Zip v9.20.0.0 but have a migration rule that will install v9.20 (readable version), the sequencing will not apply to that migration rule and 7-Zip would be installed after all specifically sequenced applications.

  3. The application is added to the end of the sequence.

Adding an application

Removing an application

To remove one or more applications:

  1. Select the applications.
  2. Click Remove, a popup to confirm the removal will appear.
  3. Click Remove to remove the selected applications.

Removing an application

Move an application to the top

To move an application to the top:

  1. Select the application, for example .NET Framework.
  2. Click the Move to top button.
  3. The application will be moved to the top of the sequence.

Before moving the application:

Move an application to the top - before

After moving the application:

Move an application to the top - after

Move an application to the bottom

To move an application to the bottom:

  1. Select the application, for example .NET Framework.
  2. Click the Move to bottom button.
  3. The application will be moved to the bottom of the sequence.

Before moving the application:

Move an application to the bottom - before

After moving the application:

Move an application to the bottom - after

Move an application up one spot

To move an application up one spot:

  1. Select the application, for example .NET Framework.
  2. Click the Move up button.
  3. The application will be moved one spot up in the sequence.

Before moving the application:

Move an application up one spot - before

After moving the application:

Move an application up one spot - after

Move an application down one spot

To move an application down one spot:

  1. Select the application, for example Visual Studio.
  2. Click the Move down button.
  3. The application will be moved one spot down in the sequence.

Users can only move one application at a time. Selecting multiple applications will disable the movement buttons.

Before moving the application:

Move an application down one spot - before

After moving the application:

Move an application down one spot - after

Move an application directly to the desired spot

A user can also move an application to the desired spot by simply dragging the application.

Alternate controls for operations

All the above operations (excluding the add operation) have shortcuts on each application row. These controls are visible by hovering over the ellipses.

Alternate controls for operations

Application Ordering

When the Application Migration step is executed in a Configuration Manager Task Sequence, applications will be sorted according to the following algorithm:

  1. Applications added in the Install Sequence page are sorted in the ascending order of the install sequence.
  2. Remaining applications are sorted as follows:
    1. If any application (defined by Vendor, Title and Edition) has multiple versions to be installed and the migration rule or application set defines a full or readable version, these applications will be installed in ascending version order.
    2. Applications with colloquial versions are not sorted at all but appear after applications with full or readable versions.


To order versions in ascending order, Application Migration attempts to convert the version number defined in the target of the migration rule or role-based application set into a 10-part version number. For a version to successfully convert into a 10-part version, it should be separated by dots and each part should be a non-negative integer. There should be a minimum of 2 and a maximum of 10 parts separated by dots.


For example, if we have the following applications which are to be installed on a machine:

VendorTitleVersionVersion TypeEdition
Microsoft CorporationVisual Studio2013ColloquialProfessional
Microsoft CorporationVisual Studio2010ColloquialProfessional
Microsoft CorporationVisual Studio2015ColloquialProfessional
Microsoft CorporationVisual Studio2017ColloquialProfessional
Microsoft CorporationVisual Studio1.12.47.803FullProfessional
Microsoft CorporationVisual Studio1.11ReadableProfessional
Microsoft CorporationVisual Studioa.b.c.dFullProfessional

and we have the following applications defined in the Install Sequence:

Install SequenceVendorTitleVersionEdition
1Microsoft CorporationVisual Studio2010Professional
2Microsoft CorporationVisual Studio2013Professional

The the final order of applications will be:

VendorTitleVersionEditionComment
Microsoft CorporationVisual Studio2010ProfessionalDefined in the Install Sequence page
Microsoft CorporationVisual Studio2013ProfessionalDefined in the Install Sequence page
Microsoft CorporationVisual Studio1.11Professional1.11 converted to 10-part version is 1.11.0.0.0.0.0.0.0.0, which comes before the 10-part version 1.12.47.803.0.0.0.0.0.0
Microsoft CorporationVisual Studio1.12.47.803Professional1.12.47.803 converted to 10-part version is 1.12.47.803.0.0.0.0.0.0, which comes after the 10-part version 1.11.0.0.0.0.0.0.0.0
Microsoft CorporationVisual Studio2015ProfessionalColloquial versions are not sorted
Microsoft CorporationVisual Studio2017ProfessionalColloquial versions are not sorted
Microsoft CorporationVisual Studioa.b.c.dProfessionalConsidered as a colloquial version as a.b.c.d cannot be converted into a 10-part version

If the applications defined in the Install Sequence use a combination of Configuration Manager Applications and Package/Programs, the installations may not follow the expected order. This is because in a Task Sequence, all Configuration Manager Applications are installed in one step and all Packages are installed in a different step.

For example, if in the above example, Visual Studio 2010 was installed using a Package/Program and Visual Studio 2013 was installed using an Application, then if the Install Package step in the Task Sequence was positioned after the Install Applications, Visual Studio 2013 would be installed first (with the Install Application step) followed by Visual Studio 2010 (with the Install Package step).