Lieven's Posts

I had exactly the same issue. The client's endpoints are primarily thinclient laptops (Wyse 5470), thinclients (Wyse 5400) or home computers (could be anything). Due to the pandemic people are a lot working from home and use different endpoints and physical screen layouts: only the (thinclient) laptop screen, (thinclient) laptop screen with 1 external screen, (Thinclient) laptop screen with 2 external screens, thinclient with one or more external screens, ...). Due to this Win10 cleartype was not always turned on and configured. After turning on and configuring cleartype the problem went away. NO more lag when typing and the fonts also appeared to be clearer.   I resolved the problem by adding the following regkeys through DEM (multiple DISPLAYs due to multiple possible screen layouts): Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Immidio\Flex Profiles\ImportMarkers] "Pre"=dword:86928386 [HKEY_CURRENT_USER\Control Panel\Desktop] "FontSmoothing"="2" "FontSmoothingGamma"=dword:000004b0 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics] [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DISPLAY1] "PixelStructure"=dword:00000001 "GammaLevel"=dword:000007d0 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000032 "GrayscaleEnhancedContrastLevel"=dword:00000064 "TextContrastLevel"=dword:00000000 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DISPLAY2] "PixelStructure"=dword:00000001 "GammaLevel"=dword:000007d0 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000032 "GrayscaleEnhancedContrastLevel"=dword:00000064 "TextContrastLevel"=dword:00000000 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DISPLAY3] "PixelStructure"=dword:00000001 "GammaLevel"=dword:000007d0 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000032 "GrayscaleEnhancedContrastLevel"=dword:00000064 "TextContrastLevel"=dword:00000000 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY4] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY5] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY6] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY7] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY8] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY9] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics\DISPLAY10] "PixelStructure"=dword:00000001 "GammaLevel"=dword:00000898 "ClearTypeLevel"=dword:00000064 "EnhancedContrastLevel"=dword:00000190 "GrayscaleEnhancedContrastLevel"=dword:0000012c "TextContrastLevel"=dword:00000002 [HKEY_CURRENT_USER\Software\Immidio\Flex Profiles\ImportMarkers] "Post"=dword:464c582b   Regards, Lieven

@RachelW    using the /qb or /restart flasg will not make a difference when installing teams For explanations on the redrections.xml see https://docs.microsoft.com/en-us/fslogix/manage-profile-content-cncpt  

Here are some of my own notes regarding Outlook SSO (and Onedrive SSO) which work perfectly for me: OUTLOOK References: https://superuser.com/questions/1265985/automate-outlook-profile-creation  https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sso-quick-start Steps: Azure AD Connect Pass-trough Authentication Enable Single-Sign-On GPO: User configuration - Administrative Templates - Windows Components - Internet Explorer - Internet Control Panel - Security page - Internet zone - Allow updates to status bar via script ==> Enable User configuration - Administrative Templates - Windows Components - Internet Explorer - Internet Control Panel - Security page - Site to zone assignment ==> Add “ https://autologon.microsoftazuread-sso.com” with a value of “1” Regkey to Enable ZeroExchangeConfig ==> Configured via DEM [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover] "ZeroConfigExchange"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover] "ZeroConfigExchangeOnce"=dword:00000001 Regkey to Enable Modern Authentication ==> Configured via DEM [HKEY_CURRENT_USER\SOFTWARE\Microsoft\OneDrive] "EnableADAL"=dword:1 ONEDRIVE References: https://docs.microsoft.com/en-us/onedrive/use-silent-account-configuration Steps: Regkey SilentAccountConfig ==> Via GPO [HKLM\SOFTWARE\Policies\Microsoft\OneDrive] "SilentAccountConfig"=dword:00000001 Regkey EnableADAL ==> ViaDEM [HKCU\Software\Microsoft\OneDrive] “EnableADAL”=dword:00000001 I hope it's helpful

