The following updates were made to the Installation and Administration guide for the OnDemand Services 2 patch dated Oct 2002:
| Location | Update |
|---|---|
Added information about installing DeFrame on Citrix MetaFrame XP Feature Release 2 (FR2). |
|
In the introduction, under the description of the DeFrame Workstation Setup program, clarified that this Setup program only needs to be run if a user needs to launch thin-client applications from Novell Application Launcher. |
|
Added a step (step 17) about applying the OnDemand Services 2 October 2002 patch to update the DeFrame snap-ins for ConsoleOne. |
|
Applying the October 2002 Patch |
Added information about applying the OnDemand Services 2 October 2002 patch to update the DeFrame server files. NOTE: This section no longer exists. For Support Pack 1, it was replaced by Applying Support Pack 1 . |
DeFrame Dynamic User (DDU) versus ZENworks for Desktops Dynamic Local User (DLU) |
Under Local Group Assignments, corrected information about DDU. When a user is added by DDU, the user is not assigned to the Users group as previously stated. The user is not assigned to any group, but is still given access equivalent to the Everyone group. |
Added information to DDU section about how to deactivate DDU on a terminal server. |
|
Added a list of characters that cannot be used in Application object names. |
|
Setting Up the Published Application Sync Service in a Multiple Terminal Server Farm Environment. |
Added this new section to provide instructions about how to set up the Published Application Sync Service in a multiple-server-farm environment. These instructions explain how to prevent one farm's Application objects from overwriting another farm's Application objects when they are added to Novell eDirectoryTM. NOTE: This section no longer exists. For Support Pack 1 (see December 20, 2002 (Support Pack 1) ), the service became a utility and this section was replaced with Using the DeFrame Published Application Synchronization Utility to Create the Application Object . |
Configuring the Published Application Sync Service |
Removed information about the classic and nonclassic switches. The classic switch instructed the Published Application Sync Service to use the Citrix master browser's preferred server information for an application. The nonclassic swtich instructed the service to ignore the master browser's preferred server information so that the DeFrame Load Balancing service would determine an application's preferred server. The classic mode is no longer an option. The Published Application Sync Service will always ignore the Citrix master browser's preferred server information. NOTE: This section no longer exists. For Support Pack 1 (see December 20, 2002 (Support Pack 1) ), the service became a utility and this section was removed because the startup switches no longer applied. |