Issues specific to installing and working with Application Migration

IssuesNotesRef
Incorrect pagination when using the Greater than filterUsing the Greater than filter in the Filter Manager causes issues with the pagination for installations. 
Greater than equals and less than equals filters not working on IE and Edge.The Greater than, Equals and Less than filters do not work with Microsoft's internet Explorer and Edge.

Workaround: Use Chrome or Firefox 
 
Alignment issue with the Information icon in the Usage column

There is an alignment issue for the Information icon in the Usage Column when you use Microsoft's internet Explorer and Edge.


Workaround: Use Chrome or Firefox.

 
Excluding a product having '--' in Vendor, Title or Edition will not delete the linked migration rules

This is due to an existing bug in SLA related to handling of special characters


Workaround: All the linked migration rules need to be deleted manually.


Export to excel feature from installations view doesn't work while using Internet Explorer 11. Also, all icons don't get downloaded.

This is due to default security settings of the browser which is very strict with respect to downloads.


Workaround: Enable 'File Download' and 'Font Download' settings in IE 11 or use Chrome browser.


Role-Based Applications not installed when IncludeRoleBasedAppsForExistingPC=true but DEPLOYMENTTYPE is not explicitly set

If the DEPLOYMENTTYPE TS variable is not explicitly set, the 1E Application Migration step will set it to Refresh but does not take into account IncludeRoleBasedAppsForExistingPC being true

Workaround: Set DEPLOYMENTTYPE variable before 1E Application Migration step.


Application Migration UI still accessible in SLA Platform after uninstalling Application MigrationUninstalling Application Migration does not remove it from the SLA Platform UI. The UI will continue to function and rules etc. will remain in the database. However the APIs used in by Task Sequence step will no longer function.

Issues specific to installing and working with Task Sequence Tools

IssuesNotesRef

An error message "No HTTP resource was found.." error message is appearing in SMSTS logs when an Application Migration task sequence runs which causes the task sequence to fail.

This is an intermittent issue which is most often caused by issues in the environment. 
The first character in each logged message for a task sequence step is truncated in the smsts.log fileConfiguration Manager causes this issue to occur occasionally, it is not related to Application Migration.
The 1E Application Migration step is not saved when added to an existing OSD task sequence and clicking Apply.

When you add the Application Migration step to an existing OS Deployment task sequence and click Apply, the step is not saved and may appear with a red X symbol.


Workaround: Save the step by clicking OK instead.



 Issues specific to Tachyon 4.1 and AppMigration.

IssuesNotesRef
Desired data corresponding to newly added management group is not shown on Installation screen when 'Evaluate rules immediately' checkbox was checked during management group creation.

Tachyon portal doesn't trigger Basic Inventory Consolidation report upon adding a new management group. Instead it triggers only the 'Management Group Evaluation' report.


Workaround: Run the Basic Inventory Consolidation report manually to see the desired management group data.


When viewing Process log under Monitoring menu in Settings app the Status column doesn't refresh on its own to show the most recent status of any report being run.

This is a known intermittent issue in the portal.


Workaround: User can click the refresh icon in top right corner of the screen to view the latest status.


Application Migration repository is not visible in Settings app.

The application Migration repository gets migrated on the back-end but it is not visible on the portal.


Workaround: There is no work-around to make the Application Migration inventory visible on the portal. It is likely to be available in a future release of Tachyon.


Any schedule created for Application Migration repository in SLA v3.3 will not be visible on Tachyon portal after the upgrade.

Managing schedules for Application Migration repository is currently not supported in Tachyon portal.


Workaround: There is no work-around to make such schedules visible on the portal. Currently, Tachyon supports creating new schedules targeting only Inventory repository. Such schedules can run on regular basis which internally triggers Application Migration report also.


Excluding a product having '--' (two successive  hyphens) in Vendor, Title or Edition will not delete the migration rules linked to the product being excluded. For example, suppose you try to exclude 'M*Modal Fluency Direct -- Dermatology Recognizer' from 'MModal IP LLC'. If there are any migration rules linked to this product then their count will not be shown on the warning pop-up. Also, the linked migration rules will not get deleted when exclusion is done.

This is due to an existing bug in SLA Platform related to handling of special characters.


Workaround: All the migration rules linked to the product being excluded need to be deleted manually from 'Manage Rules' screen.


During an upgrade from SLA Platform 3.3 to Tachyon 4.1 you may see an error for the CatalogWeb web application responds check on the Post-installation checks screen.

If this is not fixed post-installaiton you will see the following symptom:

The page for non-normalised products in the inventory doesn't show product suggestions from Catalog (you navigate to this screen by clicking the Non-normalised link on the installations view).

This is due to wrong URL of Catalog website in database.


Workaround: When upgrading from an existing SLA Platform 3.3 installation, you should specify the Tachyon HTTP Port as the same port used previously by SLA Platform. If this was not done during Tachyon setup, you can fix the Catalog web URL by running the following SQL query on the SLA-Data database:

UPDATE Component SET Url = '<Correct Catalog URL>' WHERE [Name] = '1ECatalog'

For example if your 1E Catalog was installed on TACHYON.ACME.LOCAL the SQL query would be:

UPDATE Component SET Url = 'http://TACHYON.ACME.LOCAL/CatalogWeb/api/' WHERE [Name] = '1ECatalog'

The data corresponding to a newly added management group is not shown on Installation screen when 'Evaluate rules immediately' checkbox is checked during management group creation.

Tachyon portal doesn't trigger the basic inventory consolidation report upon adding the new management group. Instead, it only triggers the 'Management Group Evaluation' report.


Workaround: Run the basic inventory consolidation report manually to see the management group data.


When viewing the process log under Monitoring menu in the Settings app, the Status column doesn't refresh on its own to show the most recent status of any report being run.

This is a known intermittent issue in the portal.


Workaround: To refresh the screen you click the refresh icon in top right corner of the screen to view the latest status as shown in below screenshot:


The export to excel feature from the installations view doesn't work while using Tachyon portal on Internet Explorer 11 and shows the following error message box:

You might also notice that the icons don't get downloaded on Internet Explorer 11.

This is due to default security settings of the browser which are very strict with respect to downloads.


Workaround: To resolve this error, you need to ensure that following settings are set to Enable.


The Application Migration Consolidation report doesn't run when the Basic Inventory Consolidation report is executed. This can happen when Application Migration repository is not correctly mapped to a valid inventory repository.

This happens when the linking of Inventory repository pointed by Application Migration repository is broken for some reason. For example this can happen if the inventory repository being use by Application Migration repository is archived.


Workaround: In Tachyon v4.1 it is not possible to fix the linking from the web portal so this need to be fixed directly in the database. We need to ensure that Source IDs (SourceProjectID and SourceInstanceID) representing inventory repositoryand Destination IDs(DestinationInstanceID, DestinationProjectID) representing Application Migration repository should match in the MapProjectProject table for the inventory repository for which IsFavorite flag is 1. The mapping of a healthy association can be seen in MapProjectProject table in the screenshot below: