Visio Viewer 2007 is an example of the app that does not seem to properly
register file extensions. You can remediate this by registering them
manually, which can be accomplished using the procedure described at
http://windowsitpro.com/article/arti...xtensions.html
Regarding your second question, my understanding is that the locally
installed app will always take the precedence.
hth
Marci
<(E-Mail Removed)> wrote in message
news:302db958-15ee-4e9f-bf36-(E-Mail Removed)...
> We would like to deploy Visio Viewer 2007 on an as-needed basis. I
> created a GPO software installation and published it to a one OU of
> users. I selected the option "Auto-install this application by file
> extension" and then tested it with a user. We ran gpupdate and had
> the user log off and back on then found a .vsd file to test.
> Visio Viewer did not install so the user was prompted to choose a
> program to open the file with. However, I checked the add-remove
> programs menu and saw that the Visio Viewer application is available
> there for manual installation, so I know the GPO is working otherwise.
> What needs to be done to get the auto-install to work?
>
>
> Also, is there anything built-into Windows to prevent Visio Viewer
> from taking over opening Visio files on the machines that already have
> the full versions of Visio installed? We only want the Visio Viewer
> GPO installation to launch if the machine doesn't already have the
> full version of Microsoft Visio installed.