Using Distribution

Software distribution allows you to automatically distribute packages of software and other files to groups of systems. You can also monitor the progress of distribution. The Distribution tab includes the following subtabs:

• Packages
• Environment
• Dependencies
• Files Sources
• Hosted Files

The distribution process consists of the following steps:

1. Create environment variables.
2. Create dependencies.
3. Host files.
4. Create file sources.
5. Create file packages.
6. Perform file package actions.

Video: Software Distribution (1:46)

Environment Variables

You can define environment variables to refer to static text, registry keys, or registry values by a convenient name. Systems Manager evaluates environment variables when it executes package actions. The following list identifies the benefits of using environment variables:

• Eliminates typographical or syntax errors
• Simplifies the distribution process
• Sets standards for distribution
• Reference data in registry specific to the target system

You can refer to environment variables in strings such as the source or destination path by enclosing the name of the variable in brackets ({}). For example, you can define the static variable 'Temporary Dir' and use it in the following destination path:

"{Temporary Dir}\MyPackage"

You can refer to system variables in the same way:

"{TEMP}\MyPackage"

The Environment Variables page displays environment variables and allows you to create, edit, and delete them. Follow these steps to display the Environment Variables page:

1. Click the Distribution tab.
2. Point to the Environment menu and choose View All Variables to display the Environment Variables page.

The Environment Variables page displays the following information:

• Name: the name of the variable
• Type: the type (static, registry key, or registry value)
• Hive: the location of the top-level key in the registry
• Key: for registry keys and registry values
• Value: for static variables
  —OR—
  Value Name: for registry values

To create a variable, click the Create button to display the Environment Variable page.

To edit a variable, click the edit button next to the environment variable you want to modify.

To delete a variable, click the delete button next to the environment variable you want to remove.

Creating & Editing Environment Variables

The Environment Variable page allows you to create environment variables.
Note: This page also allows you to edit environment variables.

Follow these steps to create an environment variable:

1. Click the Distribution tab.
2. Point to the Environment menu and choose Create Variable to display the Environment Variable page.
3. Enter a name for the environment variable.
4. Set a value for the variable. You can choose from the following types:
   
   • Static: static text
   • Registry Key: a key in the Microsoft Windows registry
   • Registry Value: a registry value; for example, you can find out the location of the Windows Program Files directory by creating a variable referring to registry value
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFiles Dir\
5. Click Save to create the environment variable.

Editing Environment Variables

Follow these steps to edit an environment variable:

1. Click the Distribution tab.
2. Point to the Environment menu and choose View All Variables to display the Environment Variables page.
3. Click the edit button next to the variable you want to modify to display the Environment Variable page.
4. Change the name or value information of the environment variable.
5. Click Save to save your changes to the variable.

Deleting Environment Variables

Follow these steps to delete an environment variable:

1. Click the Distribution tab.
2. Point to the Environment menu and choose View All Variables to display the Environment Variables page.
3. Click the delete button next to the variable you want to remove.
4. Click OK in the confirmation dialog box.

To delete multiple variables, select their check boxes and click the Delete button.

Dependencies

Dependencies are conditions that Systems Manager evaluates before or after distribution executes a package action. Dependencies can ask questions about registry keys, registry values, and files. A benefit of using dependencies is that you can be sure that endpoints have the appropriate prerequisites before installing new applications, and you can verify that applications installed properly after your distributed them.

The following table identifies the possibilities for setting dependencies:

The Dependencies page displays all of the defined dependencies and allows you to create, edit, and delete them. Follow these steps to display the Dependencies page:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose View All Dependencies to display the Dependencies page.

The Dependencies page displays the following information:

• Name: the name of the dependency
• Type: the type of dependency (registry key, registry value, or file)
• Description: the description for the dependency
• Operand: the registry key environment variable
• Operator: the specified operator
• Value: if applicable

To create a dependency, click the Create button to display the Dependency page.

To edit a dependency, click the edit button next to the dependency you want to modify.

To delete a dependency, click the delete button next to the dependency you want to remove.

Creating & Editing Dependencies

The Dependency page allows you to create new dependencies.
Note: This page also allows you to edit dependencies.

Follow these steps to create a dependency:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose Create Dependency to display the Dependency page.
3. Enter a name for the dependency.
4. Optional: Enter a description for the dependency.
5. Select a dependency type: registry key, registry value, or file.
6. Enter the information for the dependency.
7. Click Save.

