Specific features and functions provided by VMware Dynamic Environment Manager are processed in a specific order. To ensure that applications behave as you expect, familiarize yourself with the processing order.

Processing Order at Boot

VMware Dynamic Environment Manager processes the following computer environment settings at boot:
  • Horizon Smart Policies for computer environment settings
  • ADMX-based computer settings
  • Computer environment startup tasks

Processing Order at Logon

The following VMware Dynamic Environment Manager processes at logon:
  • Horizon Smart Policies for user environment settings
  • Folder redirection
  • Application blocking
  • Privilege elevation
  • Logon tasks (marked as before profile archive import)
  • Environmental variables
  • Drive mappings
  • Printer mappings
  • Files and folders/Registry settings (marked as before profile archive import)
  • Hide drives
  • Policy settings
  • ADMX-based user settings
  • Application migration
  • Triggered tasks
  • Processing INI files (that is, profile archive import, setting up the DirectFlex cache)
  • Shortcuts
  • File type associations
  • Files and folders/Registry settings (marked as after profile archive import)
  • Logon tasks (marked as after profile archive import)
  • Kick off async creation of shortcuts, drive mappings, and printer mappings

Processing Order at Logoff

The following VMware Dynamic Environment Manager processes at logoff:

  • Logoff tasks (marked as before profile archive export)
  • Processing INI files (that is, profile archive export)
  • Logoff tasks (marked as after profile archive export)
  • VMware Dynamic Environment Manager undo action

Processing Order at Shutdown

VMware Dynamic Environment Manager performs the following activities at shutdown:

  • Processing computer environment shutdown tasks
  • Reverting any Horizon Smart Policies for computer environment settings and ADMX-based computer settings that were applied at boot

Processing Order of Individual Items

Individual items within each feature are processed in alphabetical order.
Drive Mappings Example
If you have configured three drive mappings with the following names, they are processed in the following alphabetical order:
  • All users: H: home drive mapping
  • Financial department F: drive mapping
  • Sales team S: drive mapping
ADMX Policy Example
If two ADMX-based settings configuration files contain the same policy setting, but with different values, the values are applied in alphabetical order of the filenames. Specifically, if ADMX-based settings configuration file A configures policy setting P to 1, and configuration file B sets P to 2, the end result is that P is set to 2 because B sorts after A.