***Disclaimer: Publishing MSI packages will not be known to many here. In fact, apart from me and EE user Vadim Rapp, I can't remember seeing anyone here doing it ;-)
So if you are not perfectly familiar with publishing (no, it's not done per-machine), you will very probably know less about it than me, so please refrain from answering***
This "issue" is rather shared here to extend my knowledge than in order to solve a problem.
I downloaded Visio 2016 Viewer from here: https://download.microsoft.com/download/D/B/7/DB790874-4414-417F-ADF6-348B29572B9F/visioviewer_4339-1001_x86_en-us.exe
I extract the executable using 7-zip and get an MSI and a cab file and a EULA file.
If install that .msi manually, it works as expected. All users of the machine may open .vsd files.
If I publish that MSI file inside the user section of a GPO, users may install it on demand using ->appwiz.cpl ->install a program from the network and it works for them, too.
However, other users, like my administrative account cannot open .vsd files on the same machine where the user installed it, nor will visio viewer 2016 even show up in the list of installed programs. My admin user will have to open appwiz.cpl ->install programs from the network and install it again for it to work for him.
That was different with previous versions of the viewer which we used to deploy on demand as well (2007/2010). Before, the package was visible in appwiz.cpl's list and was usable by all users of that machine
Why is that? What is special about this very .msi
that it behaves differently when installed manually versus installed using the GPO and the process via appwiz.cpl?
I'd simply like to learn.