Using the Deployment Wizard

The Introduction page of the Deployment Wizard explains the purpose and capabilities of the wizard.

This page can be hidden during future deployments by selecting the Do not display this page in the future check box.

If this page displays, click Next to continue to the Available Endpoints/Groups Page.

When scheduling a deployment, you must choose endpoints and groups for patching.

Endpoint Notes

• You can select endpoints, groups, or a combination of the two.

  If you select endpoints or groups before initiating a deployment with the toolbar, those endpoints are preselected when you get to the Available Endpoints/Groups page.

• Endpoints are categorized by operating system. Click a link to display all the endpoints using that operating system.
• Groups are organized into a tree of custom groups, system groups, and directory service groups.
  • Use the search field to find specific groups quickly.
  • Wildcard searches are not supported.

Patch Notes

If you selected patches for deployment before opening the Deployment Wizard, there are a few things you should know:

• The Deployment Wizard only lists endpoints that the patches apply to. For example:
  • If you select a Windows 8.1 patch for deployment, only Windows 8.1 endpoints are available for deployment.
  • If you select a patch that requires other software to be installed, endpoints that do not meet the prerequisites are unlisted.
• The Deployment Wizard only lists groups that the patches apply to.
  • If the group contains one or more endpoint that the patch applies to, it's listed.
• If you are deploying a single patch that is marked Do Not Patch:
  • Available Endpoints does not list endpoints that are Do Not Patch.

• If you are deploying multiple patches, and one or more of those patches are marked Do Not Patch:

  • Available Endpoints or Available Groups marked Do Not Patch are automatically selected because the other patches selected for deployment still apply. However, the patch marked Do Not Patch does not deploy to the marked endpoints and groups.

After choosing endpoints and groups, click Next to proceed to the Available Packages Page.

Creating an Endpoint Deployment

When creating deployments, you can define deployment recipients by selecting individual endpoints, regardless of group membership.

Select endpoints as deployment recipients from the Available Endpoints/Groups page.

1. From the Available Endpoint list, select the Endpoint OS Name required.
   The list of endpoints within that operating system display.
2. Select an endpoint (or endpoints) from the list.
   The endpoint(s) are highlighted.

Endpoints are targeted as deployment recipients.

Creating a Group Deployment

You can select single groups, multiple groups, and group hierarchies as deployment recipients using the Available Groups directory tree. This method of selecting recipients lets you select multiple groups for a deployment without having to create deployments for each individual group.

Select endpoints as deployment recipients from the Available Endpoints/Groups page.

If endpoints are added to a group after a deployment is created but before the time the deployment occurs, the newly-added endpoints will receive the deployment.

From the Available Groups directory tree, select the group or groups requiring the deployment.

Selecting a parent group also selects its child hierarchy. If you do not want to deploy to a parent's child group hierarchy, cancel the deployment for the desired groups by clearing the applicable check boxes.

Groups are targeted as deployment recipients.

While completing the Deployment Wizard , packages must be selected for installation on target endpoints. These packages are selected from the Available Packages page.

When selecting packages for deployment, remember the following helpful information:

• Only vendors and packages applicable to the selected endpoint(s) display. Inapplicable content is hidden.
• If you opened the Deployment Wizard from one of the Content pages after selecting content items from the page list, those items are preselected in the wizard. Finding the packages you want to deploy is unnecessary (although you can select more packages if desired).

  If you pre-selected vulnerabilities for deployment, the Available Packages page may display more packages selected for deployment that the number of vulnerabilities you selected. This discrepancy is because a vulnerability may contain more than one package.

• An icon in the listed packages indicates if the package your want to deploy is already cached. If you already have the package cached, you can deploy it more quickly. Ivanti recommends caching packages before deployment.

After defining the Available Packages page, click Next to proceed to the Licenses Page.

For additional information of selecting packages, refer to Selecting Deployment Packages.

Selecting Deployment Packages

Selecting packages to deploy to selected endpoint remediates endpoint vulnerabilities.

Select packages for deployment from the Available Packages page.

