In any case, I re-tested the installation after adding the above Citrix key and it was successful, all files winding up in %ProgramFiles% (I didn’t test with the VMware key, but you only need one of the keys to spoof VDI, so it doesn’t matter). Strangely enough, though I may have missed it, there wasn’t an obvious Registry test for a “pure Microsoft” (no Citrix, no VMware) VDI machine – the installer might instead be using API calls to identify RDS or Windows 10 EVD machines. HKLM\Software\VMware,Inc.\VMware VDM\Agent.But what’s “VDI” as far as the installer is concerned? I traced a (failed) machine-wide installation attempt on a plain Windows 10 machine (Process Monitor) and it turns out that the installation looks for either one of the following two keys, and fails soon thereafter if it doesn’t find one of them: centrally in %ProgramFiles% rather than in the user profile), but it’s only allowed on VDI. Tried installing the Microsoft Teams MSI will “ALLUSER=1” on a plain W10 computer, and got this:Īs previously mentioned, the Teams MSI has an “ALLUSER=1” option to install “machine-wide” (i.e. This great little write up came from Jacques Bensimon.
0 kommentar(er)
