Milan KTG

I was a bad USB key I had, not a registry key sorry. I did not have to make any changes, looks like it was enabled by default (FIDO2).

Looks like Windows Looks like Windows 10 23H2 has another year of support? At that time we would have to move to Windows 11 anyway? We could wait for Windows 11 24H2 to be supported and move to that, or if we setup 23H2 is it recommended to do in place upgrade, or build a new gold image with every new version of Windows? Running LTSC for years never really had to worry about feature upgrades, just security patches. Finally, my last question is edition of Windows. I am sure we would still go Enterprise (just checking our licensing). I see Enterprise IoT. Is that better suited for VDI environment and longer support? I've been reading things online, but opinions from experts like you, really help. Thank you.

Thank you for the reply @StephenWagner7! I think somewhere we missed the part that Microsoft does not recommend LTSC versions for VDI. We have been using Office Semi-Annual release channel for years with it now. I guess its time to discuss internally what are future steps will be. I can get latest version of Teams running fine if I use older version of bootstrapper.exe (likely does not block LTSC).

@Victor León What edition on Windows does VMWare recommend to use?

I just found that as well! It used to be on the supported list for sure. There is a workaround to get it installed but how does Microsoft support Win 10 21H2 until 2027 but not support New Teams on it?

Hello, Been using New Teams for a few months now. Since he latest version of bootstrapper I am getting the error in the screenshot. Anyone know why? I can still use older version of bootstrapper but why?

We are on 2312, it working now. Had one bad key. Thank you both.

Hello, We have a website that requires a passkey setup to login. This uses Windows Hello. I don't believe we can use Windows Hello to setup PIN in a non persistent VDI environment? One option seems to be USB security key. I purchased a Yubikey and others to test this but Windows on VDI is not detecting device. We have USB redirection enabled, a regular USB storage device works. Can anyone help with this? I could not find any documentation. There seems to be some people that have got it working on reddit but not with much information. I tired only enabling FIDO2 on Yubikey but that still did not work.

Hello, In last few weeks we started having issues with Outlook showing "Need Password" on the bottom right. Not every time but issue seems to be getting worse. The only way to fix it is to Clear Our Shared settings in DEM, log off and log in. Seems like something is getting captured (or not getting captured) thats breaking Outlook. This just started happening recently and we made no changes to Shared Office Settings for years. We use instant clones, not persistent desktops. SSO is setup and we have Microsoft E3 licensing. # # Expanded settings for the Microsoft Office 2016 Application Template 'Shared': # [IncludeRegistryTrees] HKCU\Software\Microsoft\Office\16.0\Common HKCU\Software\Microsoft\Office\16.0\FirstRun HKCU\Software\Microsoft\Office\16.0\Microsoft Office 2016 HKCU\Software\Microsoft\Office\16.0\Registration HKCU\Software\Microsoft\Office\16.0\User Settings HKCU\Software\Microsoft\Office\Common HKCU\Software\Microsoft\Shared Tools\Proofing Tools HKCU\Software\Microsoft\VBA #Added this key to capture Previewer settings IE PDF in Outlook. Had to be set in each session HKCU\Software\Microsoft\Office\Previewers HKCU\Software\Microsoft\Office\PowerPoint HKCU\Software\Microsoft\Office\Visio HKCU\Software\Microsoft\Office\Word #New Settings HKCU\Software\Classes [IncludeIndividualRegistryValues] HKCU\Software\Microsoft\Exchange\Client\Options\PickLogonProfile [IncludeFolderTrees] <AppData>\Microsoft\AddIns <AppData>\Microsoft\Bibliography <AppData>\Microsoft\Office <AppData>\Microsoft\Proof <AppData>\Microsoft\Spelling <AppData>\Microsoft\Templates <AppData>\Microsoft\UProof <LocalAppData>\Microsoft\Office\ONetConfig #Added to capture Licensing <LocalAppData>\Microsoft\Office\16.0\Licensing #needed to capture second mailbox with Modern Auth <LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy [ExcludeFolderTrees] <AppData>\Microsoft\Templates\LiveContent <LocalAppData>\Microsoft\Office\16.0\OfficeFileCache #New settings <LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\TempState

I had no luck getting it resolved or why its happening. The workaround was to let Print Server due the processing instead of client,

@Niels Geursen I tested it about 10 times and no errors. However our capture size is around 90mb for a very basic account, 1-2 chats. I am adding our capture below. We are actually toying around with not capturing anything for New Teams, so far no issues since we have SSO. User does not get prompted to login, Teams just launches. not really sure of the benefit to capture it right now. Here is our full capture that works right now; # MS Teams v2 [IncludeRegistryTrees] HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MSTeams_8wekyb3d8bbwe\ [IncludeFolderTrees] <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\ [IncludeFiles] # Official Files to sync from Microsoft's New Teams Deployment Site <LocalAppData>\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\tma_settings.json <LocalAppData>\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json [ExcludeFolderTrees] # Official Exclusions from Microsoft's New Teams Deployment Site <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLog <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorag <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\indexedDB <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\GPUCache # Additional Exclusions <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\Crashpad # <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\GrShaderCache <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Cache <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Code Cache #<LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\IndexedDB <LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Service Worker\CacheStorage #<LocalAppData>\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Service Worker\ScriptCache [ExcludeFiles] old_logs_*.txt logs.txt LOG LOG.old *.log *.txt

@Niels Geursen I will give that a shot too. Let me know what you find.

Thanks Niels, Mine broke again after 5-6 logins with same error. Capture is copy/pasted from main post and removed the line you mentioned. Yours is still good?

Hi Murat, Would this not break some security features?

This works a few logins then something goes wrong and user is presented with this message.