Visio 2007 and Visio Viewer 2007 on Terminal Server

P

Pat Caulfield

Hello,
We have a Windows 2008 Terminal Server that will be used by most of our
employees. I'd like all users on the server to be able to view Visio
diagrams with Visio Viewer 2007. However, I also need a select few to be
able to use the full version of Visio 2007.

I've locked down the visio.exe file so that only users in a specific group
can run the program. The problem is, Visio 2007 takes control of the file
extensions / file associations. I haven't been able to set the Visio Viewer
to be the default application for launching Visio documents.

I've scoured newsgroups and the internet for a solution. One suggestion was
a registry addition for the HKEY_CURRENT_USER\Software\Classes key for all
users in a login script (see below for contents of reg keys). I've tried
implementing this but it doesn't seem to work. After implementing the key
changes, when I double-click on a Visio file, IE launches and starts a cycle
of asking me if I want to Save or Open the file (and continues over and over
until I select Cancel.)

I've also found a suggestion to run Visio with a /noreg switch so that Visio
does not overwrite the Visio Viewer file associations. Unfortunately, it
seems that the Visio Viewer never takes control of the file associations when
it is installed. If I double-click a Visio file immediately after install of
the Visio Viewer, it still launches Visio 2007. I've tried extracting the
visioviewer.exe file and installing using the vviewer.msi file but get the
same results.

I have installed all programs using the 'Install Application on Remote
Desktop...' icon in the Control Panel (equivalent to Install Mode on older
versions of TS.)

Any help greatly appreciated!

Pat Caulfield

Registry file contents below
-----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\.vsd]
@="VisioViewer.Viewer"
"Content Type"="application/vnd.ms-visio.viewer"

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex]

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex\{8895b1c6-b41f-4c1c-a562-0d564250836f}]
@="{21E17C2F-AD3A-4b89-841F-09CFE02D16B7}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CurVer]
@="VisioViewer.Viewer.1"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\DefaultIcon]
@="\"C:\\Program Files\\Microsoft Office\\Office12\VVIEWER.DLL\",-2"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell]
@=""
[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open]
@="Open"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\command]
@="\"C:\\Program Files\\Internet Explorer\\iexplore.exe\" -nohome"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec]
@="\"file:%1\",,-1,,,,,"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec\Topic]
@="WWW_OpenURL"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"
 
J

James W.

I think this issue has come up a few times. If Visio the application and the
Visio Viewer are installed on the same box the application owns the
extensions this is by design. You could make modification so that the viewer
owns the extension but this is an all or none situation. You cannot customize
it so it works for some users. Have you considered using two different
Terminal Servers, one for users that need access to the application the other
for people that use the viewer. You could set up a group policy that routes
the user to the proper Terminal Server. Since the application is only
installed on one box there is no fight over the file extensions.
--
James W.


Pat Caulfield said:
Hello,
We have a Windows 2008 Terminal Server that will be used by most of our
employees. I'd like all users on the server to be able to view Visio
diagrams with Visio Viewer 2007. However, I also need a select few to be
able to use the full version of Visio 2007.

I've locked down the visio.exe file so that only users in a specific group
can run the program. The problem is, Visio 2007 takes control of the file
extensions / file associations. I haven't been able to set the Visio Viewer
to be the default application for launching Visio documents.

I've scoured newsgroups and the internet for a solution. One suggestion was
a registry addition for the HKEY_CURRENT_USER\Software\Classes key for all
users in a login script (see below for contents of reg keys). I've tried
implementing this but it doesn't seem to work. After implementing the key
changes, when I double-click on a Visio file, IE launches and starts a cycle
of asking me if I want to Save or Open the file (and continues over and over
until I select Cancel.)

I've also found a suggestion to run Visio with a /noreg switch so that Visio
does not overwrite the Visio Viewer file associations. Unfortunately, it
seems that the Visio Viewer never takes control of the file associations when
it is installed. If I double-click a Visio file immediately after install of
the Visio Viewer, it still launches Visio 2007. I've tried extracting the
visioviewer.exe file and installing using the vviewer.msi file but get the
same results.

I have installed all programs using the 'Install Application on Remote
Desktop...' icon in the Control Panel (equivalent to Install Mode on older
versions of TS.)

Any help greatly appreciated!

Pat Caulfield

