Appendix C: Configuration Modules
A configuration is comprised of settings within one or more configuration modules. Each configuration module is designed to accomplish a specific task.
The following configuration modules are available:
| Module | Description |
|---|---|
| Main | Defines parameters that apply to all users |
| Privilege Elevation | Allows non-admin users to install applications that have been approved by the Allow and Deny policy rules defined by the administrator |
| Application Restrictions | Allows or denies users access to applications |
| FlexApp DIA | Controls the delivery of department installed applications |
| Virtual Disks | Used to mount storage |
| Printers** | Connects and disconnects network printers **Starting with version 6.7, this module was moved from following the Path module to now following the Virtual Disks module which will affect the order in which the module settings are processed. Registry rules will now be processed earlier. |
| Drive Mapping** | Connects and disconnects network drives **Starting with version 6.7, this module was moved from following the Desktop Start Menu module to now preceding the Portability Settings module which will affect the order in which the module settings are processed. Registry rules will now be processed earlier. |
| Portability Settings | Controls the storage and retrieval of personal user preferences during logoff and logon |
| File Associations | Allows administrators to control what apps open for what file types |
| Profile Cleanup | Used to clean up a user’s profile contents |
| User Defined Aliases | Retrieves information from your domain controllers about the current user's account for use throughout your ProfileUnity configuration |
| User Defined Scripts | Allows a custom written KiXtart script to execute either before or after ProfileUnity runs |
| Application Launcher | Launches applications on your client machines during or after ProfileUnity execution |
| Desktop Start Menus | Allows a user to add a start menu to the desktop |
| Environment Variables | Sets and clears environment variables |
| Registry** | Makes changes to the registry on client machines **Starting with version 6.5, this module was moved from following the RDP Client module to now following the Environment Variables module which will affect the order in which the module settings are processed. Registry rules will now be processed earlier. |
| Administrative Templates | Allows ADMX import with GPO import direct from Active Directory |
| Folder Redirection | Redirects shell folders to an alternate location, and optionally move or copy existing data |
| INI Files | Enables ProfileUnity to manipulate INI files during user logon |
| Internet Explorer | Configures Internet Explorer features such as Start Page, Download Directory, and Favorites for Internet Explorer versions 4.0 and higher |
| Internet Proxy | Adjusts Internet Explorer's proxy settings to match your network configuration for Internet Explorer versions 4.0 and higher |
| Inventory | Creates a report listing computer name, computer domain membership, username, processor, memory, display resolution, MAC address, IP address, operating system (including service pack version and installed hotfixes), Internet Explorer version, and installed applications |
| MAPI Profiles | Configures Windows Messaging subsystem profiles used by Microsoft Outlook for access to Microsoft Exchange server |
| Message Boxes | Displays popup messages to your users during logon |
| Office File Locations | Modifies the default file locations for Microsoft Office |
| Office Options | Configures Microsoft Office user information and sets options that control interaction with the user |
| Outlook | Modifies settings that control Microsoft Outlook’s behavior for message handling, message format, and AutoArchive |
| Paths | Modifies the search path |
| RDP Client | Configures RDP clients |
| Shortcuts | Creates shell shortcuts and web links |
| ThinApp | Dynamically provision ThinApp packages |
| Time Sync | Sets the time on your client machines from a centralized source |
| Trigger Points | Allows other modules to run based on various events that occur on the machine |
| Windows Options | Modifies settings that control the Windows user interface |
Note: Most configuration modules are processed in the order they are listed above. This can impact the expected results. For example, because the Environment Variables module is processed after the Application Launcher module, the Application Launcher module will not have access to any necessary environment variables set by the Environment Variables module.
However, you can layer your configuration settings by using multiple configurations. If any configuration named “Default” exists, it is run first by ProfileUnity. Then the remaining configurations are run in alphabetical order. Configurations that are processed later in the sequence can take advantage of settings that were processed earlier. For example, to use an environment variable in the Application Launcher module, you could configure the Environment Variables in the Default configuration and then have a separate configuration that uses the Application Launcher module. In this case, the Default configuration would run first and set up the environment variables. When the Default configuration finishes running, the remaining configurations would be processed in alphabetical order allowing the Application Launcher module to take advantage of the environment variable settings.
Using Macros
Macros can be used in your configuration anywhere an expression is expected. During logon, these macros expand into values based on their definition. For example, when a user with an ID of GPBurdell logs on to a client machine, the “@USERID” macro text is replaced with “GPBurdell”. Macros have many practical uses. Refer to Appendix B: Configuration Macros for a list of supported macros and their definitions.
Using Reserved Characters
The characters @, %, and $ are reserved characters. If you want to use these characters in your configuration, you will need to use @@, %%, or $$ instead. Using two reserved characters in a row acts as an escape sequence that allows you to use the character in some other capacity rather than the function for which it was reserved. For example, if you want to use the email address user@domain.com, you will need to use user@@domain.com instead.