1. Select the Vendor link containing the package(s) you want to deploy.
   A list of the vendor's packages for the selected deployment recipients opens.
2. Select the package(s) needed.
   The packages are selected.
3. [Optional] Repeat the selection process for additional vendors.
4. [Optional] Click a Package Name link to open the Associated Vulnerability Analysis page. For additional information, refer to Associated Vulnerability Analysis Page.
5. Click Next to proceed to the Licenses page.
   When using the Deployment Wizard, the wizard will not necessarily install service packs first. Verify that all relevant service packs have deployed successfully before creating deployments using the Deployment Wizard.

Associated Vulnerability Analysis Page

This page lists the package status for each endpoint that it applies to (not just the endpoints included in the deployment). Viewing this page is useful to estimate how many of your selected endpoints will not receive the deployment package due to patch status (for example, the patch does not apply to the endpoint).

The following table describes the page columns.

Name	Description
Endpoint Name	The endpoint that the package applies to.
Platform Info	The operating system that the endpoint is using.
Status	The patch status of the package for the endpoint. Values include: Patched Not Patched Not Applicable Do Not Patch

When finished viewing the page, click Back to return to the Available Packages Page.

To continue configuration of your deployment, you must first accept the vendor license agreement(s).

The number of different license agreements that appear depend upon how many packages you selected to install. For example, you selected four different packages for installation and these packages were created by three different vendors, you would have to agree to three different license agreements.

For additional information on accepting license agreements, refer to Accepting License Agreements.

After accepting licenses, click Next to proceed to the Deployment Information Page.

Accepting License Agreements

To continue configuration of your deployment, you must first accept the vendor license agreement(s).

Accept licenses from the Licenses Page .

1. Review the agreement.
2. If you accept the agreement, select the I ACCEPT the terms and conditions of this end user license agreement option.
3. If there are multiple agreements, repeat the previous steps. All agreements must be accepted before continuing.
4. [Optional] Click Next to proceed to the Deployment Information page.

You can control the user notification options associated with a deployment using the Deployment Information page. You can set the deployment job name, start time, manner, and add notes.

The following information may be useful when completing this page:

• Job and task names will later be used to identify deployment results.
• Deploying using Agent Local Time is useful in geographically dispersed networks. This deployment method helps ensure deployments complete off peak business hours.
• Deploying using UTC time is useful when you want to deploy content at one specific time.
• Concurrent deployments ensure endpoint receive packages near simultaneously, but may consume excessive network bandwidth.
• Consecutive deployments reduces network bandwidth consumption, but endpoints may receive deployment at different times.

After defining deployment information, click Next to proceed to the Package Deployment Order and Behavior Page.

Configuring Deployment Information

The deployment information contains controls for naming and configuring your deployment. You can use this page to choose a start time and the manner in which it deploys.

Configure deployment information from the Deployment Information page.

1. [Optional] Edit the Job name and Task name fields.

   Field	Description
   Job name	The name of the job. By default, jobs are named Remediation, followed by the date and time at the time of deployment creation.
   Task name	The task name for the job. Use this name to describe the purpose of the deployment. By default, tasks are named Deployment of {Package Name}.

Upon completion of the Deployment Wizard, use the Job name and Task name to identify your deployment. The Job name displays on the Deployment and Tasks page, and the Task name displays when you expand your deployment. Use the Start time options to configure the deployment start time and start date. You can also use these options to schedule a recurring deployment or select deployment time zone options.

2. [Optional] Schedule the deployment Start Time, which is the date and time that the deployment begins. Edit the Start time by clicking Change. By default, the Start time is set to the date and time the Deployment Wizard was opened.
   For additional information on start times and configuring recurring deployments, refer to Schedule Configuration Page.
3. Select the desired Deployment time zone option.
   Use this option to configure which time zone setting is used to trigger a deployment. The following table defines the options.

   Option	Description
   Agent Local Time	The deployment begins according to the local time zone on each endpoint.
   Agent UTC Time	The deployment begins according to UTC (coordinated universal time) on each endpoint.

   If you deploy to a group using Agent Local Time, the deployment remains in progress until all time zones have passed. This behavior ensures any endpoints added to the group following deployment start also receive content. This behavior does not occur when using Agent UTC Time.

