Microsoft Store Import Wizard Fails for Applications Using EXE Package Format
search cancel

Microsoft Store Import Wizard Fails for Applications Using EXE Package Format

book

Article ID: 417204

calendar_today

Updated On:

Products

IT Management Suite Software Management Solution

Issue/Introduction

Microsoft Store Import Wizard Fails with "DCatFD:NotFound" Error for Applications with 14-Character Product IDs.

When attempting to import certain applications, such as Microsoft Teams or Adobe Acrobat Reader DC, using the Microsoft Store Import Wizard in Symantec IT Management Suite (ITMS) 8.8, the process fails at the Select Package stage.

The wizard displays the following error:

"ProductId [XP8... ] search error: DCatFD:NotFound: The requested resource could not be found."

This failure prevents the discovery and import of the package metadata for the specified application.

Steps to duplicate:

  1. Manage > Software
  2. Add Software button > Import Microsoft Store Package
  3. Add a search term. Tried with Teams, but other apps give the same error
  4. Highlight searched for app and click next

Environment

IT Management Suite (ITMS) 8.8

Software Management Solution 8.8

 

Cause

This is a known limitation of the Microsoft Store Import Wizard functionality in ITMS.

The root cause is as follows:

  • The wizard is primarily designed to retrieve and process MSIX/Bundle packages from the Microsoft Display Catalog API (displaycatalog.mp.microsoft.com).

  • Applications like Microsoft Teams use a 14-character Product ID (e.g., XP8BT8DW290MPQ or XPDP273C0XHQH2), which typically signifies they are EXE packages hosted externally, not standard MSIX/Bundle packages.

  • The wizard does not currently support the import of these EXE packages and cannot resolve the correct download metadata (e.g., direct download URL, silent switches) required for import.

  •  It is part of the ITMS 8.8 Release Notes:

 

Resolution

This limitation is currently under investigation by Development, with a fix tentatively targeted for the ITMS 8.8.1 Release.

Workaround

To deploy the unsupported applications, manually import the installer package directly into the Software Catalog.

This involves:

  1. Downloading the installer (EXE or MSI) directly from the vendor's official site.

    • Example:
      Microsoft Teams installer URL: https://statics.teams.cdn.office.net/production-windows-x64/1.7.00.18901/MSTeamsSetupx64.exe

  2. Creating a new Software Resource in the Symantec Management Console (Manage > Software > Software Catalog).

  3. Adding the installer file as a package to the Software Resource.

  4. Defining the correct silent installation command lines for the EXE file.

  5. Distributing the software using a Managed Software Delivery policy.

     

Reference: For a detailed step-by-step guide on performing the manual import, do the following:


Here’s how you can package and distribute apps (like Adobe Acrobat Reader DC or Microsoft Teams) using Symantec IT Management Suite (Altiris) Software Management Solution, without relying on the Microsoft Store Import Wizard.

 

Overview

You’ll be:

  1. Downloading the installer (MSI/EXE) directly from the vendor.

  2. Creating a new Software Resource in Symantec Management Console.

  3. Associating an installation command line.

  4. Distributing it using Managed Software Delivery or Quick Delivery.


Step-by-Step Guide


Step 1: Download the installer

Get the offline installer from the vendor’s official site:

Save the .exe or .msi file to a location accessible by your Symantec Notification Server (NS), e.g.:

D:\CustomFolder\Package Files\Installers\AdobeReader\

Step 2: Create a Software Resource

  1. In the Symantec Management Console, go to:
    Manage > Software > Software Catalog

  2. Click Add > Software.

  3. In the dialog:

    • Enter Name (e.g., “Adobe Acrobat Reader DC 25.001.20693”).

    • Set Company to Adobe Inc.

    • Set Version as per the installer.

  4. Click OK — this creates a new Software Resource entry.


Step 3: Add the installer as a package

  1. In the new software’s details page:

    • Go to the Package tab.

    • Click Add > Package.

  2. Choose:

    • Source: Upload or specify an existing UNC path (\\SMPServer\AltirisShare\AdobeReader\)

    • Select the .exe or .msi installer file.

  3. Save.


Step 4: Define command lines

  1. Switch to the Command Lines tab.

  2. Click Add > New command line.

  3. For Installation command line, specify something like:

    • Adobe Reader (EXE):

      e.g.:
      AcroRdrDCx64_en_US.exe /sAll /rs /rps /msi EULA_ACCEPT=YES
    • Teams (MSI):

      e.g.:
      msiexec /i Teams_windows_x64.msi ALLUSERS=1 /qn /norestart
  4. Mark this as the Default Installation command line.

  5. (Optional) Add an uninstall command line for software removal later.


Step 5: Add detection rules (optional but recommended)

Detection rules allow the Symantec Management Platform to verify that the software installation was successful before reporting the task as complete.

  1. On the Detection Rule tab,

  2. Add a file or registry check to verify install success.

  3. Example (Adobe Acrobat Reader DC):

    • Set a rule to check if the specific program file exists.

    • File Exists: C:\Program Files\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe

       

  4.  

Step 6: Distribute the software

Option A – Quick Delivery 

  1. Go to Manage > Jobs and Tasks > System Jobs and Tasks > Software > Quick Delivery.

  2. Create a new Quick Delivery Task.

  3. Select your newly created software package.

  4. Choose target computers and click Deliver software.

Option B – Managed Software Delivery 

  1. Go to Manage > Policies > Software > Managed Software Delivery.

  2. Click New Policy or select an existing one to edit.

  3. In the policy details, navigate to the Software tab and click Add > Software to select your manually created Software Resource (e.g., "Adobe Acrobat Reader DC 25.001.20693").

  4. Define the Schedule to control when the installation should run (e.g., daily check, specific date/time).

  5. Define the Target by specifying the computers or groups that should receive the software (e.g., "All Windows 11 Workstations").

  6. Save and enable the policy to activate the deployment

 

Comparison of Distribution Options

Feature Quick Delivery (Option A) Managed Software Delivery (Option B)
Purpose

Immediate deployment for testing.

Scheduled, recurring, policy-based deployment for production.

Execution

A single, one-time task.

An ongoing policy that ensures compliance.

 

 

Location

Manage > Jobs and Tasks > Software.

Manage > Policies > Software.

Additional Information

Related Microsoft Store Import Issues

For reference, you may also encounter or be interested in these other known Microsoft Store-related import issues: