Environment Manager Engineering Setting - SpoofProfileForWholeSession

Version 1

    Verified Product Versions

    Environment Manager 8.6Environment Manager 8.5Environment Manager 8.4Environment Manager 8.2Environment Manager 8.1Environment Manager 8.3Environment Manager 8.0


    When using Mandatory Profiles, certain certificate types cannot be imported (as detailed in http://blogs.msdn.com/b/alejacma/archive/2007/10/23/rsacryptoserviceprovider-fails-when-used-with-mandatory-profiles.aspx, CryptAcquireContext will fail with NTE_TEMPORARY_PROFILE error when called from a mandatory profile).


    This is by design, but can be avoided by changing the Profile Type to appear to the OS as a Roaming Profile

    Use the following Engineering Setting introduced in Environment Manager (EM) 8.1.544.0, and made accessible as a Custom Setting within the console from


    AppSense Product:        Environment Manager

    Engineering Setting:     SpoofProfileForWholeSession

    Introduced (Agent):      Environment Manager 8.1.544

    Deprecated (Agent):      N/A

    Introduced (Console):    Environment Manager

    Deprecated (Console):    N/A

    Valid Registry Hives (* = highest priority, where applicable):


    HKEY_CURRENT_USER        Yes


    8.0.x.x Registry Key:    N/A

    8.1.x.x Registry Key:    \Software\AppSense\Environment Manager

    Registry Value Name:     SpoofProfileForWholeSession

    Registry Value Type:     REG_DWORD

    Registry Value Data:     0 or 1

    Default (if not set):    0 (do not change profile type)

    Limitations: Local/Roaming profiles incorrectly changed to Mandatory at logoff, resolved in EM 8.4:

    Profile Type intermittently changing from Local or Roaming to Mandatory