8.3 Customizing Packages

  1. In ZENworks Control Center, click the Deployment tab.

  2. Click Edit Deployment Package (located in Deployment Activities list in the left navigation pane) to launch the Edit Deployment Package Wizard.

  3. Complete the wizard by using information from the following table to fill in the fields.

    Wizard Page

    Details

    Select Deployment Package to Edit page

    In the Target Operating System field, select the operating system of the package that you want to edit.

    In the Target Architecture list, select the architecture of the package you want to edit.

    • x86 Architecture (32-bit): Used in manually deploying the agent to 32-bit devices.

    • x86_64 Architecture (64-bit): Used in manually deploying the agent to 64-bit devices.

    • All Supported Architectures: Used by the ZENworks Server to complete deployment tasks for either 32-bit or 64-bit devices.

    In the Package Install Type list, select the installation type of the package that you want to edit.

    The packages in the list are determined by the Target Operating System that you selected for the device.

    The following packages are available for Windows:

    • Network Installation (.NET required): Contains only the pre-agent, which downloads the Adaptive Agent files from the ZENworks Server and the Microsoft .NET Framework 3.5 SP1 installables.

    • Standalone Installation (.NET required): Contains the pre-agent and all the ZENworks Adaptive Agent module files.

    • Standalone Installation: Contains the pre-agent, all the ZENworks Adaptive Agent module files, and the Microsoft .NET Framework 3.5 SP1 installables.

    The following packages are available for Linux:

    • Network Installation (JRE required): Contains only the pre-agent, which downloads the Adaptive Agent files from the ZENworks Server and the JRE 1.6 Update 16 installables.

    • Standalone Installation: Contains the pre-agent, all the ZENworks Adaptive Agent module files, and the JRE 1.6 Update 16 installables.

    In the Package Name list, select the name of the package that you want to edit.

    The names in the list are determined by the architecture and installation type you selected. The list displays the names of any packages with the selected architecture and installation type.

    By default, the system package is always displayed. The system package is the predefined deployment package that meets the architecture and installation type criteria you specified.

     

    Other package names are displayed only if you have edited the system package and saved the customized version as a new package. You can specify any name for the customized package. The name must not contain any of the following invalid characters: / \ * ? : " ' < > | ` % ~. The directory, used to store the package, is given the specified name and the package name remains the same.

    Provide Primary Server Information page

    Specify the addresses that can be used to access the ZENworks Server. A device needs to access the ZENworks Server when the deployment is a network installation (the pre-agent must download the ZENworks Adaptive Agent files from the ZENworks Server) and when it registers as a managed device. All addresses you specify must belong to the same ZENworks Server.

    For example, assume that you are deploying the Adaptive Agent to devices on your private network and to devices on the other side of a firewall or router that is using NAT (Network Address Translation). You would list the ZENworks Server’s private network address (IP address, DNS name, or both) and also list its NAT address.

    Add Registration Key page

    Select a registration key to use during the registration portion of the deployment process. A registration key provides information about the folders and groups to which a device is assigned during registration.

    Selecting a registration key is optional; if you don’t select one, registration rules are used to determine the folder and group assignments. To deploy to servers or workstations, choose a server registration key or a workstation registration key respectively.

    For more information about registration keys and rules, see Section 9.0, Registering Devices.

    Additional Language Selection page

    On Windows, select additional language packages to be included with the deployment package.

    The progress and message logs for the deployment process are displayed in English by default. If you want to receive the messages in the language of the machine locale, then you must add the necessary additional language packs to the deployment package.

    Select Destination for the New Deployment Package page

    Select whether you want to overwrite the existing package or save the edited package as a custom package. The two options are:

    Overwrite Original Deployment Package: Replace the original package with this edited package.

    Select a Name for the New Deployment Package Saves the edited package as a new custom package. The original package remains unchanged.

    You can specify any name you want for the new custom package. The name must not contain any of the following invalid characters: / \ * ? : " ' < > | ` % ~. The name that you specify is used to identify the updated packages on the zenworks-setup page. The package name remains the same and the directory used to store the package is given the name you specify.

    All new packages are saved in the ZENworks Server’s %ZENworks_HOME%\novell\zenworks\install\downloads\custom directory on Windows and /opt/novell/zenworks/install/downloads/custom on Linux. For example, if you modify the x86 version of the PreAgentPkg_Agent.exe package and save it with a name of ExternalPack, the file is stored as follows:

    %ZENworks_HOME%\Novell\ZENworks\install\downloads\custom\ExternalPack\x86\PreAgentPkg_Agent.exe on Windows and /opt/novell/zenworks/install/downloads/custom/ExternalPack/x86/PreAgentPkg_Agent.exe on Linux.

    NOTE:If you want to delete custom deployment packages, you must manually delete the directory containing the packages.