The Desktop Management Agent Distributor can facilitate the initial deployment and future upgrades of the ZENworks Desktop Management Agent through the use of Microsoft domains and Microsoft Active Directory. By default, the Agent Distributor uses Microsoft domains and Active Directory when selecting target workstations and during deployment of the Desktop Management Agent to those same target workstations.
This section includes the following information:
Before you use the Agent Distributor to deploy the Desktop Management Agent in a Microsoft domain environment, make sure the following prerequisites are satisfied:
Failed - Unable to map Admin$ share drive.
To deploy the Desktop Management Agent to workstations that are members of a Microsoft domain or Active Directory:
At the Windows workstation, log in to the domain as a user who is a member of the domain Administrator group.
Launch ConsoleOne on the Windows workstation, then click Tools > ZENworks Utilities > Install Agents.
or
Copy the agentdistributor.exe file to the distributing workstation from the sys\public\mgmt\ConsoleOne\1.2\bin directory and execute it on the local workstation.
If you are not a member of the domain Administrator group, or if the workstation is not a member of the domain, the main dialog box of the Agent Distributor waits for input (this allows for the possibility of distributing the agent to Windows workgroups; see Using the Desktop Management Agent Distributor to Deploy the Agent to Workstations in a Windows Workgroup). Otherwise, the following dialog box is displayed.
Enter your domain administrator username and password, then click OK to display the following dialog box.
In the Location of ZENworks Desktop Management Agent (zfdagent.msi) field, browse to and select the zfdagent.msi file.
If the zfdagent.msi file is not already on the workstation's local drive or an available network drive, copy it from the \agentinstall\english directory located on the Novell ZENworks 6.5 Desktop Management CD.
Configure the Management Agent options. To do so:
Click Configure Agent to display the Configure ZENworks Desktop Management Agent dialog box.
Use this dialog box to configure the Desktop Management Agent options. The options you select (such as Install or Uninstall) determine the availability of other options. A description of each option is listed below.
Uninstall/Install/Reboot: Select whether you want the Desktop Management Agent installed or uninstalled. Select Reboot if you want the workstation to reboot after the operation is complete.
Features: Select the features you want installed or uninstalled. If you select Uninstall and all of the features, the ZENworks Desktop Management Agent will be uninstalled.
Middle Tier Address and HTTP Port: If you are using a ZENworks Middle Tier Server, specify the DNS name or IP address of the ZENworks Middle Tier Server that the Desktop Management Agent will be connecting to, then specify the HTTP or HTTPS port number that the Apache Web Server (NetWare) or the IIS Web Server (Windows) will use to listen for the Agent login.
If you are using the Novell Client, no Middle Tier address is required.
If no Middle Tier address is specified, the Agent Distributor verifies at installation time that a Novell Client is installed. The Agent Distributor does not install the Agent if the Middle Tier has not been specified.
Login Settings: These settings determine the ZENworks Middle Tier Server login options that are available in Workstation Manager.
Display Novell Login: Select this option to enable Middle Tier Server login to be displayed by the Workstation Manager.
Editable Middle Tier Address: Select this option to enable users to edit the Middle Tier Server address during login.
Application Launcher Settings: These settings apply to the Novell Application Launcher.
Limit Application Launcher to One Tree: Select this option to limit the Novell Application Launcher access to applications in one tree only. Specify the tree in the ZENworks for Desktops Tree field.
Launch on Windows Startup: Select the Novell Application Launcher view (Application Explorer or Application Window) that is added to the Windows Startup folder and launched when Windows starts. If you don't want to use the Windows Startup folder to start Novell Application Launcher, don't select either view.
Tree Settings: Use this field to specify the eDirectory tree to be used as the ZENworks tree. If Workstation Manager is installed, this tree becomes the tree where it looks for policies. If Limit Application Launcher to One Tree has been selected and Application Launcher is installed, this tree becomes the tree where it looks for applications.
When you are finished configuring the Desktop Management Agent options, click OK to save the settings and return to the ZENworks Desktop Management - Agent Distributor Utility dialog box.
Add the workstations where you want to deploy the Desktop Management Agent. To do so:
In the Target Workstations box, click Add to display the Browse for Domain dialog box.
This dialog box lists the domain that you are authenticated to as an administrator. If your workstation is attached to a domain that has trusts with other domains, those domains are also listed.
Select the domain that includes the workstations you want to add, then click OK to display the Select Workstation Using Active Directory dialog box.
NOTE: If you select a trusted domain, you are prompted to enter the domain administrator credentials.
The Search Results list displays all workstations that are located in the context displayed in the LDAP Context field. You can use the Browse button to change contexts. Changing contexts displays workstations contained in the selected context.
IMPORTANT: The data in Search Results list of the Agent Distributor is obtained from Active Directory. If you remove a workstation from the domain or directory but you do not remove the workstation from Active Directory using the Active Directory management tool, the Search Results list will be inaccurate.
In the Search Results list, select the workstations you want to add, then click Add.
Repeat Step 6.a through Step 6.c to add all the workstations where you want to deploy the Desktop Management Agent.
If you want to save your settings to a project (.pad) file for reuse another time, select File > Save As, specify the filename, then click OK.
The project file is saved in readable .ini format.
Click Deploy Agent to deploy the Management Agent to the selected workstations and display the Distributing ZENworks Desktop Management Agents to Target Workstations dialog box.
The dialog box displays deployment successes and failures. You can save a failure event to a project file (.pad) and open it from the File menu after you have corrected the problems with the failed workstations.
The Agent Distributor also keeps a log file (lastrun.log) that includes the list of successes and failures of each distribution attempt. The log file includes the same output that the deployment window displays, but it also includes start and end times. The file is saved in the same directory as agentdistributor.exe. A sample lastrun.log file is shown below.
============= Start time Thursday, April 01, 2004 11:32 AM ==============
Workstation SWILLIAMSDELL Successful
Workstation SWDESKPRO-W98 Successful
============= End time Tuesday, April 06, 2004 11:34 PM ================
============= Start time Friday, April 09, 2004 12:49 PM =================
Workstation testing6 Failed - Unable to contact workstation.
Workstation WILLIAMS2KSP3 Failed - Unable to map $Admin share drive.
============= End time Friday, April 09, 2004 12:49 PM =================
The Agent Distributor also copies an MSI debug file from each workstation and stores it at the root of the Windows drive under a \workstationlogs directory. This directory contains only the most recent log files; all files are deleted on the next attempt to distribute the ZENworks Desktop Management Agent. This debug file can help you to troubleshoot a deployment failure on a particular workstation. The name of the file is the workstation name with a .log extension (for example, c:\workstationlogs\williams2ksp3.log).