MigrationStudio provides the ability to connect to inventory systems such as SCCM, Snow, SysTrack and Nexthink. The applications detected by these systems can be nominated as in-scope, out-of-scope, or rationalised in MigrationStudio.


View the Pending applications

Applications imported from an inventory solution such as SCCM will appear in the application submissions [MW1] view within AppTracker.

  1. Change to the AppTracker screen by clicking the AppTracker tab.

  1. Click the Grid Extensions button and select App Submissions -> Switch to Pending View.

  1. The grid shows all the applications which have been detected by the inventory system. Note that the ’Num. Requests’ column shows how many people have run that application (within the timeframe set in the connector).

  1. Applications with zero users (within the timeframe set in the connector), rejected apps, and rationalised apps will not be shown by default, though these can be viewed via Grid Extensions -> App Submissions.

Options to view more applications:

  1. To view the most-used applications sort the ’Num. Requests‘ column in descending order.

 

 

How to process pending apps

 

 


 

 Candidates for Rejection

Review Candidates for rejection

MigrationStudio includes a feature that helps the administrator to identify certain applications as possible candidates for rejection. This provides a fast and easy way to mark applications commonly rejected during a migration project as out-of-scope.

  1. Change to the AppTracker screen by clicking the AppTracker tab.

  1. Click the Grid Extensions button and select[MW2]  App Submissions -> Switch to Pending View from the menu.  

  1. To automatically mark commonly rejected application, click Application Segments -> Discovery Information -> Dynamic Rationalisation -> Candidate for Rejection -> Yes from the pop-out menus.

 

  1. To review the applications that have been marked for rejection, return to the main application view by clicking Grid Extensions -> App Submissions -> All Applications. [MW3] 

 

  1. Select an application and click the Discovery Info tab beneath the main application title.  Click the Dynamic Rationalisation button on the left to review the examination results.  The users that originally had access to the application can be found in the Requested By tab.

 

A screenshot of a cell phone

Description automatically generated

  1. To add an explanation as to why you are rejecting these applications, right-click on the application and select Add Note To Applications from the context menu.  Leave a comment, for example, “Application is a candidate for rejection and has been confirmed as out-of-scope.”

  1. To reject the application, right-click on the application name and click Set Submission Status -> Rejected from the context menu.[MW4] 

  1. When all candidates for rejection have been processed remove the 'Candidate for Rejection' filter by clicking Application Segments -> Discovery Info -> Dynamic Rationalisation -> Candidate for Rejection -> <Any>[MW5] 

 

 

 

Line of business (LOB) Applications

Option 1: Multiple versions of an Application will be Rationalised to a single version

Rationalising Applications 

Where multiple versions of an application will be replaced by a single master version, this is called rationalisation.

  1. Change to the AppTracker screen.

  1. Click the Grid Extensions button and select App Submissions -> Switch to Pending View.

  1. Type the application name or vendor name in the Search Grid to find all versions of that application.

  1. Select the applications to rationalise.

 

  1. Right-click the selection and select ‘Set Submission Status -> Supersede and Rationalise’ from the context menu.

  1. You will now be prompted to choose the master version for the new environment. You may need to change the filter (top-left) to be able to find the master version. Once you have selected the application click ‘Supersede and Rationalise’.

Notes:

  • Look out for applications which have a status of ‘Accepted’ (marked in green). These applications may have been previously rationalised so take care not to create duplicate entries of accepted applications.
  • If the master version of the application doesn’t exist use the ‘Raise New Application’ button to create the new application, then select this application and click ‘Supersede and Rationalise’.

  1. The application will be moved into the Applications View. To switch to this view, click the ‘Grid Extensions’ button and select ‘App Submissions -> Switch to Applications View’ from the menu.

 

Option 2: a Single version of the Application is in scope

Accept the Application

