No Policy or Personalization after upgrade from Environment Manager 8.0

Version 1

    Verified Product Versions

    AppSense Environment Manager 8.2AppSense Environment Manager 8.1

    Introduction

    After an upgrade from Environment Manager 8.0 to either 8.1 or 8.2, you discover that no Policy or Personalization is working within a Users Session.

    From launching Task Manager you also see that the there is no EMUser.exe process running within the affected session.

    Detail

    Following the architectural changes made in Environment Manager 8.1, the EMCoreService is now responsible for launching the EMUser.exe process when a new User Logon is initiated.

    One of the checks that the Core Service validates, is for the existence of the Shell value within either of the Following Registry Keys:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

    HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
    If neither of these keys contains a REG_SZ value called Shell, then the Shell will not be discovered and as a consequence EMUser.exe will not be launched within the session.
     
    EMUser.exe is the process used within session to run Policy/Personalization processes for the user.
     

    To resolve this issue, ensure that the Shell values are present in either/or both of the Registry Keys listed above.

    Note - The actual Shell value data will be dependant on your environment, by default this is set to Explorer.exe.

     

    To check if this issue applies, you can also enable Environment Manager debug logging and check the EMCoreService Debug Logs for the following entries:

    L3  T5948 58191218 [CUserShell::GetUserShell] Shell isn't located in the users hive, trying the system hive
    L4  T5948 58191218 [CUserShell::GetStringFromRegistry] [ENTER]
    L1  T5948 58191218 [CUserShell::GetUserShell] Failed to find the shell in the system hive : 2
    L1  T5948 58191218 [CSessionMessages::HandleFirstStageLogon] Failed to find the shell : 2