Desktop Management Server Installation Prerequisites
Before you can install Desktop Management Services, there are several prerequisites that must be met. This section contains the prerequisite information you need.
- Make sure that you have made and archived a reliable backup of the server.
- Make sure that the recommended version of ConsoleOne is installed on the server where you will install the Desktop Management Server software.
- Make sure that you have Admin or equivalent rights to eDirectory on all servers where you will install the Desktop Management Server software.
- Make sure that you have Admin or equivalent rights to extend the directory schema.
- If you will be installing to a NetWare server, unload java.nlm (at the Server Console, type java -killall, then type java -exit). Make sure you do this when Java* is not being used by another process and the proper Java components have already been installed.
- Exit any program that uses files in the sys:public directory on any server where you will be installing Desktop Management Server software.
- The display on the workstation you use to install or administer the Desktop Management Server software must be set at a resolution of 1024 x 768. Installing with the display set at 800 x 600 will make the resolution of the installation and ConsoleOne screens too large for displaying important information.
- If you choose to install Desktop Management Server software on a Windows server, make sure that you close the Service Control Manager window.
- If you choose to install Desktop Management Server software from a Windows 2000/XP workstation to a Windows 2000/2003 server, the workstation should be authenticated to both eDirectory and as the local or domain administrator of the Windows server you will be installing to.
- If you will be installing the Inventory Server component, make sure that the name of the server where you will install the Inventory server and the tree where the server resides does not contain "#".
The Desktop Management Server installation program lets you install any of the Desktop Management components individually (or in a grouping of your choice) on the servers you select. For more information about these components, see What Is ZENworks Desktop Management?.
If you know that you want to use only certain Desktop Management components, this can save time and server space. The following components can be individually selected:
Desktop Management Services
- Application Management
- Workstation Management Common Components
- Remote Management
Additional Options
- Desktop Management Database
- Inventory Database
- Inventory Server
- Inventory Proxy Server
- Imaging Server
- PXE Server
- Workstation Import/Removal Server
- Desktop Management Services Snap-ins
If you choose to install Remote Management:
- Make sure you have administrator rights to install the Remote Management Agent.
If you choose to install Workstation Inventory:
- Do not install the Workstation Inventory component of the Desktop Management Server software and the ZENworks Middle Tier Server software on the same Windows 2000 server.
- Stop Sybase Adaptive Server Anywhere.
On NetWare: Enter Q at the Sybase console prompt.
On Windows 2000: In the Control Panel, double-click Administrative Tools > Services, select Novell Database - Sybase, then click Stop.
- Use top-down deployment for Inventory installation. Always begin the installation at the topmost-level server and proceed with the next lower-level servers. For example, in an inventory setup with a Root Server and a Leaf Server, complete the inventory installation at the Root Server, and then run the installation for the Leaf Server.
- Make sure that the servers where you want to install the Desktop Management Inventory server and the Database components have a valid DNS name configured. Also, make sure that the workstation you will use for installing Desktop Management Server software is properly configured to perform DNS lookup.
If the servers do not have a DNS name, you must select an IP address for the server during Desktop Management Inventory policy configuration. For more information about configuring a server IP address or DNS name, see Configuring the Inventory Database Object on a NetWare Server.