Ability to Use Existing Collections While Creating a Catalog

Currently, administrators have to maintain multiple collections created per application in ConfigMgr via App Portal during catalog creation. This can cause performance issues and collection evaluation takes more time and is expensive in terms of performance. ConfigMgr also takes time to deploy the application to a device as it runs at certain intervals, this will cause the delay in delivering the application.

With this new capability being introduced which is available only for applications created in ConfigMgr. By default, this feature is turned off and can be turned on by navigating to Admin > Settings > Deployment > ConfigMgr and selecting the Enable selection of existing collection when creating/editing a catalog option.

When this feature is enabled, the administrator will have a choice in the way catalog items are created. The administrator can either

•

Use the legacy capability where App Portal creates the collection(s) for the catalog.

-OR-

•

Choose from the list of existing device or user collections available in ConfigMgr and link it to the catalog being created.

When the second option is chosen, App Portal will use the Approve application requests for user per device capability in ConfigMgr. This feature will deploy the application immediately for a given user and device at a time. If the user has multiple devices associated, then the user will have to request the application for each device separately.

An Administrator can use the API to create catalogs using existing collections.

Prerequisites

•

Applies to Configuration Manager version 1802 or above.

•

Approve application requests for users per device feature should be turned on in Configuration Manager.

•

User/Device collections should be available in SCCM.