Use the Manner options to configure how endpoints receive the deployment in relation to one another. The Manner options also include:

• A feature to disable the entire deployment should deployment to an individual endpoint fail.
• A feature to redeploy packages to an endpoint, even if the package has been previously installed.
4. Select a Manner deployment option.
   The following table describes each manner deployment option and how to use them.

Option	Description and Instructions
Concurrent	This option deploys the package(s) to a defined number of endpoints simultaneously. New deployments are distributed when agents report back after completing the previous deployment. If an endpoint takes longer than four hours to complete the deployment, it is no longer counted against the concurrent deployment limit. To deploy to endpoints concurrently, complete the following steps: Select the Concurrent option. Type a number in the Deploy to <x> nodes at a time field.
Consecutive	This option deploys the packages simultaneously to all endpoints. However, the global deployment limit will always take precedence over the defined distribution options defined. To deploy to endpoints consecutively, select the Consecutive option.

5. [Optional] Define the remaining Manner options. Enable or disabled the options by selecting or clear each option check box.
   The following table describes the remaining Manner options.

Option	Description
Suspend the deployment of this package if it fails to deploy to one or more nodes.	This option suspends all subsequent deployments following any deployment failure.
Deploy package even if the computer has been previously patched.	This option deploys the package(s) to all selected endpoints regardless of patch status.

Finally, the Deployment Information page features a Notes field to type text about the deployment. You can view this text after you complete the Deployment Wizard by viewing the deployment details on various Ivanti Endpoint Security pages.

6. [Optional] Type notes and comments in the Notes field.

   After completing the Deployment Wizard , you can view deployment notes by expanding the deployment from an Endpoint Details page Deployment and Tasks tab.

Deployment information is defined. Click Next to continue to the Package Deployment Order and Behavior page.

Schedule Configuration Page

You can set the timing and frequency of a deployment using the Schedule Configuration page. Deployments can be defined as one-time or recurring. Additional schedule configuration options are also available.

If endpoints are added to a group after a deployment is created but before the deployment occurs, the newly-added endpoints will receive the deployment.

Complete one of the following tasks based on how you want to schedule the deployment:

• If you want to run the deployment once, complete Scheduling a One Time Deployment.
• If you want to run the deployment on a recurring basis, complete Scheduling a Recurring Deployment.

Scheduling a One Time Deployment

A one time deployment starts on the selected day at the selected time.

Prerequisites:

• Begin Configuring Deployment Information.

1. From the Deployment Wizard Schedule Configuration page, click Change located in the Start Time option.
2. Ensure One Time is selected.
   The deployment will start on the selected day at the defined time.
3. [Optional] Select a date from the calendar. This is the date that the deployment will begin.
4. Define a Time. This is the time that the deployment will begin.

   Select from the 12 hour and 24 hour options to change time listing values. When the 24 hour option is selected, the AM/PM list is unavailable.

1. Select a value from the Hour list.
2. Select a value from the Minute list.
3. Select a value from the AM/PM list.
5. Click Next.
   The deployment is configured to start on the selected date and time, and the Deployment Information page opens. If you scheduled the deployment for a lapsed date and time, the deployment will start the next time applicable agents contact the Ivanti Endpoint Security server.

After Completing This Task:
Complete Configuring Deployment Information.

Scheduling a Recurring Deployment

A recurring schedule starts deployments on the selected day at the selected time. The deployment repeats every day, week, or month and if defined, ends on a specific date.

To schedule a recurring deployment, complete one of the following tasks:

The packages selected for deployment can have their order and behavior edited. For instance, you may want a particular package deployed before another. Use the Package Deployment Order and Behavior page to edit order and behavior.

The following table describes each page column.