Editing Dependencies

Follow these steps to edit a dependency:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose View All Dependencies to display the Dependencies page.
3. Click the edit button next to the dependency you want to modify to display the Dependency page.
4. Change the name, description, and/or type information for the dependency.
5. Click Save to save your changes to the dependency.

Deleting Dependencies

Follow these steps to delete a dependency:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose View All Dependencies to display the Dependencies page.
3. Click the delete button next to the dependency you want to remove.
4. Click OK in the confirmation dialog box.

To delete multiple dependencies, select their check boxes and click the Delete button.

Registry Key Dependencies

Registry key dependencies allow you to check the existence of a key in the target system's registry. For example, before you install Adobe Acrobat Reader 7.0, you can verify that the key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\7.0 does not exist. To accomplish this task, you can create a registry key variable (for example, Acrobat Reader 7.0 Key) referring to the key and create a registry key dependency to verify that this key does not exist. You can use this dependency as one of the pre-action checks in an Adobe Acrobat Reader 7.0 installation action.

Follow these steps to create a registry key dependency:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose Create Dependency to display the Dependency page.
3. Enter a name for the dependency.
4. Optional: Enter a description for the dependency.
5. Select the Registry Key option.
6. Select a registry key environment variable from the Operand drop-down list.
   Note: Systems Manager populates the Operand drop-down list with variables that you define.
7. Select the operator from the Operator drop-down list.
8. Click Save to create the dependency.

Registry Value Dependencies

Registry value dependencies allow you to perform various checks on values stored in the target system's registry. For example, after you install the Adobe Acrobat 7.0 products, you can verify that the products are installed in the expected folder. You can verify that the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\7.0\Installer\Path is equal to C:\Program Files\Adobe\Acrobat 7.0\.

Follow these steps to create a registry value dependency:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose Create Dependency to display the Dependency page.
3. Enter a name for the dependency.
4. Optional: Enter a description for the dependency.
5. Select the Registry Value option.
6. Select a registry value environment variable from the Operand drop-down list.
   Note: Systems Manager populates the Operand drop-down list with variables that you define.
7. Select the operator to perform from the Operator drop-down list.
   Note: Most operators require a value for comparison; you can enter that value in the Value column.
8. Click Save to create the dependency.

File Dependencies

With file dependencies, you can check if a file exists and whether it is a certain size. For example, you can verify that the file {Adobe Acrobat 7.0 path}Reader\AcroRd32.exe is 7671876 bytes in size after install. This also demonstrates how you can use a registry value variable named Adobe Acrobat 7.0 path to refer to the registry value stored at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\7.0\Installer\Path in your file path.

Follow these steps to create a file dependency:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose Create Dependency to display the Dependency page.
3. Enter a name for the dependency.
4. Optional: Enter a description for the dependency.
5. Select the File option.
6. Enter the full path name of the file in the Operand field.
   Note: Systems Manager populates the Operand drop-down list with variables that you define.
7. Select the operator to perform from the Operator drop-down list.
8. If you want to check the file's size, enter the size (in bytes) in the Value column.
9. Click Save to create the dependency.

Hosted Files

The Hosted Files page displays files hosted at the Systems Manager Network Operations Center (NOC). You can upload files to the NOC to distribute them to endpoints that are not connected to your company intranet.

Note: If the hosted files feature is not configured for your company, contact Support.

Follow these steps to display the Hosted Files page:

1. Click the Distribution tab.
2. Point to the Hosted Files menu and choose View All Hosted Files to display the Hosted Files page.

The Hosted Files page displays the name and URL for each hosted file.

To edit a hosted file, click the edit button next to the hosted file you want to modify.

To delete a hosted file, click the delete button next to the hosted file you want to remove. Then, click OK in the confirmation dialog box.

Creating & Editing Hosted Files

The Hosted File page allows you to create and edit hosted files.

Follow these steps to create or edit a hosted file:

1. Click the Distribution tab.
2. Point to the Hosted Files menu and choose Create Hosted File to display the Hosted File page.
3. Enter a name for the hosted file.
4. Click the Browse button to locate the file to import.
5. Click Save.

Systems Manager displays the new hosted file on the Hosted Files page. The hosted file can then be referenced in the file source of a file package by using the URL of the hosted file.

