Novell ZENworks OnDemand Services 2
Novell DeFrame 2.01
May 29, 2002

Indicates new or updated information as of December 20, 2002 (Support Pack 1).

TABLE OF CONTENTS

1.0 Pre-Installation Information
  1.1 Supported Environments
  1.2 Non-Supported Environments and Functionality
  1.3 Specific Supported Configurations
    1.3.1 OnDemand Services
    1.3.2 DeFrame
  1.4 Scalability
    1.4.1 OnDemand Services
    1.4.2 DeFrame
  1.5 Internationalization
  1.6 Interoperability
    1.6.1 ZENworks for Desktops
    1.6.2 Novell iFolder/NetDrive
    1.6.3 Novell iChain
    1.6.4 Novell SecureLogin
    1.6.5 LDAP
    1.6.6 Novell iPrint
    1.6.7 General Interoperability Functionality
    1.6.8 Other Novell Products
  1.7 Backwards Compatibility
2.0 Installation Instructions and Known Issues
  2.1 Installing ZENworks OnDemand Services
  2.2 Installing DeFrame 2.01
  2.3 Known Installation Issues
    2.3.1 Installation Errors Caused by Non-Supported LDAP Characters
    2.3.2 Installing the OnDemand Services UsageServer Process to a Terminal Server
    2.3.3 Novell iFolder and Novell Portal Services Compatibility Issues on Windows 2000 Servers Using IIS
    2.3.4 DNS-Rooted Trees Are Not Supported
    2.3.5 Novell Cluster Services
    2.3.6 Novell Portal Services Installation Progress
3.0 Post-Installation Known Issues
  3.1 ZENworks OnDemand Services
    3.1.1 UsageServer Process Issues on Multiprocessor Systems
    3.1.2 OnDemand Services Gadget Style Sheets Override Other Portal Gadget Style Sheets
    3.1.3 Timed-Out NPS Sessions Not Redirected to the Login Page
    3.1.4 Using Environment Variables with the Profile Path Setting in the Launch Item and User Administration Gadgets
    3.1.5 Launch Item Gadget Causing the NetWare GUI to Load on NetWare Servers
    3.1.6 Do Not Use Extended Characters In Application and Package Object Names
    3.1.7 Synchronizing Server Dates and Times
    3.1.8 Uninstalling the DeFrame Plug-Ins for OnDemand Services
    3.1.9 Clearing Sensitive Information from the Browser's Cache
    3.1.10 Removing Applications from OnDemand Services Packages
    3.1.11 Launch Item and User Admin Gadgets' Roaming Profile Settings Apply to DDU Only
    3.1.12 Removing Purchase Objects
    3.1.13 Null Pointer Exception in Approval Gadget
  3.2 DeFrame
    3.2.1 Upgrading the Novell Client After Installing the DeFrame Client
    3.2.2 Using the Clipboard to Cut and Paste Between RDP Sessions
    3.2.3 No Warning When DDU Roaming Profiles Are Unavailable
    3.2.4 Issues Caused by Users Having the Same Common Name in eDirectory
    3.2.5 Do Not Use Periods/Dots (.) When Creating DeFrame Objects
    3.2.6 iFolder Connection Error Caused by Resetting a Session
    3.2.7 Using Novell SecureLogin with DeFrame Terminal Servers
    3.2.8 Citrix Load Balancing Services Currently Not Supported
    3.2.9 Default Load Balancing Weights
    3.2.10 Windows XP Applications Appear to Hang
    3.2.11 Error when Stopping the DeFrame Access Control Service (DeACL)
    3.2.12 Error when Saving a File to an iFolder Server
    3.2.13 Novell iFolder 2.x Not Supported
    3.2.14 RDP Client Session Fails after Running DeFrame Thin-Client Application
    3.2.15 ICA Connection Center Message Appears When ICA Application is Launched
    3.2.16 ICA Applications and DeFrame ICA Applications Cannot Be Run at the Same Time
  3.3 ZENworks for Desktops 3.2
    3.3.1 Application Distribution to Different Users on the Same Machine
    3.3.2 Application Management Reporting Doesn't Work for Thin-Client Applications
    3.3.3 Workstation Management Scheduler Problem on Terminal Servers
    3.3.4 DLU Not Removing User Folders
    3.3.5 Application Object Folders with Unicode Characters Not Displayed Correctly in OnDemand Services Gadgets
  3.4 Novell Portal Services
    3.4.1 Resolving Potential eDirectory Object Naming Conflicts When Installing the NPs 1.5 Full Version over the NPs 1.5 Runtime Version
    3.4.2 Restoring the OnDemand Services Gadget Directories after Installing the NPs 1.5 Full Version over the NPs 1.5 Runtime Version
    3.4.3 Problems with Passwords that Include Extended Characters
