The User Administration gadget is used by budget holders to create, modify, enable, and disable user accounts, as well as assign packages to users. It has the following configuration settings:
Display Name: Specifies the name that will be used when displaying the gadget on the portal page.
OnDemandService Object: Specifies the distinguished name of the OnDemandService object that was created in eDirectory during installation. Use LDAP syntax to specify the name (for example, cn=ondemandservice,ou=services,o=novell).
RDP: This setting applies when creating new users through the User Administration gadget. It specifies whether or not a Windows Terminal Services RDP session can be used when launching a thin-client application from a terminal server. The default is TRUE.
This setting populates the user's RDP Client setting in eDirectory (User object > DeFrame tab > DeFrame Properties page > RDP Client setting).
ICA: This setting applies when creating new users through the User Administration gadget. It specifies whether or not a Citrix MetaFrame ICA session can be used when launching a thin-client application from a terminal server. The default setting is TRUE.
This setting populates the user's ICA Client setting in eDirectory (User object > DeFrame tab > DeFrame Properties page > ICA Client setting).
DDU: Specifies whether or not you want DeFrame to dynamically create the user's account on a terminal server each time he or she launches a thin-client application from the server. DeFrame will create the user's account, using his or her eDirectory username, when the user starts the application. After the user exits the application, DeFrame deletes the user account.
This setting populates the user's Dynamic User setting in eDirectory (User object > DeFrame tab > DeFrame Properties page > Dynamic User setting).
Store Roaming Profiles -- Registry: This setting applies when creating new users through the User Administration gadget and requires the DDU setting to be TRUE. It specifies whether or not a roaming profile will be used to store the user's Windows registry settings such as property settings for folders and preference settings for applications. Saving the registry settings ensures that any application modifications that are stored in the registry will persist from one session to another. If a roaming profile is not used, the registry settings will be lost when the user exits the application and his or her user account is removed.
The default is FALSE. If you set this to TRUE, you need to specify the profile storage location in the Profile Path setting. Individual user folders will be created under the profile storage location and the registry settings saved as username.dfr files (for example, \profiles\jsmith\jsmith.dfr).
This setting populates the user's Store Roaming Profile:Registry setting in eDirectory (User object > DeFrame tab > DeFrame Properties page > Store Roaming Profile:Registry setting).
Store Roaming Profiles -- Files: This setting applies when creating new users through the User Administration gadget and requires the DDU setting to be TRUE. It specifies whether or not a roaming profile will be used to store the folders and files contained in the user's home directory (c:\documents and settings\username). Saving the user's home directory ensures that any application files (such as documents) saved to the user's home directory will persist from one session to the next. If a roaming profile is not used, the folders and files will be lost when the user exits the application and his or her account is removed.
The default is FALSE. If you set this to TRUE, you need to specify the profile storage location in the Profile Path setting. Individual user folders will be created under the profile storage location and the folders and files saved to that directory (for example, \profiles\jsmith\folders and files).
This setting populates the user's Store Roaming Profiles:Files setting in eDirectory (User object > DeFrame tab > DeFrame Properties page > Store Roaming Profile:Files setting).
Profile Path: This setting applies when creating new users through the User Administration gadget and is required if you set either of the Store Roaming Profiles settings to TRUE. It specifies the location where you want to store the roaming profiles.
You can enter a local drive path or a network drive path. If you enter a local drive path (for example, c:\profiles), the user's profile will be created on each terminal server's local drive. This means the user might not have consistent settings and files from one server to another.
If you enter a network drive path, the same profile will be used regardless of which terminal server the user logs in to. The terminal server's DeFrame Access Control Service, logged in to eDirectory through the DeFrame PASS_ADMIN user, creates the profile on the network drive. The PASS_ADMIN user has Admin-equivalent rights to the tree where it resides, so the DeFrame Access Control Service can create the profile location on any server in the tree. Use a valid UNC path (\\server\vol\directory) to specify the profile location.
You can also include the Windows %USERNAME% variable in the path as well. 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%. Because DeFrame always creates a user profile directory in the specified location, this would result in the profile being saved to a \\server1\vol1\username\username directory.
This setting populates the user's Roaming Profile Path setting in eDirectory (User object > DeFrame tab > DeFrame Properties page > Roaming Profile Path setting).
Disable Unsubscribe: This setting applies when creating new users through the User Administration gadget. It enables or disables a user's ability to cancel a subscription to a package. The default is TRUE, which means that the user cannot cancel subscriptions.
This setting populates the user's Disable User's Ability to Unsubscribe Package's setting in eDirectory (User object > OnDemand tab > Purchases page > Disable User's Ability to Unsubscribe Packages).
Include URL in Email: This setting applies when assigning packages to users. It specifies whether or not to include the portal's URL in e-mail notifications sent to users. Notification messages let users know when they have been given access to packages. Including the URL in the messages enables users to launch the portal directly from the messages rather than going to their Web browsers.
iChain URL: This setting applies when assigning packages to users. If you are using Novell iChain to provide secure authentication and access to your portal, enter the appropriate iChain URL, including the protocol (for example, http://www.novell.com/nps or https://123.456.78.910). Instead of the portal's URL, this iChain URL will be used in notification messages sent to users.
Window Height: Specifies the height of the window that lists the users. If the user list is too long to fit in the window, the window will include a vertical scroll bar. The default setting is 200.
Secure Sensitive Pages: Specifies whether or not the budget holder's Web browser uses the Secure Socket Layer (SSL) protocol when transferring sensitive information such as passwords to and from the Web server. The default is FALSE. If you set it to TRUE, make sure the Web server supports SSL connections.
iFolder Server Object: This setting applies when creating new users through the User Administration gadget. If you are using Novell iFolder to enable users to save files from thin-client applications to network storage locations, this setting specifies the iFolder servers you want available to users. You must enter the distinguished name of the iFolder Server object, in LDAP syntax:
cn=ifolderserver,ou=services,o=novell
This setting populates the user's iFolder Servers setting in eDirectory (User object > DeFrame tab > iFolder Servers page > iFolder Servers setting).
Available Templates: This setting applies when creating new users through the User Administration gadget. You can use this setting to specify User templates that budget holders can choose from when creating user accounts. You must specify the distinguished name of the Template object, in LDAP syntax:
cn=usertemplate,ou=users,o=novell