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.
The time required to complete the deployment task is less if you use one deployment platform per task.
The steps for creating a deployment task vary slightly depending on whether or not the target devices are already listed as discovered devices in your Management Zone (see Section I, Device Discovery):
Before the ZENworks Server can deploy the ZENworks Adaptive Agent to a device, make sure the following prerequisites are satisfied:
In addition to these requirements, ensure that the date and time are correct on both the ZENworks Server and on managed devices.
You need to enable the
option to allow other computers on a network to access resources on your computer by using a Microsoft network.Right-click
> .The Networks Connections window is displayed.
Right-click
> .The Local Area Connection Properties dialog box is displayed.
In the
tab, ensure that the option is selected.Click
.For more information, see File and Printer Sharing for Microsoft Networks.
Right-click
> .The Network and Sharing Center window is displayed.
In the left pane, click
.Right-click
> .The Local Area Connection Properties dialog box is displayed.
In the
tab, ensure that the option is selected.Click
.Right-click
> .The Network and Sharing Center window is displayed.
Right-click
> .The Local Area Connection Properties dialog box is displayed.
In the
tab, ensure that the option is selected.Click
.Any target device that is using Windows Firewall needs to be configured to allow file and printer sharing through the firewall. This is done by enabling the
exception in the Windows Firewall configuration settings. You can access Windows Firewall through the Control Panel or through the Windows Security Center.By default, the scope of the exception applies only to a local subnet. If the target device is in a different subnet than the Primary Server from which the deployment is run, you must add the IP address of the Primary Server to the Windows Firewall along with the local subnet.
From the desktop
menu, click > .Double-click
.The Windows Firewall window is displayed.
Click the
tab.In the
list, select , then click .The Edit a Service window is displayed.
Click
to include the IP address of the Primary Server and the local subnet.Click
.From the desktop
menu, click > .Double-click
.The Windows Firewall window is displayed.
In the left pane, click
.In the
list, select .Click
.The ZENworks Server needs classic file sharing access to the administrative share (displayed as Admin$) on target devices.
Windows 2000 devices use classic file sharing by default. If deployment of the Adaptive Agent to a Windows 2000 device fails, check the HKLM\System\currentcontrolset\services\lanmanserver\parameters\AutoShareWrks registry entry to see if it is set to 0 (disabled). If it is set to 0, Admin$ share is not accessible and the error is displayed. Delete the entire setting.
Windows 2003 devices use classic file sharing by default. If deployment of the Adaptive Agent to a Windows 2003 device fails with an invalid credentials error, you must enable classic file sharing.
On the Windows 2003 device, click the desktop
menu > > .Double-click
> .The Local Security Settings window is displayed.
In
, navigate to > .Change the value of
to .Click
.You can also use a Windows Group Policy to change the setting.
Windows XP uses simple file sharing by default. You need to disable simple file sharing to enable classic file sharing.
On the Windows XP device, right-click the
icon, then click .Click the
menu > to display the Folder Options dialog box.Click the
tab.In the
list, deselect the option, then click to save the change.Disabling this option changes the setting for the
option in the Local Security Policy (Local Policies > Security Options) to . You can also use a Windows Group Policy to change the setting.Open the Windows Registry and access the following:
HKLM/Software/Microsoft/Windows/CurrentVersion/Policies/System/LocalAccountTokenFilterPolicy
If the registry key does not exist, you need to create it.
Change its DWORD (32-bit) value to 1.
This allows remote users to log in and not be forced to be “guest.”
Close the registry to save the change.
Open the Services window and set the Remote Registry service to start automatically, then start it.
Click
> .Double-click
.Select
, then click .Open the Windows Registry and access the following:
HKLM/Software/Microsoft/Windows/CurrentVersion/Policies/System/LocalAccountTokenFilterPolicy
If the registry key does not exist, you need to create it.
Change its DWORD (32-bit) value to 1.
This allows remote users to log in and not be forced to be “guest.”
Close the registry to save the change.
Open the Services window and set the Remote Registry service to start automatically, then start it.
Click the desktop
menu > > .Double-click
.Select
, then click .Open the Windows Registry and access the following:
HKLM/Software/Microsoft/Windows/CurrentVersion/Policies/System/LocalAccountTokenFilterPolicy
If the registry key does not exist, you need to create it.
Change its DWORD (32-bit) value to 1.
This allows remote users to log in and not be forced to be “guest.”
Close the registry to save the change.
Open the Services window and set the Remote Registry service to start automatically, then start it.
Click the desktop
menu > > .Double-click
.In the left pane, click
.Select
, then click .This section assumes that you’ve already performed a discovery task to add the target devices to your ZENworks database. If you have not, you can perform the discovery task before continuing (see Section I, Device Discovery) or you can perform the discovery as part of the deployment task (see Section 10.4.3, Deploying to a Non-Discovered Device).
To deploy the ZENworks Adaptive Agent to a discovered device:
In ZENworks Control Center, click the
tab.The Deployable Device panel lists all the devices (imported or discovered) to which you can deploy the Adaptive Agent.
In the Deployment Tasks panel, click
to launch the Deploy Device Wizard.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 |
|
Enter Credentials page > field |
The Enter Credentials page lets you provide the usernames and passwords required to deploy the Adaptive Agent to the devices 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. Credentials that are not saved are cleared from memory when the ZENworks Server is restarted. If you are creating a scheduled deployment task, you might want to save the credentials to ensure that they are still available when the deployment is performed. |
Enter Credentials page > field |
To add a credential:
Depending on your environment, one credential might not provide access to all of the devices where you want to deploy the Adaptive Agent. In this case, you need to add as many credentials as necessary to cover the devices included in the task. The ZENworks Server uses the first credential that works. |
Select Schedule page |
The Select Schedule page lets you choose whether you want the task to run as soon as it is created (the option) or if you want to schedule the task to run at a future date and time. If you select , choose one of the following schedules:No Schedule: Indicates that no schedule has been set. The task does not run until a schedule is set or it is manually launched. This is useful if you want to create the task and come back to it later to establish the schedule or run it manually. Date Specific: Specifies one or more dates on which to run the task. Recurring: Identifies specific days each week, month, or a fixed interval on which to run the task. See Section B.0, Schedules or click the button for more information about the schedules. |
Select Primary Server page > Primary Server field |
Select the ZENworks Server that you want to perform the deployment task. |
Select Windows Proxy page > field |
Select this option if you want to override the Windows Proxy settings configured at the Management Zone in order to modify the settings of a task. A Windows Proxy is primarily used for Linux Primary Servers that cannot perform deployment tasks on Windows managed devices. However, you can also use a Windows Proxy for Windows Servers if you want to deploy devices in a different subnet than the Primary Server. In order to protect information, such as a deployment credential, that is passed between the ZENworks Server and the Windows Proxy, the connection between the ZENworks Server and the Windows Proxy is secured through SSL. |
Select Windows Proxy page > field |
Select this option if you want to use a Windows Proxy instead of the Windows Primary Server to perform the deployment tasks. For deployment, you need to add File and Printer Sharing as an exception in the Windows Firewall configuration settings. By default, the scope of the exception applies only to a local subnet. If the target device is in a different subnet than the Primary Server from which the deployment is run, you also need to add the IP address of the Primary Server as an exception. However, if you use a Windows Proxy in the same subnet as a target device, you do not need to change the scope of the Windows Firewall exception. Windows Proxy: Select the managed Windows device (server or workstation) on which you want to perform deployment tasks on behalf of Linux Primary Servers or Windows Servers. Windows Proxy Timeout: Specify the number of seconds you want the ZENworks Server to wait for a response from the Windows Proxy. |
General Options page > field |
Depending upon the processor architecture of the managed device, select the deployment package to be used for installing ZENworks Adaptive Agent on the device. If you are not sure about the device's processor architecture, choose the package with target architecture as All, which applies to 32-bit and 64-bit platforms. If the selected package has been deleted from the Primary Server, then the default deployment package is deployed. |
General Options page > field |
Specify the directory on the managed device where you want to install ZENworks Adaptive Agent. By default, the agent is installed to the directory specified in the %ZENWORKS_HOME% system environmental variable or to the %ProgramFiles%\novell\zenworks directory if the variable is 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. |
General Options page > |
After the installation of ZENworks Adaptive Agent, a device must reboot to make the Adaptive Agent functional. Do the following:
|
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. |
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. The preagent executes the commands in the system space, so you must specify commands that do not require user interaction. For more information about predeployment and post-deployment commands, click the button. |
When you finish the wizard, the deployment task is added to the list in the Deployment Tasks panel. You can use the panel to manage current tasks and create new tasks for deploying the ZENworks Adaptive Agent to devices. The panel includes the following information for each task:
Name: Displays the name given to the task. If
is displayed below the task name, the credentials required to perform the task on the targeted devices have been cleared from the ZENworks Server’s memory and must be entered again. To avoid having credentials lost when they are cleared from memory, you must store them in the ZENworks database.Schedule: Displays the dates on which the task is scheduled to run.
Status: Displays the following status information:
, , , , , , or . You can mouse over certain statuses to receive more information about the status.If an error occurred, the error is also recorded for the target device in the Deployable Devices panel. You can click the target device in the Deployable Devices panel to receive more information about the error.
If a target device has not been added to your ZENworks database through a discovery task, you can select the device while you are creating the deployment task. The following sections explain how to create the deployment task depending on whether you want to identify the target device by its IP address/hostname, from a CSV file, or from an LDAP directory.
In ZENworks Control Center, click the
tab.In the Deployment Tasks panel, click
to launch the Deploy Device Wizard.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. Click to display the Discovered Device Browser dialog box. |
Discovered Device Browser dialog box > > |
|
Discovered Device Browser dialog box > > |
|
Discovered Device Browser dialog box > > existing user source |
|
Discovered Device Browser dialog box > > |
|
Enter Credentials page > field |
The Enter Credentials page lets you provide the usernames and passwords required to deploy the Adaptive Agent to the devices 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. Credentials that are not saved are cleared from memory when the ZENworks Server is restarted. If you are creating a scheduled deployment task, you might want to save the credentials to ensure that they are still available when the deployment is performed. |
Enter Credentials page > field |
To add a credential:
Depending on your environment, one credential might not provide access to all of the devices where you want to deploy the Adaptive Agent. In this case, you need to add as many credentials as necessary to cover the devices included in the task. The ZENworks Server uses the first credential that works. |
Select Schedule page |
The Select Schedule page lets you choose whether you want the task to run as soon as it is created (the option) or if you want to schedule the task to run at a future date and time. If you select , choose one of the following schedules:No Schedule: Indicates that no schedule has been set. The task does not run until a schedule is set or it is manually launched. This is useful if you want to create the task and come back to it later to establish the schedule or run it manually. Date Specific: Specifies one or more dates on which to run the task. Recurring: Identifies specific days each week, month, or a fixed interval on which to run the task. See Section B.0, Schedules or click the button for more information about the schedules. |
Select Primary Server page > Primary Server field |
Select the ZENworks Server that you want to perform the deployment task. |
Select Windows Proxy page > field |
Select this option if you want to override the Windows Proxy settings configured at the Management Zone in order to modify the settings of a task. A Windows Proxy is primarily used for Linux Primary Servers that cannot perform deployment tasks on Windows managed devices. However, you can also use a Windows Proxy for Windows Servers if you want to deploy devices in a different subnet than the Primary Server. In order to protect information, such as a deployment credential, that is passed between the ZENworks Server and the Windows Proxy, the connection between the ZENworks Server and the Windows Proxy is secured through SSL. |
Select Windows Proxy page > > field |
Select this option if you want to use a Windows Proxy instead of the Windows Primary Server to perform the deployment tasks. For deployment, you need to add File and Printer Sharing as an exception in the Windows Firewall configuration settings. By default, the scope of the exception applies only to a local subnet. If the target device is in a different subnet than the Primary Server from which the deployment is run, you also need to add the IP address of the Primary Server as an exception. However, if you use a Windows Proxy in the same subnet as a target device, you do not need to change the scope of the Windows Firewall exception. Windows Proxy: Select the managed Windows device (server or workstation) on which you want to perform deployment tasks on behalf of Linux Primary Servers or Windows Servers. Windows Proxy Timeout: Specify the number of seconds you want the ZENworks Server to wait for a response from the Windows Proxy. |
General Options page > field |
Depending upon the processor architecture of the managed device, select the deployment package to be used for installing ZENworks Adaptive Agent on the device. If you are not sure about the device's processor architecture, choose the package with target architecture as All, which applies to 32-bit and 64-bit platforms. If the selected package has been deleted from the Primary Server, then the default deployment package is deployed. |
General Options page > field |
Specify the directory on the managed device where you want to install ZENworks Adaptive Agent. By default, the agent is installed to the directory specified in the %ZENWORKS_HOME% system environmental variable or to the %ProgramFiles%\novell\zenworks directory if the variable is 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. |
General Options page > |
After installation of the ZENworks Adaptive Agent, a device must reboot to make the Adaptive Agent functional. Do the following:
|
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. |
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. The preagent executes the commands in the system space, so you must specify commands that do not require user interaction. For more information about predeployment and post-deployment commands, click the button. |
When you finish the wizard, the deployment task is added to the list in the Deployment Tasks panel. You can use the panel to manage current tasks and create new tasks for deploying the ZENworks Adaptive Agent to devices. The panel includes the following information for each task:
Name: Displays the name given to the task. If
is displayed below the task name, the credentials required to perform the task on the targeted devices have been cleared from the ZENworks Server’s memory and must be entered again. To avoid having credentials lost when they are cleared from memory, you must store them in the ZENworks database.Schedule: Displays the dates on which the task is scheduled to run.
Status: Displays the following status information:
, , , , , , or . You can mouse over certain statuses to receive more information about the status.If an error occurred, the error is also recorded for the target device in the Deployable Devices panel. You can click the target device in the Deployable Devices panel to receive more information about the error.