Understanding and troubleshooting the Microsoft Store for Business integration with ConfigMgr


What does this guide do?

This guide helps an administrator understand how Microsoft Store for Business is integrated with Microsoft System Center Configuration Manager(ConfigMgr), shows where critical information regarding Microsoft Store for Business can be gathered, and provides key troubleshooting tips and fixes for some of the top issues that may be encountered. 

Note: This guide does not cover implementation and usage, however if you’d like more details on these topics, the Microsoft Store for Business product documentation can be found here.

Who is it for?

This guide is for administrators charged with onborading Microsoft Store for Business as well as those responsible for diagnosing and resolving Microsoft Store for Business problems.

How does it work?

This guide provides a brief overview of the Microsoft Store for Business license types, , management features of System Center Configuration Manager that hold additional information about the operation of Microsoft Store for Business, and offers troubleshooting suggestions and resolutions for some of the most common problems encountered.

Estimated time of completion:

15-30 minutes.

The Microsoft Store for Business (MSfB) is where you can find and buy Windows apps for your organization, individually or in volume. By connecting the store to System Center Configuration Manager (ConfigMgr) , you can sync the list of apps you've bought with ConfigMgr, view them in the Configuration Manager console, and deploy them like you would any other app.

This guide explains the license types (online vs offline) of app and the management features of System Center Configuration Manager (ConfigMgr) for Microsoft Store for Business. It also helps troubleshoot common issues with Microsoft Store for Business.

Select a topic to continue:

The Microsoft Store for Business (MSfB) is where you can find and buy Windows apps for your organization, individually or in volume. By connecting the store to System Center Configuration Manager (ConfigMgr) , you can sync the list of apps you've bought with ConfigMgr, view them in the Configuration Manager console, and deploy them like you would any other app.

This guide explains the license types (online vs offline) of app and the management features of System Center Configuration Manager (ConfigMgr) for Microsoft Store for Business. It also helps troubleshoot common issues with Microsoft Store for Business.

Select a topic to continue:

After the integration configuration is completed, the administrator can view the sync status or the synchronized apps in the System Center Configuration Manager (ConfigMgr) administration console.

Check the sync status

In the System Center Configuration Manager  console, click Administration > Overview > Cloud Services >Microsoft Store for Business, and check the Last Sync Status.

View synchronized apps

In the System Center Configuration Manager console, click Administration > Overview > Cloud Services >Microsoft Store for Business, and check the License Information for Store Apps.

To troubleshoot Microsoft Store for Business issues, you need to additionally check some log files to more accurately identify the issue you encounter. To learn more about these log files and how the Microsoft Store for Business components work with each other, click the last option “Learn more about the log files”.

Select the issue you are experiencing:

 

Cause

This can occur if the configured AAD application (ClientID) does not have permissions to manage the Microsoft Store for Business for this tenant.

Workaround

  1. Browse to the MSfB web portal and log in as MSfB administrator.
  2. Navigate to Settings -> Management tools.
  3. If the application is not listed, select “Add a management tool”, then search and select the AAD application (by name) associated with the ClientID that Configuration Manager is configured to use for MSfB integration.
  4. If the status does not show “Active”, then under the “Action” column, click “Activate”.
  5. From Configuration Manager, retrigger a sync or wait for the next sync interval to occur.

Cause

This can occur if the Secret key entered in the configuration of MSfB has expired.
 

Resolution

  1. From the Azure Active Directory portal, create a new secret key for the client.
  2. In the Configuration Manager UI, navigate to Administration \ Cloud Services \ Microsoft Store for Business.
  3. Select the AAD account and go to Properties.
  4. Enter the new secret key.
  5. Verify and apply changes. 
 

Cause

This can occur if the AAD application used during configuration of Microsoft Store for Business has been deleted from AAD.


