If you configured FlexEngine to start as a Group Policy client-side extension, but you did not configure the GPO setting, Always wait for the network at computer startup and logon, VMware Dynamic Environment Manager cannot run at login, or it may run every second login.

Problem

VMware Dynamic Environment Manager does not run at login, or it runs every second login when FlexEngine is configured to start as a Group Policy client-side extension.

Cause

You configured FlexEngine to start as a Group Policy client-side extension, but you did not also configure the GPO setting, Always wait for the network at computer startup and logon.

Solution

  • ♦ Enable the Always wait for the network at computer startup and logon Computer Group Policy setting to ensure that the FlexEngine Group Policy client-side extension runs during each logon. Apply this setting to an OU in Active Directory where all the Windows clients that are managed with VMware Dynamic Environment Manager are located.