Where an existing version of application will be carried forward to the new environment use the process below.

  1. Change to the AppTracker screen.

  1. Click the Grid Extensions button and select App Submissions -> Switch to Pending View from the menu.

  1. Type the application name or vendor name in the Search Grid to find all versions of that application. 
  2. If you find multiple versions of the application which should be replaced by a single version then use the application rationalisation process rather than this one.

 

  1. Right-click the application to be marked as in-scope and select Set Submission Status -> Accepted from the context menu.

  1. The application will be moved into the Applications View. To switch to this view click the Grid Extensions button and select App Submissions -> Switch to Applications View from the menu.

 

 

Application Upgrades


Rationalising Accepted Applications 

Where an accepted application needs to be rationalised, follow this process.

  1. Change to the AppTracker screen.

  1. Type the application name or vendor name in the Search Grid to find all versions of that application.

  1. Right-click on the application to rationalise and select Set App Superseded By from the menu.

  1. You will now be prompted to choose the replacement application. You may need to change the filter (top-left) to be able to find the replacement application. Once you have selected the application click Set Superseded By
  2. If the master version of the application doesn’t exist use the Raise New Application button to create the new application, then select this application and click Set Superseded By.

  1. You should now archive the applications which have been rationalised. Right-click on the application and select Archive from the context menu.

 

 
 
Out-of-Scope Applications

Marking applications as out-of-scope (Reject)

Where an application is not required for the migration it is deemed out-of-scope. Examples might be drivers, utilities and games. This process is also used for [MW6] core applications.

  1. Change to the AppTracker screen by clicking the AppTracker tab.

  1. Click the Grid Extensions button and choose App Submissions -> Switch to Pending View from the menu.

  1. Type the application name or vendor name in the ‘Search Grid’ to find all versions of that application. 
  2. It may be useful to use the column filters to refine the list of applications.

  1. Select the application(s) to be marked as out-of-scope (use the ‘Shift’ or ‘Control’ key to select multiple entries).

  1. Add a description as to why these applications have been rejected.  Right-click on an application and choose Add Note to Applications from the context menu. Finally, right-click on the application(s) and select Set Submission Status -> Rejected from the context menu.


 

 

Core Applications

Method 1: Simple

Accept/rationalise the core application(s) from the pending view

  1. Rationalise or accept the core applications as covered in the ’Individual User Applications‘ section.

 

 

Mark the application as “Core” 

  1. Click the Grid Extensions button and choose App Submissions -> Switch to Applications View from the menu.
  2. Double-click the application to be marked as core.
  3. Tick the Is Core App checkbox* from the ‘Misc. Info’ panel.
  4. Click the Save button to commit the changes.
  5. The core applications will be automatically linked to all users. This may take some time depending on the interval setting specified in the ‘Housekeeping Tasks’ section of ‘Initial Setup’.

 

 

 

* If this option is not visible, click the ‘Admin Settings’ icon in the top right and select ‘Applications’ from the right menu bar.  Scroll down to the ‘Misc Info’ panel at the bottom and enable the ‘Show in AppDetails’ checkbox for ‘IsCoreApp’.

 

Click the Save button to commit the changes and refresh the web browser.

 

 

 

Method 2: Advanced

Accept/rationalise the core application(s) from the pending view

  1. Rationalise or accept the core applications as covered in the ‘Individual User Applications‘ section.

 

 

Mark the application as “Core” 

  1. Click the Grid Extensions button and select App Submissions -> Switch to Applications View from the menu.
  2. Double-click the application to be marked as core.
  3. Tick the Is Core App checkbox*, found in the ‘Misc Info’ panel.
  4. Click the Save button.
  5. The core applications will be automatically linked to all users. This may take some time depending on the ‘Interval’ setting in the ‘Housekeeping Tasks’.

 

 

 

* If this option is not visible, open the ‘Admin’ section and select  Applications from the menu bar on the left. Scroll down to the ‘Misc Info’ panel and tick the Show in App Details option for ’Is Core App‘ property and refresh the web browser.

 

ADD the application to the container application 

It’s assumed that you have already setup the ’Core Applications container’. If not, see the final page for instructions

  1. Select the Core Applications container in AppTracker.

 

  1. Change to the Dependencies sub-tab.

  1. Search for the core application.

  1. Select the application from the list, ensure that ‘Pre-Rec’ is selected from the drop-down menu and click the Add Dependency button.