File Sources

A file source consists of a "bundle" of files and the location from which those files are retrieved. Most packages use one or more file sources to obtain the files they need to deliver.
Note: You can use a file source for multiple packages.

The File Sources page displays all of the defined file sources and allows you to create, edit, and delete them. Follow these steps to display the File Sources page:

1. Click the Distribution tab.
2. Point to the File Sources menu and choose View All File Sources to display the File Sources page.

The File Sources page displays the following information:

• Name
• Description
• Location
• Files (number of files in the file source)

To create a file source, click the Create button to display the Create File Source page.

To edit a file source, click the edit button next to the file source you want to modify.

To delete a file source, click the delete button next to the file source you want to remove.
Note: You cannot delete a file source until you remove all references to the file source from packages.

Creating File Sources

A file source can be referenced from any package in the package definition, as well as any action defined within the package.

Follow these steps to create a file source:

1. Click the Distribution tab.
2. Point to the File Sources menu and choose Create File Sources to display the Create File Source page.
3. Enter the name for the file source.
4. Optional: Enter a description for the file source.
5. Enter the source location.
   Example of a Microsoft Windows file share path: \\lan-server\share-name\path
   Example of a Web server path: http://web-server/path
   Note: You can enter a variable for the location.
   You can reference hosted files by splitting the hosted file URL at the final slash (/) and using the first part as the location and the filename at the end.
6. For each file that is to be retrieved from the source (the location you specify in the previous step), enter the remote file name.
   Example: install.exe
7. Optional: Enter a local file name. This file name will be appended to the destination path specified on the package, and the file will be retrieved from the source and copied to that location on each destination endpoint.
8. Click the Add File button to add a space for another file and the Remove File button to remove a file that you no longer want to include.
   Note: You can add multiple files from a single location.
9. Click Save.

Editing File Sources

Follow these steps to edit a file source:

1. Click the Distribution tab.
2. Point to the Dependencies menu and choose View All File Sources to display the File Sources page.
3. Click the edit button next to the file source you want to modify to display the Edit File Source page.
4. Update the name, description, location, and/or files included in the file source.
5. Click Save to save your changes to the file source.

Deleting File Sources

Follow these steps to delete a file source:

1. Click the Distribution tab.
2. Point to the File Sources menu and choose View All File Sources to display the File Sources page.
3. Click the delete button next to the file source you want to remove.
4. Click OK in the confirmation dialog box.

To delete multiple file sources, select their check boxes and click the Delete button.

Note: You cannot delete a file source until you have deleted all references to the file source from packages.

Packages

Packages typically consist of a collection of files and actions that can be performed on these files. You can include any type of file in a package. You can "run" the following types of files in packages:

• *.exe
• *.bat
• *.cmd
• *.msi
• *.vbs

Systems Manager runs *.exe files as is. Systems Manager runs *.bat, *.cmd, and *.vbs files in the context of a new command processor. Systems Manager generates the appropriate command processor for each:

• command.com /c "user_specified_batch_file user_specified_arguments" for Microsoft Windows 95, Windows 98, and Windows Me
• cmd.exe /c "cmd.exe /c "user_specified_command_file user_specified_arguments"" for all other Windows platforms for both *.bat and *.cmd files

Systems Manager runs *.msi files with msiexec.exe (the Microsoft installer engine). By default, Systems Manager generates the following command: msiexec.com /i "user_specified_msi" /qb "user_specified_arguments".

Note: If the action specifies /i or -i as one of its arguments (or if it specifies no arguments), then Systems Manager generates the default command in the example. If the action specifies /x or -x in the arguments, then the "/i" in the command is replaced with "/x".

Viewing Packages

The Package View page displays the summaries of the defined packages and allows you to select a number of their actions to invoke.

To display the Package View page, click the Distribution tab. The Package View page displays by default.

The Package View page displays the following information for each package:

• Name
• Version
• Actions
• Created
• Last modified

You can create, view, edit, and delete packages. You can also distribute and export packages, and you can perform package actions.

Creating & Editing Packages

Follow these steps to create a package:

1. Click the Distribution tab.
   The Package View page displays by default.
2. Click the Create Package button to display the package editor.
3. Enter information in the Summary, Source, Destination, Actions, and Options tabs.
   Note: You can navigate between the tabs and make your changes.