Resolution

  1. First, delete the existing AAD account for Microsoft Store for Business:
    1. Navigate to Administration \ Cloud Services \ Microsoft Store for Business.
    2. Select the existing account.
    3. Select “Delete”, then confirm.
  2. Add the new AAD account for Microsoft Store for Business with properly set up AAD application.
  3. Leave the “Microsoft Store for Business” node and return to the Enable button.
  4. Select “Add Microsoft Store for Business Account
 
 

Cause

This can occur if the configured share for syncing Microsoft Store for Business content does not exist or has incorrect permissions.
 

Workarounds

  1. If it does not already exist, create the share. To see what is configured:
    1. Go to Administration \ Cloud Services \ Microsoft Store for Business.
    2. Select Account \ “Properties”.
    3. Go to Configuration \ Location to store application content downloaded from the Microsoft Store for Business.
  2. Check permissions on the share. Note that the COMPUTER$ account where the SCP role is installed must have read and write permissions.
  3. If you wish to reconfigure the location to a new location, you must delete the AAD account and re-add it with the new content location.
 
 

Cause

This can occur if syncs are triggered less than 10 minutes apart. Sync is not allowed more frequently than every 10 minutes.
 

Resolution

Wait for 10 minutes before requesting another sync.

Cause

This can occur if the sync of other applications took so long that the content URL received is expired.
 

Workaround

Retrying the sync should continue further each time, although it may take a several retries depending on how many offline applications you have, how big the packages are, and your network speed. You should see the error fewer times each subsequent attempt. If the number of errors does not decline, something else is happening.
 

When the last sync status is failed. Check the following files for issues on the site system with the Service Connection Point installed to identify the symptom.

  • Check the <InstallDir>\Logs\MSfBSyncWorker.log for errors.
  • Check the <InstallDir>\Logs\SMS_CLOUDCONNECTION.log for status messages.

Which symptom are you experiencing?

Cause

This can occur if the application’s package is larger than 500MB. In Configuration Manager version 1610, only offline applications with packages that are less than 500MB in size are supported with automatic sync.

 

Workaround

While you cannot sync automatically, you can download the content and create the application manually:
  1. From MSfBSynWorker.log, can get the failing application ID from this log line:
     

