App Portal 2017
After you have specified a default OS deployment technology, as described in Specifying the Default OS Deployment Technology, you need to also specify global OS deployment settings for that deployment technology on the OS Deployment tab of the Site Management > Settings > Deployment view.
OS Deployment Tab of Site Management > Settings > Deployment View
On the OS Deployment tab, you can specify the following types of global settings:
| • | Application migration—You can enable the migration of existing installed applications from the source machine to the target machine (when performing either a computer upgrade or when performing a side-by-side migration). You can also specify whether to enable the requester to either migrate all existing applications or only those that they select during checkout. |
| • | Installation of additional applications—You can select an option to enable the requester to select additional applications to install during OS deployment. |
| • | OSD site server settings—You need to provide settings specific to the default OS deployment technology that you selected, as described in Specifying the Default OS Deployment Technology. |
The OS Deployment tab includes the following properties.
|
Property |
Description |
||||||
|
Enable application migration and installation of additional applications |
Select this option to enable a requester to select existing applications to migrate during the checkout of an OSD task sequence catalog item. If this option is selected, along with the Auto detect installed apps option on the Deployment > Roles tab of the Catalog Item Properties dialog box for an OSD task sequence catalog item, the Choose Existing Applications to Migrate Panel panel of the Checkout Wizard will be displayed during the checkout of an OSD task sequence catalog item. Also, if this option is selected, applications will be listed in the Applications Included column of the roles table on the Choose Roles panel of the Checkout Wizard (which is displayed if roles are associated with a task sequence catalog item). If this option is not selected, this column will be empty; only the names of the roles will be listed. Note • This option must be selected in order to enable its sub-options: Enable requester to specify which existing applications to migrate and Prompt requester to select additional applications to install. Note • For more information, see Global vs. Catalog Item Level Settings for Migrating or Installing New Applications During OS Deployment. |
||||||
|
Enable requester to specify which existing applications to migrate |
This option is enabled if you select the Enable application migration and installation of additional applications option.
Note • To prevent an application from being listed on the Choose Existing Applications to Migrate panel, select the Core application option on the General > Global tab of the catalog item’s Catalog Item Properties dialog box. |
||||||
|
Prompt requester to select additional applications to install |
If this option is selected, the Choose Additional Applications to Install During OS Deployment Panel will be displayed in the Checkout Wizard, prompting the requester of an OSD task sequence catalog item to select additional applications to install on the target computer. Note • This option is enabled if you select the Enable application migration and installation of additional applications option. Note • To prevent an application from being listed on the Choose Additional Applications to Install During OS Deployment panel, select the Core application option on the General > Global tab of the catalog item’s Catalog Item Properties dialog box. |
||||||
|
Path to inboxes |
Specify the path to the System Center Configuration Manager In Boxes, such as: \\FLEXDCCM\sms_flx\inboxes\ This path is used to transfer the Discovery Data Record (DDR) for user and computer discovery, when the new computer is created during a “bare metal” scenario. Important • Specify the path to the same System Center Configuration Manager technology you selected in the Inventory / OS Deployment field on the Site Management > Settings > Deployment > Common tab. Note • When System Center Configuration Manager runs a discovery, it creates DDRs. The information contained in a DDR varies depending upon the discovered resource. For example, it can include the NetBIOS name of a computer, the IP address and IP subnet of a computer or device, and the computer operating system name. |
||||||
|
Default OSD site server |
Choose the System Center Configuration Manager site where new computer objects will be imported when using bare metal OS deployment. |
||||||
|
Default OSD time zone |
Enter the default time zone for new computers imported into System Center Configuration Manager as a part of an OS deployment. For example, enter -6 to indicate that the time zone is 6 hours behind Coordinated Universal Time (UTC), the world's time standard. |
||||||
|
Store OSD packages as computer variables |
If you select this option, when applications are targeted to an OS deployment, the applications will 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 select this option, you will need to obtain the applications using SQL or web service calls. |
||||||
|
Base application variable name |
This base variable will be used to deploy applications as part of the Install Applications step in a System Center Configuration Manager OSD task sequences. 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 object. The default value is COALESCEDAPPS. |
||||||
|
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 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. |
||||||
|
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:
...and so forth. |
||||||
|
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 |
You could select this option to overwrite existing resources for computer import. However, for operating system deployments, leave this option unselected. |
||||||
|
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. |
See Also
Configuring App Portal Global Settings for OS Deployment
App Portal / App Broker 2017 Administration Guide18 July 2017 |
Copyright Information | Flexera Software |