4. Click Save.

Note: You can leave the package editor temporarily, for example to create environment variables or dependencies. Click the edit button for the package to return to the package editor.

Summary Tab

The Summary tab provides a quick overview of the package. Follow these steps to complete the summary information for a package:

1. Click the Summary tab on the package editor to display the package summary information.
2. Enter a name for the package.
3. Enter a version for the package.
4. Optional: Enter a description for the package.
5. The Read me URL field allows you to attach files to packages. For example, you can attach supplemental instructions or reference information to those packages that need further explanation.
   Note: File locations must be available to the specialists who request it. For example, if a file is located on your company intranet, only specialists on the intranet can access the file.
   In the Read me URL field, enter a path to link files to the package. You can link files using the following formats:
   http://...
   ftp://...
   file://server/share/...
   Note: If you attach a file using this method, Systems Manager displays the "Read me" link next to the package name on the Summary tab.
6. Click Save.

Source Tab

The Source tab allows you to specify one or more file sources to include in the package.
Note: File sources included at this level are distributed for all actions in the package.

Follow these steps to complete the file source information for a package:

1. Click the Source tab on the package editor to display the package source information.
2. Select a file source from the drop-down list and click the Add File Source button.
   —OR—
   Click the Create File Source button to display the Create File Source page.
3. Repeat the previous step to add any number of file source objects to the package.
4. Click Save.

Destination Tab

When Systems Manager performs a package action on an endpoint, the files you listed in the Source tab (and in the specified action) are downloaded to the directory specified in the Destination tab. This directory can be either automatically generated (default setting) or specified. You can also specify if the package should abort when the directory already exists and whether the package should remove the destination directory when it has completed running.

Follow these steps to complete the destination information for a package:

1. Click the Destination tab on the package editor to display the package destination information.
2. Select the Temporary Directory option.
   Note: Systems Manager only runs the files from this location; it does not install the files here.
   —OR—
   Select the Specified Path option and enter a directory.
3. Optional: Select the Fail if directory already exists check box to stop the package from running if it finds that the directory already exists on each target machine.
4. Optional: Select the Delete directory on successful completion check box to instruct the package to remove the destination directory when it finishes running.
   Note: Systems Manager recommends that if you select the Fail if directory already exists check box, you also select the Delete directory on successful completion check box. Or, clear both check boxes.
5. Click Save.

Actions Tab

The Actions tab allows you to create, modify, and delete the actions for the package. You must define at least one action for each package.

An action consists of an executable file (or data file, in the case of Microsoft Installer) with arguments and options; it can include pre-action checks and success checks. When an action is invoked on an endpoint, the following things happen:

• All pre-action dependencies are checked.
• If the dependencies succeed, files are downloaded from the source path into the destination directory.
• If the previous step was successful, the executable is run.
• If the previous step was successful, all post-action dependencies are checked.

Each action must have a unique name and platform combination; however, you can use the same name for more than one action. For example:

In this example, the action.bat executable runs on all non-Microsoft Windows 2000 Professional endpoints. (It also evaluates all the pre- and post-actions in that action.) The win2kaction.exe runs only on the Windows 2000 endpoints.

Follow these steps to assign actions to a package:

1. Click the Actions tab on the package editor to display the package action information.
2. Required: Enter an action for the package.
3. Required: Select the platform for which this package is designated. You must create a different action for each platform.
   Note: Systems Manager creates the Platform list from your asset list.
4. Enter a description for the action.
5. Enter a File to Run for the action. The drop-down list contains files you specified in the Source tab.
6. If you select a file to run, enter Command Line Arguments, the command line switches necessary to run the application on the target machine.
7. In the Executive Timeout field, enter the number of seconds to wait before aborting the file execution (if the executable does not complete on its own).
   Note: Enter 0 to wait indefinitely (not recommended).
8. Click the Add File Source to add additional files specific to the action.
   —OR—
   Click the Create File Source button to add new files sources to a package.
   Note: The files in these file sources are only downloaded when this action is invoked.
9. Specify any Pre-action checks, or dependencies, that must be satisfied before running the action.
   To add a pre-action check to the list, select it and click Add.
   To remove a pre-action check from the list, select it and click Remove Selected.