Registry file contents below
-----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\.vsd]
@="VisioViewer.Viewer"
"Content Type"="application/vnd.ms-visio.viewer"

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex]

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex\{8895b1c6-b41f-4c1c-a562-0d564250836f}]
@="{21E17C2F-AD3A-4b89-841F-09CFE02D16B7}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CurVer]
@="VisioViewer.Viewer.1"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\DefaultIcon]
@="\"C:\\Program Files\\Microsoft Office\\Office12\VVIEWER.DLL\",-2"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell]
@=""
[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open]
@="Open"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\command]
@="\"C:\\Program Files\\Internet Explorer\\iexplore.exe\" -nohome"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec]
@="\"file:%1\",,-1,,,,,"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec\Topic]
@="WWW_OpenURL"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"
Click to expand...
 
P

Pat Caulfield

James,
Thanks for the reply. I don't mind having Visio Viewer being the default
app for Visio files, and having users who need to run Visio open files
through the app. The problem is I have not been able to get Visio Viewer to
be the default app for Visio files when Visio 2007 is installed. Do you know
how this is done? If I try to change file associations through Windows, it
does not allow me to select Visio Viewer (not an option from what I can see.)
I've tried making the HK_Users reg change, but that did not work (files open
in IE but go through an endless loop of asking if I want to open or save.)

We have considered using a seperate server, but can't justify a seperate
server for just a few people.

Thanks.

Pat

James W. said:
I think this issue has come up a few times. If Visio the application and the
Visio Viewer are installed on the same box the application owns the
extensions this is by design. You could make modification so that the viewer
owns the extension but this is an all or none situation. You cannot customize
it so it works for some users. Have you considered using two different
Terminal Servers, one for users that need access to the application the other
for people that use the viewer. You could set up a group policy that routes
the user to the proper Terminal Server. Since the application is only
installed on one box there is no fight over the file extensions.
--
James W.


Pat Caulfield said:
Hello,
We have a Windows 2008 Terminal Server that will be used by most of our
employees. I'd like all users on the server to be able to view Visio
diagrams with Visio Viewer 2007. However, I also need a select few to be
able to use the full version of Visio 2007.

I've locked down the visio.exe file so that only users in a specific group
can run the program. The problem is, Visio 2007 takes control of the file
extensions / file associations. I haven't been able to set the Visio Viewer
to be the default application for launching Visio documents.

I've scoured newsgroups and the internet for a solution. One suggestion was
a registry addition for the HKEY_CURRENT_USER\Software\Classes key for all
users in a login script (see below for contents of reg keys). I've tried
implementing this but it doesn't seem to work. After implementing the key
changes, when I double-click on a Visio file, IE launches and starts a cycle
of asking me if I want to Save or Open the file (and continues over and over
until I select Cancel.)

I've also found a suggestion to run Visio with a /noreg switch so that Visio
does not overwrite the Visio Viewer file associations. Unfortunately, it
seems that the Visio Viewer never takes control of the file associations when
it is installed. If I double-click a Visio file immediately after install of
the Visio Viewer, it still launches Visio 2007. I've tried extracting the
visioviewer.exe file and installing using the vviewer.msi file but get the
same results.

I have installed all programs using the 'Install Application on Remote
Desktop...' icon in the Control Panel (equivalent to Install Mode on older
versions of TS.)

Any help greatly appreciated!

Pat Caulfield

Registry file contents below
-----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\.vsd]
@="VisioViewer.Viewer"
"Content Type"="application/vnd.ms-visio.viewer"

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex]

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex\{8895b1c6-b41f-4c1c-a562-0d564250836f}]
@="{21E17C2F-AD3A-4b89-841F-09CFE02D16B7}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CurVer]
@="VisioViewer.Viewer.1"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\DefaultIcon]
@="\"C:\\Program Files\\Microsoft Office\\Office12\VVIEWER.DLL\",-2"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell]
@=""
[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open]
@="Open"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\command]
@="\"C:\\Program Files\\Internet Explorer\\iexplore.exe\" -nohome"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec]
@="\"file:%1\",,-1,,,,,"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec\Topic]
@="WWW_OpenURL"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"
Click to expand...
Click to expand...
 
P

Pat Caulfield

I've spoken with MS Support. They state that this configuration is not
supported. That is a shame because I don't understand what they expect users
of Terminal Servers to do if they want some users to have access to Visio
while others have the ability to view Visio documents.

