Managing File Type Associations (FTA) natively using Dynamic Environment Manager

Almost two years ago I created the blog post Export/Import File Type Associations (FTA) successfully using UEM that describes a custom implementation which makes it possible to import and export configured file type associations (FTA) in Windows 10 successfully using UEM (from now on referred to as DEM, Dynamic Environment Manager). A third-party tool called SetUserFTA was used in that implementation to correctly handle hash secured FTA’s and protocols, while DEM handled the import/export.

Read more

Share

App Volumes 4.0 Beta: My First Review

Recently VMware announced the public availability of App Volumes 4.0 Beta. This new major version introduces a different approach to creating, managing and assigning applications compared to the 2.x version of App Volumes. This blog post gives you a “short” introduction to the most important changes and my personal review and opinion on this beta. For those interested, a more in-depth walkthrough is also provided. From AppStacks to Applications In the 2.

Read more

Share

VMworld Europe 2019: My Personal Recap

On 4 November 2019, it was that time of the year again. VMworld Europe in Barcelona. Again, this year my employer, Login Consultants, gave me the opportunity to travel to the south of Europe for this amazing event, for the third time in a row. A couple of weeks ago I already looked forward to going to VMworld. It is a great place to meet people you know, competition colleagues, but also new people.

Read more

Share

Fixing the "No VMware Horizon View Logon Monitor session logs are created" issue

Recently I came across an issue at a VMware Horizon View customer, where VMware Horizon View Logon Monitor session logs were not being created. The fix for this issue is described in this blog post. Issue The VMware Horizon View Logon Monitor session log file starts with vmlm_session__<session_id>.txt.bak and should normally be located in C:\ProgramData\VMware\VMware Logon Monitor\Logs. In our case, there was no session log file. Only the generic vmlm.txt file.

Read more

Share