This message was deleted.

Will check tomorrow what I actually did, have it in an Appsense config file for you. If I remember correctly I did full Visio using setuserfta and viewer via reg import which isn’t being recovered by w10

That would be nice, because I am currently digging myself into a hole that uses FSLogix, Ivanti and SetUserFTA and it doesn't feel at all sustainable 🙂

Can you combine with App Masking to redirect the HKLM keys?

That's an idea, let me try

Nice solution. You can disable Visio's File association Repair function to stop the MSI from running. I've had it all working by pumping the associations into the HKCU keys at logon depending on group membership. But it's a PITA. You would think after all these years the Viewer and Full apps would have a "nicer" working arrangement under this scenario.

@Jeremy Saunders any details on that Repair function? That's the last bit that's annoying me......looks a bit rubbish

Extracted from a 9 year old script: • Key: HKCU\Software\Microsoft\Office\14.0\Visio\Application • Type: REG_SZ • Value: RegistrationFlags • Data: 0xBDCF I have no idea if it's still relevant for the newer versions. My notes from that script... • Disable Visio's File association Repair function. Note that this disables only the auto-repair when Visio is opened. Users can still repair both from within the application and from the Control Panel. • Visio default = 0xBDEF • Clear bit 5 (AND 0xFFDF) to disable Visio's file association repair = 0xBDCF

Sorry, I got it from your previous comment 🙂 I just need to overwrite the HKCU entries for .vsd and .vsdx for the users in the "Use Visio" group. Cheers!

Blimey that was fast https://james-rankin.com/articles/forcing-citrix-rdsh-users-to-open-files-in-either-visio-or-visio-viewer/

Why do ladies keep saying that to me