4.0 Legal Information
  4.1 Disclaimer, Export Notice, Patents, and Copyright
  4.2 Trademarks

NOTE: Some issues listed below include a REF number (for example REF 295374). This is a Novell internal reference number. It is not a TID (Technical Information Document) number. Searching on a REF number on the Novell Web site will not return any information pertaining to the referenced issue.

1.0 PRE-INSTALLATION INFORMATION

1.1 Supported Environments
For complete OnDemand Services software and hardware requirements, see the OnDemand Services 2 installation information.

For complete DeFrame software and hardware requirements, see the DeFrame 2.01 installation information.

1.2 Non-Supported Environments and Functionality
The following information lists hardware, software, features, and functionality not supported by OnDemand Services 2 and DeFrame 2.01. This list is the result of frequently asked customer questions that surfaced during the development and beta testing of the products.

Workstation non-supported environments:

Server and directory non-supported environments:

OnDemand Services non-supported functionality:

DeFrame non-supported functionality:

1.3 Specific Supported Configurations
The following sections list specific OnDemand Services and DeFrame hardware and software configurations that have been proven to work and are supported.

1.3.1 OnDemand Services
Configuration 1 (Most common current customer configuration, using a mixed NetWare 5 and NetWare 6 environment):

Configuration 2 (Second most common current customer configuration, using NetWare 5 and Windows 2000):

Configuration 3 (Most common new customer configuration, using NetWare 6 only):

Configuration 4 (Windows 2000 only):

1.3.2 DeFrame
Configuration 1 (Most common current configuration):

Configuration 2 (Most common new configuration):

Configuration 3 (Least common current configuration):

1.4 Scalability
The following scalability information was compiled during scalability testing in the Novell SuperLab. This information is provided so that you can better gauge the hardware and software levels required to attain the performance required in your environment.

1.4.1 OnDemand Services (REF 294294, 295618, 296421)
In general, OnDemand Services does not impact the performance of your Web server any more than any other portal-hosted product.

Depending on the workstation specifications and network traffic, you may experience considerable time delays when administering (adding, removing, assigning applications to) large numbers (500+) of users through the OnDemand Services gadgets.

In addition, when running clock-time reports on subscription purchases, you may experience considerable time delays if there are many Purchase objects.

1.4.2 DeFrame
Extensive boundary and scalability testing was performed on DeFrame in the Novell SuperLab. The following sections describe the hardware and software used in the tests, the test configurations, and the test results.

Hardware and Software Configurations:

Test 1:

Test 2a:

Test 2b:

Test 2c:

Test Summary:
As a result of the above tests, the following claims can be made:

1.5 Internationalization
OnDemand Services is not fully enabled for localization. Several defects exist that will be resolved in Support Pack 1.

OnDemand Services does not fully support all international character sets for all functions of the product. Again, several defects remain that will be addressed in a future release. (The OnDemand Services patch dated Oct. 2002 and the Support Pack 1 resolve many extendend character issues. For details, please see the readme included with the patch or the support pack.)

All non-installation utilities and ConsoleOne snap-ins have been tested and meet internationalization guidelines.

The following configurations are currently supported:

1.6 Interoperability

The following sections summarize the issues between ZENworks OnDemand Services 2 and products it works with.

1.6.1 ZENworks for Desktops

  1. OnDemand Services 2 is designed and supported to work only with ZENworks for Desktops (ZfD) 3.2. Customers who wish to use other versions of ZfD (for example, ZfD 4) should do so in a standalone environment and not with OnDemand Services 2.

  2. The following ZfD 3.2 Application Management (NAL) features are not supported with OnDemand Services:

    • Reporting - unable to generate reports for DeFrame applications launched from NAL
    • License/Metering
    • Drive Mappings and Port Captures
    • Launch Scripts
    • Availability Termination Messages
    • Imaging
    • Sources
    • Uninstall
    • Fault Tolerance
    • Load Balancing

    (REF 293567, 295352, 293693)

  3. The DeFrame server login conflicts with Workstation Manager resulting in high CPU utilization and the inability to apply workstation-based policies to the DeFrame server.

    The Workstation Manager and DeFrame Access Control service can both be loaded on a terminal server. However, a system-level login conflict exists between the two. The workaround is to ensure that the terminal server is not imported as a Workstation object into eDirectory. You can do this by not allowing the terminal server to perform a DNS lookup for ZENWSIMPORT.

    The result of not importing the terminal server as a Workstation object is that the DeFrame Access Control service will function properly, but you will not be able use workstation-associated policies or applications on the terminal server.

    (REF 270425) (Related TID: 10072768)

  4. The OnDemand Services User Administration and Launch Item gadgets do not set the attributes required for Dynamic Local User (DLU) roaming profile support. You must use ConsoleOne to set the required attributes. See also Launch Item and User Admin Gadgets' Roaming Profile Settings Apply to DDU Only.

    (Related TID: 10072769)

  5. Usage-billed thin-client (DeFrame) applications cannot be launched from Novell Application Launcher.

    (Related TID: 10072772)

  6. Shared workstations (where multiple users login with different contexts) can result in the inability to launch usage-billed desktop (ZfD) applications. In addition, for OnDemand Services to track usage for a desktop application, the user must be logged in to the OnDemand Services portal. If the user is not logged in, he or she will not be charged for the time used.

    (Related TID: 10072773)

