Ryfujk

We have installed a Windows Server 2016 Remote Desktop Session Host (actually 1 broker server with 2 session host servers, all Windows Server 2016).
Users log in with roaming profiles (stored on the broker server), local profiles are deleted when users log off.

Each time the users log in and try to open a website, they have to choose wich browser they want to use: Google Chrome or IE. The option "always use this program..." is checked. While in their current session, it is not asked any more, but when they logoff and they log back in, they get the question again.

Any one knows how to fix this? This setting should be stored in the users' registry not?

Thanks,
Michiel.

The information of the default browser is stored in following registry keys in HKCU or HKEY_CURRENT_USER, which is actually a pointer to HKEY_USERS Security ID (SID).

HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.htmUserChoiceProgid

HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.htmlUserChoiceProgid

HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.xhtUserChoiceProgid

HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.XhtmUserChoiceProgid



HKCUSoftwareMicrosoftWindowsShellAssociationsUrlAssociationshttpsUserChoiceProgid

HKCUSoftwareMicrosoftWindowsShellAssociationsUrlAssociationshttpUserChoiceProgid

HKCUSoftwareMicrosoftWindowsShellAssociationsUrlAssociationsftpUserChoiceProgid

They are REG_SZ values with associated default browser: FirefoxURL / ChromeHTML / IE.HTTP etc.

A new HKEY_CURRENT_USER subtree is created each time a user logs on.
The data for the subtree comes from the profile of the current user.
If no profile is available, the subtree is built from the user profile
settings established for a default user, which are stored in %SystemDrive%UsersDefaultNtuser.dat.

So, HKCU is stored in user's profile: by default these settings should follow the user as local %USERPROFILE% gets synchronized with the roaming profile at logoff, if you have deployed roaming user profiles correctly.

However, for reducing the size of roaming profiles there are options for limiting the profile size with Profile Quotas and Excluded Folders.

You should check that you don't accidentally exclude ntuser.dat in

[HKEY_CURRENT_USERSOFTWAREMicrosoftWindows NTCurrentVersionWinlogon]

"ExcludeProfileDirs"="AppData\Local;AppData\LocalLow;$Recycle.Bin;OneDrive;Work Folders"

Then, look inside User ConfigurationAdministrative TemplatesSystemUser Profiles on the GPOs applied to the roaming profile users:

• 
  

  Exclude directories in roaming profile

  
  
  

  
  

  This policy setting lets you exclude folders that are normally
  included in the user's profile. As a result, these folders do not need
  to be stored by the network server on which the profile resides and do
  not follow users to other computers.

  
  
  

  Note: When excluding content from the profile you should try to
  exclude the narrowest set of data that will address your needs. For
  example, if there is one application with data that should not be
  roamed then add only that application's specific folder under the
  AppDataRoaming folder rather than all of the AppDataRoaming folder
  to the exclusion list.

  
  

  
  


• 
  

  Limit profile size

  
  
  

  
  

  This policy setting sets the maximum size of each user profile and
  determines the system's response when a user profile reaches the
  maximum size. This policy setting affects both local and roaming
  profiles.

  
  
  

  If you enable this policy setting, you can:

  
  
  

  
  
  • Set a maximum permitted user profile size.
  
  
  • Determine whether the registry files are included in the calculation of the profile size.
  
  

  
  

  
  

Check that these settings are rational and not limiting the synchronization of ntuser.dat.