10. Specify any Success checks, or dependencies, that must be satisfied after running the action.
    To add a success check to the list, select it and click Add.
    To remove a success check from the list, select it and click Remove Selected.
11. Select the User can defer delivery check box to allow end users to postpone a package delivery. Indicate the number of times users can defer the package.
12. In the Defer time choices field, enter the options for end user deferrals.
    For example, if you want users to have the option of delaying the package delivery for 30, 60, and 90 minutes, enter 30,60,90.
    These options display in the user notification dialog box in a drop-down list below your customized message.
    After a user defers a package delivery the maximum number of times, Systems Manager delivers the package.
13. Select the User can reject delivery check box to allow end users to refuse the package. If a user rejects a package delivery, check the Action Status for details.
14. In the Message to be displayed in user notification dialog field, enter a message to communicate the reason for the package.
    For example: This package is optional. Do you really want it?
15. Select the Check Return Code is 0 check box to fail the action unless the executable returns 0. If the return code is 0, the action is considered a success (assuming post-action checks pass, too).
16. Select the Reboot on Success check box to automatically reboot the endpoint after a successful action.
17. Select the Display Reboot Notification Dialog check box to notify the user before rebooting. This notification informs end users before the reboot takes place, but it moves forward without user consent (after 60 seconds or after the Max wait time, if set). Also, enter a Max wait time in seconds to have the reboot proceed if the user is not at the machine.
18. Recommended: Select the Require Reboot User Consent check box to require the user to confirm the reboot.
    Note: If you set Max wait time to 0, the reboot waits indefinitely until the user confirms it.
19. Click the Add Action button to add the action to your package.
20. Click Save.

The Action List at the top of the Actions tab displays the actions already defined for the package, if any.
To edit an action in this list, click the edit button next to the action.
To delete an action from this list, click the delete button next to the action you want to remove. Then, click OK in the confirmation dialog box.

Options Tab

The Options tab allows you to enter the following information for a package:

• Maximum download speed
• Maximum simultaneous downloads
• Error sample
• Error threshold

Follow these steps to add options information for a package:

1. Click the Options tab on the package editor to display the package options information.
2. Enter the maximum download speed. The default value is 150. If you enter 0, the download executes as fast as it can.
3. Enter the number of endpoints in the Maximum Simultaneous Downloads field to set the number of machines that connect to the source at one time. The default value is 10.
4. Enter the number of hours after which Systems Manager terminates the package action.
   Note: If you enter 0, the package distribution continues forever or until all actions are complete (or failed) for all endpoints.
5. Enter a number in the Error Sample field to indicate the first x percent of install attempts to be monitored for success or failure.
   —AND—
   Enter a number in the Error Threshold filed to instruct the package to stop after the specified amount of attempts have failed.
   For example, if you distribute a file package to 100 endpoints and set the Error Sample to 30% and the Error Threshold to 10%, these settings will abort the installation after 30 attempts if three or more installations failed.
6. Click Save.

Deleting Packages

Follow these steps to delete a package:

1. Click the Distribution tab.
   The Package View page displays by default.
2. Click the delete button next to the package you want to remove.
3. Click OK in the confirmation dialog box.

To delete multiple packages, select the packages and click the Delete Selected Package(s) button.

Distributing Packages

You can distribute packages to selected endpoints or to groups.

See Also: Troubleshooting: Resolving a Credentials Error

Distributing Packages to Selected Endpoints

Follow these steps to distribute a package to selected endpoints:

1. Click the Distribution tab.
   The Package View page displays by default.
2. To invoke an action on any package, select the action from the Action drop-down list.
3. Click the Distribute Selected Package(s) button to display the Target Systems page.
4. Select the check boxes next to the endpoints to which you want to distribute the packages.
5. Optional: Set the Schedule for package distribution, including the Date, Hour, and Minute.
   —OR—
   Accept the default values in the Schedule fields to distribute the package now.

Click the Invoke Selected button.

Distributing Packages to System Groups

Follow these steps to distribute a software package to a system group:

1. Click the Assets tab.
2. Point to the System Inventory menu and choose System Groups to display the System Groups page.
   
3. Click the action button for the group to which you want to distribute the package. The Group Actions page displays.
4. Select the Distribute packages option and click Continue to display the Package View page.
5. Optional: Set the Schedule for package distribution, including the Date, Hour, and Minute.
   —OR—
   Accept the default values in the Schedule fields to distribute the package now.
