<< Click to Display Table of Contents >> Managing Packages |
PDQ Deploy Packages are viewed (along with their Deployments and Schedules) on their specific package page in the Main Console window. Packages are modified in the Package Window. Packages can also be duplicated, exported and imported, and organized on the Main Console window tree.
This section describes how to manage packages and includes the following topics:
•Exporting and Importing Packages
Packages can be organized by:
•Renaming
To rename a package select it in the tree, then click Edit > Rename (or press F2 or right-click and select Rename), edit the name, then click OK.
NOTE: Nested packages remain linked even after changing their name.
•Moving
Select and drag packages to change their order in a list or move them from folder to folder. For details about organizing packages with custom folders, see Custom Folders.
•Customizing Appearance
For information about setting custom appearance options, see Item Appearance Window.
You can streamline the creation of new packages by duplicating, renaming, and editing a package that is similar to the new package you need. Examining and repurposing prebuilt packages is also a great way to learn how packages are constructed and configured.
To duplicate a package:
1.Select the package you want to duplicate.
2.Click File > Duplicate (or press Alt+Insert or right-click and select Duplicate).
A duplicate package appears in the tree with a number appended to its name. You can also copy and paste a package to create a duplicate.
3.(Optional) To rename a package, click Edit > Rename (or press F2 or right-click and select Rename), edit the name, then click OK.
It’s good practice to rename the package so it matches its new purpose and to avoid confusion when using the original package.
4.To edit the selected package, double-click it or click Edit Package on its Package page.
For information about modifying packages, see Editing Packages below.
Packages can be exported to an XML file and then imported into PDQ Deploy on another computer.
To export packages:
1.Select one or more packages or a folder of packages.
When exporting a folder, all of the packages and folders within it are also exported.
2.Click File > Export (or press Ctrl+E or right-click and select Export).
3.Browse to where you want to save the package, then click Save.
IMPORTANT: Only the package definition is exported, not the files used by the package or any schedules associated with it.
To import packages:
1.To determine where the imported package or packages are placed in the Main Console Tree, do one of the following:
•To import at the top level of the tree, click the empty part of the tree.
•To import into a folder, select the folder or an item in the folder.
2.Click File > Import (or press Ctrl+I or right-click and select Import).
3.Browse to and select the package definition, then click Open.
IMPORTANT: When importing packages on another computer, copy the install files to the repository on the second computer.
PDQ Deploy Packages can be edited in the Package Window. You may need to update one of your custom packages, for example, if there is a new release of the install or updater files it uses. You can also duplicate existing custom or prebuilt packages to use as templates for a new package.
To edit a package:
1.Locate and select the package you want to edit in the Main Console Tree or the Packages folder page.
2.Double-click the package, or on its specific package page, click Edit Package.
The Package Window opens containing the package and package step properties.
For an introduction to the Package Window, see Package Window. For detailed information, see Package and Step Properties.
3.To modify the package, see the following table for a list of tasks and details.
As you progress through the package editing process you should periodically save changes. You can also close (and save) the package window, then continue later.
Task |
Details |
---|---|
Edit Package Properties |
To edit the basic properties of the package, click Properties in the tree. For details, see Creating a New Package, Part 1: Package Properties. |
Edit a Step |
To edit a step: 1.Select the step in the tree. 2.To edit the deployment properties, click the Details tab. For more information, see Creating a New Package, Part 3: Conditions and Options. 3.To edit the step properties unique to the step type, do the following: •To edit the conditions that must be met for a step to run, click the Conditions tab. •To edit additional step level options, such as the Run As option used to execute the step on the target and error settings, click the Options tab. For details, depending on the step type you are editing, see one of the following topics: •For an Install Step, see Creating a New Package, Part 2: Install Step Properties. •For a Command Step, see Creating a New Package, Part 4: Adding Command Steps. •For other step types, see Creating a New Package, Part 5: Adding Additional Steps. |
Add a Step |
To add a new step to the package, click New Step > Step Type or Steps For details, depending on the step type you are adding, see one of the following topics: •For an Install Step, see Creating a New Package, Part 2: Install Step Properties. •For a Command Step, see Creating a New Package, Part 4: Adding Command Steps. •For other step types, see Creating a New Package, Part 5: Adding Additional Steps. |
To rearrange the order of the steps do one of the following: •Click the step, then drag and drop to the desired location. •Select the step, then click the Move Up |
|
Disable/Enable a Step |
To disable a step or enable a step that is currently disabled: 1.Select the step in the tree. 2.Right-click and toggle from Enabled to Disabled. If a step is disabled, the name of the step is struck-through and the step will be skipped during deployment. This feature enables administrators to “turn off” steps that they may want to enable in the future without deleting the step itself. |
Delete a Step |
To remove a step from the package, select the step, then click Delete |
Delete a Package |
To delete a package, select it in the tree, then click Delete |
4.When you have finished editing the package, click Save , and close the Package window.
If you are ready to create a deployment to test your edited package, see Manually Deploying Packages.
Using PDQ Deploy in Central Server mode grants all console users the ability to create packages privately before making them public. The Private Packages folder is added to the console when it is set to either Server or Client mode. All packages, target lists, and custom folders created within this folder remain private to other console users.
To create a private package:
1.Select the Private Packages folder in the tree of the Main Console.
2.Click New Package on the toolbar (or click File > New Package or press Ctrl+N).
A new blank Package window opens with the Detail tab of the Package Properties selected.
3.Set the package properties and add the appropriate steps as spelled out in Creating a New Package.
4.Click Save .
The package is now saved in the Private Packages folder and can only be seen and used by the console user that created it.
To make a private package public:
1.Locate and select the package you want to make public in the Private Packages folder in the tree.
2.Click and drag the package to another folder or any location in the tree outside the Private Packages folder.
Once the package no longer exists in the Private Packages folder, the package has been made public and can be seen by all other console users.
To make a public package private:
1.Locate and select the package you want to make private in the Main Console tree.
2.Click and drag the package to the Private Packages folder .
This will bring up a dialog box that lets you choose whether to move the packages, or just create a copy of the packages. If you choose to create a copy, the original package is still public, but the copied package has been made private. |
3.(Optional) If the package was copied to the Private Packages folder, you can delete the original.
© 2024 PDQ.com Corporation. All rights reserved.
PDQ.com is a trademark of PDQ.com Corporation. All other product and company names are the property of their respective owners.
Help Version: 19.3.553.0