App Portal 2017
You specify System Center 2007 Configuration Manager settings on the Deployment > SCCM 2007 subtab of the Settings view, which is opened by selecting Settings under Site Management on the Admin tab.
Settings > Deployment View / SCCM 2007 Tab
The SCCM 2007 subtab includes the following properties:
Property |
Description |
|||||||||
Central Site Server |
Enter the machine name of the System Center 2007 Configuration Manager Server. |
|||||||||
Central Site Database Server |
Enter the machine name where the System Center 2007 Configuration Manager Server database resides. |
|||||||||
Central Site Database Name |
Enter the database name of the System Center 2007 Configuration Manager Server database. |
|||||||||
Central Site Code |
Defines the Central Site Code (in SITE_XXX format). |
|||||||||
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.
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:
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>/ |
|||||||||
Maximum levels for Sub Collection Evaluation |
When using System Center Configuration Manager collections for conditions within App Portal, sub-collection membership can be evaluated up to the level you specify in this field. This allows you to apply an empty collection as a condition if the collection has sub-collections with the target members in those sub-collections. |
|||||||||
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. |
|||||||||
Hide sites from software publication |
To hide a specific site from software publication, select the site. |
|||||||||
Allow publication to all sites |
Select this option to allow publication to all sites. |
|||||||||
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. |
|||||||||
MDT Database Name |
If Microsoft Deployment Toolkit (MDT) is installed on the Central Administration Site (CAS) server, enter the database name here (such as MDT) 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. |
|||||||||
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. |
|||||||||
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. |
See Also
Entering System Center 2007 Configuration Manager Deployment Technology Settings
App Portal / App Broker 2017 Administration Guide18 July 2017 |
Copyright Information | Flexera Software |