ConfigMgr Tab

Enter the machine name of the System Center Configuration Manager (current branch) server.

Enter the database name of the System Center Configuration Manager (current branch) server database.

By default, when creating a collection for a catalog item, App Portal uses “All System” as the limiting collection for device-based deployments. If you instead want to specify which limiting collection to use, enter a collection name in this field to set as the limiting collection ID for all device-based collections created by App Portal for device-based deployments.

Click to test the connection settings that are entered. If the test is successful, the message [SERVER_NAME] settings are valid appears.

Specify the user/computer relationship that App Portal needs to use by selecting one of the following options:

Note • When workstation verification is enabled, the user’s current computer is checked against System Center Configuration Manager to determine if this device is their primary device. Therefore, the Use SCCM last logon user is not available for workstation verification because it is not as accurate as the other methods.

If status updates for packages and task sequences are not getting updated in your environment, select this option to instruct App Portal to obtain the deployment status from an alternate view in System Center Configuration Manager.

App Portal can impersonate a client location request for content to ensure that the computer will have access to the System Center Configuration Manager content when a request is submitted. Disabling this option may cause a request to stall in “Waiting for Content” state if the content is not available for the computer. May require the registration (Regsvr32) of the smsmsgapi.dll in Web\Bin.

Specify the path to the System Center Configuration Manager in boxes. This path is used to transfer the DDR for user and computer discovery when the new computer is created during a bare metal scenario.

Choose the System Center Configuration Manager site where new computer objects will be imported to when using bare metal OS deployment.

If MDT is installed on the Central Site server, enter the database name here to obtain the list of supported MDT variables for OSD.

This base variable will be used to deploy applications as part of the Install Applications step in a System Center Configuration Manager OSD Task Sequence. It should match the value specified in the Install Applications Task Sequence step exactly. The variable name and value will be appended to the variables list of the System Center Configuration Manager Computer object. The default value is COALESCEDAPPS.

Note • You also need to select the Apply Computer Variables (Task Sequence)? option on the Deployment > Global tab of the Catalog Item Properties dialog box for a catalog item.

This setting, which works in conjunction with the Base Application Variable Name (ConfigMgr): COALESCEDAPPS, is used during OS deployment when App Portal writes applications that need to be migrated as computer variables. This value sets the number of digits used in variable names. For example:

...and so forth.

Specify the System Center Configuration Manager view to use to read the user/computer relationship. Possible values are:

Select this option to overwrite existing resources for computer import.

If this setting is selected, upon deployment failure, App Portal will remove the device from the collection.

Identifies the status IDs from System Center Configuration Manager that constitute a failed installation.

Identifies the status IDs that would cause the removal of a computer from the task sequence collections. The use case is that the computer is not removed from the collection at an early enough stage to prevent the task sequence from rerunning after the computer is rebooted.

Note • You also need to select the Remove from collection when complete? option on the Deployment > Global tab of the Catalog Properties dialog box.