The rep pointed me towards App-V
(http://technet.microsoft.com/en-us/appvirtualization/default.aspx) for
virtualizing Visio and keeping it in a seperate environment.



Pat Caulfield said:
James,
Thanks for the reply. I don't mind having Visio Viewer being the default
app for Visio files, and having users who need to run Visio open files
through the app. The problem is I have not been able to get Visio Viewer to
be the default app for Visio files when Visio 2007 is installed. Do you know
how this is done? If I try to change file associations through Windows, it
does not allow me to select Visio Viewer (not an option from what I can see.)
I've tried making the HK_Users reg change, but that did not work (files open
in IE but go through an endless loop of asking if I want to open or save.)

We have considered using a seperate server, but can't justify a seperate
server for just a few people.

Thanks.

Pat

James W. said:
I think this issue has come up a few times. If Visio the application and the
Visio Viewer are installed on the same box the application owns the
extensions this is by design. You could make modification so that the viewer
owns the extension but this is an all or none situation. You cannot customize
it so it works for some users. Have you considered using two different
Terminal Servers, one for users that need access to the application the other
for people that use the viewer. You could set up a group policy that routes
the user to the proper Terminal Server. Since the application is only
installed on one box there is no fight over the file extensions.
--
James W.


Pat Caulfield said:
Hello,
We have a Windows 2008 Terminal Server that will be used by most of our
employees. I'd like all users on the server to be able to view Visio
diagrams with Visio Viewer 2007. However, I also need a select few to be
able to use the full version of Visio 2007.

I've locked down the visio.exe file so that only users in a specific group
can run the program. The problem is, Visio 2007 takes control of the file
extensions / file associations. I haven't been able to set the Visio Viewer
to be the default application for launching Visio documents.

I've scoured newsgroups and the internet for a solution. One suggestion was
a registry addition for the HKEY_CURRENT_USER\Software\Classes key for all
users in a login script (see below for contents of reg keys). I've tried
implementing this but it doesn't seem to work. After implementing the key
changes, when I double-click on a Visio file, IE launches and starts a cycle
of asking me if I want to Save or Open the file (and continues over and over
until I select Cancel.)

I've also found a suggestion to run Visio with a /noreg switch so that Visio
does not overwrite the Visio Viewer file associations. Unfortunately, it
seems that the Visio Viewer never takes control of the file associations when
it is installed. If I double-click a Visio file immediately after install of
the Visio Viewer, it still launches Visio 2007. I've tried extracting the
visioviewer.exe file and installing using the vviewer.msi file but get the
same results.

I have installed all programs using the 'Install Application on Remote
Desktop...' icon in the Control Panel (equivalent to Install Mode on older
versions of TS.)

Any help greatly appreciated!

Pat Caulfield

Registry file contents below
-----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\.vsd]
@="VisioViewer.Viewer"
"Content Type"="application/vnd.ms-visio.viewer"

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex]

[HKEY_CURRENT_USER\Software\Classes\.vsd\shellex\{8895b1c6-b41f-4c1c-a562-0d564250836f}]
@="{21E17C2F-AD3A-4b89-841F-09CFE02D16B7}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\CurVer]
@="VisioViewer.Viewer.1"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\DefaultIcon]
@="\"C:\\Program Files\\Microsoft Office\\Office12\VVIEWER.DLL\",-2"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell]
@=""
[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open]
@="Open"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\command]
@="\"C:\\Program Files\\Internet Explorer\\iexplore.exe\" -nohome"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec]
@="\"file:%1\",,-1,,,,,"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer\shell\open\ddeexec\Topic]
@="WWW_OpenURL"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1]
@="Microsoft Visio Document"

[HKEY_CURRENT_USER\Software\Classes\VisioViewer.Viewer.1\CLSID]
@="{279D6C9A-652E-4833-BEFC-312CA8887857}"
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Opening Visio Docs in Visio Viewer with Visio Installed (Again!) 1
Using Visio 2007 Viewer when Visio 2007 application is installed 4
visio viewer cant open in IE8 on Win7 1
Visio viewer issue 3
Visio 2007 vs Visio Viewer - cannot see headers/footers 1
visio viewer not opening in Internet Explorer 3
Install visio 2007 viewer OPCMigrateStartFolders did not close 0
Visio 2007 on Terminal Sevrer 0

Top