Column	Description
Action	Contains Edit and Delete icons. Click the Edit icon to open Package Deployment Behavior Options page, which you can use to change package behavior options. Click the Delete icon to remove the package from the deployment. For additional information on editing package behavior, refer to Selecting Deployment Behavior Options.
Order	Indicates the order number of the package.
Package Name	Indicates the name of the package.
Selected Options	Displays icons that indicate behaviors selected for the package. Mouse over for a text description of the behavior. For additional information, refer toBehavior Icon Definitions.
Reboot	Displays icons that indicate whether a reboot follows the package deployment. For additional information, refer to Reboot Icon Definitions.

From this page, you can change the order that packages are deployed in using the page controls. For additional information on settings the package deployment order, refer to Selecting Deployment Behavior Options.

Chained packages cannot be moved without first removing their chained status. When a package is chained, Ivanti Endpoint Security determines the deployment order. However, when no longer chained, the package can be deployed at anytime following the chained deployments.

After defining deployment order and behavior, click Next to proceed to the Notification Options Page.

Setting Package Deployment Order

Set the deployment order to determine which packages are installed first.

Define the deployment order from the Package Deployment Order and Behavior page.

1. Select the package(s) you want to move within the queue.

   You can remove a package from the deployment clicking its Delete icon ().

2. Move the selected packages within the queue.
   Click the following icons to move packages to desired queue position.

Icon	Description
Double Up Arrow	Moves the selected package(s) to the top of the queue.
Up Arrow	Moves the selected package(s) up one queue position.
Double Down Arrow	Moves the selected package(s) to the bottom of the queue.
Down Arrow	Moves the selected package(s) down one queue position.

After editing package deployment order, you can restore the default order by clicking Restore Defaults.

3. [Optional] Edit deployment behavior options for packages by clicking the Edit icon ().
   For additional information, refer to Selecting Deployment Behavior Options.

   Package deployment order is defined. Click Next to proceed to the Notification Options page.

Selecting Deployment Behavior Options

Each package in a deployment can have its behavior changed by selecting behavior options.

Select deployment behavior options for a package from the Package Deployment Behavior Options page.

1. Select the check box for each behavior you want the package to use.
   The behaviors available change for each package. For a complete list of behaviors and their descriptions, refer to Behavior Icon Definitions.
2. Define additional behaviors typing entries in the Optional Flags field.
   For a complete listing of behavior flags, refer to Package Flag Descriptions.
3. Select a Display option.
   This option defines the notification that deployment recipients receive when user notifications are enabled. Select one of the following options.

Option	Description
Behavior options settings	Displays the expected deployment behavior.
Package description	Displays the package description.

Modifying behavior options initiates a system reevaluation of the deployment, which may result in a change in the package order.

The package enables the selected behaviors. Click Next to return to the Package Deployment Order and Behavior page.

Behavior Icon Definitions

Behavior icons appear on the Package Deployment Order and Behavior page and indicate the activities related to the deployment configuration.

The following table describes the deployment behavior icons and their descriptions. The icons representing the selected behaviors appear in the Selected Options column.

Icon	Action	Use to
	Uninstall	Uninstall the packages.
	Force Shutdown	Force all applications to close if the package causes a reboot.
	Do Not Backup	Uninstall package without backing up files.
	Suppress Reboot	Prevent a reboot after installation.
	Quiet Mode	Suppress any user interfaces during the deployment.
	Unattended Setup	Set up packages in unattended mode.
	List Hot Fixes	Return a listing of hot fixes installed on the target devices.
	Force Reboot	Force a reboot regardless of package requirements.
	Reboot is Required	Indicate a reboot is required prior to completing the installation.
	Chain Packages	Set the package as chainable (package must support chaining).
	Suppress Chained Reboot	Suppress the reboot, so that other chained packages can be sent following this package. When creating multiple deployment jobs, this option is recommended.
	Repair File Permissions	Repair file permissions following the package installation.
	Download Only	Distribute the package without running the package installation script.
	Suppress Notification	Suppress any user notifications during installation.
	Debug Mode	Run the package installation in debug mode.
	Do Not Repair Permissions	Suppress the repair of file name permissions after the reboot.
	May Reboot	Force a reboot, if required.
	Multi-User Mode	Perform the installation in multi-user mode.
	Single-User Mode	Perform the installation in single-user mode.
	Restart Service	Restart the service following the deployment.
	Do Not Restart Service	Suppress the restart of the service following the deployment.
	Reconfigure	Perform the system reconfigure task following deployment.
	Do Not Reconfigure	Suppress the system reconfigure task following deployment.