1.6.2 Novell iFolder/NetDrive

  1. Users in different eDirectory contexts but with the same common name (CN) will have problems with iFolder mappings using DeFrame applications. For detailed information, see Issues Caused by Users Having the Same Common Name in eDirectory.

    (Related TID: 10072774)

  2. Novell Portal Services/OnDemand Services 2 and iFolder 1.0 cannot run simultaneously on the same Windows 2000/IIS server.

    (REF 297809, 294775) (Related TID: 10072775)

  3. Uninstalling DeFrame files from a terminal server breaks the existing NetDrive client.

    (Related TID: 10072776)

  4. DeFrame servers can't map drives to iFolder 2.0 servers. (Resolved in OnDemand Services patch dated Oct 2002 and Support Pack 1. For details, please see the readme included with the patch or the support pack.)

    (REF 294525) (Related TID: 10072779)

1.6.3 Novell iChain

  1. DeFrame Load Balancing Services is not compatible with other load balancing methods such as iChain. See also Citrix Load Balancing Services Currently Not Supported.

    (Related TID: 10072780)

  2. Session reconnect for thin-client (DeFrame) applications using iChain or other load balancing methods does not work.

    (Related TID: 10072781)

1.6.4 Novell SecureLogin

  1. Novell Single Sign On 3.0 with thin-client (DeFrame) applications requires updated SSO files on the DeFrame terminal server.

    (Resolved with OnDemand Services 2 patch dated Oct 2002 (or Support Pack 1) and SecureLogin 3.0.3.)

    (Related TID: 10072811)

1.6.5 LDAP

  1. The Launch Item and User Administration gadgets set the DeFrame (DDU) profile path with garbage characters. When this occurs, no warning is given that profile information may be lost. See also Using Environment Variables with the Profile Path Setting in the Launch Item and User Administration Gadgets.

    (Related TID: 10072787)

1.6.6 Novell iPrint

  1. When running thin-client (DeFrame) applications, users can't connect to IPP printers.

    (Related TID: 10072789)

1.6.7 General Interoperability Functionality

  1. DeFrame (DDU) deletes existing SAM users. (Resolved with OnDemand Services 2 patch dated Oct. 2002 or Support Pack 1.)

    (Related TID: 10072790)

  2. If the DeFrame (DDU) roaming profile isn't available, users don't receive a warning that their profile and data can't be saved. See also No Warning When DDU Roaming Profiles Are Unavailable.

    (Related TID: 10072791)

  3. The connection for usage billing fails when the UsageServer is running on servers with multiple CPUs. See also UsageServer Process Issues on Multiprocessor Systems.

    (Related TID: 10072792)

  4. Microsoft Word XP (included in the Microsoft Office XP suite) hangs when launched as a thin-client (DeFrame) application. See also Windows XP Applications Appear to Hang.

    (Related TID: 10072793)

  5. OnDemand Services does not support per-minute usage tracking of Web applications or content.

    (REF 293793, 287332, 273973)

  6. If the UsageServer fails, users will still be able to launch usage-based applications. However, usage will not be tracked and recorded.

    (REF 293793, 287332, 273973)

1.6.8 Other Novell Products
Interoperability issues may exist with using OnDemand Services with the following products because limited interoperability testing was performed:

1.7 Backwards Compatibility
OnDemand Services 1.5/1.5a running under Novell Portal Services is not supported.

The OnDemand Services 1.5/1.5a JSPs and servlet engine are not supported with DeFrame 2.01.

2.0 INSTALLATION INSTRUCTIONS AND KNOWN ISSUES

2.1 Installing ZENworks OnDemand Services 2
To install ZENworks OnDemand Services 2, run ODSETUP.EXE from the ONDEMAND subdirectory of the Novell ZENworks OnDemand Services 2 CD. For ZENworks OnDemand Services installation instructions, see the OnDemand Services installation information.

If you are upgrading from an earlier version of OnDemand Services, please see the Novell ZENworks OnDemand Services 2 upgrade information.

2.2 Installing DeFrame 2.01
To install DeFrame 2.01, you must run two Setup programs available on the Novell ZENworks OnDemand Services 2 CD:

