Among the biggest keys to using software tools effectively is properly installing them. Properly installing a software product enables you to get started faster and avoid problems later. This chapter focuses on helping you prepare to install ZENworks for Desktops and its components.
This chapter breaks the installation of ZENworks for Desktops into the following main sections. This breakdown helps you prepare and install the product fast and correctly:
• Prerequisites for installing ZENworks for Desktops
• Installing ZENworks for Desktops Server Components
• Installing ZENworks for Desktops Middle Tier Server Components
• Installing ZENworks for Desktops Management Agent on Workstations
The first step you should take to install ZENworks for Desktops is to make certain your network hardware and software meet the requirements. The following sections discuss the hardware and software requirements needed to install ZENworks for Desktops as well as pre-install checklists that you should perform to make certain you are ready to begin the install.
The following tables list both the hardware and software requirements that must be met on your NetWare and Windows servers before you can install ZENworks for Desktops. Taking the time to review the hardware and software requirements will help you resolve any deficiencies in your network and help eliminate problems during and after installation.
Table 2.1 contains the hardware and software requirements that must be met on NetWare 5.1, NetWare 6, and Windows NT/2000 servers to install the ZENworks for Desktops server software.
Table 2.2 contains the hardware and software requirements that must be met on NetWare 5.1, NetWare 6, and Windows 2000 servers to install the ZENworks for Desktops Middle Tier server software.
Table 2.2. ZENworks for Desktops Middle Tier Server Requirements
|
REQUIREMENT |
NETWARE 5.1 |
NETWARE 6 |
WINDOWS 2000 |
|---|---|---|---|
|
Minimum Free Disk Space |
160MB |
160MB |
160MB |
|
Processor |
Pentium III (minimum) |
Pentium III (minimum) |
Pentium III (minimum) |
|
RAM |
256MB or 1GB if scaled to 200 concurrent users |
256MB or 1GB if scaled to 200 concurrent users |
256MB or 1GB if scaled to 200 concurrent users |
|
Web Server |
Apache HTTP Server, version 1.3.22 |
Apache HTTP Server (shipping) |
Microsoft IIS Web Server |
|
Installed Software |
Novell Certificate Server version 2.20 |
Novell NetStorage |
N/A |
|
Software Updates |
NW51SP4.EXE (or later) patch applied |
N/A |
Windows 2000 Server Service Pack 2 |
Table 2.3 contains the hardware and software requirements that must be met on NetWare 5.1 and NetWare 6 servers to install the ZENworks for Desktops Inventory server software.
Table 2.3. NetWare Inventory Server Requirements
|
REQUIREMENT |
NETWARE 5.1 |
NETWARE 6 |
|---|---|---|
|
Novell eDirectory |
8 with Certificate Server v2.03 and LDAP |
8 with Certificate Server v2.03 and LDAP |
|
Support Pack |
3 |
N/A |
|
JVM |
1.3.1 (or later) |
1.3.1 (or later) |
|
JVM Disk Space |
105MB |
N/A |
|
Memory |
256MB |
512MB |
|
CPU Speed |
Pentium II |
Pentium II |
|
Inventory Disk Space |
35MB without database 50MB with database |
35MB without database 50MB with database |
|
ConsoleOne Disk Space |
70MB |
70MB |
|
Miscellaneous |
Valid IP address Long name support |
Valid IP address Long name support |
Table 2.4 contains the hardware and software requirements that must be met on NetWare 5.1 and NetWare 6 and Windows NT/2000 servers to install the ZENworks for Desktops Inventory server database.
Table 2.4. Inventory Server Database Requirements
|
REQUIREMENT |
NETWARE 5.1 AND NETWARE 6 |
WINDOWS NT/2000 |
|---|---|---|
|
Database |
Sybase ASA 7.0.1.1583 Oracle 8i can be used as an alternative |
Sybase ASA 7.0.1.1540 Oracle 8.1.5, 8.1.6, 8.1.7 MS SQL Server on Windows 2000 servers |
|
Memory |
256MB minimum 512MB recommended |
256MB minimum 512MB recommended |
|
CPU Speed |
Pentium III |
Pentium III |
|
Disk Space |
1.5GB leaf level 20GB root level (varies from 1-25GB) |
1.5GB leaf level 20GB root level (varies from 1-25GB) |
The following sections contain checklists that you should review prior to beginning the installation of ZENworks for Desktops server and Middle Tier software. These checklists help you ascertain whether your network is ready for the install.
• Make and archive a reliable backup!
• Make sure that all of the hardware and software requirements are met. In particular, make sure that the recommended version of ConsoleOne is installed on the server where you will install the ZENworks for Desktops server software.
• Make sure you have Admin rights to all NetWare servers where you will install ZENworks for Desktops server software.
• Make sure you have Admin rights to extend the directory schema.
• Make sure that the workstation from where you will run the installation program is authenticated to the server or servers where you are installing the software.
• If you are installing on a NetWare server, you need to unload JAVA.NLM by executing the java -exit command.
• Exit any program that uses files in the SYS:PUBLIC directory on any server where you will be installing ZENworks for Desktops server software.
• Exit any Windows programs on the network workstation from which you will be running the installation program.
• Set your screen display for 1024×768.
• Novell Client must be installed on the workstation or server where you will be running ConsoleOne for administering the ZENworks for Desktops server.
• A Windows 2000 workstation or server is recommended for running the ZENworks for Desktops server installation.
• Uninstall any third-party remote control agent or remote control application running on the managed workstation.
• Associate the Remote Management policy settings for the managed workstation.
• Ensure that you have installed Novell Certificate Server and LDAP on the NetWare server that will be your Inventory server.
• Stop Sybase Adaptive Server Anywhere by typing Q at the Sybase console prompt.
• Use top-down deployment for Inventory installation.
• Verify that the hardware and software requirements in Table 2.2 are met on the servers you are planning to install the Middle Tier server components on.
• On NetWare 5.1 and NetWare 6 servers, edit the ThreadsPerChild APACHECONFADMINSERVER.CONF file. You should change the value from the default of 50 to 512.
Once you have reviewed the hardware and software requirement and completed the pre-install checklist for the servers you plan to install ZENworks for Desktops on, you can begin the installation procedure to install the ZENworks for Desktops server components as outlined in this section. The following sections detail the steps to install the ZENworks for Desktops server components.
The first step to installing the ZENworks for Desktops server components is to log in to the eDirectory tree as Admin or as a user with supervisor rights to the NetWare servers and eDirectory containers where you want to install ZENworks for Desktops.
Once you are logged in as Admin or an Admin equivalent, you are ready to launch the ZENworks for Desktops install. The ZENworks for Desktops installation CD-ROM is supplied with an auto-run feature, which is automatically launched when you insert the CD-ROM into your client. You can also start the install by executing the WINSETUP.EXE file on the root of the CD-ROM.
To install the ZENworks for Desktops components on servers in your tree, select New Install, Install ZENworks for Desktops Server from the main install screen. This will launch the install for the ZENworks for Desktops server components.
The first screen you will see in the ZENworks for Desktops Server install is the welcome screen. Read the contents and click Next to continue.
The second screen you will see is the license agreement screen. Read the license agreement and select the Accept button if you agree to the terms. Click Next to continue.
The next screen you will see is the verification screen reminding you of the requirements that must be met to install ZENworks for Desktops server components. Review the requirements one last time and click Next to continue.
The next screen in the install is the tree selection screen, shown in Figure 2.1. This screen enables you to specify which tree you want to install ZENworks into. The ZENworks for Desktops install can install ZENworks to only one tree at time. Therefore, if you are authenticated to multiple trees, you must select one tree to update with ZENworks schema extensions, programs, and files.
To select a tree, click the Browse button and find the tree you want to use. You can log in to the tree, if you are not already authenticated, by clicking the login button and entering the login information.
If you have not already extended the schema on this tree, check the Extend schema option to have the install do it prior to installing the software and creating eDirectory objects. Once you are finished selecting the tree, click Next to continue.
The next screen in the install is the ZENworks for Desktops server component selection screen, shown in Figure 2.2. This screen enables you to specify which ZENworks for Desktops components you want to install on your network.
Select which of the following components you want to install and then click the Next button:
• Application Management—Installs the desktop software distribution components and creates Application objects on the eDirectory.
• Automatic Workstation Import—Installs the programs and files necessary to complete the automatic workstation import to the servers.
• Workstation Imaging—Installs the programs and files necessary to perform workstation management functions.
• Remote Management Tools—Installs the programs and files necessary to manage workstations remotely.
• Workstation Inventory—Installs the programs and files necessary to inventory workstations.
• Workstation Management—Installs the workstation manager on the selected servers. This option allows you to have DLU and workstation policies and applications.
• Sybase Database—Installs Sybase to the selected servers and sets up the database for workstation inventory management.
The next screen in the install is the ZENworks for Desktops server selection screen, shown in Figure 2.3. You can select which servers to install ZENworks for Desktops to by clicking the Add Servers button and selecting NetWare and Windows servers.
You do not need to install ZENworks to every server in your tree, just the ones that ZENworks for Desktops server components will be used on.
Once you have selected which servers you want to install ZENworks for Desktops on, you need to define which of the following components should be installed and then click Next to continue:
• ConsoleOne Snapins—Installs the ZENworks for Desktops snap-ins to the SYS:PUBLICMGMTCONSOLEONE1.2SNAPINS directory.
• Import—This server automatically imports workstations, but does not remove them. There must be at least one import server.
• Removal—This server removes workstations, but does not import them. This server type is optional. However, you should have at least one removal server if your workstation count changes very much.
• ZEN Preboot—Installs components for ZENworks for Desktops Preboot Services.
• XML Proxy Service—Installs the XML proxy service on the server if you are planning on configuring a proxy server to roll up and scan data that is across a firewall.
The next screen in the install, if you selected the workstation inventory component, is the Inventory installation screen, shown in Figure 2.4. This screen enables you to set the volume and path to install the workstation inventory files and database to.
To set the path, select the server in server list and then click the Browse button or simply specify a path that exists on that server. Once you have set the path for all servers, click the Next button to continue.
The next screen in the install, if you selected the XML Proxy service component, is the XML Proxy service configuration screen, shown in Figure 2.5. This screen enables you to set the volume and path as well as the port that the XML Proxy service will use.
To set the path and port, select the server in the server list, set the port number and then click the Browse button or simply specify a path that exists on that server. Once you have set the path for all servers, click the Next button to continue.
The next screen in the install, if you selected the remote management component, is the remote management installation screen. This screen enables you to set the volume and path to install the workstation remote management components to.
To set the path, select the server in the server list and then click the Browse button or simply specify a path that exists on that server. Once you have set the path for all servers, click the Next button to continue.
Once you have completed the setup options, you see the summary screen as shown in Figure 2.6. This screen shows you the product components you selected and the servers that they will be installed on. If you need to make any changes you can click the Back button; otherwise, click Finish and the ZENworks for Desktops install performs the tasks listed in the following sections.
The ZENworks for Desktops install checks for available disk space on the servers you requested to install to. If there is insufficient disk space, you can proceed. The ZENworks for Desktops install installs some files that already exist on the server. The older files are overwritten. Therefore, there may be enough disk space to install ZENworks for Desktops even if the available showing is less than needed.
The ZENworks for Desktops install also checks the DS schema for problems prior to updating it. If no problems are found, the schema is extended to include new objects and attributes necessary for the components you selected to install.
Once the file system, schema, and DS objects are checked and any problems are resolved, the ZENworks for Desktops install copies the files to each server selected in the previous menu in sequential order. A status screen lets you know which server is being installed and a percentage of progress to completion. Once the file copy is done you can click the Finish button. The ZENworks for Desktops server component install is complete.
All problems with the file system, schema, or DS objects are reported in a log file that can be displayed once the installation is complete. You can review the log file and correct any errors and re-install necessary components.
Once you have verified the hardware and software prerequisites for the servers you plan to install the ZENworks for Desktops Middle Tier Server components to, you can begin the installation procedure to install the Middle Tier server components as outlined in this section. The following sections detail the steps to install the ZENworks for Desktops server components.
To install the ZENworks for Desktops Middle Tier server components on servers in your tree, you need to authenticate to the tree and start the install as described the ZENworks for Desktops Server install section. Once you have started the install, select New Install, Install ZENworks Middle Tier Server from the main install screen. This will launch the install for the ZENworks for Desktops Middle Tier server components.
The first screen you will see in the ZENworks for Desktops Middle Tier server install is the welcome screen. Read the contents and click Next to continue.
The second screen you will see is the license agreement screen. Read the license agreement and select the Accept button if you agree to the terms. Click Next to continue.
The next screen you will see is the verification screen reminding you of the requirements that must be met to install ZENworks for Desktops Middle Tier server components. Review the requirements one last time and click Next to continue.
The next screen in the install is the server selection screen, shown in Figure 2.7. This screen enables you to specify which servers you want to install the ZENworks for Desktops Middle Tier components to. You can select which servers to install ZENworks for Desktops Middle Tier components to by clicking the Add Servers button and selecting NetWare and Windows servers.
Once you have selected which servers you want, you need to define the following primary eDirectory tree information for each server:
• DNS Name or IP Address of eDirectory Server and Context—Specify the DNS name or the IP address and the eDirectory context of a NetWare or Windows server that has the ZENworks for Desktops Server components installed on it. Use the following format:
<dns_name_or_ip_address>:<context> i.e. ZfD_Server.novell.com:xAccess.novell
• Full DN and Password of Admin User—Specify the full username and password of a user who has admin rights to the server.
Once you have configured the primary eDirectory tree information for each server, click Next to continue.
Once you have completed the setup options, you see the summary screen as shown in Figure 2.8. This screen shows you servers you selected and the primary eDirectory tree info you specified for each. If you need to make any changes, you can click the Back button; otherwise click Finish. The ZENworks for Desktops Middle Tier server install will install the components to the servers you specified.
Once the ZENworks for Desktops Middle Tier server install is complete, you should perform the following checks on the network:
• Allow Clear Text Passwords—Make certain that the servers you specified in the primary eDirectory tree info section of the install have the Allows Clear Text Passwords option enabled.
• IP Address—If you are running the Apache Web server on a secondary IP address on your NetWare 6 server, make certain that the add secondary IP address lines are placed towards the top of the SYS:SYSTEMAUTOEXEC.NCF file instead of at the bottom.
• Reboot Middle Tier Server—You must reboot the NetWare or Windows servers that you installed the Middle Tier software on.
• Check Middle Tier Server—Check that the Middle Tier Server is running by entering the following address in your Web browser:
http://<dns_name_or_IP_address_of_Middle_Tier_Server>/oneNet/zen
The ZENworks for Desktops management agents must be installed on each workstation that you want to distribute applications to, remotely manage, or maintain inventory for. The following sections discuss running the install for the management agent for the first time. This agent creates an install record that you can use to distribute the management agents to your workstation through NAL or as a silent install from a central network location.
You can start the management agent install by running SETUP.EXE from the AGENTINSTALL directory on the CD-ROM, or from the \SYSpubliczenworks directory on the ZENworks for Desktops server. Use the /r parameter to instruct the install to record the settings in the SETUP.ISS file located in the Windows or WINNT directory of the workstation. You can also use the /f1 parameter to specify your own path and filename for the .ISS file. For example:
setup /r /f1"c: empstandard.iss"
The first screen you will see in the ZENworks for Desktops management agent install is the welcome screen. Read the contents and click Next to continue.
The second screen you will see is the license agreement screen. Read the license agreement and select the Accept button if you agree to the terms. Click Next to continue.
The next screen you will see is the destination screen, which enables you to specify where to install the agents. Keep in mind that if you specify a drive other than C:, workstations with only a C: drive will be unable to use the .ISS file. Browse to the path you want workstations to use and click Next to continue.
The next screen is the ZENworks for Desktops workstation component selection screen, shown in Figure 2.9. This screen enables you to specify which ZENworks for Desktops components you want to install on your workstations.
Select the following components you want to install and then click the Next button:
• Application Management—Installs the Application Launcher agent and software to the workstation, thus allowing it to receive application distributions.
• Workstation Manager—Installs the agent and files to allow administrators to import, configure, and manage the workstation using eDirectory.
• Workstation Imaging—Installs the agent and drivers necessary for ZENworks to create and maintain an image of the workstation.
• Remote Management Tools—Installs the agents and files necessary to manage the workstation from a remote console.
• Workstation Inventory—Installs the agent and scan utilities necessary to scan the workstation for hardware and software inventory data.
The next screen in the install is the Middle Tier server selection screen, shown in Figure 2.10. This screen enables you to specify which Middle Tier server the ZENworks for Desktops agent will use to connect to the network. Set the DNS name or the IP address of the Middle Tier server and click Next to continue.
The next screen in the install, if you are installing on a workstation without the Novell Client, is the Workstation Manager settings screen. This screen enables you to specify how the workstation manager behaves on the workstation through the following settings:
• Display ZENworks Middle Tier authentication dialog box—Enabling this option displays the Middle Tier authentication dialog box whenever a user logs in or tries to access a resource that requires authentication. This dialog box will replace the standard Microsoft login dialog box. If you leave this check box blank, ZENworks will log in in the background and the standard Microsoft login dialog box will pop up on the workstation.
• Let users change the ZENworks Middle Tier Server address on authentication dialog box—Enabling this option allows the users to specify the IP address or DNS name of the Middle Tier server they want to authenticate to. If you are restricting access through specific Middle Tier servers, disable this option. However, if you need to give users dynamic access to resources that lie beyond different Middle Tier Servers, enable this option.
Once you have set the options correctly, click Next to continue.
The next screen in the install is the Novell Application Launcher/Windows Startup options screen, shown in Figure 2.11. This screen enables you to specify how you want Novell Application Launcher (NAL) to behave on startup:
• Launch Application Explorer—Enabling this option starts the Novell Application Launcher when the workstation is booted. Use this option if you have updates that you want to periodically install on user workstations as soon as they are booted, for example, when updating anti-virus software. Any pending applications that are associated with the workstation or user will be executed.
• Launch Application Window—Enabling this option launches the application window when a user logs in. This gives the users easy access to their applications as soon as they log in.
• None—If you do not select either of the two options, the workstation will boot normally and the users must access the Application Explorer and Application window through the Program menu. Use this option if you are trying to impact users minimally.
Figure 2.11. Novell Application Launcher/Windows Startup options selection screen for the ZENworks for Desktops Management agent install.
Once you have set the options correctly, click Next to continue.
Once you have completed the setup options, you see the summary screen. This screen shows you the settings that you have selected for the management agent install. If you need to make any changes, you can click the Back button; otherwise click Next. The ZENworks for Desktops management agent will be installed on the workstation. Once the agent has been installed on the workstation, you will be prompted to either reboot the workstation immediately or to wait. The workstation must be restarted in order to activate the agents.
After you run the initial install and create an .ISS file, you can automate future installs by using the .ISS file to create an application object, or enable users to run a silent install from the network or other source. The following sections discuss how to use the ISS file to automate the Management agent install.
The easiest and fastest way to install the ZENworks for Desktops management agent on workstations is to create an Application object and distribute it. This works only when the workstations already have the Novell Client and Application Launcher running on them.
Use the following steps to create an Application object for the management agent and to distribute it to users who are currently running Application Launcher:
-
Create a network directory for the management agent source files.
-
Copy
AgentInstallSETUP.EXEand the .ISS file you created into the source file directory. -
Create a simple Application object (no .AOT/.AXT/.MSI file).
-
Modify the command line of the application object to include the
/soption. This option tells the install to use an .ISS file and to not display dialog boxes. For example:
setup.exe /s /f1"E:WAGENTSETUP.ISS" -
Define the system requirements for the workstation to receive the distribution.
-
Add the Source directory you created in step 1 to the application object.
-
Associate the Application object with the users and workstations that you want to receive the Management agent install.
-
Set the Run Application Once option and schedule the distribution.
-
Save the Application object settings by clicking Finish.
Note
The install will run in silent mode using the /s option. Instead of displaying errors to the screen, errors will be saved to a SETUP.LOG file in the same directory as the .ISS file. You can specify a different log file by using the following option on the setup command line: /f2"<path_and_filename>".
If you need to install the ZENworks for Desktops management agent on workstations that do not have Application Launcher running on them, you need to make the SETUP.EXE application and the .ISS file you created available to the user from a different source. There are many ways to do this:
• You can create a directory on the network that those workstations have access to and copy the SETUP.EXE and .ISS files to it. The workstations can then copy the files.
• You can Zip the files up and e-mail them to users and they can extract them to their local workstations.
• You can also create an install CD containing the files and distribute the CD to users so they can copy the files to their local workstations.
• You can also deliver SETUP.EXE through a Web browser. For example, you can copy SETUP.EXE to the root of your Web server. You then edit the MYAPPS.HTML file that is created automatically by the Middle Tier installation so it replaces the ZFDWEBSW.EXE with SETUP.EXE.
Once the files are installed on the local workstation, the users will need to run the setup using the /s option and use the .ISS file settings. For example:
setup.exe /s /f1"c:clientsetup.iss"