When using a chained deployment, reboots are suppressed whenever possible. The final deployment is represented as MayReboot because Ivanti Endpoint Security determines if the agent is in a dirty state. If so, a System Task - Reboot deployment is sent before deploying the remaining packages.

Reboot Icon Definitions

Reboot icons appear on the Package Deployment Order and Behavior page and determine the reboot conditions for a deployment.

The following table describes the reboot icons.

Icon	Name	Reboot Status
	Reboot may occur	The device may be rebooted, dependent upon the package installer requirements (at the time of install).
	Reboot may occur chained	The device may be rebooted, dependent upon the package requirements. However if a reboot is required and the device is not rebooted, the device will enter a reboot state.
	Reboot required	No other (chainable or non-chainable) packages will be installed until the device reboots.
	Reboot required chained	Only chainable packages will continue to be installed until the device has been rebooted.
	Reboot will occur	The device will be rebooted following the package installation.

Click Next to proceed to the Notification Options Page.

Click Finish to create the deployments and proceed to the Deployment Confirmation Page.

Package Flag Descriptions

You can attach behavior to package deployments using package flags.

The following table defines flag behavior and their descriptions:

Description (flag behavior)	Display Flag	Select Flag
Perform an uninstall; can be used with -mu or -q.	-yd	-y
Force other applications to close at shutdown.	-fd	-f
Do not back up files for uninstall.	-nd	-n
Do not restart the computer when the installation is done.	-zd	-z
Use quiet mode, no user interaction is required.	-qd	-q
Use unattended setup mode.	-dmu	-mu
Install in multi-user mode1	N/A	-su
Restart service after installation1	N/A	-restart
Do not restart service after installation1	N/A	-norestart
Reconfigure after installation1	N/A	-reconfig
Do not reconfigure after installation1	N/A	-noreconfig
Download packages to the default package cache directory for the Linux distro, but don't install them2 Packages are downloaded to the following locations: Redhat and CentOS: /var/cache/yum SUSE: /var/cache/zypp/packages Ubuntu: /var/cache/apt	N/A	-CACHEPACKAGES
Install packages cached in the tmp folder2	N/A	-INSTALLFROMCACHE
If you are patching Linux and Unix endpoints that receive content directly from vendor repositories, deployments may exceed your scheduled window because the patch content must first be downloaded, a process that may be excessively long. To reduce the likelihood of deployments that exceed maintenance schedules: Cache the content to the endpoints by completing a deployment using the -CACHEPACKAGES flag. This deployment downloads the content, but doesn't install it. Install the cached content by completing a second deployment using the -INSTALLFROMCACHE flag. The deployment skips the download of content, and installs the content already cached.
Ignores discrepancies between libraries available in different architectures2	N/A	-YUM_PROTECTED_MULTILIB
Skips packages with broken dependencies when updating the endpoint2	N/A	-YUM_SKIP_BROKEN
Performs a trial run of the deployment with no package changes made.3	N/A	-TRIAL_RUN
This package is chainable and will run Qchain.exe (Windows) or (UNIX/Linux).	-dc	-c
Suppress the final chained reboot.	-dc	-sc
Repair permissions.	-dr	-r
Deploy only.	-PLD1	-PLDO
No Pop-up	-PLN1	-PLNP
Debug	-PLDG	-PLDEBUG
Suppress Repair	-dsr	-sr
Force the script to reboot when the installation is done.	-1d	-1
Reboot is required.	N/A	-2
Reboot may occur.	N/A	-3
Reboot is required, and may occur.	N/A	-4
This flag applies to Linux and Unix operating systems only. This flag applies to only Red Hat Enterprise Linux 5.5-7.x, Oracle Enterprise Linux 5.5-7.x, and CentOS Linux 5.5-7.x. This flag applies to only Oracle Solaris 10 Update 9.

