Do you have a question about the ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - DISCOVERY-DEPLOYMENT-RETIREMENT REFERENCE 10.3 30-03-2010 and is the answer not in the manual?

Questions and answers

Summary of Contents for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - DISCOVERY-DEPLOYMENT-RETIREMENT REFERENCE 10.3 30-03-2010

Page 1 AUTHORIZED DOCUMENTATION Discovery, Deployment, and Retirement Reference Novell ® ZENworks 10 Configuration Management SP3 ® 10.3 March 30, 2010 www.novell.com ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 2 Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
Page 4 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 5: Table Of Contents
Contents About This Guide Part I Device Discovery 1 Basic Concepts Discovery Methods............13 IP and LDAP Discovery Tasks .
Page 6 8.4.2 Rebuilding the Custom Packages ........59 9 Registering Devices What Happens During Registration .
Page 7 Part III Device Removal and Retirement 13 Deleting Devices from Your ZENworks System 14 Retiring or Unretiring Devices Part IV Appendixes A Viewing the Predefined Reports B Schedules Now ..............119 No Schedule.
Page 8 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 9: About This Guide
ZENworks 10 Configuration Management documentation (http:// www.novell.com/documentation/zcm10/index.html). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
Page 10 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 11: Part I Device Discovery
Device Discovery The following sections provide information and instructions to help you add devices to your ® ZENworks database. After a device is added to the database, a ZENworks Server can automatically deploy the ZENworks Adaptive Agent to the device. Chapter 1, “Basic Concepts,”...
Page 12 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 13: Basic Concepts
Basic Concepts ® Device discovery is the process of adding workstation and server information to the Novell ® ZENworks database so that you can use that information to automatically deploy the ZENworks Adaptive Agent from a ZENworks Server to the devices. The following sections provide information to help you understand the discovery terminology and concepts: Section 1.1, “Discovery Methods,”...
Page 14 The requests are queued and the discovery engine processes five requests at a time until no requests remain. Five requests is the default. You can change the default if necessary (see Section 2.1, “Configuring Discovery Settings,” on page 23) or override the settings in the discovery task. Using fewer discovery technologies reduces the time required to complete the discovery task but might also reduce the amount of information received.
Page 15 The following table provides detailed information about the IP discovery technologies: IP Discovery Technologies Table 1-1 IP Discovery Functionality Requirements Prerequisites Technology WMI is the infrastructure Because WMI is a Microsoft Windows (Windows for management data Windows-specific Management Instrumentation Management and operations on technology, the Service to be installed and...
Page 16 IP Discovery Functionality Requirements Prerequisites Technology WinAPI Issues a request to the Because WinAPI is a Microsoft Remote Registry registry on the devices Windows-specific Service to be installed and identified by the IP-based technology, the running on the target discovery task to retrieve requests generated Windows device.
Page 17 IP Discovery Functionality Requirements Prerequisites Technology MAC Address Retrieves the MAC For the command to be Address of the successful, the target devices discovered device. Uses must reside in the same ping network as the ZENworks (Address Resolution Server that performs the Protocol) commands to discovery request.
Page 18 IP Discovery Functionality Requirements Prerequisites Technology ZENworks Issues a request to the The preagent is only installed ZENworks Adaptive on OEM devices or on Agent or ZENworks devices whose registration preagent on the devices was removed from the zone. identified by the IP-based discovery task.
Page 19: Ldap Discovery Technology
IP Discovery Functionality Requirements Prerequisites Technology Uses the SSH protocol to To query a device using SSH, communicate with the the device should have SSH SSH server on the enabled, and the username devices identified by the and password must be IP-based discovery task.
Page 20 Discovered panel (Devices tab > Discovered page) Figure 1-1 Each discovered device is categorized by type. All Types: All discovered devices, regardless of type. Servers: All discovered devices that have been identified as servers. Workstations: All discovered devices that have been identified as workstations. Printers: All discovered devices that have been identified as printers.
Page 21: Deployable Devices
1.7 Deployable Devices Devices that meet the requirements for the ZENworks Adaptive Agent are displayed in ZENworks Control Center in the Deployable Devices panel on the Deployment page. Deployable Devices panel (Deployment tab) Figure 1-2 Using this panel, you can deploy the Adaptive Agent to devices, remove them from the ZENworks database, or ignore them by filtering them out of the list.
Page 22 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 23: Discovering Devices By Using Ip Addresses
Discovering Devices By Using IP Addresses ® You can perform an IP-based discovery of your network to add devices to your ZENworks database. With an IP discovery, the ZENworks Server uses a set of technologies (WMI, WinAPI, MAC Address, NMAP, ZENworks, SNMP, SSH) to discover as much information about the target devices as possible.
Page 24 3 In the Discovery Process Settings panel, modify the following settings as necessary: Maximum Concurrent Discoveries: A discovery task consists of one or more discovery requests. For IP-based discovery tasks, a request is created for each discovery technology and each IP address in the specified range. Therefore, if you use six technologies to discover 10 IP addresses, 60 requests are created.
Page 25 Using fewer discovery technologies reduces the time required to complete the discovery task but might also reduce the amount of information received. For detailed information about each technology, see Section 1.3, “IP Discovery Technologies,” on page 4 In the IP Addresses to be Excluded panel, specify the IP subnets or address ranges to be excluded from the discovery.
Page 26: Designating A Discovery And Deployment Proxy Server
Perform name lookups: Uses a reverse lookup to associate the target IP address with a DNS name. Deselect this option if you do not want the DNS name discovered. SNMP Settings: These settings apply when using the SNMP discovery technology. Initial SNMP timeout: Specifies how long the discovery technology waits for a response to an SNMP query before assuming that the packet is lost.
Page 27: Creating An Ip Discovery Task
2 In the Management Zone Settings panel, click Discovery and Deployment, then click the Windows Proxy option. 3 Fill in the following fields: Windows Proxy: Click to browse for and select the managed Windows device (server or workstation) on which you want to perform discovery tasks on behalf of Linux-based ZENworks Servers.
Page 28 When a discovery task runs, the ZENworks Server creates a discovery request for each IP address and discovery technology (WMI, WinAPI, MAC Address, NMAP, ZENworks, SNMP, SSH) used. For example, if you specify one IP address and use all seven discovery technologies, the ZENworks Server initiates seven discovery requests.
Page 29 Wizard Page Details Select Discovery Type page Select IP Discovery Task. Specify a name for the task. The name cannot include any of the following invalid characters: / \ * ? : " ' < > | ` % ~ Discovery Settings page >...
Page 30 Wizard Page Details Enter IP Discovery Settings To specify a range of IP addresses for the discovery task: page > Range field 1. In the Range field, specify an IP address range using one of the following formats: xxx.xxx.xxx.xxx: Standard dotted-decimal notation for a single address.
Page 31 Wizard Page Details Enter IP Discovery Settings To specify the IP subnets or address ranges to be excluded from the page > Excluded Addresses IP discovery. These ranges are added to the ranges specified in the dialog box Management Zone, and the combined ranges are excluded while running the discovery task.
Page 32 Wizard Page Details Enter IP Discovery Settings Not all technologies use the same credentials, and all devices might page > Credentials field not have the same credentials, so you might need to specify multiple credentials to cover all targeted devices and to utilize all discovery technologies.
Page 33 Wizard Page Details Set the Discovery Schedule Choose whether you want the task to run as soon as it is created page (the Now option) or if you want to schedule the task to run at a future date and time. If you select On a Schedule, choose one of the following schedules: No Schedule: Indicates that no schedule has been set.
Page 34 Wizard Page Details Select Windows Proxy page Select this option if you want to use a Windows Proxy instead of the > Use Windows Proxy for Windows Primary Server to perform the discovery tasks. Windows Primary Server field Discovery through WMI, WinAPI and SNMP requires certain ports to be reachable on the target devices, so the Primary Server can send Remote Registry, WMI, or SNMP requests to the target devices.
Page 35: Discovering Devices In Ldap Directories
Before performing an LDAP discovery, make sure the following prerequisites are satisfied: An LDAP search requires the ZENworks Server to provide credentials that give read access to ® the contexts being searched. When accessing Novell eDirectory , the account also requires read rights to the WM:NAME DNS attributes on the workstation and server objects.
Page 36 Wizard Page Details Select Discovery Type page Select LDAP Discovery Task. Specify a name for the task. The name cannot include any of the following invalid characters: / \ * ? : " ' < > | ` % ~ Enter LDAP Settings page >...
Page 37 The user can have more than read-only access, but read-only access is all that is required and recommended. When accessing Novell eDirectory, the user account also requires read rights to the WM:NAME DNS attributes on the workstation and server objects.
Page 38 Wizard Page Details Discovery Settings page LDAP discovery retrieves the hostname, operating system type and version, and IP address of a discovered device from the LDAP source. Based on the selected discovery technologies, you can obtain the following additional information on a device: ZENworks Management Status Operating System Suites MAC Address...
Page 39 Wizard Page Details Select Windows Proxy page Select this option if you want to use a Windows Proxy instead of the > Use Windows Proxy for Windows Primary Server to perform the discovery tasks. Windows Primary Server field Discovery through WMI, WinAPI and SNMP requires certain ports to be reachable on the target devices, so the Primary Server can send Remote Registry, WMI, or SNMP requests to the target devices.
Page 40 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 41: Importing Devices From Csv Files
Importing Devices from CSV Files You can add devices to the ZENworks database by importing their information from a CSV (comma-separated values) file. When you import information from a CSV file, you map the CSV ® fields to ZENworks database fields. At a minimum, the CSV file must contain the DNS name or IP address for each device you want to import.
Page 42 Wizard Page Details Select File to Import page Browse for and select the CSV file that contains the devices you want to import. At a minimum, the CSV file must contain the DNS name or IP address for each device you want to import. Configure Import Map the columns in the CSV file to the device fields in the ZENworks database.
Page 43: Advertised Discovery
Advertised Discovery ® The ZENworks discovery engine allows you to collect information about advertised devices your network. Section 5.1, “Configuring the Advertised Discovery Settings,” on page 43 Section 5.2, “Discovering Advertised Devices,” on page 45 5.1 Configuring the Advertised Discovery Settings Advertised discovery uses the following configuration settings that can be modified, if necessary: Advertised discovery interval.
Page 44 3 In the Advertised Discovery Interval panel, modify the following settings as necessary: Allow the system to check for advertised devices: Select this option to enable advertised discovery. All ZENworks Servers perform the discovery. When a preagent receives a discovery request, it responds to the ZENworks Server that initiated the request.
Page 45: Discovering Advertised Devices
5.2 Discovering Advertised Devices 1 In ZENworks Control Center, click the Deployment tab. 2 In the Deployment Activities list located in the left pane, click Discover Advertised Devices. The ZENworks Server sends an advertised discovery request to all the devices on the network. On receiving the request, the preagent responds to the ZENworks Server.
Page 46 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 47: Viewing Or Updating Device Details
Viewing or Updating Device Details ® After a device is discovered, its details are listed in ZENworks Control Center, based on the information available for a discovered device. For example, if the SNMP information is not available for a discovered device, then the SNMP Information panel is not displayed. If the discovered information for a device is incorrect or insufficient, administrators with the Edit Discovered Device rights can manually change the details for the fields that have the Edit button next to them.
Page 48 Discovered panel (Devices tab > Discovered page) Figure 6-1 2 In the Discovered panel, click a device type, then click a discovered device for which you want to view or update the details. The Details page lists information about the discovered devices. 3 (Conditional) If the discovered information for a device is incorrect or insufficient, click Edit, then manually change the details for the fields.
Page 49: Part Ii Zenworks Adaptive Agent Deployment
ZENworks Adaptive Agent Deployment ® The following sections provide information and instructions to help you deploy the ZENworks Adaptive Agent to devices so that you can manage them. Chapter 7, “Basic Concepts,” on page 51 Chapter 8, “Managing Deployment Packages,” on page 55 Chapter 9, “Registering Devices,”...
Page 50 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 51: Basic Concepts
Adaptive Agent deployment package. For example, you can use a login script, or, if you have a previous version of ZENworks, you can distribute the Adaptive Agent deployment ® package as an Application object through Novell Application Launcher Installation instructions are provided in Chapter 10, “Deploying the ZENworks Adaptive Agent,”...
Page 52: Adaptive Agent Versus Inventory-Only Module
7.3 Adaptive Agent Versus Inventory-Only Module The ZENworks Adaptive Agent supports Windows 2000, Windows XP, Windows 2003, Windows Vista, and Windows 7 devices. You can fully manage devices on which the Adaptive Agent is deployed. This includes distributing software, enforcing policies, remotely managing the device, and so forth.
Page 53 Inventoried Devices page > Workstations folder Figure 7-2 Deployment instructions for the Inventory-Only module are provided in Chapter 12, “Deploying the Inventory-Only Module,” on page 101. Basic Concepts...
Page 54 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 55: Managing Deployment Packages
Managing Deployment Packages ® Deployment packages contain the files and information needed to install the ZENworks Adaptive Agent on devices and register the devices in the Management Zone. Each ZENworks Server contains nine default system packages. These packages are built during installation and system update of the ZENworks Server.
Page 56: Default System Packages Versus Custom Packages
The x86 packages ( ) are PreAgentPkg_Agent.exe PreAgentPkg_AgentComplete.exe located in the following ZENworks Server directory: on Windows and %ZENWORKS_HOME%\novell\zenworks\install\downloads\setup\x86 on Linux. /opt/novell/zenworks/install/downloads/setup/x86 x86_64 version: You can use the x86_64 version for manual deployments to 64-bit Windows devices. The x86_64 packages ( PreAgentPkg_Agent.exe...
Page 57 3 Complete the wizard by using information from the following table to fill in the fields. Wizard Page Details Select Deployment Package In the Target Architecture list, select the architecture of the package to Edit page you want to edit. x86 Architecture (32 bit): Used in manual deployments of the agent to 32-bit devices.
Page 58 PreAgentPkg_Agent.exe PreAgentPkg_AgentComplete.exe ) 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...
Page 59: Rebuilding Packages
“Deployment Packages” on page To rebuild the default packages: 1 Do one of the following: On Windows: At the command prompt, enter: novell-zenworks-configure -c CreateExtractorPacks -Z On Linux: At the console prompt, change to the directory, /opt/novell/zenworks/bin then enter: ./novell-zenworks-configure -c CreateExtractorPacks -Z...
Page 60 To rebuild the custom packages: 1 Do one of the following: On Windows: At the command prompt, enter: novell-zenworks-configure -c RebuildCustomPacks -Z On Linux: At the console prompt, change to the directory, /opt/novell/zenworks/bin then enter: ./novell-zenworks-configure -c RebuildCustomPacks -Z 2 When prompted to select whether to rebuild the custom packages, press Enter.
Page 61: Registering Devices
Registering Devices ® When you install the ZENworks Adaptive Agent to a device, the device is registered in your Management Zone and becomes a managed device. The following sections provide information to help you understand and manage the registration process: Section 9.1, “What Happens During Registration,”...
Page 62: Creating Registration Keys And Rules
9.2 Creating Registration Keys and Rules The first time a device registers, it is added to a folder. By default, it is added to either the /Servers folder or the folder, depending on the device type. /Workstations You can use registration keys and registration rules to override the default folder assignment and specify another folder, and to assign the device to groups.
Page 63 2 In the Registration Keys panel, click New > Registration Key to launch the Create New Registration Key Wizard. Registering Devices...
Page 64 3 Complete the wizard by using information from the following table to fill in the fields. Wizard Page Details Basic Information page Define the registration key’s name and folder location, add information to describe the key, and specify the number of times the key can be used.
Page 65: Creating A Registration Rule
Wizard Page Details Group Membership page Specify the groups that devices will become members of when they register. Adding groups causes registering devices to receive any assignments provided by membership in the groups. Assignments from group membership are additive, so if a device is assigned to both groups A and B, the device receives all assignments from both groups.
Page 66 2 In the Registration Rules panel, click New to launch the Create New Registration Rule Wizard. 3 Complete the wizard by using information from the following table to fill in the fields. Wizard Page Details Basic Information page Define the rule’s name and add information to describe the rule. Name: Provide a name for the rule.
Page 67 Wizard Page Details Device Criteria page Define the criteria that must be met for the registration rule to be applied to a device. The criteria are defined through the use of filters. At least one filter must be defined. 1. Click Add Filter to add a filter line. 2.
Page 68 Wizard Page Details Device Fields Specify the department, site, and location information you want entered on a device’s details page when it registers. For example, if you enter in the Department field, then Accounting Accounting is entered in the Department field on the device’s details page. Group Membership page Specify the groups that devices will become members of when they register.
Page 69: Modifying The Device Naming Template Used During Registration
9.3 Modifying the Device Naming Template Used During Registration The device naming template determines how devices are named when they register. By default, a device’s hostname is used. You can change it to use any combination of the following machine variables: ${HostName}, ${GUID}, ${OS}, ${CPU}, ${DNS}, ${IPAddress}.
Page 70: Enabling Dynamic Renaming Of Devices During Registration
3 In the Device Naming Template panel, click , then select the desired machine variable from the list. You can use any combination of one or more variables. For example: ${HostName}${GUID} 4 Click OK to save the changes. 9.4 Enabling Dynamic Renaming of Devices During Registration The Device Dynamic Rename setting lets you enable devices to be renamed, if necessary, whenever they refresh their registration information.
Page 71: Enabling The Setting At The Management Zone
9.4.1 Enabling the Setting at the Management Zone 1 In ZENworks Control Center, click the Configuration tab. 2 In the Management Zone Settings panel, click Device Management, then click Registration to display the Registration page. 3 In the Device Dynamic Rename panel, click Enable automatic renaming of devices. 4 Click OK to save the changes.
Page 72: Disabling The Use Of Registration Rules
2 Browse to find the device folder for which you want to change the setting, then click Details to display the folder’s details. 3 Click the Settings tab. 4 In the Settings panel, click Device Management, then click Device Dynamic Rename to display the Device Dynamic Rename page.
Page 73 If you want to rely completely on registration keys, you can disable registration rules. You have two options when you disable registration rules: Disable the default registration rules only: Any device that attempts to register without a registration key or that does not meet the criteria in a custom registration rule is rejected. The default registration rules are ignored.
Page 74: Manually Registering A Device
2 Enter the following command: zac reg [-k key] [-u ZENworks Administrator username -p ZENworks Administrator password] [server_url:port For example: zac reg -k acct -u zadmin -p novell https://zserver.novell.com , and parameters are optional. If you don’t use the parameters, you are prompted to enter a username and password.
Page 75: Unregistering A Device
2 Enter the following command: zac unr [-f] [-u ZENworks Administrator username -p ZENworks Administrator password] For example: zac unr -u zadmin -p novell , and parameters are optional. If you don’t use the parameters, you are prompted to enter a username and password. The parameter ignores the ZENworks database and forces the device to be unregistered locally;...
Page 76 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 77: Deploying The Zenworks Adaptive Agent
Deploying the ZENworks Adaptive Agent ® Any devices you want to manage through ZENworks must have the ZENworks Adaptive Agent deployed to them. The Adaptive Agent performs all ZENworks management tasks on the managed device. For detailed information about the supported platforms and system requirements for a managed device, see “Managed Device Requirements”...
Page 78: Customizing The Agent Features
The Asset Management, Inventory Management, Policy Management, and Remote Management features overlap with the ZENworks Desktop Management features. Therefore, when you deploy the Adaptive Agent to a device that has the traditional ZENworks Desktop Agent installed, if you install any of the Adaptive Agent features other than Asset Management, Inventory Management, Policy Management, and Remote Management, the Adaptive Agent removes the ZENworks Desktop Agent before installing the features.
Page 79 2 In the Management Zone Settings panel, click Device Management, then click ZENworks Agent. Deploying the ZENworks Adaptive Agent...
Page 80: Customizing Features After Deployment
10.3 Changing the Target Installation Directory By default, the ZENworks Adaptive Agent is installed to the following locations: On a Windows 32-bit device: Windows_drive:\Program Files\Novell\ZENworks On a Windows 64-bit device: Windows_drive:\Program Files(x86)\Novell\ZENworks To install the agent to a different location, you can create a ZENWORKS_HOME system environment variable on the device prior to deployment and set the variable to the new target installation directory.
Page 81: Using A Task To Deploy The Agent
10.4 Using a Task to Deploy the Agent The ZENworks Server can deploy the ZENworks Adaptive Agent to devices. This requires that you create a task, called a deployment task, for the ZENworks Server. The task identifies the target devices, the credentials required to perform an installation on the devices, the registration key to use (optional), the date and time to perform the installation, and other tasks you want performed on the devices either before or after the installation.
Page 82 2 In the left pane, click Manage network connections. 3 Right-click Local Area Connection > Properties. The Local Area Connection Properties dialog box is displayed. 4 In the Networking tab, ensure that the File and Printer Sharing for Microsoft Networks option is selected.
Page 83 4 In the Allowed Programs and Features list, select File and Printer Sharing. 5 Click OK. Enabling Classic File Sharing The ZENworks Server needs classic file sharing access to the administrative share (displayed as Admin$) on target devices. “Windows 2000” on page 83 “Windows 2003”...
Page 84 Disabling this option changes the setting for the Network access: Sharing and security model for local accounts option in the Local Security Policy (Local Policies > Security Options) to Classic - local users authenticate as themselves. You can also use a Windows Group Policy to change the setting.
Page 85: Deploying To A Discovered Device
4 Open the Services window and set the Remote Registry service to start automatically, then start 5 Click the desktop Start menu > Settings > Control Panel. 6 Double-click Network and Sharing Center. 7 In the left pane, click Change advanced sharing settings. 8 Select Turn on file and printer sharing, then click Save Changes.
Page 86 Wizard Page Details Enter Credentials page > The Enter Credentials page lets you provide the usernames and Save Credentials to passwords required to deploy the Adaptive Agent to the devices DataStore field included in the task. Unless you save the credentials, they are stored only in memory. Saved credentials are encrypted in the database for increased security.
Page 87 Wizard Page Details Select Primary Server page > Select the ZENworks Server that you want to perform the Primary Server field deployment task. Select Windows Proxy page Select this option if you want to override the Windows Proxy settings > Override Zone Windows configured at the Management Zone in order to modify the settings Proxy Settings field of a task.
Page 88 %ZENWORKS_HOME% system environmental variable or to the directory if the variable is %ProgramFiles%\novell\zenworks not set on the managed device. Ensure that the installation path does not contain spaces. NOTE: If the directory you specify cannot be created, then the agent is installed in the default location.
Page 89: Deploying To A Non-Discovered Device
Wizard Page Details Pre/Post Deployment page Specify commands that you want run before and after the Adaptive Agent is installed on a device. For example, you can execute operating system commands, run scripts, and launch executables. The commands are passed to the preagent as part of the deployment task package.
Page 90 3 Complete the wizard by using information from the following table to fill in the fields. Wizard Page Details Enter Deployment Task page Specify a name for the task. The name cannot include any of the following invalid characters: / \ * ? : " ' < > | ` % ~ Select Devices page Allows you to identify the devices to which you want to deploy the ZENworks Adaptive Agent.
Page 91 The user can have more than read-only access, but read-only access is all that is required and recommended. For Novell eDirectory access, use standard LDAP notation. For example: cn=admin_read_only,ou=users,o=mycompany For Microsoft Active Directory, use standard domain notation.
Page 92 Wizard Page Details Enter Credentials page > The Enter Credentials page lets you provide the usernames and Save Credentials to passwords required to deploy the Adaptive Agent to the devices DataStore field included in the task. Unless you save the credentials, they are stored only in memory. Saved credentials are encrypted in the database for increased security.
Page 93 Wizard Page Details Select Primary Server page > Select the ZENworks Server that you want to perform the Primary Server field deployment task. Select Windows Proxy page Select this option if you want to override the Windows Proxy settings > Override Zone Windows configured at the Management Zone in order to modify the settings Proxy Settings field of a task.
Page 94 %ZENWORKS_HOME% system environmental variable or to the directory if the variable is %ProgramFiles%\novell\zenworks not set on the managed device. Ensure that the installation path does not contain spaces. NOTE: If the directory you specify cannot be created, then the agent is installed in the default location.
Page 95: Manually Deploying The Agent
Wizard Page Details Pre/Post Deployment page Specify commands that you want to run before and after the Adaptive Agent is installed on a device. For example, you can execute operating system commands, run scripts, and launch executables. The commands are passed to the preagent as part of the deployment task package.
Page 96 The Web browser displays a list of deployment packages. For each architecture (32-bit and 64- bit), there are two types of packages: Network: The network package downloads and installs only the preagent to the target device; the preagent then downloads and installs the ZENworks Adaptive Agent from the ZENworks Server.
Page 97: Tasks To Be Performed After Deploying The Agent On Citrix Servers
In addition to the options listed above, there are two additional BUILDTIME options (-f file and -o output_file) that are used when building packages. These options should only be used under the direction of Novell Technical Services. 10.6 Tasks to be Performed After Deploying the...
Page 98: Uninstalling The Agent
10.7 Uninstalling the Agent For information on how to uninstall the ZENworks Adaptive Agent, see “Uninstalling a Windows Primary Server, Satellite, or Managed Device” in the ZENworks 10 Configuration Management Installation Guide. ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 99: Deploying The Zenworks Adaptive Agent To Linux Devices
Deploying the ZENworks Adaptive Agent to Linux Devices ZENworks 10 Configuration Management does not support management of Linux devices. However, you can use a Linux device as a ZENworks Satellite by installing the Linux Adaptive Agent package on the device and configuring the device as a Satellite. A Satellite is a device that performs the roles that a ZENworks Primary Server normally performs.
Page 100 100 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 101: Deploying The Inventory-Only Module
Deploying the Inventory-Only Module If a Windows device does not meet the requirements for deploying the Adaptive Agent, or if you ® want to inventory a Windows, Linux, NetWare , or Macintosh OS X device, you can deploy the Inventory-Only module. See “System Requirements”...
Page 102: Installing On Linux/Unix
Platform Filename ® Novell NetWare ZENworks_Adaptive_Agent_Netware.zip Mac OS X ZENworks_Adaptive_Agent_OSX.dmg Microsoft Windows ZENworks_Adaptive_Agent_Windows.exe zaaio-10.3.0-aix-powerpc.tar.gz HP-UX zaaio-10.3.0-hpux.-parisc.tar.gz Linux zaaio-10.3.0-linux-x86.tar.gz Solaris zaaio-10.3.0-sunos-sparc.tar.gz 3 Click the filename for the desired platform and download the file. 4 Skip to one of the following sections to continue with installation of the module: Section 12.2, “Installing on Linux/UNIX,”...
Page 103: Installing On Netware
12.3 Installing on NetWare 1 Make sure you have downloaded to a device that ZENworks_Adaptive_Agent_Netware.zip has access to the target NetWare server. If you haven’t, see Section 12.1, “Downloading the Module from a ZENworks Server,” on page 101. 2 Extract on the target ZENworks_Adaptive_Agent_Netware.zip sys:\temp\zen_aa...
Page 104 file is generated on the desktop. ZENworks_Adaptive_Agent_OSX.zip 4 Double-click the file to generate the ZENworks_Adaptive_Agent_OSX.zip file. ZENworks_Adaptive_Agent_OSX.pkg 5 Double-click the file to launch the installation ZENworks_Adaptive_Agent_OSX.pkg package. 6 If a message appears telling you a program needs to run to determine whether the package can be installed, click Continue until you reach the Select Destination page.
Page 105 5 Copy the file into the file. zenumia.pkg You can now use the package file without the TextEdit window appearing as part of the installation. Deploying the Inventory-Only Module 105...
Page 106 106 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 107: Part Iii Device Removal And Retirement
Device Removal and Retirement I I I The following sections provide information and instructions to help you delete or retire devices from ® your ZENworks system. ® If you delete a server or workstation device, the selected device is removed from your ZENworks system.
Page 108 108 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 109: Deleting Devices From Your Zenworks System
Deleting Devices from Your ZENworks System ® If you delete a server or workstation device, the selected device is removed from your ZENworks system, its GUID is deleted, all inventory information is removed, and all policy and bundle assignments are removed. 1 In ZENworks Control Center, click the Devices tab.
Page 110 110 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 111: Retiring Or Unretiring Devices
Retiring or Unretiring Devices ® If you retire a server or workstation device, the selected device is retired from your ZENworks Zone. Retiring a device is different from deleting a device. When you retire a device, its GUID is retained (as opposed to when you delete a device, which also deletes its GUID). As a result of retiring a device, all inventory information is retained and is assessable but all policy and bundle assignments are removed.
Page 112 To retire or unretire an inventoried device: 1 In ZENworks Control Center, click Devices > Inventoried. 2 Click the underlined link next to the Servers or Workstations folder to display the list of servers or workstations in your ZENworks system. Devices panel showing list of inventoried devices.
Page 113 Search box with Retired selected. Figure 14-3 4 Click Search. Retiring or Unretiring Devices 113...
Page 114 114 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 115: Part Iv
Appendixes Appendix A, “Viewing the Predefined Reports,” on page 117 Appendix B, “Schedules,” on page 119 Appendix C, “Configuring NMAP for ZENworks,” on page 123 Appendix D, “Troubleshooting Discovery, Deployment, and Retirement,” on page 125 Appendix E, “Documentation Updates,” on page 131 Appendixes...
Page 116 116 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 117: A Viewing The Predefined Reports
2 In the ZENworks Reporting Server Reporting panel, click ZENworks Reporting Server InfoView to launch the ZENworks Reporting Server InfoView. 3 Navigate to the Novell ZENworks Reports > Predefined Reports folder and expand the list. 4 Click Discovered Devices. The following predefined reports are included for discover devices: CISCO Routers: Displays information on the discovered Cisco routers.
Page 118 118 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 119: B Schedules
Schedules The following schedules are available for discovery and deployment tasks: Section B.1, “Now,” on page 119 Section B.2, “No Schedule,” on page 119 Section B.3, “Date Specific,” on page 119 Section B.4, “Recurring,” on page 120 B.1 Now Runs the task immediately after completing the task wizard. B.2 No Schedule Indicates that no schedule has been set.
Page 120: Use Coordinated Universal Time (Utc)
B.3.4 Use Coordinated Universal Time (UTC) The Start Time is converted to Universal Coordinated Time (UTC). Select this option to indicate that the Start Time you entered is already in Coordinated Universal Time and should not be converted. For example, suppose you are in the Eastern time zone. If you enter 10:00 a.m. and select this option, the Start Time is scheduled for 10:00 UTC.
Page 121: Fixed Interval
Use Coordinated Universal Time: The Start Time is converted to Universal Coordinated Time (UTC). Select this option to indicate that the Start Time you entered is already in Coordinated Universal Time and should not be converted. For example, suppose you are in the Eastern time zone.
Page 122 122 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 123: C Configuring Nmap For Zenworks
Configuring NMAP for ZENworks Network discovery is done by the ZENloader module, which runs with as the username, zenworks and the command with the option. However, the command needs privileges to nmap nmap root successfully execute. Consequently, the NMAP discovery fails when it runs with the zenworks username.
Page 124 124 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 125: D Troubleshooting Discovery, Deployment, And Retirement
Troubleshooting Discovery, Deployment, and Retirement The following sections provide solutions to the problems you might encounter while discovering devices, deploying the Adaptive Agent to devices, and retiring devices: “An error occurs while installing the ZENworks Adaptive Agent through a deployment task” on page 125 “Manual installation of the ZENworks Adaptive Agent hangs with the status as starting”...
Page 126: Manual Installation Of The Zenworks Adaptive Agent Hangs With The Status As Starting
“ ” for a Starting... considerable amount of time. The status of Novell ZENworks PreAgent service is not Started in the Windows Service Control Manager. %SystemRoot%\novell\zenworks\bin\zenpreagent.installerr file contains the following error message: Exception during start: Cannot start service ZENPreAgent on computer.
Page 127: How Do I Enable Debug Logging
How do I enable debug logging? Source: ZENworks 10 Configuration Management; Discovery, Deployment, and Retirement. Action: To enable the logs, see TID 3418069 in the Novell Support Knowledgebase (http://support.novell.com/search/kb_index.jsp). Where do I find the PreAgent log files? Source: ZENworks 10 Configuration Management; Discovery, Deployment, and Retirement.
Page 128: Discovery Task Remains In A Pending State If It Has A Large Ip Address Range
On Windows: Do the following: 1. From the Windows desktop Start menu, click Settings > Control Panel. 2. Double-click Administrative Tools > Services. 3. Restart the Novell ZENworks Loader Service. On Linux: At the console prompt, enter /etc/init.d/novell- zenloader restart 4 Restart the ZENworks Loader.
Page 129: Zenworks-Related Files Might Be Reported As Malicious Software During The Zenworks Adaptive Agent Installation
ZENworks Adaptive Agent: 1 Manually add to the System_drive:\windows\novell\zenworks Exclusion list of the anti-virus software installed on the managed device. 2 Install the ZENworks Adaptive Agent. The device that has the ZENworks Adaptive Agent installed is not registered in the Management Zone Source: ZENworks 10 Configuration Management;...
Page 130 130 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...
Page 131: E Documentation Updates
This section contains information on documentation content changes that were made in this ® ® Discovery, Deployment, and Retirement Reference for Novell ZENworks 10 Configuration Management SP3. The information can help you to keep current on updates to the documentation.
Page 132 132 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference...

This manual is also suitable for:

Zenworks 10 configuration management sp3

Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - DISCOVERY-DEPLOYMENT-RETIREMENT REFERENCE 10.3 30-03-2010 Deployment Manual

Table of Contents

Device Discovery

Part I Device Discovery

1 Basic Concepts

2 Discovering Devices by Using IP Addresses

3 Discovering Devices in LDAP Directories

4 Importing Devices from CSV Files

5 Advertised Discovery

6 Viewing or Updating Device Details

Part II Zenworks Adaptive Agent Deployment

7 Basic Concepts

8 Managing Deployment Packages

9 Registering Devices

10 Deploying the Zenworks Adaptive

10 Deploying the Zenworks Adaptive Agent

11 Deploying the Zenworks Adaptive Agent to Linux Devices

12 Deploying the Inventory-Only Module

Part III Device Removal and Retirement

13 Deleting Devices from Your Zenworks System

14 Retiring or Unretiring Devices

Part IV

A Viewing the Predefined Reports

B Schedules

C Configuring NMAP for Zenworks

D Troubleshooting Discovery, Deployment, and Retirement

E Documentation Updates

Quick Links

Chapters

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - DISCOVERY-DEPLOYMENT-RETIREMENT REFERENCE 10.3 30-03-2010

Summary of Contents for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - DISCOVERY-DEPLOYMENT-RETIREMENT REFERENCE 10.3 30-03-2010

This manual is also suitable for:

Table of Contents