Error(s) syncing or downloading application <ApplicationID> from the Microsoft Store for Business.

  1. Sign in as the MSfB administrator and navigate to the application page in the Microsoft Store for Business web portal for the failing application. The URL should look something like this:
    https://businessstore.microsoft.com/en-us/store/p/app/<ApplicationID>
  2. Click “Offline” if not already selected, then click the “Manage” button.
  3. For all desired platforms, create a separate folder on your application content share.
  4. Download the package to package folder.
  5. Download the encoded license file as a .bin file to the package folder.
  6. Download all required frameworks to the package folder.
  7. In the Configuration Manager admin console, navigate to Software Library \ Application Management \ Applications.
  8. Click on “Create Application”.
  9. Select “Manually specify the application information” and then click Next.
  10. Populate “General Information” and “Application Catalog” as desired.
  11. In the Deployment Types tab, create a Deployment Type for each downloaded platform (each folder in #4 above)
    1. Type: “Windows app package (*.appx, *.appxbundle”).
    2. Point to the appx/appxbundle that represents the actual package (not required dependencies). On the “Import Information” page, once you see “Import succeeded”, confirm the details. There is a line starting with “License file:” that points to the .bin file. This is required for offline license to be properly absorbed and applied on clients. Also, under “Windows app dependencies:”, verify that all of the “required dependencies” are downloaded for this package.
    3. Complete wizard, filling in properties as desired.

Cause

This can occur if the log level for MSfBSyncWorker is set incorrectly.
 

Resolution

  1. Edit \bin\x64\smsexec.exe.config.
  2. For source name=" MSfBSyncWorker ", update switchValue to a valid value.
  3. Restart sms_executive. This is required to pick up the new log level.
    Note that this will also trigger a MSfB sync.
  4. You should see the following line in MSfBSyncWorker.log:

Starting Microsoft Store for Business Sync Worker in component SMS_CLOUDCONNECTION

Cause

This can occur if the log level for BusinessAppProcessWorker is set incorrectly.

 

Resolution

  1. Edit <InstallDir>\bin\x64\smsexec.exe.config.
  2. For source name="BusinessAppProcessWorker", update switchValue to a valid value.
  3. Restart sms_executive. This is required to pick up the new log level. Note this will also trigger a MSfB sync.
  4. At this point you should no longer get the same exception in SMS_BUSINESS_APP_PROCESS_MANAGER.log.

Cause

This can occur if MSfBSyncWorker is stopped by SMS_BUSINESS_APP_PROCESS_MANAGER.
 

Workaround

  1. Restart sms_executive, or for less intrusive fix, complete #2 below.
  2. Restart both components with MSfB workers together (stop both, then start both)
    1. Open the registry and navigate to HKLM\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_CLOUDCONNECTION
    2. Set Requested Operation to Stop.
    3. Refresh to verify Current State = “Stopped”.
    4. Navigate to HKLM\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_BUSINESS_APP_PROCESS_MANAGER.
    5. Set Requested Operation to Stop.
    6. Refresh to verify Current State = “Stopped”.
    7. In SMS_CLOUDCONNECTION, set Requested Operation to Start.
    8. In SMS_BUSINESS_APP_PROCESS_MANAGER, set Requested Operation to Start .

Cause

This can occur if MSfBSyncWorker is stopped by SMS_BUSINESS_APP_PROCESS_MANAGER.
 

Workaround

  1. Restart sms_executive, or for less intrusive fix, complete #2 below.
  2. Restart both components with MSfB workers together (stop both, then start both)
    1. Open the registry and navigate to HKLM\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_CLOUDCONNECTION
    2. Set Requested Operation to Stop.
    3. Refresh to verify Current State = “Stopped”.
    4. Navigate to HKLM\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_EXECUTIVE\Threads\SMS_BUSINESS_APP_PROCESS_MANAGER.
    5. Set Requested Operation to Stop.
    6. Refresh to verify Current State = “Stopped”.
    7. In SMS_CLOUDCONNECTION, set Requested Operation to Start.
    8. In SMS_BUSINESS_APP_PROCESS_MANAGER, set Requested Operation to Start.

When you click on “Sync from Microsoft Store for Business” it does not trigger a new sync, or the sync is not occurring on daily basis, check the following files for issues to identify the specific symptom you encounter.

  • Files on the top level site server (CAS or standalone primary)
    • \<InstallDir>\bin\x64\smsexec.exe.config
    • \<InstallDir>\Logs\ BusinessAppProcessWorker.log
    • \<InstallDir>\Logs\SMS_BUSINESS_APP_PROCESS_MANAGER.log
  • Files on the site system with the Service Connection Point installed
    • \<InstallDir>\Logs\ MSfBSyncWorker.log
    • \<InstallDir>\Logs\SMS_CLOUDCONNECTION.log

 

Which symptom are you experiencing?

Cause

This can occur if the language selection is cached and is not cleared after the property values are changed.
 

Workaround

To resolve this problem, restart the SMS_Executive service.

Cause

This can occur if the Microsoft Store for Business application represented by the license information does not contain localized data for language “X”.
 

Workaround

To resolve this problem, the administrator can manually add any missing languages for created applications.

Cause

This can occur if the synced content for the offline application has been corrupted or tampered with.
 

Workaround

To resolve this problem, trigger a new sync. When the sync completes, it should have redownloaded any corrupt content files.

Cause

This can occur is the application is deployed to a client running a version of Windows prior to build 1511. Offline licensed apps from the Microsoft Store for Business are only supported on the Windows 10 November 2015 (1511) release and later.
 

Resolution

Install the latest version of Windows 10.

Congratulations! Your Microsoft Store for Business problem has been resolved. If you’d like more information regarding Microsoft Store for Business, please see the following:

For additional information regarding Microsoft Store for Business, please see the following:

 

You can also post a question in our Configuration Manager support forum, or Visit our Configuration Manager blog for all the latest news, information and tech tips.

 

 

 

Select the issue you are experiencing:

Select the issue you are experiencing:

The following diagram shows how the Microsoft Store for Business components work with each other.

Architecture

MSfBSyncWorker.log

Located on the site system with the Service Connection Point installed and check it under the installation folder: \<InstallDir>\Logs. This log file records information about the actual communication with MSfB service including metadata, icon, package and license file retrieval.

To change log level:

  1. Edit <InstallDir>\bin\x64\smsexec.exe.config
  2. For source name="MSfBSyncWorker", change switchValue.
    See valid values (case sensitive):

https://msdn.microsoft.com/en-us/library/system.diagnostics.traceeventtype(v=vs.110).aspx

  1. Restart sms_executive required to pick up new log level. Note this will also kick off MSfB sync

SMS_CLOUDCONNECTION.log

Located on the site system with the Service Connection Point installed and check it under the installation folder: \<InstallDir>\Logs. If MSfBSyncWorker appears to not be started or starting/stopping appropriately, look at this log next.  Note: This log is shared with other features.

BusinessAppProcessWorker.log

Located on the top level site server (CAS or standalone primary) and check it under the installation folder: \<InstallDir>\Logs. This log file records information about inserting the metadata information synced by BusinessAppProcessWorker into the database and processing of files in \ <InstallDir>\ inboxes\businessappprocess.box

To change log level:

  1. Edit <InstallDir>\bin\x64\smsexec.exe.config
  2. For source name=" BusinessAppProcessWorker", change switchValue. See valid values (case sensitive):

https://msdn.microsoft.com/en-us/library/system.diagnostics.traceeventtype(v=vs.110).aspx

  1. Restart sms_executive required to pick up new log level. Note this will also kick off MSfB sync

SMS_BUSINESS_APP_PROCESS_MANAGER.log

Located on the top level site server (CAS or standalone primary) and check it under the installation folder: \<InstallDir>\Logs. If BusinessAppProcessWorker appears to not be started, or it is not starting/stopping as expected, check this log.

The System Center Configuration Manager administration console provides useful management features for your Microsoft Store for Business apps.

Manage account and sync

Administration \ Overview \ Cloud Services \Microsoft Store for Business

Here you can:

  • Add, edit, or remove the Azure Active Directory account and configuration used for syncing.
  • Trigger a sync.
  • View the status and time of last sync.

View license information for business store apps

Administration \ Overview \ Cloud Services \Microsoft Store for Business \ License Information for Store Apps

Here you can:

  • View synced license information for business store apps.
  • Create Configuration Manager applications from license information.
  • View synced metadata information for each license information.

Monitor status of Microsoft Store for Business components

Monitoring \ System Status \ Component Status

Here you can:

  • View status messages from Microsoft Store for Business and its related components.

Monitor the status of Microsoft Store for Business integration with ConfigMgr

Administrator \ System Status \ Component Status

Here you can monitor the status of the following components:

  • SMS_BUSINESS_APP_PROCESS_MANAGER
  • SMS_CLOUDCONNECTION

The Microsoft Store for Business supports two types of licensed app:

  • Online This license type requires users and devices to connect to the Microsoft Store for Business to get an app and its license. It requires Windows 10 devices to be Azure AD domain-joined;
  • OfflineThis license type enables organizations to cache apps and licenses to deploy them directly within their on-premises network, without connecting to the Microsoft Store for Business or having a connection to the Internet.

 Distribution options for online-licensed apps include the ability to:

  • Assign an app to employees.
  • Add an app to your private store, allowing employees to download the app.
  • Distribute through a management tool.

You have the following distribution options for offline-licensed apps:

  • Include the app in a provisioning package, and then use it as part of imaging a device.
  • Distribute the app through a management tool.