SETUP.EXE in the \DEFRAME\NDSSETUP subdirectory
SETUP.EXE in the \DEFRAME\TSSETUP subdirectory

For DeFrame 2.01 installation instructions, see the DeFrame 2.01 installation information.

If you are upgrading from an earlier version of DeFrame, please see the DeFrame 2.01 upgrade information.

2.3 Known Installation Issues

2.3.1 Installation Errors Caused by Non-Supported LDAP Characters
The OnDemand Services Installation program accesses Novell eDirectory through LDAP. You need to ensure that any eDirectory objects accessed or entered in the Installation program do not contain invalid LDAP characters. Otherwise, the Installation program will fail and generate an error stating "...install has finished with errors." You will need to rename the invalid objects and re-run the Installation program.

2.3.2 Installing the OnDemand Services UsageServer Process to a Terminal Server
We recommend, if possible, that you do not install the OnDemand Services UsageServer to a terminal server. When installed on a terminal server, the UsageServer is unable to broadcast its IP address to other DeFrame terminal servers. Usage-based applications hosted on those DeFrame terminal servers will fail to launch.

If you find it necessary to install the UsageServer to a terminal server, you must manually add the UsageServer's IP address or fully-qualified domain name to the ORBagentaddr key in the registry of all other DeFrame terminal servers. The path to the ORBagentaddr key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Novell\on-demand \Objects\-ORBagentaddr

2.3.3 Novell iFolder and Novell Portal Services Compatibility Issues on Windows 2000 Servers Using IIS (REF 297809, 294775)
Novell iFolder and Novell Portal Services should not be installed on the same Windows 2000 server if you are using Microsoft Internet Information Server (IIS) as the Web server. Doing so can cause one or both products to stop working.

We are currently working to resolve this issue. As updates to this issue become available, they will be posted here.

2.3.4 DNS-Rooted Trees Are Not Supported
OnDemand Services, and in particular the OnDemand Services snap-in for ConsoleOne and DeFrame, are not compatible with DNS-rooted trees.

2.3.5 Novell Cluster Services
If you plan to install OnDemand Services in a NetWare cluster environment, please be aware that currently OnDemand Services does not fully support clustering. For example, DeFrame roaming profiles will be unavailable in the event of a failover.

2.3.6 Novell Portal Services Installation Progress
The Novell Portal Services Installation program, launched by the OnDemand Services Installation program, installs the OnDemand Services gadgets. During installation of the OnDemand Services gadgets, progress may appear to stop. This is not the case. The gadgets are being installed, which may take from 30 seconds to 3 minutes, depending on hardware speed and network traffic. Do not terminate the installation process.

3.0 POST-INSTALLATION KNOWN ISSUES

3.1 ZENworks OnDemand Services