@RachelW  You're almost there. One of the important things with MS Teams in VDI environments is the way you install it. Make sure you do a "per-machine installation" of MS Teams. This can be done in the following way: msiexec /i Teams_Windows_x64.msi /lv C:\Windows\Temp\Teams_install.log ALLUSER=1 ALLUSERS=1 /qb /norestart To ensure MS Teams starts up automatically at logon make sure the below registry exists: REG ADD HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run /v Teams /t REG_SZ /d "C:\Program Files (x86)\Microsoft\Teams\current\Teams.exe" /f The fact that you are prompted for your password the first time you startup teams is "normal". There is a bug in teams where SSO does not seem to work. If anybody finds a solution I am interested in knowing it. To keep the FSLogix profile container small, I am also excluding some MS Teams (and other) folders from the FSLogix profile container by using the below FSLogix redirections.xml file <?xml version=”1.0? encoding=”UTF-8??> <FrxProfileFolderRedirection ExcludeCommonFolders=”###VALUE###”> <Excludes> <Exclude Copy="0">$Recycle.Bin</Exclude> <Exclude Copy="0">AppData\Local\Google</Exclude> <Exclude Copy="0">AppData\Local\SquirrelTemp</Exclude> <Exclude Copy="0">AppData\Local\OneDrive\cache</Exclude> <Exclude Copy="0">AppData\Local\Microsoft\OneNote\16.0\cache</Exclude> <Exclude Copy="0">AppData\Local\Microsoft\Office\SolutionPackages</Exclude> <Exclude Copy="0">AppData\Local\Microsoft\Office\16.0\Lync\Tracing</Exclude> <Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude> <Exclude Copy="0">AppData\Local\Microsoft\Teams\Packages\SquirrelTemp</Exclude> <Exclude Copy="0">AppData\Local\Microsoft\Teams\current\resources\locales</Exclude> <Exclude Copy="0">AppData\Local\Apps\2.0</Exclude> </Excludes> </FrxProfileFolderRedirection>   Regards, Lieven

Hi @RachelW , You can certainly run FSLogix in combination with DEM. I use FSlogix for all profile related things and DEM for mapping printers, assigning shortcuts, setting registry keys, applying ADMX settings, .... For FSLogix is does not matter where the file shares are located. So yes, they can be on the same server where you store the DEM folders. Just be aware to calculate the space needed. By default the FSlogix VHD files can grow up to 30 GB. Personally I use 4 different shares: Share 1 = Redirected folders (My documents, My Music, desktop, favorites, ...) Share 2 = DEM share Share 3 = FSlogix profile share Share 4 = FSlogix Office share I hope this helps. Regards, Lieven

I agree with you @RachelW , the cache folder can get really big. This is why I choose to use FSLogix in stead of DEM for saving he profile. I use DEM only for saving some Windows settings and pushing ADMX based settings, shortcuts, drive mappings, reg keys, FTA's, Printer mappings, ... This way I keep logon time to a minimum (<30s)

I have a similar error when trying to access the helpdesk functionality from within the Horizon console. Error: "Failed to do helpdesk for session ...." This error occurs only when we want to take Remote control for users who mention that there VDI is stuck. Any ideas?

I received a (pre-packed) answer from VMware support on this: According to the VMware interoperability matrix, Horizon 8 (2006) is not compatible with App Volumes 2.18.x. It means  that there is known incompatibility to use both products together  on production environment and due to that VMware cannot offer a solution to  any  issues caused by those incompatibilities while using  in production environment. So this means I will have to do some extensive testing on App Volumes 4.1 before moving to Horizon 8 or move away completely from App Volumes.

Hi DEMdev​ After implementing the workaround, what exactly is the failure mode if printer mapping does not work correctly? Same as before, as in: async FlexEngine.exe instance hangs, or something else? Same as before: async FlexEngine.exe instance hangs You will see in the attached async log, that it suddenly stops logging. From that moment on I am unable to open the fog file as it is in use by another process. After the user logs off and the machine is deleted by Horizon vIew, I can access the log again. Does this seem related to a particular printer? Not 100% sure, but I have the impression that it might be related to printers that are offline at the moment we are trying to map Can you "divide and conquer", by temporarily disabling individual printer mappings in DEM to see if there's a particular problematic one? Very difficult to do as I am working remote and it's hard to choose a "victim" to test. Additionally there's about 80 printers around How do elevated tasks fail? Does DEM's log indicate success with running your logon task and the referenced elevated task, but does the script not have the intended effect? According to the blogs, the elevated task launched successfully. Attached are the logs If you launch that batch file from a command prompt that you have elevated "manually" (as in, Run as Administrator via standard Windows functionality), does it always work? Yes, this always works BTW, refreshing does not serve a purpose here, unless you have modified elevated task definitions in the Management Console in the meantime. Ah, yes. That's true. My mistake.