You can define whether users will receive notification of deployments and/or reboots, and if so, what the notification will contain using the Notification Options page of the Deployment Wizard.

When an agent is installed on a server where multiple users are logged in simultaneously, the deployment manager will provide each user with the ability to snooze or reject the deployment and/or reboot if snooze or reject is enabled.

For additional information on defining notification options, refer to Setting Notification Options.

After editing the Notifications Options page, click Next to view the Deployment Confirmation Page.

Setting Notification Options

During deployments, you can notify recipients that their endpoints are receiving a deployment or require a reboot. From the Notification Options page, you can define the message that recipients receive.

Define notification options from the Notification Options page.

1. Select a Define the Deployment Notification Options option.
   • Do not notify users of this deployment
   • Notify users of this deployment
2. If you selected the Notify users of this deployment option, complete the following sub-steps.
   1. [Optional] Type a notification in the Message field.
   2. Select whether you want to manually define remaining notification options or use the default settings defined in the agent policy set that applies to the target endpoints.
      • To use the default notification option settings defined in the agent policy set that applies to the target endpoints, select the Use Policies check box and continue to the next step.
      • To manually define the individual notification options, ensure the Use Policies check box is cleared. Select Yes or No from the Setting list for each of the following notification options:
        • Allow user to cancel

        • Allow user to snooze

        • Notification on top

          For additional information about this option, refer to About the Show on Top Option.

          If you want to allow LUM (Linux, Unix, and Mac) endpoint users to cancel or snooze deployments, manually set the options for Allow user to cancel and Allow user to snooze. Don't select the Use Policies or Use Agent Policy check boxes. These options are for Windows endpoints only. If you select these check boxes, the system ignores their selection, and your LUM endpoint users will not receive notifications.

   3. Select and define a Deploy option.
      • To deploy the notification within a specific time frame, select the Within option and define the field and list (Mins, Hours, Days).
      • To deploy the notification by a specific deadline, select the By option and define a date and time.
        Use the calender controls that display to define the date and time, and then click OK.
3. Select a Define the Reboot Notification Options option.
   • Do not notify users of this reboot
   • Notify users of this reboot
4. If you selected the Notify users of this reboot option, complete the following sub-steps to define the remaining options.
   1. [Optional] Type a notification in the Message field.
   2. Select whether you want to manually define remaining notification options or use the default settings defined in the agent policy set associated with the target endpoints.
      • To use the default notification option settings defined in the agent policy set that applies to the target endpoints, select the Use Policies check box and continue to the next step.
      • To manually define the individual notification options, ensure the Use Policies check box is cleared. Select Yes or No from the Setting list for each of the following notification options:
        • Allow user to cancel
        • Allow user to snooze
        • Notification on top

          For additional information about this option, refer to About the Show on Top Option.

          If you want to allow LUM (Linux, Unix, and Mac) endpoint users to cancel or snooze deployments, manually set the options for Allow user to cancel and Allow user to snooze. Don't select the Use Policies or Use Agent Policy check boxes. These options are for Windows endpoints only. If you select these check boxes, the system ignores their selection, and your LUM endpoint users will not receive notifications.

   3. Define the Reboot within option.

      • To manually define this option, enter a value in the field and select a value from the list (Mins, Hours, Days).
      • To use the default notification option setting defined in the agent policy set associated with the target endpoints, select the Use Agent Policy check box.

Notification options are configured. Click Next to continue to the Deployment Confirmation page.

About the Show on Top Option

When creating a deployment or a Mandatory Baseline item for Windows endpoints, you can define the Show on Top options. These options determine whether notifications for deployments or reboots display on top or on bottom of all other open endpoint windows. These options are not available on Linux, Unix, and Mac endpoints.

