SCCM 2012 Tab

App Portal / App Broker for ServiceNow 2016 | Settings > Deployment

You specify System Center 2012 Configuration Manager settings on the Deployment > SCCM 2012 subtab of the Settings view, which is opened by selecting Settings under Site Management on the Admin tab.

Settings > Deployment View / SCCM 2012 Tab

The SCCM 2012 subtab includes the following properties:

Settings > Deployment View / SCCM 2012 Tab

Property

Description

Central Site Server

Enter the machine name of the System Center 2012 Configuration Manager Server.

Central Site Database Server

Enter the machine name where the System Center 2012 Configuration Manager Server database resides.

Central Site Database Name

Enter the database name of the System Center 2012 Configuration Manager Server database.

Central Site Code

Defines the Central Site Code (in SITE_XXX format).

Limiting Collection For Device

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.

Limiting Collection For User

By default, when creating a collection for a catalog item, App Portal uses “All Users as the limiting collection for user-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 user-based collections created by App Portal for user-based deployments.

Test

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

Enable workstation verification?

Enables/disables the actions in the Select verification level list. Users matching one of the specified attributes will not be required to accept the EULA.

Depending on the User / Computer relationship, this will be the last user inventoried or the most logged on user.

•

Select verification level—Tells App Portal how to handle users who visit from machines that were not originally registered with App Portal. Select one of the following options:

•

Warning—Users will be prompted with a notification that they are not using the discovered machine.

•

Disallowed—Users will not be able to visit the App Portal Storefront from other machines.

Important • This field is disabled when the User / Computer relationship field is set to Use SCCM last logon user.

User / Computer relationship

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

•

Use SCCM last logon user—The user to computer relationship will use SMS last logon user.

•

Use SCCM Primary Console Usage—Makes use of the System Center Configuration Manager / SMS SP3 feature of tracking login duration to determine primary machine usage

•

Use AD Computer Managed By—Uses the AD Computer object "Managed By" attribute to determine the primary user of the computer. This setting requires inventory of the "ManagedBy" AD attribute in System Center Configuration Manager System Discovery.

•

Use User Affinity—In System Center 2012 Configuration Manager, you can directly define the users for a computer and the computers for a user. The option could also be referred to as “Use System Center 2012 Configuration Manager user and device assignment”.

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.

Reporting Path

The full HTTP path to the System Center Configuration Manager reporting URL, including the trailing backslash. When not specified, the standard format will be used:

http://<server>/smsreporting_<site _code>/

Use v_ClassicDeploymentAssetDetails to get package deployment status

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.

Create DDRs when On Demand

Important • No longer supported.

Validate available DP for software requests

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.

Use Central Site for All Deployments

All deployments will be generated from the central site as opposed to using each primary site.

In some cases you may elect to do all your deployments from the Central Site instead of using each primary site. App Portal manages all the collections at each primary site, however if you still wish to use the Central site for all deployments select this option. Your deployment times will be subject to intra-site replication delays.

Path to Inboxes

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.

Client polling interval

Enter the client polling interval of the System Center Configuration Manager client. This value is used to calculate date and time data for email messages when explaining when a request should begin no later than.

Default OSD Site Server

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

Default OSD Time Zone

Choose the default time zone for new computers imported into System Center Configuration Manager as a part of an OS deployment.

MDT Database Name

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

Store OSD Packages as Computer Variables

When applications are targeted to an OS Deployment the applications can be stored on the computer object as variables. This allows for the MDT process to automatically install the applications without any further customizations. If you do not use this option you will need to obtain the applications using SQL or web service calls.

Base Application Variable Name (SCCM 2012)

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.

Base Package Variable Name

This base variable will be used to deploy packages as part of the Install Software step in a System Center Configuration Manager OSD task sequence. It should match the value specified in the Install Software 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 PACKAGES.

Coalesce Digits for OSD Variable (Applications)

This setting, which works in conjunction with the Base Application Variable Name (SCCM 2012): 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:

•

If this field is set to 2 and App Portal has to write three applications, then the variables App Portal would write would be COALESCEDAPPS01, COALESCEDAPPS02, COALESCEDAPPS03.

•

If this field is set to 3 and App Portal has to write three applications, then the variables App Portal would write would be COALESCEDAPPS001, COALESCEDAPPS002, COALESCEDAPPS003.

...and so forth.

Coalesce Digits for OSD Variable (Packages)

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

•

If this field is set to 2 and App Portal has to write three packages, then the variables App Portal would write would be PACKAGES01, PACKAGES02, PACKAGES03.

•

If this field is set to 3 and App Portal has to write three packages, then the variables App Portal would write would be PACKAGES001, PACKAGES002, PACKAGES003.

...and so forth.

User Computer Relationship View

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

•

v_UserMachineRelationship

•

vUsersPrimaryMachines

Use single Task Sequence for Capture and Deployment

Determines whether both the source and target computers are inserted into the same collection for side-by-side migrations.

Important • If this option is used you must properly configure your Task Sequence to perform only specific steps based on computer variable values. Failure to do so can result in the source computer being reimaged!

Overwrite existing resources for computer import

Select this option to overwrite existing resources for computer import.

Use SCCM server for machine policy refresh

When a user requests software, his machine is added to a catalog-item specific collection in System Center Configuration Manager. By default, this list only refreshes once per hour. If you select this option, System Center Configuration Manager will trigger a policy refresh on desktop machines.

Enable Collection Cleanup on Failure

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

Success Status IDs

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

Failure Status IDs

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

Program Collection Cleanup Status IDs

Identifies the status IDs from System Center Configuration Manager where App Portal should remove the machine from the collection for requests that have Enable Collection Clean-up enabled.

Task Sequence Collection Cleanup Status IDs

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.

Enable Rerun Advertisement for Status IDs

Identifies the status IDs from System Center Configuration Manager where App Portal should allow an advertisement to be rerun for requests that Enable Rerun is enabled.

SCCM 2012 Tab

App Portal / App Broker for ServiceNow 2016 Administration Guide

09 August 2016

SCCM 2012 Tab

App Portal / App Broker for ServiceNow 2016 Administration Guide

09 August 2016

App Portal / App Broker for ServiceNow 2016 Administration Guide