At a terminal server where you've installed DeFrame, make sure you are authenticated to Novell eDirectoryTM and have Admin-equivalent rights.
Run glbalias.exe, located in the c:\winnt\system32\deframe directory, to start the User Configuration utility and display the User Selection dialog box.
You use this dialog box to select the users you want to configure.
In the list of eDirectory trees, make sure the correct eDirectory tree is selected.
In the left pane, select a user you want to configure, then click the >> button to add the user to the right pane.
You can select User objects or container objects. If you select a container object, all users in the container and its subcontainers are added to the list in the right pane. A non-DeFrame user is indicated by a normal User icon 
and an existing DeFrame user is indicated by a yellow-shaded User icon 
.
When you've added all users who you want to configure, click Next to display the User Properties dialog box.
You use this dialog box to configure the DeFrame user settings. The settings you choose will be applied to all the users you selected in the previous dialog box.
Configure the following settings:
Associated iFolder Servers: If you've installed Novell iFolderTM 1.x to enable network file storage, click Browse to select the iFolder Server objects to associate with the users.
ICA Client: Select this option to force applications that are configured to run in either an ICA or RDP client session to run in an ICA client session on the user's workstation. The application's terminal server must support the ICA protocol (in other words, the Windows server must have Citrix MetaFrame installed). Otherwise, an RDP client session will be used.
RDP Client: Select this option to force applications that are configured to run in either an ICA or RDP client session to run in an RDP client session on the user's workstation.
If you select both ICA Client and RDP Client, and an application is configured to run in either type of session, an ICA client session will be used. For a summary showing the protocol (RDP or ICA) depending on the user's Client setting, an application's protocol setting, and a server's supported protocols, see Configuring the Application Object .
Dynamic User: Select this option to have DeFrame use its DeFrame Dynamic User (DDU) functionality to dynamically create the user's local account each time the user launches an application from the server. DeFrame creates the user's account, using his or her Novell eDirectory username, when the user starts the application. After the user exits the application, DeFrame deletes the user account. If the terminal server is a member of an NT domain and the Domain Controller server name is included in the terminal server's Domain field (DeFrame Server object > DeFrame Server Environment tab > Environment page) and the user's eDirectory username and password matches the user's NT domain username and password, the local user account will be created using the NT domain account information.
IMPORTANT: If a user account already exists that matches the user's eDirectory username, DeFrame will use the existing account rather than create a new account. When the user exits the application, the account will be deleted, even though DeFrame did not create the account. If you have persistent accounts (local or domain) that you want to remain persistent, you should not use DDU.
If you don't enable this option, you need to ensure that the user has a permanent local or domain user account, or you need to use ZENworks for Desktops 3.2 Dynamic Local User (DLU) policies to create the user's account. If you create permanent user accounts for the user, the username and password for those accounts must match the user's eDirectory username and password.
Store Registry Profile: By default, with Dynamic User enabled, when the user is logged out of the terminal server, his or her user profile is removed from the terminal server. This includes the user's registry settings. You can use this option to specify that you want the user's registry settings stored in a persistent location, such as a c:\userprofile directory on the terminal server or a network location accessible by the terminal server, so that the registry settings will be restored the next time the user is logged in to the terminal server. The User Profile Directory field is used to specify the storage location.
Store Document Profile: By default, with Dynamic User enabled, when the user is logged out of the terminal server, his or her user profile is removed from the terminal server. This includes the user's document (c:\documents and settings\username) folder. You can use this option to specify that you want the user's documents stored in a persistent location, such as a c:\userprofile directory on the terminal server or a network location accessible by the terminal server, so that the documents will be restored the next time the user is logged in to the terminal server. The User Profile Directory field is used to specify the storage location.
User Profile Directory: If you chose to store registry or document profiles, enter or browse for the directory where you want the profiles stored.
You can also include Windows environment variables in the path as well as a special DeFrame variable (%USERNAME%). For example, if you want the user's profile saved to his or her user directory on a network server, you could specify \\server1\vol1\%USERNAME%.
Click Finish to enable the users as DeFrame dynamic users and to apply the user settings.