There are two different Show on Top options:

• A Show on Top option for Deployment Notification Options
• A Show on Top option for Reboot Notification Options

The following table describes the notification dialog behaviors for each option setting (Yes or No).

Always on Top Option Setting	Notification Dialog Behavior
Yes	The deployment or reboot notification displays as the topmost window. All other open windows display behind it.
No	The deployment or reboot notification displays as the bottommost window. All other open windows display in front of it. When sending a deployment or reboot notification for the first time, the deployment or reboot notification displays as the topmost window (with the exception of some dialogs, such as Windows Task Manager). The notifications will display as the bottommost window in subsequent notifications.

Tip:

You can configure an agent policy to define the default Show on Top option setting for deployments and reboots when configuring a deployment or Mandatory Baseline. For additional information, refer to the following tasks:

• Creating an Agent Policy Set
• Editing an Agent Policy Set

This page displays the options that you've selected while completing the Deployment Wizard. Use this page to verify the options that you've chosen before finishing the wizard and beginning the deployment.

Deployment Confirmation Text

The upper portion of the page summarizes what options you selected while completing the Deployment Wizard.

Text	Description
Job Name	The job name that you entered.
Schedule	The deployment schedule that you chose.
Manner	The manner that the patches are deployed.
Deployment notification	The option that you selected for notifying endpoint users of deployments.
Reboot notification	The option that you selected for notifying endpoint users of deployment reboots.
Total selected packages	The total number of packages included in the deployment. Some patches include more than one package. If the number of packages in the deployment exceeds the number of patches you selected for deployment, one or more package likely includes multiple packages.
Total selected endpoints/groups	The total number of endpoints and groups included in the deployment. Both endpoints and groups add a value of 1. For example, if you select 5 endpoints and 1 group of 5 endpoints, the total is 6, not 10.
Notes	Any notes that you entered to describe the deployment and its purpose.

When an agent is installed on a server where multiple users are logged in simultaneously, the deployment manager will provide each user with the ability to snooze or reject the deployment and/or reboot if snooze or reject is enabled.

The lower portion of the page lists the packages you chose for deployment.

Column	Description
Order	The package's place in queue during the deployment. The order is optimized to minimize reboots.
Package Name	The name of the package being deployed.
Selected Options	The Behavior Icon Definitions and Package Flag Descriptions that you selected while configuring the deployment.
Reboot	Indicates if a reboot is required to complete installation of the package.
Endpoints/Groups	The number of endpoints and groups the package is deploying to.

After reviewing the Deployment Confirmation page, click Finish to proceed to the Deployment Summary Page.

This page lists all the options that you chose while completing the Deployment Wizard. You can also use this page to cache packages before beginning the deployment.

All information displayed is identical to the info displayed on the Deployment Confirmation Page.

More importantly, you can use the page to cache packages before beginning the deployment.

What's Caching?

Caching is the process of commanding the Ivanti Endpoint Security Server to download selected packages to its local hard drive.

Why Should I Cache Packages Before a Deployment?

• Caching ensures that packages are installed in an optimized, predictable order.
• Starting a deployment without caching the packages first may result in unpredictable endpoint behavior. Packages are deployed as they are downloaded. For example, if deployment includes multiple packages that require a reboot, endpoints may repeatedly enter a reboot state, or (even worse) endpoints force reboots multiple times, thus interrupting employee work.

How do I Know When I Need to Cache Packages?

If you haven't already cached the packages you're deploying, the Selected Pages list includes red warning text and controls related to caching. We recommend waiting until caching completes before closing the Deployment Wizard. Read about caching information in the table that follows.

Column	Description
Package Icon	Contains an icon that indicates if the package is cached or is being requested. Mouse over the icon for a description.
Package Name	The name of the package being deployed.
Status	Indicates the package cache status. Cached Requesting

If you don't see these controls, go ahead and close the wizard. You're all set because the packages are cached.

After you finish reviewing the summary, click Close to dismiss the Deployment Wizard.