Editing a Deployment

Navigation:  Managing a Site > Application Management > Deployments >

Editing a Deployment

Previous pageReturn to chapter overviewNext page

 

Overview

 

Only deployments with a "Planned" or an "Active" status can be edited. The "Edit" option is NOT available in an ongoing deployment's "Deployment Plan Details" page, meaning, a deployment with a "Started" status is NOT editable.

 

Step-by-step

 

1. To access the Deployments sub-module, click Applications button( in the Control Panel) and, in the resulting row below, click Deployment Sub Module Button.

This opens the "Deployment Plans" page.

 

Site Deployments0

 

TIP

Make sure the selected view mode displays the planned and active deployments.

 

 

2. Click the name of the deployment you want to edit (displayed in light blue).

 

Deployment Plan Details Planned Dep 2

 

3. Click Edit Button to set the page to "edit" mode.

 

Deployment Plan Details Edit Mode

 

4. If required, modify the configuration and version, the mode and "Planning Date" in the "Properties" tab (the fields marked with an asterisk are mandatory):

 

Plan Name *

Maintain or enter a new name for the deployment (minimum of 4 characters).

 

TIPRemember to avoid special characters and simply use alphabetic/numeric characters (a-z; A-Z; 0-9).

The underscore and/or dash characters are allowed. Start the deployment plan's name with an alphabetic character.

Apply to Device Group *

Maintain or select a different target device group (click the corresponding lupa button to open a "Select a Device Group" window and check another device group).

Configuration to Deploy *

Maintain or select a different configuration for deployment (click the corresponding lupa button to open a "Select a Configuration" window and check another configuration).

Version

The selected configuration's version. This field is NOT editable, it is automatically filled in once a configuration is selected.

Deployment Mode *

Maintain or select another deployment mode:

Incremental: only components present in the deployed configuration, that are not present in the device, will be implemented.

Full Install: deletes all the MCL applications/firmware and forces the installation of the components present in the deployed configuration.

 

NoteDepending on the configuration's components, the “Full Install” mode will remove/replace the corresponding components in the target device(s).

Check the following examples:

 

Configuration Component(s)

Deployment Result in the Target Device(s)

Only MCL Application(s)

Existing MCL applications are removed + MCL applications present in the configuration are deployed + existing MCL firmware and miscellaneous files are maintained.

Only MCL Firmware

Existing MCL firmware is removed + MCL firmware present in the configuration is deployed + existing MCL applications and miscellaneous files are maintained.

MCL Applications + MCL Firmware

Existing MCL applications and firmware are removed + MCL applications and firmware present in the configuration are deployed. + existing miscellaneous files are maintained.

Only Miscellaneous files (added in the configuration’s “Misc” tab)

Existing MCL applications and firmware are maintained + existing miscellaneous files are maintained + miscellaneous files present in the configuration are deployed.

 

Due to their multipurpose nature, Misc files are an exception. No matter what the selected deployment mode (“Incremental” or “Full Install”), deployed misc files are NOT removed from the target device, they are added to it.

Planning Date *

Maintain or define a different planning date:

As soon as possible:  Check this option so that the deployment starts as soon as the device contacts the account and the deployment criteria are met.

Date: Check this option and enter the intended date and time with the use of the Date button button and resulting calendar. See Scheduling a Deployment.

 

5. To save your changes, click Confirm button.