/build/static/layout/Breadcrumb_cap_w.png

Microsoft Visio Viewer 2003

Version: 11

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 5.2k  |  Created: 12/31/2003

Average Rating: 0
Visio Viewer 2003 has 1 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (15)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 2 ratings
Most Commonly Reported Deployment Method
Windows Installer Command Line (No MST)
121
Command Line
Appears to work same was as visio viewer 2002(XP). Beware as with the office version, the visio viewer 2003 only works with 2k & higher, if you still have win9x, you will still have to keep your visio 2k/xp viewer around.

In order to install vv2k3 extract the msi from vviewer.exe which is found here.

run
"vviewer.msi /qn /m vviewer ACCEPTEULA=1 ASSOCIATE=1"

There are probably more complex/complete ways to install this, but this seems to work fine for me.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • kkbass
  • 12/31/2003  
  • Show Comments   ( 0 )

119
Note

I used ORCA and added the rows ACCEPTEULA=1 and ASSOCIATE=1 to the Property table. No problems at all.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • yipperzz
  • 09/15/2005  
  • Show Comments   ( 0 )

119
Command Line
Even easier:

vviewer.exe /q /c:"msiexec.exe /i vviewer.msi /qb-! ACCEPTEULA=1 ASSOCIATE=1"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • rasa
  • 10/17/2005  
  • Show Comments   ( 0 )

118
Command Line
To extract the MSI from the exe use the following 2 switches to define to folder & to extract only:

vviewer.exe /T:<Full Path> /C

i.e. c:\download\vviewer.exe /T:E:\VV_MSI /C

Once extracted then run msiexec to get an admin install:

msiexec /a <Full Path + MSI name>

i.e. msiexec /a E:\VV_MSI\VVIEWER.MSI


Then follow the setup to create the new package - this will add the ACCEPTEULA=1 and ASSOCIATE=1 properties for you.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

117
Note

I created a package for AD GPO distribution using Install Shield. I added ACCEPTEULA=1 and ASSOCIATE=1 to the Property table. It works :)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

117
Note
This works perfectly, there is no need to look for another way to do this imo.
Nice work.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • dbowe
  • 06/13/2005  
  • Show Comments   ( 0 )

117
Note
If you are set on using the Office 2003 Custom Installation Wizard from ORK you will have to Configure the Local Installation Source with a Product Key. Neither your Office keys will work, though. You will find the needed Product Key inside the msi's property table under PIDKEY. It's the same for all localized Versions.

On a side note: when grabbing the Setup and MSI from temp, wait a little for the CAB file to appear after starting vviewer.exe. You will get strange errors when you happen to miss that.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • KPrinz
  • 08/10/2005  
  • Show Comments   ( 0 )

117
Note
We cannot get this .MSI to install by extension activation in Group Policy. I think it is buggy. We can get the 2002 version to work fine, but when we publish or assign Visio Viewer 2003 to users, the extensions for Visio files do not show up in AD and when users click on .VSD files nothing happens.

This happens whether or not we add the ASSOCIATE=1 property. If you use AD/GPO you can confirm this by showing properties of User Configuration > Software Settings > Software Installation. Click the File Extensions tab and note there are none even though you've add the 2003 MSI.

I'm too lazy to call MS about this, so we're just going to tell users to go to Add/Remove programs.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • MrWumpus
  • 01/05/2006  
  • Show Comments   ( 0 )

117
Note
just extract using winzip or other extractor and open msi (windows installer) add new keys in property table in setup editor ACCEPTEULA=1 and ASSOCIATE=1 save and run in quite mode

msiexec /i vviewer.msi /qb

it works (wise 6.01)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • theBug
  • 03/23/2006  
  • Show Comments   ( 0 )

117
Note
"Setting the SETVISIO6EXTENSIONS will associate the Viewer with VSD, VST, and VSS documents. SETVISIO10EXTENSIONS will associate the Viewer with VDX, VTX, and VSX documents."

Also see this article
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • rascal
  • 08/01/2006  
  • Show Comments   ( 0 )

117
Note
I bypassed MS and just hacked the hell out of the MSI. I have now managed to create a package that will deploy through AD ;)

If anyone requires this package as it saves ALOT of time (especially in large organisations), please let me know.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • aurora
  • 08/08/2006  
  • Show Comments   ( 0 )

117
Note

For me AcceptEULA = 1 did work.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • t.born
  • 10/27/2006  
  • Show Comments   ( 0 )

117
Command Line
There are lots of ways to install this. Be careful because if you don't extract it first, it is not 100% silent. The extractions is still visible. That will generate support calls. You have to extract it to get it to go silent.

To deploy Visio Viewer 2003 with LANDesk, any of the following methods worked:

Method 1 - Extracting VVIEWER.EXE and using the MSI
1. First run this command:
vviwer.exe /C

When prompted enter a folder to extract the files to.

2. Copy the files to a package server.
3. Create an MSI distribution package that includes only the .cab file as an additional file.
4. Add the following commandline parameters:

ACCEPTEULA=1 ASSOCIATE=1

5. Deploy the MSI distribution package with a silent delivery method.

Method 2 - Extracting VVIEWER.EXE and using the Setup.exe and Setup.ini
Alternately the Setup.ini can be modified with these values.
1. First run vviwer.exe /C and extract the files to a folder.
2. Copy the files to a package server.
3. Open setup.ini
4. Uncomment out this line:

Display=none

5. Add the following two lines to the [Options] section:
ACCEPTEULA=1
ASSOCIATE=1

6. Create an executable distribution package. Include all files from the folder.

Method 3 - Using only the default exectuble VVIEWER.EXE
Warning: With this method the extraction is not silent
1. Create an executable distribution package.
2. Add the following to the command line parameters
/Q /C:"setup /q ACCEPTEULA=1 ASSOCIATE=1"
3. Deploy the distribution package

Method 4 - Extracting VVIEWER.EXE and using the MSI with a Transform
1. Follow the step from method 1.
2. Instead of adding command line parameters, use ORCA to create a transform file to set the following:
ACCEPTEULA=1
ASSOCIATE=1
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • rhyous
  • 09/05/2007  
  • Show Comments   ( 0 )

0
Virtualization
App-V (former SoftGrid) sequencing troubleshoot guide from Microsoft:

http://support.microsoft.com/kb/931987/en-us/

PLEASE NOTE: Visio Viewer 2003 is a plug-in for IE so you should sequence it like web-based application.

Find out more info about it in the latest Microsoft Application Virtualization Sequencing Guide
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Damirson
  • 12/13/2010  
  • Show Comments   ( 0 )

0
Virtualization
We have IE shortcut in a bubble, and VisioViewer is installed on the base image.

To open .vsd files with sequenced IE you need to change the regkey:

[HKEY_CLASSES_ROOT\VisioViewer.Viewer\shell\open\command]
@="\"C:\\Program Files\\Microsoft Application Virtualization Client\\sfttray.exe\" /launch \"Internet Explorer_b2 6.0.3790.3959.0\" \"%1\""

My problem was that every time I double clicked on a file an error message "Windows cannot find file..." and then IE started , and the file was opened.
TO solve this I deleted :

[HKEY_CLASSES_ROOT\VisioViewer.Viewer\shell\open\ddeexec]
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • magellan3
  • 01/21/2011  
  • Show Comments   ( 0 )

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Visio Viewer 2003

Version

11

Questions & Answers (0)

Questions & Answers related to Microsoft Visio Viewer 2003

Blogs (0)

Blog posts related to Microsoft Visio Viewer 2003

Reviews (0)

Reviews related to Microsoft Visio Viewer 2003

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