3.1.1 UsageServer Process Issues on Multiprocessor Systems
On multiprocessor systems, the UsageServer process may not start if you are using a JVM older than 6/26/2001. If this occurs, you can update the JVM (http://download.novell.com) or continue to use your current JVM and bind the UsageServer to processor 0 (zero). To do so, edit the UsageServer.ncf or UsageServer.bat file, located in the \ONDEMAND\BIN directory, and add -mp0 to the Java command. For example:

Java -mp0 -Dusage...

In addition, sometimes the UsageServer process will appear to start correctly but when users launch usage-based applications they receive the following error: "Usage error: Failed activating application usage." No activity is shown on the UsageServer console screen when this occurs. To resolve this problem, use the -mp0 switch to bind the UsageServer to processor 0 (zero).

(With OnDemand Services 2 patch dated Oct 2002 or Support Pack 1, the -mp0 switch has been added to the UsageServer.ncf and UsageServer.bat files.)

3.1.2 OnDemand Services Gadget Style Sheets Override Other Portal Gadget Style Sheets
(Fixed with OnDemand Services 2 patch dated Oct 2002 and Support Pack 1.)

If you have OnDemand Services gadgets and other portal gadgets on the same portal page, the OnDemand Services gadgets' style sheets override the formatting applied through the other portal gadget's style sheets. For example, with the OnDemand Services gadgets, text links becomes bold when the cursor passes over them. This style will be applied to other gadgets on the page, even if their style sheets are configured differently.

This should only affect you if you are using the full version of Novell Portal Services 1.5 (rather than the runtime version included with OnDemand Services). The runtime version does not enable you to add portal gadgets other than OnDemand Services gadgets.

3.1.3 Timed-Out NPS Sessions Not Redirected to the Login Page
When a user's Novell Portal Services session times out while using the OnDemand Services gadgets, the user is not redirected back to the login page. Instead, the login page may unsuccessfully attempt to load the current gadget or a blank Java script window may appear. The user will need to relink to the NPS login page.

To minimize the likelihood of this problem, you can increase the Novell Portal Services session time-out (see the NPS 1.5 documentation on the Novell Documentation Web site). If you are using a security product such as Novell iChain to secure access to your NPS portal, you can decrease that product's session time-out so that it times out before NPS. Your choice depends on where you want the reauthentication to occur: the portal service or the security service.

3.1.4 Using Environment Variables with the Profile Path Setting in the Launch Item and User Administration Gadgets (REF 276495)
Windows environment variables such as %USERNAME% can be included in the Profile Path field used to establish the storage location for roaming user profiles (used in conjunction with DeFrame Dynamic User (DDU) functionality).

However, you cannot include variables in the Launch Item or User Administration gadgets' Profile Path setting if you are using a version of Novell eDirectory older than version 8.6 (for example, 8.5) and you use a UNC path when specifying the path.

With a UNC path, the pre-8.6 version of the LDAP server doesn't correctly interpret the \\first_character segment of the UNC path, which results in an invalid path being added to the user's Roaming Profile Path in eDirectory (User object > DeFrame tab > User Settings page).

You can work around this issue by manually defining the profile path for each user in eDirectory, or by using the DeFrame User Configuration utility to define it for multiple users at one time. For information about using the utility, see the DeFrame 2.01 Installation and Administration guide on the root of the Novell ZENworks OnDemand Services 2 CD.

For updated information regarding this issue, see Technical Information Document (TID) 10072787.

3.1.5 Launch Item Gadget Causing the NetWare GUI to Load on NetWare Servers
(Fixed with OnDemand Services 2 patch dated Oct 2002 and Support Pack 1)

This applies only if the OnDemand Services gadgets are installed to Novell Portal Services on a NetWare 6 server.

The first time the Launch Item gadget displays an application for any user, the gadget launches the NetWare GUI program on the NetWare server. Regardless of how many users are using the Launch Item gadget, the NetWare GUI is started one time only.

Do not close the NetWare GUI. A library used by the NetWare GUI is required by the Launch Item gadgets to render the application icon in the Launch Item gadget. Closing the NetWare GUI also shuts down the Tomcat Servlet Engine, which in turn shuts down access to your portal. If you were to close the NetWare GUI and then restart Tomcat, the NetWare GUI would simply be launched again the next time any user accessed the Launch Item gadget.

3.1.6 Do Not Use Extended Characters In Application and Package Object Names
(Fixed with OnDemand Services 2 patch dated Oct 2002 and Support Pack 1. For details, see the readme included with the patch or the support pack.)

Do not include extended characters in the names used for OnDemand Services Package objects or Application objects. Extended characters are currently not supported and will generate Java exception errors.

3.1.7 Synchronizing Server Dates and Times
The OnDemand Services gadgets, the Maintenance process, and the UsageServer process all place time stamps on Purchase and Usage objects in Novell eDirectory and perform various tasks (expiring purchases, deleting objects, and so forth) based on the time stamps.

If you installed the gadgets and processes to different servers, you need to synchronize the date and time on those servers to ensure that no problems occur. For example, if you installed the gadgets to Server 1, the Maintenance process to Server 2, and the UsageServer process to Server 3, synchronize the date and time of those three servers.

3.1.8 Uninstalling the DeFrame Plug-Ins for OnDemand Services
The first time a user runs a thin-client application from a DeFrame terminal server, the OnDemand Services Launch Item gadget installs the DeFrame plug-in files to the user's workstation. If you find it necessary to uninstall the plug-ins, complete the following steps:

  1. Execute the following commands at the workstation's command line to unregister the plug-ins:

    regsvr32 /u axdappx.ocx
    regsvr32 /u axdappxica.ocx

  2. Delete the following files from the Windows System directory (for example, C:\WINNT\SYSTEM32):

    axdappx.ocx
    axdappxica.ocx
    conman.exe
    dappx.dll
    mstsc.exe
    mstscax.dll
    rdpclient.dll
    rdpdr.dll

  3. Delete the DAPPX folder located in the Windows System directory (for example, C:\WINNT\SYSTEM32\DAPPX).

3.1.9 Clearing Sensitive Information from the Browser's Cache (REF 300527)
The OnDemand Services Launch Item gadget includes sensitive information (username, password, etc.) that the DeFrame plug-in requires in order to launch thin-client applications. This information is protected (or can be protected) during transmission through SSL and other encoding. However, after the information is embedded in the Launch Item gadget's Web page, availability of the information is subject to how the browser handles caching of pages.

To ensure that the Web browser properly removes this information, you should configure the Web browser to remove all temporary Internet files when the Web browser is closed.

In Internet Explorer, click the Tools menu > Internet Options > Advanced. In the list, scroll to the Security heading > enable the Empty Temporary Internet Files Folder when Browser is Closed option.

Netscape browsers are not supported in this release of OnDemand Services.

3.1.10 Removing Applications from OnDemand Services Packages (REF 298947)
When you use ConsoleOne to remove an application from an OnDemand Services package, any users who have purchased the package will still have access to the application because the users are still associated to the application. You will need to manually remove the associations (Application object > Associations page) before the users' access will be revoked.

3.1.11 Launch Item and User Admin Gadgets' Roaming Profile Settings Apply to DDU Only (REF 290609)
The OnDemand Services Launch Item gadget and User Admin gadget include configuration settings that allow you to specify whether or not to use roaming user profiles and, if so, where to store them. These settings apply only if you are using the DeFrame Dynamic User (DDU) functionality to manage local user accounts. They do not apply if you are using the ZENworks for Desktops 3.2 Dynamic Local User (DLU) policies.

3.1.12 Removing Purchase Objects (REF 296776)
Whenever a user purchases a package, a Purchase object is created in eDirectory. The Maintenance process removes Purchase objects from eDirectory only after the purchase has expired and the Billed status has been set (either manually or through a third-party billing system) on the Purchase object.

If you have many purchases that expire and must be renewed on a regular basis (such as a Subscription purchase based on clock time), you should make sure the expired Purchase objects are being marked as Billed so that the Maintenance process can remove them. An excessive number of expired Purchase objects can slow down synchronization between server replicas and substantially increase network traffic.

3.1.13 Null Pointer Exception in Approval Gadget (REF 306898)
The Approval gadget will create a null pointer exception if the User objects for any OnDemand Services users reside below the catalog root. The catalog root is the container specified as the root container for OnDemand packages. To resolve this issue, do not have any User objects within the catalog root.

3.2 DeFrame

3.2.1 Upgrading the Novell Client After Installing the DeFrame Client
If a user upgrades the Novell Client on his or her workstation after installing the DeFrame client, several registry settings used by DeFrame are reset and the user will not be able to successfully launch a thin-client application. To resolve this problem, you can reinstall the DeFrame client on the user's workstation, or you can update the workstation's registry by applying the NVLOGINEXT.REG file included with DeFrame.

To update the registry using the NVLOGINEXT.REG file:

  1. Copy the NVLOGINEXT.REG file to a location accessible from the user's workstation.

    There are two NVLOGINEXT.REG files, one for Windows NT/2000 and one for Windows 98. The files are located on the Novell ZENworks OnDemand Services 2 CD in the WIN9X and WINNT directories under DEFRAME\UTILITIES\CLIENT.

  2. Double-click the NVLOGINEXT.REG to launch the Registry Editor and add the setting information to the registry.

3.2.2 Using the Clipboard to Cut and Paste Between RDP Sessions
Microsoft Terminal Services supports cutting and pasting of information between two applications running in different RDP sessions or an RDP session application and a local application. This support is provided through the RDPCLIP.EXE file and has nothing to do with DeFrame. However, during Terminal Services installation, the Registry setting that specifies the RDPCLIP.EXE file is incorrectly set.

To enable the functionality to work for users, you need to do the following on each terminal server:

  1. Use REGEDIT to edit the registry file.

  2. Go to the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Control\Terminal Server\Wds\rdpwd

  3. Change the StartupPrograms value from

    rdpclip\rdpclip.exe

    to

    rdpclip.exe

  4. Save the file.

3.2.3 No Warning When DDU Roaming Profiles Are Unavailable (REF 294507)
If you are using roaming profiles with the DeFrame Dynamic User (DDU) functionality and a user's profile is not available when the user starts an application, no indication of this is provided to the user. The server's default user profile will be used when creating the user's local account, and any registry settings and documents saved with the roaming profile will be unavailable.

If the user's profile location becomes unavailable while running the application, when the user exits the application, he or she receives a warning explaining that changes to the profile could not be saved. The original profile remains in the storage location.

3.2.4 Issues Caused by Users Having the Same Common Name in eDirectory (REF 294513, 294020)
We strongly recommend that users in the same eDirectory tree not have the same common name (CN). For example, you should avoid having two bsmith common names (for example, bsmith.sales.novell and bsmith.support.novell).

Having users with the same common name can result in the following problems:

3.2.5 Do Not Use Periods/Dots (.) When Creating DeFrame Objects
The DeFrame snap-ins for ConsoleOne will not create a DeFrame object (DeFrame Server, Watchdog, iFolder Server, and so forth) if you include periods/dots (.) in the object name.

3.2.6 iFolder Connection Error Caused by Resetting a Session (REF 294847)
When you reset the session of a user who has iFolder drives mapped, the next time the user launches a thin-client application and attempts to open or save a file, he or she will receive the following error:

Drive drive_letter : is currently mapped to server_name. Please select another drive or disconnect this drive first.

As soon as the user clicks OK to dismiss the error message, the iFolder connection will be made and the drive will be available. No further intervention is required.

3.2.7 Using Novell SecureLogin with DeFrame Terminal Servers
For information about configuring Novell SecureLogin on DeFrame terminal servers, see for Technical Information Document (TID) 10072811.

3.2.8 Citrix Load Balancing Services Currently Not Supported
DeFrame does not currently support Citrix Load Balancing Services. If you want to load balance your DeFrame terminal servers, you can use the DeFrame Load Balancing Services.

3.2.9 Default Load Balancing Weights
DeFrame includes a Novell eDirectory object, the DEFAULT_REG object, where you can set the default weights given to each of the resources that will be to determine a terminal server's workload. When this object is created during installation, no default weights are set. If you want to set these default weights, the following values are recommended:

Memory: 20
CPU Usage: 80
Users: 20
Page File: 5
Virtual Memory: 5
Maximum Number of Users: 25
Log File Duration: 3
Load Refresh Rate: 4

The default values will be applied to any terminal servers whose weights you have not manually changed through the DeFrame Server object's Load Configuration page.

3.2.10 Windows 2000/XP Applications Appear to Hang (REF 311311)
Some Windows 2000/XP applications, such as Microsoft Word, may appear to hang immediately after the user launches the application or performs a task that requires the application to display a new dialog box. The application's title bar will flash, but the user will not be able to do anything with the application.

This problem occurs because the focus is on a dialog box that is not being displayed on top of the application. Users can resolve this problem by pressing Alt+Tab to select another open application and then selecting the Windows XP application again. When focus is returned to the Windows 2000/XP application, the dialog box that wasn't initially displayed will now be displayed and the user can continue working in the application. The user will need to do this one time per application session.

3.2.11 Error when Stopping the DeFrame Access Control Service
When stopping the DeFrame Access Control Service (DeACL), you may receive the following error:

The instruction at 0x76fb291b referenced memory at 0x006c0088. The memory could not be read.

There is no observable side effect to this error. When you restart the service, it will function properly.

3.2.12 Error when Saving a File to an iFolder Server
The first time a user saves a file to an iFolder server, he or she may receive the following error:

...cannot complete save due to file permission error (filepath)

After clicking OK to dismiss the error, the user will be prompted to resave the file. If the user clicks Yes and retypes the filename (it defaults to a .TMP filename), the file is successfully saved.

3.2.13 Novell iFolder 2.x Not Supported (REF 294525)
(Fixed with OnDemand Services 2 patch dated Oct 2002 and Support Pack 1. For details, please see the readme included with the patch or the support pack.)

The NetDrive client used with DeFrame 2.01 does not support mapping to iFolder 2.x servers.

3.2.14 RDP Client Session Fails after Running DeFrame Thin-Client Applications (REF 319121)
After running a DeFrame thin-client application, a user will be unable to open an RDP client session to a terminal server. To resolve this issue, the user must delete the following key from the Windows registry before launching the RDP client (mstsc.exe):

HKEY_LOCAL_MACHINE\Software\NvxClient\UserDn

The key will be restored each time a user launches a DeFrame thin-client application and will need to be deleted before he or she can open an RDP client session.

3.2.15 ICA Connection Center Message Appears When DeFrame ICA Application is Launched (REF 313278)
If each time a user launches a DeFrame thin-client application, the ICA Connection Center generates the error listed below, please refer to Citrix Document CTX150199.

Connection Center has detected that "Show window content while dragging" effect is enabled.

3.2.16 ICA Applications and DeFrame ICA Applications Cannot Be Run at the Same Time (REF 303318)
Users cannot launch ICA application using the ICA client at the same time they are running DeFrame ICA applications launched through the OnDemand Services Launch Item gadget.

3.3 ZENworks for Desktops
If you will use ZENworks for Desktops 3.2 to distribute applications to OnDemand Services users, please be aware of the following issues.

3.3.1 Application Distribution to Different Users on the Same Machine
If an OnDemand Services user launches a desktop application (ZENworks for Desktops), disconnects from Novell eDirectory, logs in as another user on the same machine, and then attempts to launch a desktop application again, the ZENworks Novell Application Launcher/Explorer will fail to distribute the application.

3.3.2 Application Management Reporting Doesn't Work for Thin-Client Applications
ZENworks for Desktops 3.2 Application Management reporting allows you to log the success or failure of application events such as distribution and installation. Application Management reporting does not work for thin-client applications distributed through DeFrame, even if you configure the reporting options on the Application object.

3.3.3 Workstation Management Scheduler Problem on Terminal Servers (REF 293560)
If you use Workstation Management Scheduler to schedule the periodic launching and running of applications on a terminal server, do not configure the schedule with an Impersonation level of Interactive User.This causes the scheduled application to be displayed in the most recently launched RDP or ICA client session instead of on the terminal server's console. This occurs whether the client session was initiated through an OnDemand Services thin-client application or through a standard client session startup. To avoid this problem, change the Impersonation level to Unsecure System.

3.3.4 DLU Not Removing User Folders (REF 276561)
When using a Dynamic Local User policy (with Use NetWare Credentials and Volatile User checked) to manage user profiles on terminal servers, user folders (C:\DOCUMENTS AND SETTINGS\ username) are not being deleted. The first time a user is logged in, DeFrame creates a username folder. The next time, a username.001 folder will be created, then a username.002 folder, and so on. You may want to periodically remove the extra user folders.

3.3.5 Application Object Folders with Unicode Characters Not Displayed Correctly in OnDemand Services Gadgets (REF 317690)
This issue applies only when running the OnDemand Services gadgets with a NPS portal on a NetWare server.

If an Application object's folder includes unicode characters in the folder name, the Launch Item gadget will not properly display the folder name. This is a display issue only. The application will still launch correctly.

3.4 Novell Portal Services

3.4.1 Resolving Potential eDirectory Object Naming Conflicts When Installing the NPS 1.5 Full Version over the NPS 1.5 Runtime Version
When upgrading the NPS 1.5 runtime version (included with OnDemand Services) to the NPS 1.5 full version, if you select the same eDirectory context for the NPS 1.5 full version objects as you did for the NPS 1.5 runtime version and OnDemand Services gadgets, you need to ensure that existing objects and objects created by the NPS 1.5 full version Installation program will not have the same names.

The Installation program will create gadget objects with the following default object names. If necessary, change the default name during installation to avoid naming conflicts. Naming conflicts may cause the NPS Installation program to stop functioning.

AdvancedProperties
AppletLauncher
Authenticator
AVSearch
Bookmark
ChangePassword
Chat
Citrix
CommunityAccess
CommunityAdmin
CommunityCalendar
CommunityDiscussion
CommunityFileSharing
CommunityManager
DynamicGroupAdmin
EGuide
Exchange
GadgetAdmin
GroupWiseCalendar
GroupWiseMail
GWWebAccess
HTML
Iframe
LegacyAdmin
Message
MoreOverNewsGadget
NetworkFileGadget
Nims
NNTP
Notes
PageAdmin
PageSetAdmin
PCOAdmin
Phonebook
PortalAdmin
PortalGroupAdmin
PortalStats
Preferences
Query
Registration
RemoteAdmin
RSS_News
SelfAdmin
ShortCuts
SlimPage
StockApplet
StockTicker
Survey Topics
UserAdmin
WebMailGadget
XML_Remote

3.4.2 Restoring the OnDemand Services Gadget Directories after Installing the NPS 1.5 Full Version over the NPS 1.5 Runtime Version (REF 295374)
If you install the full version of NPS 1.5 over the runtime version and the OnDemand Services gadgets no longer work, do the following:

  1. During installation, the NPS Installation program creates a WEBAPPS\NPS\PORTAL.date/time\GADGETS directory and backs up the existing gadgets to that directory. Copy the OnDemand Services gadget directories from the backup directory to the WEBAPPS\NPS\PORTAL\GADGETS directory. The OnDemand Services gadget directories are:

    com.novell.ondemand.gadgets.ApprovalGadget com.novell.ondemand.gadgets.ConfigWizardGadget com.novell.ondemand.gadgets.CurrentBHGadget com.novell.ondemand.gadgets.EditAccountGadget com.novell.ondemand.gadgets.LaunchItemGadget com.novell.ondemand.gadgets.PackageRequestGadget com.novell.ondemand.gadgets.ReportGadget com.novell.ondemand.gadgets.UserAdminGadget com.novell.ondemand.gadgets.WorkflowTrackingGadget

  2. Restart the Web Server, Web Application Server, and JVM.

3.4.3 Problems with Passwords that Include Extended Characters (REF 293184)
If you use ConsoleOne to assign a password to a user, and that password includes extended characters, the user will be unable to log in to NPS. This does not apply if you use the OnDemand Services gadget to assign the password; in this case, extended characters are acceptable.

4.0 LEGAL INFORMATION

4.1 Disclaimer, Export Notice, Patents, and Copyright
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. US Patent Pending.

Copyright (C) 2002 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

U.S. Patent Pending.

4.2 Trademarks
BorderManager, ConsoleOne, GroupWise, iChain, NetWare, Novell, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.

ApprovalFlow, eDirectory, NIMS, Novell Application Launcher, Novell Client, Novell Cluster Services, Novell DeFrame, Novell iFolder, Novell Internet Messaging System, and ZENworks OnDemand Services are trademarks of Novell, Inc.

All third-party trademarks are the property of their respective owners.