Use the following information if you are performing a new installation of ZENworks 7 Desktop Management with Support Pack 1 in a Windows environment:
The following Windows network setup is assumed for the back end of this sample Windows environment:
A Windows Server 2003 (SRV-01), to serve as the Active Directory Domain Controller of an Active Directory domain.
The ZENworks 7 Middle Tier Server with SP1 installed on a Windows Server 2003 server (SRV-02) where Microsoft IIS is installed. This server must be in the same domain as the Active Directory Domain Controller. It can be the same server that has ZENworks software installed, but you should consider keeping the IIS server independent to minimize performance issues. You must also keep it on a separate server from the Password Synchronization Module in Identity Manager.
The ZENworks 7 Desktop Management Server with SP1 installed on a Windows Server 2003 (SRV-03) with Novell eDirectory, the Novell Client, Novell ConsoleOne, Identity Manager 3 Bundle Edition, and Novell iManager 2.6 installed. This server must be in the same domain as the Active Directory Domain Controller, but it is not the domain controller.
For information about the user workstation configuration options for ZENworks in a Windows environment, see ZENworks Desktop Management User Workstation Configuration Options.
ZENworks Desktop Management can run on user workstations using either the Novell Client or by using two other non-client modes:
It is assumed that in a Windows network environment, the Novell Client is not used on user workstations; therefore, you need to decide on the features you need in your network and configure ZENworks Desktop Management for your users in one of the non-client modes.
In this mode, a single Application Browser View is delivered when a user connects to IIS and opens the application page (myapps.html) provided by ZENworks Desktop Management. The Web view is automatically installed on the workstation if the user has rights to install applications locally.
The Application Browser mode can deliver applications to the workstation only when the user connects to a personalized application Web page. Dynamic local user account creation, hardware and software inventory, automated imaging services, and remote management capabilities are not included in this mode.
In Full Desktop Management Agent mode, all of the Desktop Management components are installed on the workstation by an administrator, as part of an image, or by the user. By including all of the Desktop Management components in the Desktop Management Agent installation, you provide your users all of the capabilities that ZENworks Desktop Management has to offer.
If you want to create a Dynamic Local User account on the workstation, you can configure the Desktop Management Agent to prompt the user to log in to eDirectory prior to the local login to Windows. When the agent has this configuration, the user is prompted for an eDirectory user name and password (which should be the same as the Active Directory account, because the two accounts are being synchronized by Identity Manager 3), then ZENworks Desktop Management creates a local account on the workstation if one is not present and logs the user into Windows with the provided username and password.
If you do not require Dynamic Local User account creation, ZENworks silently passes Novell user credentials to Windows when the user logs into the workstation if that user already has an account on the workstation (the user does not need an account on the workstation if he or she is logging in to Active Directory and the workstation is part of the Active Directory domain). The Desktop Management Agent then connects to eDirectory using the provided username and password in order to distribute applications to the user.
NOTE:With the Desktop Management Agent installed on the workstation, you might still choose to deliver applications through the browser view only.
ZENworks 7 Desktop Management with Support Pack 1 requires the following software in this sample Windows network:
Installed on one Windows Server 2003 (SRV-02) in a Windows domain:
Microsoft IIS Web Server
Installed on a second Windows Server 2003 (SRV-03):
Novell Client 4.91 SP2 (or higher) for Windows 2000/XP/2003, necessary for installing ZENworks (not otherwise installed in a Windows network)
You can download the client from the Novell Download Web site.
The following software is available on The Novell ZENworks 7 with Support Pack 1 Companion 1 CD:
eDirectory 8.8 (or later)
Novell ConsoleOne 1.3.6e (or later) for managing ZENworks resources in eDirectory
Novell iManager 2.6 for configuring and administering the Identity Manager drivers.
The following software available on The Novell ZENworks 7 with Support Pack 1 Companion 2 CD
Novell Identity Manager 3 Bundle Edition to synchronize eDirectory resources with Active Directory
The Identity Manager (IDM) engine provides the ability to synchronize eDirectory data with any outside data service. The IDM engine has several drivers that describe how output and input should be sent between data sources.
The driver for Active Directory is specifically designed to synchronize data between Novell eDirectory and Microsoft Active Directory. The synchronization is bidirectional; you determine whether information should flow to and from both directories, or whether information should flow only from one directory to the other.
Many Identity Manager drivers are available for installation on Windows Server 2003 for synchronization with other data sources such as PeopleSoft, JDBC, any LDAP directory, Lotus Notes, SAP HR, and WebSphere MQ. For information about other drivers, see the Novell Identity Manager Web site or the Identity Manager Drivers Guides.
IDM architecture uses a publisher/subscriber model. In this model, the publisher's responsibility is to place information into eDirectory while the subscriber places changes from eDirectory into the external, synchronized data source. The behavior of the publisher and subscriber and the attribute mapping are determined by a set of rules that are part of the driver. Drivers can be customized through XML rules to deliver nearly any data configuration you want.
For more details about how IDM can be configured, see the Novell Identity Manager 3 documentation Web site.
For information about licensing IDM 3, see Activating the Identity Manager 3 Bundle Edition.
The Novell ZENworks 7 with Support Pack 1 Companion 2 CD includes Novell Identity Manager 3 Bundle Edition. For more information about activating the bundle, see Section D.0, Using Identity Manager 3 Bundle Edition for ZENworks 7 with SP1.
When you install ZENworks in a Windows network environment/Active Directory test environment, you need perform the following tasks in order:
An actual enterprise environment might include many servers used for a variety of things, such as application execution, terminal services, and so on. This section uses the following small-scale Windows network configuration as a sample test lab environment:
A Windows Server 2003, to serve as the Active Directory Domain Controller of the ZENDEMO domain. This server is designated as SRV-01.
A Windows Server 2003 with the IIS Web Server also installed. The server also needs Novell eDirectory, the ZENworks Desktop Management Server, Novell iManager, and Identity Manager 3 Bundle Edition (including Password Synchronization) installed. This server is a member of the ZENDEMO domain. It is designated as SRV-02.
A Windows Server 2003, where the ZENworks Middle Tier Server is installed. It is designated as SRV-03.
A Windows XP Professional SP1a (or later) workstation, which will operate in the Desktop Management Agent mode (that is, where all components of the Desktop Management Agent are installed). This workstation is designated as WKS-01.
A Windows XP Professional SP1a (or later) workstation where the Application Browser View of the Novell Application Launcher is installed. This workstation is designated as WKS-02.
NOTE:This is a sample configuration only to be used as a test environment. For information about the server platforms and user workstations that are supported, see Section 8.0, Platform Support for the Desktop Management Infrastructure and Section 6.0, User Workstation Requirements.
As you set up ZENworks 7 with SP1 in a Windows network environment, you need to access the first two Novell ZENworks 7 with Support Pack 1 Companion CDs.
You can access the contents of the Companion CDs through the installation program. To do so, insert any Novell ZENworks 7 with Support Pack 1 CD into the CD drive of a Windows workstation. The installation program should run automatically. If it does not, run winsetup.exe from the root of the CD. Click , insert the CD you are prompted for (if needed), then browse for the component you need on one of the two menu pages.
You need the following components from the Companion CDs:
Novell Identity Manager 3 Bundle Edition, available on the Novell ZENworks 7 with Support Pack 1 Companion 2 CD. The IDM 3 installation program (install.exe) is available on the Novell ZENworks 7 with Support Pack 1 Companion 2 CD in the \nsure identity manager 3 bundle edition\nt directory.
Novell eDirectory 8.8.1 for Windows Server 2003. The self-extracting .zip file (edir_88_win.exe) containing the eDirectory 8.8.1 installation program is available on the Novell ZENworks 7 with Support Pack 1 Companion 1 CD in the \novell edirectory for windows 2k directory.
Novell ConsoleOne 1.3.6e. The ConsoleOne installation program (c1.exe) is available on the Novell ZENworks 7 with Support Pack 1 Companion 1 CD in the \novell consoleone directory.
Novell iManager 2.6. The .zip file (iman_26_nw65_standalone.zip) containing the iManager 2.6 installation program is available on the Novell ZENworks 7 with Support Pack 1 Companion 1 CD in the \novell imanager\program files\installs\win directory.
We recommend that you install the latest Novell Client for Windows, which is available for download from the Novell Product Download web site
To download the client:
Download the client self-extracting file to a temporary directory.
In the temporary directory, double-click the file and specify the path where you want the files to be extracted.
A specific directory structure will be created in the path you specify.
Click
and follow the on-screen instructionsTo install the client, follow these instructions:
Double-click setupnw.exe in the download_location\winnt\I386 directory.
In the Novell Client license agreement dialog box, click
.(Conditional) If you do not agree with the terms of the license agreement, do not install the software. Click
.Select
, then click .Verify that only the client is selected on the modules list, then click
.Verify that
and are selected and that is deselected, then click .Select
and (if present), then click .Select
to instruct the client to default to using NDS connections, click , then click .When the installation is finished, select
.NOTE:The bundling of eDirectory 8.8.1 with ZENworks Suite 7 with Support Pack 1 constitutes a valid license; that is, when you license ZENworks, you also license eDirectory.
To start the eDirectory installation program for the SVR-02 server in your Windows network environment test system:
Log onto the SVR-02 Windows Server 2003 as administrator and launch the eDirectory installation program from the Novell ZENworks 7 with SP1 Companion 1 CD (see Accessing Software on the ZENworks 7 with SP1 Companion CDs). The CD should autorun. If not, run winsetup.exe located at the root of the CD.
Select c:\edir88 directory to unzip the files, then click when the files are extracted.
, select to launch a program that unpacks the eDirectory installation files into a specified directory, specify theBrowse to the c:\edir88\nt directory and launch setup.exe, then click .
At the eDirectory Installation Welcome dialog box, click
.Read the license agreement, then click
if you agree with the terms of the license agreement.(Conditional) If you do not agree with the terms of the license agreement, do not install the software. Click
.Select a language for the installation, then click
.Click
to accept the default installation path. If the path has not been created previously, the installation program prompts you for authorization to do so.Click
to create the new directory.Click
to accept the default installation path for the location of a new Directory Information Base (DIB). If the path has not been created previously, the installation program prompts you for authorization to do so.Click
to create the new directory.Select
, then click .Set up the access to the new tree and server.
Specify a name for the new tree, such as ZENTREE.
Specify a Server object context, such as SVR-02.SERVICES.ZEN.
This document assumes that you are creating an Organization container in eDirectory named ZEN, an Organizational Unit container named SERVICES where SVR-02 will reside, and an Organizational Unit container named USERS where the Admin user object will reside.
Specify the name of the Admin user object, such as Admin.
Specify the password of the Admin user object, such as Novell, then click
.On the HTTP Server Port Configuration page, accept the HTTP Stack Ports as default, because there will be no conflicting ports on this server, then click
.On the LDAP Configuration page, specify which LDAP ports to use.
When Active Directory and eDirectory are installed on the same Windows server, you need to choose other LDAP ports, because eDirectory must not interfere with default Active Directory ports 389 and 636.
Change the
number to 388, then change the to 635.Deselect
to allow password synchronization to function, then click .Click
to accept the default NMAS login method.Click
to complete the eDirectory installation.The eDirectory installation program performs the installation on the SRV-02 server. When the program completes successfully, click
in the Success dialog box.When the eDirectory installation is complete, you need to manually install ConsoleOne on SRV-02.
Insert the Novell ZENworks 7 with Support Pack 1 Companion 1 CD into the CD drive of SRV-02 (see Accessing Software on the ZENworks 7 with SP1 Companion CDs). If the CD does not autorun, run winsetup.exe from the root of the CD.
Select
, then select .In the WinZip self-extractor dialog box, click
to launch the extraction and to start the ConsoleOne installation program.On the ConsoleOne Installation Wizard welcome page, click
.Read the License agreement, then click
if you agree with the terms of the License Agreement.(Conditional) If you do not agree with the terms of the license agreement, do not install the software. Click
.Accept the default installation path, then click
.Accept the default components for installation, then click
.On the Additional Languages page, select any additional languages you want to install, then click
.Read the JInfoNet Licensing Agreement page, then click
if you agree with the terms of the license agreement.(Conditional) If you do not agree with the terms of the license agreement, do not install the software. Click
.On the ConsoleOne Installation Summary page, click
to install ConsoleOne 1.3.6e on the SRV-02 server.On the ConsoleOne Installation Success page, click
.The iManager 2.6 tool is required for configuring Identity Manager 3 drivers, which are used to synchronize Active Directory and eDirectory.
NOTE:We recommend that you install Novell iManager on a server where the Microsoft IIS Web server has already been installed. Although iManager can run on Windows 2003 servers without IIS installed, the absence of IIS requires that you install the Apache Web server with the Tomcat servlet.
When the eDirectory installation is complete, you can manually install and set up Novell iManager 2.6 on SRV-02.
Insert the Novell ZENworks 7 with Support Pack 1 Companion 1 CD into the CD drive of SRV-02. If the CD does not autorun, run winsetup.exe from the root of the CD.
Select
, then select .On the Novell iManager Installation Wizard welcome page, click
.On the iManager Introduction page, click
.Read the License agreement, click
if you agree with the terms of the License Agreement, then click .(Conditional) If you do not agree with the terms of the license agreement, do not install the software. Click
.On the Detection Summary page, make sure that the IIS Web server is already installed (version 6 on Windows Server 2003), visually check the other default values, then click
.If the IIS Web server is not already installed, the iManager installation program installs the Apache Web server with the Tomcat servlet.
On the Choose Install Folder page, accept the default on the installation path, then click
.On the Get User and Tree Names page, fill in the fields:
Username: Specify the username and context (for example, admin.users.novell) of the administrative account with which you will configure iManager and its modules.
Tree Name: Specify the name of the eDirectory Tree that iManager will primarily manage, for example ZENTREE.
On the Pre-Installation Summary page, click
.On the Install Complete page, click
to finish the iManager installation on the SRV-02 server.Use the following steps to complete the setup of iManager for launching:
From the Windows desktop, double-click the Novell iManager shortcut to launch Internet Explorer and display the Getting Started with Novell iManager help page.
In Internet Explorer, click
> to open the Internet Options dialog box.From the Internet Options dialog box, click
, click , then click to open the Trusted Sites dialog box.In the server_IP_address), click , click , then click to open the iManager Login page.
field of the Trusted Sites dialog box, specify the URL of SRV-02 (for example, http://From the iManager Login page, make sure the
, or is supplied, then enter the user password to launch iManager.From the iManager Home page, click the View Objects icon, then click the
tab in the left pane to locate the tree (ZENTREE) and to verify that the Admin object and the server are present.When the installation of eDirectory and iManager is complete, verify that the tree is viable:
Log in to eDirectory.
From the Windows server desktop, right-click the red N in the taskbar and select N
.Type Admin in the field.
Type novell in the field.
Click Advanced to open the NDS page of the login dialog box.
Type ZENTREE in the field.
Type USERS.ZEN in the field.
Type SRV-02 in the field, then click to log in to eDirectory.
To verify that you are logged into the tree as Admin, right-click the red N in the taskbar, select
, verify that a resource is listed for ZENTREE and for the username (CN=Admin).The authentication state for this connection should be listed as
.Click
to close the NetWare Connections dialog box.Create a shortcut on your server for c:\novell\nds\ndscons.exe.
NDSConsole is a utility that lets you view the state of the eDirectory tree and the services that are running.
Click the NDSConsole shortcut, then verify that at least ds.dlm and nldap.dlm are running.
You now have an eDirectory tree running on your Windows Server 2003.
When eDirectory is running and stable, you need to install Novell Identity Manager 3 Bundle Edition (IDM 3) with the proper drivers so that users can be synchronized between your Active Directory Domain and eDirectory.
Before you install IDM 3, make sure you read and understand the information included in Section C.0, Using the Identity Manager Bundle 2 Edition for ZENworks 7 Desktop Management.
IMPORTANT:Make sure that no ZENworks services are running on the Windows server when you install IDM 3.
Log on to the SRV-02 Windows Server 2003 as administrator and into eDirectory as admin.
Insert the Novell ZENworks 7 with Support Pack 1 Companion 2 CD into the CD drive of SRV-02, then use Windows Explorer to browse to the \nsure identity manager 3 bundle edition folder.
Double-click setup.bat to launch the IDM 3 installation program.
On the Identity Manager Welcome page, click
.Read the License agreement, then click
if you agree with the terms of the license agreement.(Conditional) If you do not agree with the terms of the license agreement, do not install the software. Click
.On the Identity Manager Overview page, click
twice.On the component selection page, select
, select , deselect , then click .On the
page, click , select , select (in the list), then click .(Conditional) On the Identity Manager Warning: Activation Notice dialog box, you are reminded to license Novell Identity Manager. Click
.If you continue without activating the license, these components function only for a 90-day evaluation period. A license for the Metadirectory engine and Active Directory driver is included as part of the overall ZENworks 7 with SP1 license. If you choose not to activate the license, you can return and do so later.
(Conditional) In the Password Synchronization Upgrade Warning dialog box, you are informed that older versions of Password Synch need to be upgraded. Read the information in the dialog box if applicable, then click
.On the Schema Extension page, verify that the tree is appropriate (ZENTREE), type or browse to and select the fully distinguished name (DN) of the admin user and the user's password (admin user name is CN=admin,OU=Users,O=ZEN), then click
.On the
page, retain the selected defaults, then click .Read the Summary page, then click
.In the Installation Complete dialog box, click
for DirXML to finish the installation.Reboot the server to allow the drivers to be properly registered.
When you have finished installing the Novell Identity Manager 3 Bundle Edition, you must configure the Identity Manager drivers before synchronization can occur. For more information, see Configuring Identity Manager Drivers.
When you have finished installing eDirectory and Identity Manager on the SRV-02 server, you need to configure the Identity Manager drivers to begin synchronization between Active Directory Domain and eDirectory.
Log on to the SRV-01 server as the Active Directory administrator.
Insert the ZENworks 7 with Support Pack 1 Companion 2 CD into the server's CD drive, browse to the nsure identity manager 3 bundle edition\nt\dirxml\utilities\ad_disc folder, then double-click admanager.exe to run the Active Directory Driver Preparation Tool.
Click
.The tool runs and discovers data for the fields on the tool window.
In the
grouping of the tool window, locate the field, type the password, locate the field, type the password again, then click .In the Create Account Notification dialog box, click
.Copy and paste the
, , , and into a text file, then save the file to the desktop so that you can have access to the data later.HINT:If you prefer, you can leave the tool running. You will then be able to retrieve (copy) this data directly from the tool one field at a time for pasting into the fields of another configuration tool. See Step 12 for more information.
Click
to close the Preparation tool.Complete the security setup for the DirXML account user.
From the Windows desktop, click
> > , then select .In the Tree view, click
> > .Double-click
> click > > > > .Select the user you created (ADDriver_zendemo), click
, then click again in the three succeeding dialog boxes.Close the
.At SRV-02, extend the eDirectory schema to accommodate the new Active Directory driver.
In the Windows Control Panel, double-click
.In the Novell eDirectory Services dialog box, select install.dlm, then click .
Click
, then click .Type the eDirectory admin login name (admin), type the context (ZEN\Users), type the password (novell), then click OK.
Browse to and select c:\novell\nds\dvr_ext.sch, then click .
Click
to apply the schema.Click the close (X) button in the Novell eDirectory Services dialog box.
At SRV-02, launch iManager, then click the Roles and Tasks icon to open the iManager Roles and Tasks pane of the main iManager page.
From iManager, create a new organizational unit (OU) container under the ZEN organizational container, then name this OU container IDM3.
In the Roles and Tasks pane, click
, then click to open the Create New Driver Wizard.On the Create Driver Wizard opening page, click
, then click to open the Create Driver page.On the Create Driver page, fill in the fields:
Name: Type a driver set name, for example ADDriverSet.
Context: Browse to and select the IDM3 container.
Server: Browse to and select the SRV-02 server.
Click
.The wizard creates the objects for the driver set, then displays the ADDriver Set page.
Select
, browse to and select from the drop-down menu, then click to display the Page 1 of the Active Directory Driver Set in the Create Driver Wizard.Configure the driver parameters in the Create Driver Wizard:
On Page 1 of the Create Driver Wizard, fill in the fields that are listed (visible by scrolling):
Driver Name: Leave the name of the driver as the default.
Authentication Method: Use the default value (Negotiate).
Authentication ID: Type the AD Domain Name (NetBios) followed by a forward slash and the Driver Account User that was created (see Step 2.b). You can obtain the Driver Account User from the Account DN name you copied in Step 2.d. (Also see item 1 in the graphic referenced in Step 2.d).
For example, enter ZENDEMO/ADDriver_zendemo on this line.
Authentication Password: Use the same password used to create the Proposed DirXML Driver Account in the admanager.exe tool (see Step 2.b).
Reenter the Password: Re-enter the password you used in the field above.
Authentication Context: Copy and paste the Domain Controller name from the line items that you saved in a text file as you used admanager.exe (see Step 2.d and item 2 shown on the screen shot referred to in this step).
Domain Name: Copy and paste the Domain DN name from the line items that you saved in a text file as you used admanager.exe (see Step 2.d and item 3 shown on the screen shot referred to in this step).
Domain DNS Name: Copy and paste the Domain name from the line items that you saved in a text file as you used admanager.exe (see Step 2.d and item 4 shown on the screen shot referred to in this step).
Driver Polling Interval: Specify the polling interval you want. In a lab environment, the interval should be set at approximately one minute. In a production environment, you should set the interval at approximately 15 minutes.
Password Sync Timeout (minutes): Retain the default value (5 minutes).
Driver is Local/Remote: Retain the default value (Local).
Click
to continue to Page 2 of the Create Driver Wizard.On Page 2 of the Create Driver Wizard, fill in the fields that are listed (visible by scrolling):
Base Container in eDirectory: Specify the container where you want your users to be created and synchronized with Active Directory (for example, users.zen). You can browse for this container by clicking
. If you are going to mirror the Active Directory containers, this would be the top container in eDirectory.Publisher Placement: Select
or . If you choose , all user objects coming from Active Directory are placed in the same container. If you choose , all user objects and containers are re-created in eDirectory.Base Container in Active Directory: Type the name of the base container in Active Directory. This is the container where you want users to be synchronized with eDirectory (for example, CN=Users,DC=zendemo,DC=com).
Active Directory Placement: See the Publisher Placement field to choose your placement.
Configure Data Flow: Retain the default value (Bi-directional).
Password Failure Notification User: Leave the field blank.
Configure Entitlements: Select
from the drop down list.Click
to continue to Page 3 of the Create Driver Wizard.On Page 3 of the Create Driver Wizard, fill in the fields that are listed (visible by scrolling):
Exchange Policy: Retain the default value (No).
Group Membership Policy: Choose a method for assigning group membership in Active Directory. Set to
for the purpose of this lab.For more information, see the Group Membership Policy field in Configuration Parameters in Configuring the Active Directory Driver in the Novell Identity Manager Driver for Active Directory Implementation Guide.
Click
to continue to Page 4 of the Create Driver Wizard.On Page 4 of the Create Driver Wizard, fill in the fields that are listed:
Name Mapping Policy Selection: Retain the default (
) displayed in the drop down list.Click
to continue to Page 5 of the Create Driver Wizard.On Page 5 of the Create Driver Wizard, fill in the fields that are listed:
User Principal Name Mapping: Retain the default (
) displayed in the drop down list.Click
to launch the Security Equivalences page of the Create Driver Wizard.Click
to launch the Security Equals window.Click
to launch the browser window, browse to and select the Admin.Users.ZEN user, add this user to the list, click , then click again.On the Security Equivalences page of the Create Driver Wizard, click
.In the Synchronization Exclusion window, click
, browse to and select all users that are administrators of eDirectory, then click .This prevents the users from being created in the Active Directory domain and synchronized later.
The Summary - Current Driver Configuration page of the wizard is displayed.
Click
.Before the Identity Manager driver can run, you need to install the Password Synchronization software. For more information, see Installing Password Synchronization and Enabling Universal Password.
Password Synchronization allows each user object automatically created in Identity Manager to have the same password as the corresponding user you created in Active Directory. This is necessary to allow for single login to both Active Directory and eDirectory when users log into their workstations.
Password Synchronization requires that platform-specific password policies are not in conflict with each other. Password policies that are in conflict prevents successful password synchronization. For example, if eDirectory passwords are required to be at least eight characters in length and Windows passwords have no length requirements, users could create shorter Windows passwords that would not be accepted by eDirectory. Password Synchronization does not override platform policies.
Identity Manager lets you generate an initial password for an account based on the account's attributes or other information available through Java services. For instance, you can generate a password based on a user's surname plus a four-digit number. Generating an initial password requires driver customization, but it is a good way for you to manage passwords when you provision an account through an existing personnel management toolset.
iManager lets you set an initial password when you create a user account if you select
, then select . In this case, iManager sets the password before an account is associated in NT or Active Directory accounts. This prevents the initial password from being synchronized. Passwords are synchronized only after the first password change. To avoid this delay, you can do one of the following things:Deselect
and assign the password later. A brief delay allows account associations to be completed.Select
so that password setting is delayed until the account is actually used.The Microsoft Management Console (MMC) lets you set an initial password on a user account by typing the password when you create the account. The password is set before Password Synchronization is able to associate an eDirectory account with the Active Directory account, so the Password Synchronization service is not able to update the eDirectory account immediately. However, the service will retry the password update and the account will be properly updated within several minutes.
To install Password Synchronization on your servers:
Log in to the SRV-02 server as administrator, then log in to eDirectory as Admin.
In iManager, click the Roles and Tasks icon , then in the left pane, click
, click Password Policies, then click to open the Password Policy Wizard.Configure the Password Policy.
In the
field, enter a name for the policy (such as IDM UnivPassword), then click to display the Step 2 page of the wizard.On the Step 2 page of the wizard, click
to open the password synchronization options.Select
, then click .On the Advanced Password Rules page, click
.On the Step 4 page of the wizard (Enable Forgotten Password Feature), retain the default (No), then click
.Click
twice to skip the Step 5 page and the Step 6 page of the wizard.On the Step 7 page of the wizard (Assign the Password Policy), select
to open the browse window, select the Users.ZEN container, click , then click to display the Step 8 page of the wizard (Summary of the Password Policy).Click
, then click .From the Windows desktop, click
> > , then double-click .In the PassSynchConfig dialog box, click
for the question “Is this machine where the DirXML Driver is configured to run?”The Password Synchronization dialog box is displayed.
In the Password Synchronization dialog box, click
.The Password Synchronization - Add Domain dialog box is displayed.
In the Password Synchronization - Add Domain dialog box, open the drop-down list in the Domain field, select ZENDEMO from the list, then click
.Do not add information to the
field.In the PassSyncConfig dialog box, click
.Select the Domain DNS Name, then click
to display the Password Filters dialog box.In the Password Filters dialog box, select the Domain Controller name, then click
.This option copies files to the Domain Controller. After the copy is complete, the status changes to “Installed - Needs Reboot.”
Click
, then wait until the server reboots and the dialog box shows that it is running, then click after SRV-01 restarts (if the status has not changed).Click
, then click again.Reboot the SRV-02 server to complete the installation.
When you have installed and configured both the DirXML drivers and the PasswordSync driver, you need finalize the configuration so that these drivers start automatically and function properly. Use the following steps to finalize the configuration:
Log on to the SRV-02 server as administrator.
From the Windows Server 2003 desktop, click
> > > to open the Novell eDirectory Services dialog box.Click dstrace.dlm service, then click Start to display the Novell eDirectory Trace window.
, select theIn the Novell eDirectory Trace window, click
> to open the Novell eDirectory Trace Options dialog box.On the Events page of the dialog box, click
, select , select , then click .Make sure you leave the Novell eDirectory Trace window open.
Launch iManager, then click the server link to log in as Admin.
In iManager, click the
icon to open the Roles and Tasks left pane, click , then click to open the Identity Manager Overview utility in the right pane.In the Identity Manager Overview utility, select
, then click to open the Active Directory- eDirectory configuration page.Click the icon to open a menu options list, then select
.When you start the driver, the Novell eDirectory Trace window displays red messages as errors, yellow messages as warnings, and green messages as successful processes. Although there might be initial errors and warnings, the final message should be green and the status shown as
for the Active Directory DirXML log event.When the driver is running successfully, the icon changes to the icon.
Click the icon, then select
to open the Modify Object window.(Conditional, if a Certificate Authority has not been installed on your network). In the Modify Object Window, select the
tab, click , scroll to the section of the window, then, in the field, select in the drop-down menu.A certificate must be enabled in Active Directory for SSL configuration to work in the driver.
In the Modify Object window, select the
tab, click , scroll to the section of the window, select , then click .A message dialog box displays the question, “Do you want to restart the driver to put your changes into effect?”
Click
in the message dialog box to restart the driver.Roll your mouse pointer over the icon to reveal the status message: “Driver is Running.”
(Conditional) If it is not already open (see Step 2), open the Novell eDirectory Services dialog box, then verify that dirxml.dlm is running.
To verify that eDirectory, DirXML, and Password Synchronization are working properly in your environment, you need to create a few users in Active Directory to verify that they are automatically created in eDirectory with the proper passwords.
Log on to server SRV-01 as the administrator of the Active Directory Domain.
Launch the Active Directory administration tool and create a test user in Active Directory
Example: TestUser1@zendemo.com
Log in to SRV-02 as the administrator of the domain and as admin in eDirectory.
Open iManager, then verify that TestUser1 has been created in the administered container.
You might need to wait for a synchronization cycle to complete before the user is listed in eDirectory.
Log in to eDirectory as TestUser1, verify that the password is the same as the one given in Active Directory, then verify that you successfully authenticated to eDirectory.
Another synchronization cycle might be necessary before the password is updated.
For completeness, create a user in eDirectory (using iManager while logged in as Admin), then verify that the user is now in the domain and that you can log in to the domain as that user using the password you specified in eDirectory.
The default synchronization rules do not create an Active Directory user until the full name attribute field is populated in eDirectory. Check this in iManager >
.IMPORTANT:If the password still fails to work for an eDirectory user being synchronized to Active Directory, see TID 10092646 and TID 10092822 in the Novell Knowledgebase for information on how to correct the issue.
Although you might not choose to install all of these components, this section explains the installation procedure for each of them.
Use the following steps to install the Desktop Management Server onto SRV-02 server, where you previously installed eDirectory.
Log on to the SRV-02 server as administrator, then log in to eDirectory as Admin.
At a Windows workstation, insert the Novell ZENworks 7 Desktop Management CD.
The winsetup.exe program will autorun. If it does not autorun, launch it from the root of the CD.
If you run the installation from a directory location where you have copied the ZENworks Desktop Management ISO files, make sure that all of these files are copied to the same location from which you are running winsetup.exe.
In this situation, the installation program notifies you that it might not run properly. This is because the options you choose during the installation might require a CD swap.
IMPORTANT:If you remove the Novell ZENworks 7 Desktop Management CD from the CD drive during the installation, or if you lose your connection to the server you are installing to, the installation program stops and does not proceed. To terminate the installation process, open the Windows Task Manager click Processes, select javaw.exe, then click .
Click
to display a page with options to install in various languages.Click
to display a page with Desktop Management installation options.Click
to launch the Desktop Management Server installation wizard.On the first Installation page, read the details about running the installation program, then click
.Read the License agreement, then click
if you agree with the terms of the License Agreement.(Conditional) If you do not agree with the terms of the license agreement, do not install the software.
On the Installation Requirements page, read the requirements for installing the Desktop Management Server software, make sure that the server where you plan to install meets the listed requirements, then click
.On the Tree Selection page, type or browse to the name of the Novell eDirectory tree on the SRV-02 server (ZENTREE). If you have not already extended the schema for this installation (see Section 9.1.1, Extending the Schema Before the Installation), select to extend the schema on the tree where you will be installing Desktop Management Server software, then click .
You cannot install Desktop Management Server software on multiple trees at the same time.
You need to extend the schema on a tree only once. You can authenticate to a tree by clicking the
button and entering a user ID and password with the appropriate rights.On the ZENworks Desktop Management Licensing page, specify the license code that was e-mailed to you as part of the SmartCert product registration package.
If you do not specify a license code on this page, the wizard considers this installation of ZENworks Desktop Management to be an evaluation version. If you install for an evaluation, you are periodically reminded to license the product. After 90 days, the product evaluation version no longer functions.
On the Server Selection page, click
to browse to the SRV-02 server.You can select servers only from the ZENTREE tree. You can install to up to 7 servers at a time.
(Optional) In the Add Servers dialog box, you can list servers by their eDirectory tree names. To install to a server, select
, browse to and click the name of the SRV-02 server, click the right-arrow button to move your selected servers to the list, then click OK.If you want to add a Windows server that you might not be authenticated to, you can double-click the server icon to display a dialog box where you can enter credentials to allow for Windows authentication.
(Optional) In the Add Servers dialog box, you can specify the hostname or IP Address of a server in the
field. The value that you provide must be resolvable to the name of a server.Click to begin the name resolution process and add the server to the
list.On the now-populated Server Selection page, you can further specify the services you want to install for the Desktop Management components you previously selected, then click
to save your settings.The list of settings includes the following:
Local Workstation: Even though the ConsoleOne 1.3.6 installation program lets you install ConsoleOne files to a local hard drive (minor performance enhancements can be achieved by doing so) such an installation does not include the Desktop Management Services snap-ins.
You have the option of installing Desktop Management Services snap-ins to your local workstation by selecting Desktop Management Service Snap-ins under the Local Workstation option. ConsoleOne must be installed on the workstation before the snap-ins can be added.
Desktop Management Services: Desktop Management Services (collectively referred to as the “Desktop Management Server”) are commonly used files and programs that enable the configuration and distribution of workstation applications and policies. These services provide automatic management of Windows applications, user and workstation configurations, processes, and behaviors.
Application Management: Select this option to install software that enables the automated distribution, healing, and tracking of applications, updates, and patches.
Workstation Management Common Components: Select this option to install workstation-resident modules that are used to authenticate the user to the workstation and network, and used to transfer configuration information to and from eDirectory.
Remote Management: Select this component to install files and programs that enable the remote management of workstations from a central console. Make sure that the selected servers do not have the ZENworks for Servers 3.0.2 (or earlier) Remote Management component already installed.
Additional Options: If you want to customize your deployment of Desktop Management Services, there are a number of services to choose from, each with a specialized purpose.
Desktop Management Database: Select this option if you want to install a network database to be used by the Novell Application Launcher as a repository for data about application events (install, launch, cache, and so forth) that have occurred.
Inventory Database: Select this option if you want to install a network database to be used by Workstation Inventory as a repository for hardware and software inventory information collected from inventoried workstations.
IMPORTANT:If you want to use the Inventory database with an existing Oracle or MS SQL setup, do not select this option during the Server Inventory installation. Follow the steps in Setting Up the Inventory Database
in the Novell ZENworks 7 Desktop Management Administration Guide.
Inventory Server: Select this option if you want to install files and programs to enable the gathering and viewing of hardware and software inventory information for managed workstations.
If the selected servers have the Server Inventory component of ZENworks for Servers 3.0.2 or earlier installed, you must upgrade the component to ZENworks 7 Server Management.
Inventory Proxy Server: Select this option if you want to install a proxy service that enables the roll-up of inventory scan data to an Inventory server located across a network firewall. Make sure that the selected servers do not have the ZENworks for Servers 3.0.2 (or earlier) Inventory component already installed.
Imaging Server: Select this option if you want to install a Linux imaging environment to be used to create, store, send, or restore workstation image files to a workstation.
IMPORTANT:You should install the Imaging Server service and the PXE Server service on the same server; do not install the PXE Server service separately.
PXE Server: Select this option if you want to install Preboot Execution Environment (PXE) protocols and programs to be used by the server to communicate with a PXE-enabled workstation and to enable sending imaging tasks to that workstation.
When you install Preboot Services, one of the components that is installed is the Proxy DHCP server. If the standard DHCP server is on the same server where you are installing the Proxy DHCP server, you must set option tag 60 in DHCP services.
IMPORTANT:You should install the Imaging Server service and the PXE Server service on the same server; do not install the PXE Server service separately.
Workstation Import/Removal Server: Select this option if you want to install files and programs that add workstation objects into eDirectory (or remove those already added), where they can be managed to receive applications or computer settings.
Desktop Management Services Snap-Ins: Select this option if you want to install additions to ConsoleOne to enable you to launch Desktop Management tools and utilities, to view Desktop Management object property pages in eDirectory, and to browse and configure those objects.
You can perform a “custom selection” by selecting one or more servers and right-clicking to display a pop-up menu with options to add
, , or to all of the servers you have selected. The option returns the selections to their initial state. The selection launches another dialog box that you can use to select specific components for all of the selected servers. This selection overrides any other selections you have made.(Optional)
is selected by default. Retain the selection if you want the installation program to verify that the server or servers meet the installation requirements for ZENworks Desktop Management Services. The installation program checks the version of the server's network operating system (including any required service or support packs), the presence and version of the Novell Client (4.9 SP1a) on Windows servers and on the installing workstation, and the presence and version of ConsoleOne (1.3.6).If the server operating system and support/service packs are not the correct version, the installation displays a warning message, and does not continue. The installation displays a warning and does not continue until the required software is installed and detected or until you deselect the check box.
(Optional if C: for Windows servers.
or is selected.) On the File Installation Location page, select one or more target servers in the list, then browse for or type the volume or drive where you want the Workstation Inventory or Remote Management files to be installed. The default isIf a previous installation of ZENworks 7 Workstation Inventory or Remote Management component is detected on the machine, the existing path is displayed and dimmed. The current installation installs all the files in the same path.
(Optional) The Database Location Installation page is displayed if you choose to install the Inventory database or the Desktop Management database. Select a previously designated server in the left pane, then in the
field, browse for or type in the name of the volume or drive where the database file will be installed, then click .You can provide a different drive for each database server. However, you cannot have multiple instances of the database files on the same server because you can run only one instance of the database engine per server.
(Optional) The Inventory Standalone Configuration page is displayed if you choose to install the Inventory Server and the Inventory Database on the same server. If you want the installation program to automatically create the Server Package and to start the Inventory Service on the server, configure the settings on the Inventory Standalone Configuration page.
Select
, select the server or servers that you want to point to a common Database Location Search Policy, type in the name or browse to the tree container where you want to create and configure the Server Package containing this policy, then click .(Optional) On the Inventory Proxy Service Configuration page, select the server or servers with a port you want to designate as one to allow XMLRPC requests pass through to the Inventory Proxy service, then in the
field, designate the port you want to use.You can configure the same port number for all servers by selecting all of them, or you can define the values individually by selecting the servers one at a time. If you want to change the Port 65000 default, specify a value between 0 and 65535. Ensure that the port number is not used by other services on the server.
On the Summary page, review the list of components and their parts that are to be installed. If the summary is correct, click
to launch the installation program.You can click
as many times as necessary to make changes.If you click
, no installation information is saved.You can review the installation log file after the installation has completed. The log file name is datestamp_timestamp_zdmserver_install.log (for example: 20040304_024034_zdmserver_install.log). It is located in the \novell\zfdtemp directory on the machine you are installing from. This log file indicates whether any component failed to install.
You can also review the installation summary to review the selections you made. The summary is saved in a log file named datestamp_timestamp_zdmserver_installsummary.log (for example: 20040304_024034_zdmserver_installsummary.log). It is also located in c:\novell\zfdtemp.
In ConsoleOne, select the tree where you installed the Desktop Management Server software, then right-click the
> click > > select .If you use ConsoleOne 1.3.6e,
must be deselected in the LDAP Group object for each server acting as the Authentication Domain for a ZENworks Middle Tier Server. If you need to set this parameter after you have installed the Desktop Management Server, make sure you reboot the ZENworks Middle Tier Server after you change the setting.If you are installing to Windows servers in an Active Directory domain, configure the LDAP Group object for servers that are to be used as Authentication Domains to use an alternate port number, because Active Directory will use ports 389 and 636.
If you have already installed the ZENworks Middle Tier Server, you need to reboot the ZENworks Middle Tier Server so that it recognizes the change to LDAP clear text passwords at the Desktop Management Server.
To deliver Desktop Management features through an Internet browser, you must install the ZENworks Middle Tier Server. In this deployment scenario, you install the software on SRV-02, where the Microsoft IIS Web server has already been installed. The Middle Tier Server installation program requires the presence of the Novell Client on the installing workstation or server, so you must first install the Novell Client on the SRV-03 server and then install the ZENworks 7 Middle Tier Server on the same server. You can download the Novell Client (version 4.90 SP1a or later) from the Novell downloads Web site.
When the client has been installed, you can use the following procedure to install the Middle Tier Server:
Log on to SRV-03 as local workstation administrator of the server.
Insert the Novell ZENworks 7 Desktop Management CD.
The winsetup.exe program autoruns. If it does not autorun, launch the program from the root of the CD.
If you run the installation from a directory location where you have copied the ZENworks Desktop Management ISO files, make sure that all of these files are copied to the same location from which you are running winsetup.exe.
In this situation, the installation program notifies you that it might not run properly. This is because the options you choose during the installation might require a CD swap.
IMPORTANT:If you remove the Novell ZENworks 7 Desktop Management CD from the CD drive during the installation, or if you lose your connection to the server you are installing to, the installation program stops and does not proceed. To terminate the installation process, open the Windows Task Manager, click , select javaw.exe, then click .
Click
to display a page with options to install in various languages.Click
to display a page with Desktop Management installation options.Click
to launch the Middle Tier Server installation program.On the first Installation page, read the details about running the installation program, then click
.Read the License agreement, then click
if you agree with the terms of the License Agreement.(Conditional) If you do not agree with the terms of the license agreement, do not install the software.
On the Installation Requirements page, read the requirements for installing the Middle Tier Server software, make sure that the server where you plan to install meets the listed requirements, then click
.On the eDirectory Location and Credentials page, fill in the fields:
DNS/IP Address: Specify the DNS name or IP address of the SRV-02 server, where eDirectory is installed.
Username (full DN): Specify the fully-qualified distinguished username of the Middle Tier proxy user account (for example,admin.users.zen). To ensure that these credentials remain secure, you can set up an arbitrary user with specific administrative rights.
For a description of the required rights, see Section 10.3, Required Rights for the Middle Tier Proxy User Account and the NSAdmin Utility.
Password: Specify the eDirectory password for the Middle Tier proxy user.
On the ZENworks User Context page (
field), specify the eDirectory context where the Middle Tier Server can look for user objects to be used by Desktop Management. For this example, the context is Users.You should use the context of the highest-level container where user objects reside. This value is passed to the ZENworks Middle Tier Server, which uses it as a starting point in searching for a user.
For any Middle Tier Server you designate during this installation, currently configured authentication domains (for example, the authentication domain configured for NetStorage) are replaced by a single authentication domain with the context that you specify here.
After the installation, you can reconfigure this authentication domain context using the NSAdmin utility. You can open the utility in a Web browser (http://srv-02/oneNet/nsadmin).
The installation program verifies the existence of the context (that is, the container) before continuing.
On the ZENworks Files Location page, select the network location where you will access application and policy files managed by ZENworks.
The ZENworks Middle Tier Server requires access to ZENworks files installed elsewhere on your network. As the ZENworks Administrator, you define the location of these files when you create policies or applications for distribution. The information you provide on this page is used to help the Middle Tier Server determine how to access different file systems. This decision is necessary for the installation now, even if you have not yet created any ZENworks files.
Select the first option button if your ZENworks-managed application and policy files will be located on NetWare servers only.
Select the second option button if some or all of your ZENworks-managed application and policy files will be located on Microsoft Windows servers.
If your ZENworks files will be located in a Windows file system, the Middle Tier Server might not be able to access them using a username and password for Novell eDirectory; instead, it requires Windows domain credentials to access the files.
If the files are located on a server not belonging to a domain, enter server-specific credentials.
Specify the username of any user in the Microsoft domain who has Windows file system rights to the ZENworks file locations.
Specify the password for the user in the Microsoft domain who has file system rights to ZENworks files.
Specify the same password to confirm that it was entered correctly.
On the Server Selection page, you need to build a list of target servers that you want to function as Middle Tier Servers. The
button calls a dialog box that is used to find and add servers to the list. The button lets you delete servers from the target list after they are added. Click .(Optional)
is selected by default. Retain this selection if you want the installation program to verify that the server or servers meet the installation requirements for ZENworks Middle Tier Servers.The installation program checks the version of any previously installed Middle Tier Server software, the server's network operating system (including any required service or support packs), the presence and version of the IIS Web server on Windows servers, the presence and version of the appropriate Web server on NetWare servers, and the presence and version of NetStorage (2.6.0) on target servers.
If the server operating system and support/service packs are not the correct version, the installation displays a warning message, but can continue. If other requirements are not met, the installation displays a warning and does not continue until the required software is installed and detected.
In the Add Servers dialog box, open the
drop-down list to show the options of listing the servers according to their location in Novell eDirectory trees, in Microsoft Windows Network structures, or in Microsoft Active Directory trees.You can install the ZENworks Middle Tier Server software to several servers during the installation. When you have finished adding servers to the list, click
.Both the Desktop Management Server installation program and the Middle Tier Server installation program allow you to select servers from only one eDirectory tree. If you run either of these installation program from a Windows server and if that server is not part of the tree you have selected, you cannot install the Desktop Management Server locally.
(Conditional if you want to list servers in Microsoft Windows Network structure.) In the
drop-down list, select to list all of the Windows Workgroups and Microsoft Domains to which you are currently authenticated, browse the structure to the server of your choice, then click the double right-arrow to move it to the list box.Other options in this dialog box include the following:
You must be an administrative user for a server in order to add it to the
list. If you are not authenticated to a server, the object is designated by a question mark. You can double-click the question mark to authenticate to the server, then click the double-right arrow to move the server to the list, provided it is a supported server platform for ZENworks 7 Desktop Management.When you list servers in Microsoft domains, NetWare servers are not listed for browsing because ZENworks files that are located on a Windows server cannot be obtained through a Middle Tier Server installed on NetWare.
You can specify the hostname or IP Address of a server in the Add Server Via Hostname/IP Address field. The value that you enter must be resolvable to the name of a server located in the designated operating environment.
Click to begin the name resolution process and add the server to the Selected Servers list.
If you are using multiple hostname aliases for a Windows server, the first alias must be the physical name of your Windows server.
If the credentials you provided for authentication to the server (see Step 11) are not administrative credentials, you can add it as a target server, but you are re-prompted for Administrative credentials when you close the Add Servers dialog box.
Click
to add all of the servers in a selected domain or workgroup. Selecting a domain or workgroup selects all of the authenticated servers in that domain or workgroup.To remove a server from the
list and return it to the list, click the server name in the list, then click the double left-arrow. You can remove multiple servers from the list by selecting them with the Shift and Ctrl keys.(Conditional if you want to list servers in a Microsoft Active Directory.) In the
drop-down list, select . If your workstation is a member of an Active Directory, the domains in the Active Directory trees are displayed. You can browse to all of the servers listed in Active Directory (on a per domain basis), browse the structure to the server of your choice, then click the double right-arrow to move it to the list box.Other options in this dialog box include the following:
You can also click
to open a dialog box where you can specify the name of the domain you want to add, then authenticate to it with the proper credentials prior to displaying its servers in the drop-down list.You can specify the hostname or IP address of a server in the
field. The value that you enter must be resolvable to the name of a server located in the designated operating environment.Click to begin the name resolution process and add the server to the
list.Right-click a domain object to select one of three search methods:
Search Standard Locations: Lists the computers and domain controllers at the root of the domain. This is the default search method.
Search Entire Directory: Lists all directory containers where computers are located.
Browse Directory Hierarchy: Lists all of the containers in the directory, which you can expand and browse one at a time to find the computer you want. This search method might be useful if you have computers in a non-standard location of a large directory.
Click
to add all of the servers in a selected domain or container. Selecting a domain or container selects all of the servers in that domain or container.To remove a server from the
list and return it to the list, click the server name in the box, then click the double left-arrow. You can remove multiple servers from the list by selecting them with the Shift and Ctrl keys.On the Summary page, review the location where you have chosen to install the ZENworks Middle Tier Server software and the Desktop Management Server to which it is associated, then click
to begin the installation process if the summary is correct.The Middle Tier Server Installation Wizard launches another installation program. Wait until this program is completed.
IMPORTANT:You can review the installation log file after the installation has completed. The log file name is datestamp_timestamp_zdmmidtier_install.log (for example: 20040304_024034_zdmmidtier_install.log). It is located in the \novell\zfdtemp directory on the machine you are installing from. This log file indicates whether any component failed to install.
You can also review the installation summary to review the selections you made. The summary is saved in a log file named datestamp_timestamp_zdmmidtier_installsummary.log (for example: 20040304_024034_zdmmidtier_installsummary.log). It is also located in c:\novell\zfdtemp.
In ConsoleOne pointing to eDirectory on the Desktop Management Server, make sure you have set up the Desktop Management Server to allow clear text passwords.
Reboot the server where you installed the ZENworks Middle Tier Server software.
Verify that the ZENworks Middle Tier Server is installed and running by entering one of the following URLs at a browser on the workstation:
http://srv-02/oneNet/xtier-stats
http://srv-02/oneNet/zen
If the ZENworks Middle Tier Server is running, the first URL opens a Web page where server statistics are displayed. You should be able to see where the request count increases by clicking the Refresh button on your browser.
The second URL launches a dialog box that prompts for user credentials.
At a network browser, enter http://srv-02/oneNet/nsadmin and log in as the Admin user to eDirectory to change the LDAP ports to match those you changed in Step 14.a in Installing eDirectory.
Because eDirectory and Active Directory are installed on the same network server, you might not be able to log in to eDirectory. If this is the case, go to the registry of the server where the ZENworks Middle Tier is installed, then change the LDAP Port DWord value of the HKLM\Software\Novell\Xtier\Configuration\Xsrv registry key to the port you specified in Step 14.a in Installing eDirectory.
Before running the inventory reports, review the following:
Make sure that the appropriate ODBC client for Sybase, Oracle, or MS SQL is installed on the machine running ConsoleOne. The ODBC driver is automatically configured on the machine when you invoke the Inventory report.
To install the ODBC driver for the Sybase database,
For Oracle, you must install the appropriate client for ODBC. For example, for Oracle9i Inventory database, install the Oracle9i client because Inventory reports are not compatible with either the older or the later version of the client.
For MS SQL, the client is available on all Microsoft Windows operating systems.
Make sure that at least MDAC 2.6 SP1 (Microsoft Data Access Component) is installed particularly on a Windows NT machine for running Crystal Reports. Check the version of MDAC on your box, select Microsoft Download Center.
> the tab pane. The minimum version required is 3.520.7326.0. If the version you have does not match the minimum requirement, you need to upgrade the ODBC core components by downloading them from theWhen ZENworks 7 Desktop Management with SP1 is running in a Windows server environment., you need to install the Desktop Management Agent onto user workstations and begin to use the Desktop Management features to manage those workstations.
The Desktop Management Agent Distributor facilitates the initial deployment and future upgrades of the ZENworks Desktop Management Agent through the use of Microsoft domains and Microsoft Active Directory. 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.
For more information about using the Desktop Management Agent Distributor to deploy the Desktop Management Agent to workstations in your Windows network, see Section 12.5, Using the Desktop Management Agent Distributor to Deploy the Agent to Workstations in a Microsoft Domain.