6. Select the check box for the package you want to distribute.
7. Click the Distribute Selected Package(s) button to instruct Systems Manager to distribute the package at your specified time.

Target Systems

The Target Systems page allows you to set the schedule and download options for packages.

Follow these steps to complete the Target Systems page:

1. Click the Distribution tab.
2. Select one ore more packages to distribute and click Distribute Selected Package(s) to display the Target Systems page.
3. Optional: Set the Schedule for package distribution, including the Date, Hour, and Minute. This feature allows you to distribute packages at convenient times.
   Note: If you do not specify a schedule for the package, Systems Manager distributes the package immediately.
4. Select the systems to which you want to distribute the package.
5. Click Distribute Package to Selected System(s) to distribute the package and display the Action Status View to view the status of your package distribution.

Exporting Package Data

Follow these steps to export package data:

1. Click the Distribution tab.
   The Package View page displays by default.
2. Click the export button next to the package you want to export.
3. Select a location for saving the file and click OK.

Systems Manager writes the definition of the package and file sources to a file in XML format.

Action Status

As an action invocation progresses, the system updates the status for each endpoint and for the overall action. You can monitor the progress of the action invocation via Action Status and Endpoint Status entries. As the invocation progresses, Systems Manager updates the status for each endpoint and for the overall action.

Viewing Action Status

The Action Status View page displays a status overview for each package that has been distributed.

Follow these steps to display the Action Status View page:

1. Click the Distribution tab.
2. Point to the Packages menu and choose Action Status to display the Action Status View page.

The Action Status View page displays the following information about each invoked action:

• Package - the name of the package being distributed
• Action - the name and platform of the action being invoked
• Start Time - the date and time when the action was invoked
• Percent Complete - portion of the distributions attempted
• Error Count - number of distributions which reported errors

To monitor action progress, click the Refresh button to get the latest status information available.

To view the status entries of individual endpoints, click the Detail link of the action you are interested in to display the Endpoint Action Status list.

To abort an action in progress, click its Abort link.

To clear an action status that has completed (showing 100%), either click the Delete link in its row or select the check box for it and click the Delete Selected button.

Viewing Endpoint Status

The Endpoint Status page displays status information for individual endpoints to which a package action is being distributed.

Follow these steps to display the Endpoint Status page:

1. Click the Distribution tab.
2. Point to the Packages menu and choose Action Status to display the Action Status View page.
3. Click the Detail link for a package to display the Endpoint Status page.

The header of the page displays which package and action the list represents. The Endpoint Status page displays the following information about each endpoint for the distribution:

• Endpoint - the name of the endpoint
• Status - the current status of the distribution
• Percent Complete - the percentage of the distribution completed
• Message - further explanation of the status or specific error message
• Start Time - date and time when the distribution began

To monitor action progress, click the Refresh button to get the latest status information. Typically, the status of the distribution changes from "None" to "Ready" to "In Progress" to "Complete" or "Error" as you click Refresh. Possible status values include:

• None - waiting for distribution to be invoked
• Cancel - the distribution is about to be cancelled (waiting for the endpoint to acknowledge)
• Cancelled - the distribution was cancelled
• Complete - the distribution completed successfully
• Deferred - the distribution was deferred by a user on an endpoint
• Error - an error has occurred
• In Progress - the distribution is in progress
• No Response - no response from the endpoint
• Queued - the distribution is ready to be started
• Stalled - the distribution has been started and did not update its status within 30 minutes
• Reboot - the distribution is about to reboot the endpoint
• Rebooting - the endpoint is rebooting
• Unavailable, Queued - waiting for the machine to register with the Network Operations Center (NOC); when it registers, the distribution will start

To cancel an endpoint action status, click the Cancel link by the endpoint.

To restart the distribution to an endpoint, click the Restart link by it. This action will change the Status to "None" and the Percent Complete accordingly.

Importing File Package Definitions

The Import File Package Definition page allows you to import a file package definition from a previously exported XML definition file.

Follow these steps to import a file package:

1. Click the Distribution tab.
2. Point to the Packages menu and choose Import Package to display the Import File Package Definition page.
3. Click the Browse button to locate the file to import.
4. Enter a name for the package.
5. Enter a version for the package.
6. Click Import.

After you import a file package definition, you can edit it as a saved package.