Microsoft Visio 2002 Resource Kit
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Appendix
On This Page
Creating an SMS file
Creating Visio Security Templates
Switching Languages in Visio
Deploy Microsoft Visio Viewer 2002
Deploy Microsoft Visio IFilter 2002
Glossary
Creating an SMS file
SMS files contain the information required for Systems Management Server to create a software distribution package. The SMS file for Microsoft Visio 2002 is named Vis2002.sms.
Follow this procedure to create the SMS file for Visio:
To create an SMS file
Copy the text that follows this procedure.
Open Notepad or another text editor.
Paste the text into Notepad.
Save the file as Vis2002.sms.
[PDF] Version=2.0 [Package Definition] Publisher=Microsoft Name=Visio 2002 Version=10.0 Language=English Programs=TypicalOSP, ManualOSP, CustomOSP, OSP, Typical, Manual, Custom, Uninstall MIFName=vis10 [TypicalOSP] Name=Typical including System Update (quiet) CommandLine=setup.exe /qb- REBOOT=ReallySuppress /m vis10 AdminRightsRequired=True UserInputRequired=False DriveLetterConnection=False AfterRunning=SMSRestart CanRunWhen=AnyUserStatus RemoveProgram=False SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win 9x MinVersion1=4.10.1998 Win 9x MaxVersion1=4.10.9999.9999 [ManualOSP] Name=Manual including System Update CommandLine=setup.exe REBOOT=ReallySuppress /m vis10 UserInputRequired=True AdminRightsRequired=True DriveLetterConnection=False AfterRunning=SMSRestart RemoveProgram=False SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win 9x MinVersion1=4.10.1998 Win 9x MaxVersion1=4.10.9999.9999 [CustomOSP] Name=Custom including System Update (quiet) CommandLine=setup.exe /qb- TRANSFORMS="New Custom Setup File.MST" REBOOT=ReallySuppress /m vis10 AdminRightsRequired=True UserInputRequired=False DriveLetterConnection=False AfterRunning=SMSRestart CanRunWhen=AnyUserStatus RemoveProgram=False SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win 9x MinVersion1=4.10.1998 Win 9x MaxVersion1=4.10.9999.9999 [OSP] Name=System Update only (quiet) CommandLine=setup.exe /qb- /sponly REBOOT=ReallySuppress /m vis10 AdminRightsRequired=True UserInputRequired=False DriveLetterConnection=False AfterRunning=SMSRestart CanRunWhen=AnyUserStatus SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win 9x MinVersion1=4.10.1998 Win 9x MaxVersion1=4.10.9999.9999 [Typical] Name=Typical (quiet) CommandLine=setup.exe /qb- /nosp /m vis10 AdminRightsRequired=True UserInputRequired=False DriveLetterConnection=False CanRunWhen=AnyUserStatus RemoveProgram=False SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win NT (I386) MinVersion2=5.00.0000.0 Win NT (I386) MaxVersion2=5.00.9999.9999 Win 9x MinVersion1=4.90.0.3000 Win 9x MaxVersion1=99.99.9999.9999 [Manual] Name=Manual CommandLine=setup.exe /nosp /m vis10 UserInputRequired=True AdminRightsRequired=True DriveLetterConnection=False RemoveProgram=False SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win NT (I386) MinVersion2=5.00.0000.0 Win NT (I386) MaxVersion2=5.00.9999.9999 Win 9x MinVersion1=4.90.0.3000 Win 9x MaxVersion1=99.99.9999.9999 [Custom] Name=Custom (quiet) CommandLine=setup.exe /qb- TRANSFORMS="New Custom Setup File.MST" /nosp /m vis10 AdminRightsRequired=True UserInputRequired=False DriveLetterConnection=False CanRunWhen=AnyUserStatus RemoveProgram=False SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win NT (I386) MinVersion2=5.00.0000.0 Win NT (I386) MaxVersion2=5.00.9999.9999 Win 9x MinVersion1=4.90.0.3000 Win 9x MaxVersion1=99.99.9999.9999 [Uninstall] Name=Uninstall CommandLine=setup.exe /qb- REBOOT=ReallySuppress /m vis10 /x AdminRightsRequired=False UserInputRequired=False DriveLetterConnection=False CanRunWhen=AnyUserStatus SupportedClients=Win NT (I386), Win 9x Win NT (I386) MinVersion1=4.00.1381.6 Win NT (I386) MaxVersion1=4.00.9999.9999 Win NT (I386) MinVersion2=5.00.0000.0 Win NT (I386) MaxVersion2=5.00.9999.9999 Win 9x MinVersion1=4.10.0.1998 Win 9x MaxVersion1=99.99.9999.9999
Creating Visio Security Templates
Microsoft Visio 2002 Security Templates (ADM files) contain the information required for the System Policy Editor to set security levels for Visio. You must create two ADM files, Visio10_Machine.adm, and Visio10_User.adm.
Use the procedures that follow to create Visio Security Templates:
To create Visio 10_Machine.adm
Copy the text that follows this procedure.
Open Notepad or another text editor.
Paste the text into Notepad.
Save the file as Visio10_Machine.adm.
CLASS MACHINE CATEGORY !!Visio CATEGORY !!VBASecurity KEYNAME Software\Policies\Microsoft\Visio\Security POLICY !!MacroSecurityLevel EXPLAIN !!MacroSecurityLevelExplain PART !!MacroSecurityLevel DROPDOWNLIST VALUENAME Level ITEMLIST NAME !!High VALUE NUMERIC 3 NAME !!Medium VALUE NUMERIC 2 DEFAULT NAME !!Low VALUE NUMERIC 1 END ITEMLIST NOSORT END PART END POLICY POLICY !!AccessVBObjectModel EXPLAIN !!AccessVBObjectModelExplain PART !!CheckAccessVBOM CHECKBOX VALUENAME AccessVBOM VALUEON NUMERIC 1 VALUEOFF NUMERIC 0 DEFCHECKED END PART END POLICY POLICY !!No_VBA EXPLAIN !!NoVBAExplain PART !!CheckNoVBA CHECKBOX VALUENAME NoVBA VALUEON NUMERIC 1 VALUEOFF NUMERIC 0 END PART END POLICY END CATEGORY END CATEGORY [strings] Visio= = "Microsoft Visio 2002" VBASecurity = "Visio: Security Settings" MacroSecurityLevel = "Security Level" High = "High" Medium = "Medium" Low = "Low" MacroSecurityLevelExplain = "The Security Level governs the minimum security level at which users must run. \n\nA user will be allowed to elevate his/her security level but will not be allowed to lower it to a value below this setting." AccessVBObjectModel = "Enable access to the Microsoft VBA object model" AccessVBObjectModelExplain = "Disabling access to the Microsoft Visual Basic for Applications (VBA) object model, will prevent macros and programs to access the Application.VBE and Document.VBProject properties. This is a common way for macro viruses to infect other documents." CheckAccessVBOM = "Check to allow access; uncheck to disable access." No_VBA = "Disable Microsoft Visual Basic for Applications" NoVBAExplain = "This setting will prevent Visio from using Microsoft Visual Basic for Applications (VBA), regardless of whether the VBA feature is installed or not. Changing this setting will not install or remove the VBA files from the machine. \n\nUsers will not be able to create VBA projects or run macros. It is also possible that some solutions that use VBA may not run. \n\nSee the Visio on MSDN for more important information about configuring security settings." CheckNoVBA = "Check to disable VBA; uncheck to enable VBA."
To create Visio 10_User.adm
Copy the text that follows this procedure.
Open Notepad or another text editor.
Paste the text into Notepad.
Save the file as Visio10_User.adm.
CLASS USER
CATEGORY !!Visio
CATEGORY !!VBASecurity
KEYNAME Software\Policies\Microsoft\Visio\Security
POLICY !!MacroSecurityLevel
EXPLAIN !!MacroSecurityLevelExplain
PART !!MacroSecurityLevel DROPDOWNLIST
VALUENAME Level
ITEMLIST
NAME !!High VALUE
NUMERIC 3
NAME !!Medium VALUE
NUMERIC 2 DEFAULT
NAME !!Low VALUE
NUMERIC 1
END ITEMLIST
NOSORT
END PART
END POLICY
POLICY !!AccessVBObjectModel
EXPLAIN !!AccessVBObjectModelExplain
PART !!CheckAccessVBOM CHECKBOX
VALUENAME AccessVBOM
VALUEON NUMERIC 1
VALUEOFF NUMERIC 0
DEFCHECKED
END PART
END POLICY
POLICY !!No_VBA
EXPLAIN !!NoVBAExplain
PART !!CheckNoVBA CHECKBOX
VALUENAME NoVBA
VALUEON NUMERIC 1
VALUEOFF NUMERIC 0
END PART
END POLICY
END CATEGORY
END CATEGORY
[strings]
Visio = "Microsoft Visio 2002"
VBASecurity = "Visio: Security Settings"
MacroSecurityLevel = "Security Level"
High = "High"
Medium = "Medium"
Low = "Low"
MacroSecurityLevelExplain = "The Security Level governs the
minimum security level at which users must run. \n\nA user will be
allowed to elevate his/her security level but will not be allowed to
lower it to a value below this setting."
AccessVBObjectModel = "Enable access to the Microsoft
VBA object model"
AccessVBObjectModelExplain = "Disabling access to the Microsoft
Visual Basic for Applications (VBA) object model, will prevent macros
and programs to access the Application.VBE and Document.VBProject
properties. This is a common way for macro viruses to infect other
documents."
CheckAccessVBOM = "Check to allow access; uncheck to
disable access."
No_VBA = "Disable Microsoft
Visual Basic for Applications"
NoVBAExplain = "This setting will prevent
Visio from using Microsoft Visual Basic for Applications (VBA),
regardless of whether the VBA feature is installed or not. Changing
this setting will not install or remove the VBA files from the machine.
\n\nUsers will not be able to create VBA projects or run macros. It is
also possible that some solutions that use VBA may not run. \n\nSee
the Visio on MSDN for more important information about configuring
security settings."
CheckNoVBA = "Check to disable VBA;
uncheck to enable VBA."
Switching Languages in Visio
To permit users to take advantage of language switching, you must install Microsoft Visio 2002 from volume license media, commonly distributed to customers under Open and Select license agreements. In addition, you must purchase and deploy versions of Visio in two or more languages, and you must have already deployed Microsoft Office XP and the Microsoft Office XP Multilingual User Interface Pack. For more information about deploying Microsoft Office XP and the Microsoft Office XP Multilingual User Interface Pack, see the Office Resource Kit.
After you have met all of these requirements, individual users who have more than one language version of Visio installed on their computers can switch languages as follows:
To switch languages in Visio
On the Start menu, point to All Programs (or to Programs, in versions other than Microsoft Windows XP), point to Microsoft Office Tools, and then click Microsoft Office XP Language Settings.
Click the User Interface tab.
In the Display menus and dialog boxes in list, select the language you want.
Deploy Microsoft Visio Viewer 2002
You can deploy Microsoft Visio Viewer 2002 across your corporate network. Within a Microsoft Windows 2000 Server environment and using Active Directory directory service, you can also customize the deployment of the Visio Viewer to target specific users, groups, or computers within your corporate network.
For deployment of the Visio Viewer over your corporate network, you might also need the Microsoft Windows Installer SDK. The Windows Installer includes applications that allow you to modify the MSI file for the Visio Viewer and/or create a transform file. You can download the Windows Installer SDK from the Microsoft Platform SDK Web site.
About Deployment Methods for the Visio Viewer
When you download the Visio Viewer to a single computer that multiple users access, all users of that computer can use the Visio Viewer. If Microsoft Visio is already installed on the computer, those users will be able to use both Visio and the Visio Viewer. Installation of the Visio Viewer for a user on a computer will not change the file extension associations for other users who have Microsoft Visio installed on that computer.
In Microsoft Windows NT 4.0, Windows 2000, and Windows XP environments, different users have different levels of rights and permissions. In these environments, default users have limited access to system areas of the computer. Because of this, the Visio Viewer must be installed by an account with administrative privileges or each user accounts must have elevated installation privileges.
In Windows 2000 and Windows XP, you can set Windows Installer system policies that grant users the elevated permissions they need to install the Visio Viewer. To enable elevated installations permissions, you must set group policies for elevating privileges on each computer by setting a Windows Installer system policy.
Important Use caution when granting elevated permissions to your users. It may compromise your system security by allowing them to install other applications you may not want them to install.
To enable elevated privileges by policy
On the Start menu, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
In the console tree, right-click the domain or organizational unit for which you want to set the policy.
Click Properties, and then click the Group Policy tab.
In the Group Policy Objects Links box, select a Group Policy Object, and then click Edit.
Open the Local Computer Policy\Administrative Templates\Windows Installer folder.
In the details pane, double-click the Always install with elevated privileges policy.
In the Group Policy Property dialog box, enable the policy, select the check box to turn the setting on, and then click OK.
Open the User Configuration\Administrative Templates\Windows Installer folder and repeat steps 6 and 7.
Deploy the Visio Viewer from an Administrative Installation Point
To set up an administrative installation point
Download the Visio Viewer executable file (vviewer.exe) and extract vviewer.msi. To extract the .msi file, at the command line, type the following: vviewer.exe /c. Note /c is a command-line option that extracts files to a temporary folder. The files are not installed in this location.
Enter the path where you want to save the extracted files.
Click the Windows Start button, and then click Run.
In the Open box, add the command Msiexec /a <path to vviewer.msi>. For example, Msiexec /a c:\temp\vviewer.msi.
On the Setup screen, do the following, and then click Next.
Enter your Organization name.
Change the Install Location. **Important ** You must change the installation location from the default location to the location where you would like to create the administrative installation point. If you are using a Universal Naming Convention (UNC), this location should be at least three levels deep.
If you downloaded the vviewer.exe file from the Microsoft Office Downloads Web page, accept the default Product Key. If you are installing the Visio Viewer from a CD, enter the product key from the CD case.
Accept the Microsoft End-User License Agreement (EULA).
Click Install.
Setup runs for the administrative installation. Users on your corporate network can now access the installation point and install the Visio Viewer. You can then distribute command lines to run the Visio Viewer MSI on users computers in unattended mode by adding /qb- as a command-line option. For more information on deploying the Visio Viewer using a command line, see "Deploy the Visio Viewer Using a Command Line" below.
Note For additional information on modifying and distributing command-line options, see Customizing the Visio Installation in Chapter 4 of the Microsoft Visio 2002 Resource Kit.
Modify Installation with a Transform File
You can modify the properties of the Visio Viewer 2002 installation by using two tools included in the Windows Installer SDK:
Orca, which allows you to open vviewer.msi and make changes to the tables in the .msi file.
Msitran.exe, which allows you to generate a new transform (.mst) file based on the changed tables in the .msi file.
You can download the complete Windows Installer SDK from the Microsoft Download Center. The Windows Installer SDK includes the Msi.chm, which contains additional information about creating Windows Installer transform files.
Note Creation and modification of transform files for the Visio Viewer 2002 are not supported in the Microsoft Office XP Custom Installation Wizard.
To modify the Visio Viewer .msi file by creating a transform file
Right-click the .msi file you want to modify, then click Edit with Orca.
The Tables column displays the names of the tables in the .msi file on the left. The pane on the right displays the properties associated with those tables.
Navigate to the Property table. You can add properties and make changes to properties in the Property table. The following table provides some of the main properties you can modify.
If you would like more detailed information about each of these properties, please see the Windows Installer SDK, which you can download from the Microsoft Platform SDK Web site.
Property
Function and Property Value
ARPCONTACT
Edits the contact field on the Support Info page in Add/Remove Programs.
Value: <string>
Examples:
ARPCONTACT=Adventure Works
ARPHELPLINK
Displays the link to online Help.
Value: <string> This is an URL that points to a local file or online file.
Example:
ARPHELPLINK=https://www.adventure-works.com/support.html/
ARPHELPTELEPHONE
Displays the Support phone number.
Value: <string>
Example:
ARPHELPTELEPHONE=555-555-0100
ARPNOMODIFY
Disables the Change button in Add/Remove Programs.
Values: Null, 1
Default value: Null
Examples:
ARPNOMODIFY=1
This disables the Change button.
ARPNOMODIFY=
This enables the Change button.
ARPNOREMOVE
Disables the Remove button in Add/Remove Programs.
Values: Null, 1
Default value: Null
Examples:
ARPNOREMOVE=1
This disables the Remove button.
ARPNOREMOVE=
This enables the Remove button.
ARPNOREPAIR
Hides the Repair button on the Support Info page in Add/Remove Programs.
Values: Null, 1
Default value: Null
Examples:
ARPNOREPAIR=1
This disables the Repair button.
ARPNOREPAIR=
This enables the Repair button.
ARPPRODUCTICON
Specifies the icon that is displayed in Add/Remove Programs.
Value: Path to icon file. It does not have to reside on the network share.
Examples:
ARPPRODUCTICON=\server\share\folder\icon.ico
ARPREADME
Specifies the location of the Readme on the Support Info page in Add/Remove Programs.
Value: Path to the Readme file. It does not have to reside on the network share.
Example:
ARPREADME= \server\share\folder\readme.txt
ARPSYSTEMCOMPONENT
Prevents the Visio Viewer from being displayed in Add/Remove Programs. Can be used to lock out users.
Values: Null, 1
Default value: Null
Examples:
ARPSYSTEMCOMPONENT=
This displays the Visio Viewer in the Add/Remove Programs.
ARPSYSTEMCOMPONENT=1
This prevents the Visio Viewer from being displayed in Add/Remove Programs.
ARPURLUPDATEINFO
Links to update on the Support Info page in Add/Remove Programs.
Value: URL path to update information page. The path can be to a local file or to a Web site.
Example:
ARPURLUPDATEINFO=https://www.adventure-works.com/updates.html
ASSOCIATE
Sets whether or not files with Visio extensions will or will not be associated with the Visio Viewer.
Values: 0, 1
Default value: 1
Examples:
ASSOCIATE=0
This turns off Visio file extension association with the Viewer.
ASSOCIATE=1
This turns on Visio file extension association with the Viewer.
COMPANYNAME
Populates the Organization field on the User Information page. The default value for this field is obtained from the registry.
Value: <string>
Example:
COMPANYNAME=Adventure Works
LIMITUI
Limits the user interface. Equivalent to using /q at a command line.
Values: Null, 1
Default value: Null
Examples:
LIMITUI=
This exposes the full user interface.
LIMITUI=1
This limits the user interface.
NOCOMPANYNAME
Clears the Organization field on the User Information page.
Values: Null, 1
Default value: Null
Examples:
NOCOMPANYNAME=
This populates the Organization field with the company name.
NOCOMPANYNAME=1
This removes the company name from the Organization field.
NOUSERNAME
Clears the Username field on the User Information page.
Values: Null, 1
Default value: Null
Examples:
NOUSERNAME=0
This populates the User Name field with the default users name taken from the Windows registry.
NOUSERNAME=1
This clears the default users name from the User Name field.
OVERRIDEASSOCIATE
Turns off user intervention on the File Type Association page.
Values: 0, 1
Default value: 0
Examples:
OVERRIDEASSOCIATE=0
This allows users to change the file association setting in the Visio Viewer setup.
OVERRIDEASSOCIATE=1
This does not allow users to change the file association setting in the Visio Viewer setup.
PIDKEY
Populates the PIDKEY fields on the User Information page.
Value: 25 characters, alphanumeric, no spaces between characters.
Example:
PIDKEY=12345abcde67898fghij76543
TARGETDIR
Specifies the output directory of an administrative installation.
Value: Path to administrative installation point.
Example:
TARGETDIR=\\server\share\folder\
TRANSFORMS
Specifies a transform or list of transforms applied to the installation.
Value: Path to transform file(s). Each transform must be listed in the order in which they should be applied and enclosed in quotes ( ). Multiple transforms must be separated with a semi-colon.
Example:
TRANSFORMS=\\server\share\folder\transform1.mst; \\server\share\folder\ transform2.mst
USERNAME
Populates the User Name field on the User Information page.
Value: <string>
Example:
USERNAME=Kim Akers
After modifying the property values, click File, and then click Save As and save the .msi file to a new name in the same directory where vviewer.msi is saved.
Click the Windows Start button, and then click Run.
Create a transform file by adding Msitran.exe -g (a flag indicating the creation of a new transform file), the path to and name of the original Visio Viewer .msi file, the path to and name of your newly created .msi file, and the path to and name you want to give to the transform file at the Open command line of Run.
For example, at the Open command line, type:
Msitran.exe –g \\server\share\folder\vviewer.msi \\server\share\folder\vviewer2.msi \\server\share\folder\vtrans.mstMsitran.exe creates the transform file and saves it to the file name and location you specified in the path.
You can now apply the transform file to your deployment of the Visio Viewer, or you can use the transform file if you are deploying the Visio Viewer using Active Directory.
If you are deploying different configurations of the Visio Viewer, you need to create a transform file for each one of your configurations.
For example, you may have users who have Microsoft Visio installed, and you do not want the Visio Viewer to override the Visio file extensions. In this case you would modify and create a new .msi file based on vviewer.msi, then create a modified transform file by editing the Property table so that ASSOCIATE = 0. When users install the Visio Viewer by using the modified .msi file and applying the transform, the files that are already associated with their Microsoft Visio product version will remain associated with their product version. They will also be able to open, view, and Visio files in Internet Explorer, version 5.0 and later.
Deploy the Visio Viewer Using a Command Line
When users double-click vviewer.msi, installation runs with no command-line options. To apply your custom command-line options, users must click Run on the Windows Start menu and enter the path to vviewer.msi along with the command-line options you distribute.
To simplify this process, create a batch file that runs vviewer.msi with your command-line options. Or you can create a Windows shortcut and add your custom options to the command line. Users double-click the batch file or shortcut to run the Setup command line that you have defined. You can store the batch file or shortcut in the root folder of the administrative installation point.
Distribute Command-line Options
Deploying the Visio Viewer with a command-line option allows you to customize the command line to set specific properties from the .msi file to the installation. Instead of creating a transform file, you can set specific Property table property values at the command line. These property values will then determine what occurs during installation of the Visio Viewer. A list of the Property table properties can be found in the section "Modify Installation with a Transform File" earlier in this article.
For example:
Msiexec /i \\server\share\vviewer.msi ASSOCIATE=1 COMPANYNAME=Adventure Works /T \\server\share\folder\transform1.mst;\\server\share\folder\transform2.mst /qb
Note Any value which requires a string should be enclosed in quotes ( ). This enables the string value to contain spaces or special characters.
In the command-line example above, note the following:
Msiexec /i indicates that you are doing an installation of the .msi file indicated in the following segment. This should always be the first command in the command line.
\\server\share\viewer.msi, indicates the network path to the location of the Visio Viewer MSI file.
ASSOCIATE=1 indicates that you are associating files with Visio extensions (VST, VSD, etc.) with the Visio Viewer
COMPANYNAME=Company Name forces the name you enter for the string to display in the setup dialog box.
/T \\server\share\path\vtrans1.mst;\\server\share\path\transform2.mst indicates that you are applying two transform files, in the order you specify, to the installation.
/qb indicates a silent installation of the Visio Viewer.
Deploy the Visio Viewer using Active Directory
After creating the administrative point and any transform files, you can deploy the Visio Viewer using Active Directory. Within Active Directory you can either create a new Group Policy or modify an existing Group Policy for deploying the Visio Viewer.
Methods of deploying the Visio Viewer using Active Directory include:
Assign. Assigning the Visio Viewer to a computer automatically installs the Viewer on that computer after the computer has been rebooted.
Publish. Publishing the Visio Viewer creates an application icon in Add New Programs of Add or Remove Programs in Control Panel. The user can then click Add to install the Visio Viewer. You can also choose to publish the Visio Viewer by extension. Publishing by extension automatically installs the Visio Viewer for a user when that user double-clicks a file with a Visio extension. Publishing by extension occurs after the Group Policy has been created and the user's computer is rebooted.
Important The Visio Viewer cannot be assigned to individual users. It must either be assigned to computers, published to a user, or published by extension to a user.
To Publish or Assign the Visio Viewer to a User or Computer using Active Directory
On the Start menu, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
Right-click the Organizational Unit representing the Group you want to deploy the Visio Viewer to and click Properties.
On the Group Policy tab, do one of the following:
Select an existing Group Policy, then click Edit if you already have a Group Policy and want to add the Visio Viewer .msi file to that existing policy, then go to step 5.
Click New to create a new Group Policy, then go to step 4.
Rename the new Group Policy, for example, Visio Viewer, then click Edit.
In the Group Policy dialog box, choose one of the following:
Expand the Computer Configuration node to create a Group Policy assigning the Visio Viewer to all computers in that groups Organizational Unit.
Expand the User Configuration node to create a Group Policy publishing the Visio Viewer to users in that groups Organizational Unit.
Expand Software Settings. Then Right-click the Software Installation node, click New, and then click Package.
Browse to the Visio Viewer MSI, and in the Open dialog box, select the Visio Viewer MSI in the File Name list, and then click Open.
In the Deploy Software dialog box, do one of the following
Click Publish to publish the Visio Viewer to users in that groups Organizational Unit. Note The Auto-install this application by file extension activation option is on by default when you publish a package. If you choose to publish by extension, make sure that you do not have more than one application that uses those file extensions in the GPO. For example, if you have Microsoft Visio 2002 and the Visio Viewer both Published in the same Group Policy Object, and you choose to publish by extension, the last one published is the one that gets installed. To disable auto-installing the Visio Viewer by extension for a package, double-click the package in Group Policy to open its property sheet. Click the Deployment tab, and clear the box labeled Auto-install this application by file extension activation.
Click Assign to automatically install the Visio Viewer on computers in that groups Organizational Unit after the first reboot of those computers.
Click OK. Important You cannot add a transform file to these types of Visio Viewer installations. If you want to deploy the Visio Viewer using a transform file, see To Publish or Assign the Visio Viewer Using a transform file below.
To Publish or Assign the Visio Viewer using a transform file
Follow steps 1 through 7 above to create or modify an existing Group Policy and create a new installation package.
In the Deploy Software dialog box, click Advanced published or assigned.
In the Properties dialog box for the Visio Viewer .msi file, click the Modifications tab.
In the Open dialog box, browse to the administration installation location of the transform file that you want to apply to the installation of the Visio Viewer.
Click Move Up or Move Down to set the order for the transform to install. Note You must apply multiple transforms in the order in which you want them applied to installation.
On the Deployment tab and do one of the following:
If you are assigning the Visio Viewer to computers, make sure Assigned is selected, then click OK to close the Visio Viewer Properties dialog box.
If you are publishing the Visio Viewer, make sure Published is selected. If you don’t want the Visio Viewer to install by extension, make sure Auto-install this application by file extension activation is unchecked, then click OK.
Re-associate File Types with Microsoft Visio
Default settings associate all Microsoft Visio file types with the Visio Viewer. If Visio is already installed on a computer, Microsoft Visio Viewer will be associated with .vsd and .vdx files. Therefore, when you open a .vsd or .vdx file from within Internet Explorer, you will launch the Visio Viewer rather than Microsoft Visio.
If you want to re-associate file extensions with Microsoft Visio 2000 or Visio 2002 instead of Microsoft Visio Viewer, you must repair Microsoft Visio. If you are using Microsoft Visio 5.0 or 5.0c and want to re-associate file extensions with either of those products, first uninstall Microsoft Visio 5.0 or 5.0c, and then reinstall it.
To re-associate Visio Viewer file types with Microsoft Visio 2000 or 2002
Click the Windows Start button, and then click Control Panel.
Click Add/Remove Programs, and then select Microsoft Visio.
Click Change, and then select Repair to make file extension modifications.
Click Next.
Deploy Microsoft Visio IFilter 2002
Use Microsoft Visio IFilter 2002 to search for text, shapes, and other information in Microsoft Visio diagrams. IFilter is supported by the following versions of Visio:
Visio 2002
Visio 2000
Visio 5.0c
Visio 5.0
Visio IFilter searches the diagrams index to find specific text or shapes, information in the Visio ShapeSheet, or Visio diagram properties. When you set up the Visio IFilter on each computer, it installs a DLL on the computer that indexes all Visio documents, stencils, and templates. XML file formats are also indexed for Visio 2002.
This article describes how to:
Deploy the Visio IFilter across a corporate network.
Publish or Assign the Visio IFilter using Group Policy and Active Directory.
Start indexing services.
Search for Visio diagram properties.
Requirements
Operating Systems
Microsoft Windows must be installed on the computer on which you want to install Visio IFilter, and must be one of the following versions:
Microsoft Windows NT 4.0 with Service Pack (SP) 6
Microsoft Windows 2000
Microsoft Windows XP (Professional or Home) Note Visio IFilter is not supported by Microsoft Windows Millennium Edition (Me) or any Microsoft Windows 9x platforms.
If you choose to Publish or the Visio IFilter all the computers in your organization are required to be running Windows 2000 or later. You must also have implemented an Active Directory service and Group Policy structure
Files to Install Before Setting up Visio IFilter
For VisioIFilter to install properly, you must first install the following files on each computer:
Windows Installer 1.1 or later. You can download the Windows Installer for Microsoft Windows NT 4.0 from the Microsoft Download Center. Microsoft Windows 2000 and Microsoft Windows XP already include file versions later than 1.1.
MSXML 2.5 or later. If your operating system is Windows NT 4.0 with SP 6, MSXML should be version 2.5 or later. Windows 2000 and Windows XP already include MSXML 2.5. During installation, Visio IFilter setup checks for MSXML 2.5, but does not automatically install it. If setup determines that MSXML 2.5 is not installed on the computer, the Visio IFilter is not installed.
To install MSXML 2.5, do one of the following:
Upgrade your browser to at least Internet Explorer 5.01, which also upgrades MSXML to 2.5.
Upgrade to MSXML 2.5 to avoid installing Internet Explorer 5.01 or later and for redistribution on earlier operating systems (Windows 95, 98, and Windows NT 4.0). You can download MSXML from the XML General Downloads page on MSDN.
Additional Information for Deploying the Visio IFilter Over a Corporate Network
The following resources can help you successfully deploy the Visio IFilter:
Windows Installer SDK: The Windows Installer includes applications you can use to modify the MSI file for the Visio IFilter and/or create a transform file. You can download the Windows Installer SDK from the Microsoft Download Center.
Office XP Resource Kit: View the Office XP Resource Kit on the Microsoft Office XP Web site.
Note Deployment of the Visio IFilter is not supported by the Microsoft Office Custom Installation Wizard. To create and modify a transform file for deployment of the Visio IFilter, you should use the Windows Installer SDK.
Deployment Methods for the Visio IFilter
You can deploy Microsoft Visio IFilter 2002 across your corporate network. Within a Microsoft Windows 2000 Server environment and using Active Directory, you can also customize the deployment of the Visio IFilter to target specific users, groups, or computers within your corporate network.
When you install the Visio IFilter on a single computer that multiple users access, but that is not necessarily connected to a network, all users of that computer can use the Visio IFilter.
Important For computers connected to a corporate network, install the Visio IFilter from an administrative installation point. For instructions, see Deploy the Visio IFilter from an Administrative Installation Point later in this article.
From an administrative installation point, you can:
Distribute a command line pointing to the administrative image containing the visfilt.msi file.
Deploy the Visio IFilter.
Use Active Directory to Publish or Assign the Visio IFilter in Control Panel on your users computers. **Important **Visfilt.exe is an IExpress wrapper for the IFilter MSI package, visfilt.msi. Visfilt.exe does not support any advanced deployment methods. To pass command line parameters or use the deployment methods, first extract visfilt.msi from the Visfilt.exe package.
To extract the visfilt.msi from Visfilt.exe package
Download and save Visfilt.exe to a temporary folder.
On the command line, extract visfilt.msi using the syntax Visfilt.exe /c Note /c is an IExpress setup switch that extracts files to a temporary folder. The files are not installed in this location.
Enter the path where you want to save the extracted MSI file.
Distribute Command-line Options
When users double-click visfilt.msi on a network share, installation runs with no command-line options. To apply your custom command-line options, users must click Run on the Windows Start menu and enter the path to visfilt.msi along with the command-line options you distribute.
To simplify this process, create a batch file in MS-DOS that runs visfilt.msi with your command-line options. Or you can create a Windows shortcut and add your custom options to the command-line box. Users double-click the batch file or shortcut to run the Setup command line that you have defined. You can store the batch file or shortcut in the root folder of the administrative installation point.
Deploy the Visio IFilter from an Administrative Installation Point
For computers connected to a corporate network, first create a network share and ensure your users have permissions to use it. After creating the network share, create an administrative installation of the Visio IFilter. Users on your corporate network can then access this share and install the Visio IFilter.
In Microsoft Windows NT 4.0, Windows 2000, and Windows XP environments, different types of users have different levels of rights and permissions. In these environments, default users have limited access to system areas of the computer. Because of this, an account with administrative privileges must be used to install the Visio IFilter, or users must have elevated privileges for installing applications. To enable elevated installations, you must set a group policy for elevating privileges on each computer in order to install the Visio IFilter. Use the Group Policy editor (gpedit.msc) to enable the policy Always install with elevated privileges.
For more information on setting elevated privileges for users, and for setting group policy for computers, see Installations that Require Elevated Permissions in Chapter 3 of the Microsoft Visio 2002 Resource Kit.
For general information about installing Visio, see Planning a Visio 2002 SR-1 Deployment in Chapter 2 of the Microsoft Visio 2002 Resource Kit.
Important Use caution when granting elevated rights to your users. It may compromise your system security.
To set up an administrative installation point
Download the Visio IFilter executable file (Visfilt.exe) and extract visfilt.msi. To extract the MSI file, on the command line, use the following syntax: Visfilt.exe /c Note /c is an IExpress setup switch that extracts files to a temporary folder. The files are not installed in this location.
Click the Windows Start button, and then click Run.
In the Open box, add the command Msiexec /a <path to visfilt.msi>. For example, Msiexec /a *c:\temp\*visfilt.msi.
Change the installation location to where you want the administrative installation to be created. Note If you are using a Universal Naming Convention (UNC), this location should be at least three levels deep.
Accept the Microsoft End-User License Agreement (EULA), and then click Install. Note For more information on modifying and distributing command line options, see Customizing the Visio Installation in Chapter 4 of the Microsoft Visio 2002 Resource Kit.
Modify Installation with a Transform File
You can modify the properties of the Visio IFilter 2002 installation by using two tools included in the Windows Installer SDK:
Orca, which allows you to open visfilt.msi and make changes to the tables in the MSI.
Msitran.exe, which allows you to generate a new transform (MST) file based on the changed tables in the MSI.
You can download the complete Windows Installer SDK from the Microsoft Download Center. The Windows Installer SDK includes the Msi.chm, which contains additional information about creating Windows Installer transform files.
Note Creation and modification of transform files for Visio IFilter 2002 are not supported in the Microsoft Office XP Custom Installation Wizard.
To modify the IFilter MSI file by creating a transform file
Start the Orca tool.
Click File, and then click Open. Browse to the location where you saved visfilt.msi.
The Tables column displays the names of the tables in the MSI on the left. The window on the right displays the properties associated with those tables.
Navigate to the Property table, and modify the property values you want.
Click File, click Save As, and save the MSI file with a new name in the same directory where visfilt.msi is saved.
Copy Msitran.exe from the location where you installed the Windows Installer SDK to the folder where the two MSI files are located. By default, Msitran.exe is installed on your computer in the \\Program Files\MsiIntel.SDK\Tools folder.
Click the Windows Start button, and then click Run.
Open a command prompt, and navigate to the folder where visfilt.msi, your modified MSI, and Msitran.exe are located.
Create a transform file by typing Msitran.exe –g, the name of the original IFilter MSI, the name of your newly created MSI, and the name you want to give to the transform file at the command prompt.
For example:
Msitran.exe –g visfilt.msi ifilter2.msi trans.mstPress Enter to create the new transform file, and then exit the command prompt. Msitran.exe creates the transform file and saves it in the same folder as the two MSI files.
You can now apply the transform file to your installation of Visio IFilter, or you can use the same file if you are deploying IFilter using Active Directory or System Management Services (SMS).
Note An SMS white paper is available in the Office XP Resource Kit Toolbox. To download the white paper, see the section Using SMS 2.0 to Deploy Office XP in the Office XP Resource Kit. The Appendix of the Visio 2002 Resource Kit also contains text used to create an SMS file.
Deploy Visio IFilter using Group Policy and Active Directory
After creating the administrative point and any transform files, you can deploy the Visio IFilter using Active Directory to publish or assign the Visio IFilter installation.
When publishing, Visio IFilter is displayed under Add New Programs in Add or Remove Programs of Control Panel. The user must then choose to install the Visio IFilter using Add New Programs. After the Visio IFilter is installed, all users of that computer can use it. When assigned to a computer, Visio IFilter automatically installs on that computer.
Note You cannot deploy the Visio IFilter by assigning it to individual users, and no IFilter icon is created on the Start menu.
Publishing or Assigning the Visio IFilter
Use the Group Policy snap-in to publish or assign the Visio IFilter. After setting up IFilter to be published or assigned you can then apply a transform file to the installation, so that when Visio IFilter is installed on a computer, that transform file is applied to the installation.
To publish or assign the Visio IFilter using Active Directory
Open the Group Policy snap-in and click one of the following nodes:
For publishing the Visio IFilter, click User Configuration.
For assigning the Visio IFilter, click Computer Configuration.
Click Software Settings.
Right-click the Software Installation node, click New, and then click Package.
Browse to the Visio IFilter MSI.
In the Open dialog box, select the Visio IFilter MSI in the File Name list, and then click Open.
In the Deploy Software dialog box, click Published or Assigned, and then click OK.
To modify publishing or assigning using a transform file
Follow steps 1-4 in the preceding procedure to Publish or Assign the Visio IFilter.
In the Deploy Software dialog box, choose Advanced publish or assign.
Click the Modifications tab, and then click Add.
In the Open dialog box, browse to the administration installation location of the transform file that you want to apply to the installation of the Visio IFilter, and then click OK. If you are applying multiple transforms to the installation, you must add the transforms in the order in which you want them applied to the installation.
Start Indexing Service
You must start Indexing Service on the computer before you can perform searches. After you start Indexing Service, you can execute queries to search for specific text or shapes within a diagram, information within the Visio ShapeSheet, or diagram properties.
To start Indexing Service
In the Computer Management console, click the Indexing Service node.
Click Start Indexing on the toolbar.
If Indexing Service is running or has been set to start automatically, the Start Indexing button is dimmed.
Once Indexing Service starts, you can use it or any search mechanism to query for files. Other search mechanisms include the Windows Search functionality, SharePoint Team Services, or SharePoint Portal Server.
Searchable Diagram Properties using Visio IFilter
Visio IFilter provides index information for the following information sets: Document Contents Information, Document Summary Information, and Master Keywords Property. The following tables describe these sets.
Document Contents Information Set |
ID |
PropID |
|---|---|---|
Text Contents |
B725F130-47EF-101A-A5F102608C9EEBAC |
PropID=19 |
This set includes:
Shape Name, which indexes the data in the following order: Name, NameU, ID.
User defined properties and values.
Custom properties and values.
Document Summary Information Set
ID
PropID
DocTitle
F29F85E0-4FF9-1068-AB9108002B27B3D9
PropID=0x2
DocSubject
F29F85E0-4FF9-1068-AB9108002B27B3D9
PropID=0x3
DocAuthor
F29F85E0-4FF9-1068-AB9108002B27B3D9
PropID=0x4
DocKeywords
F29F85E0-4FF9-1068-AB9108002B27B3D9
PropID=0x5
DocComments
F29F85E0-4FF9-1068-AB9108002B27B3D9
PropID=0x6
This set includes data from:
Document Summary Information in Visio binary files. These include file formats with .VSD, .VSS, and .VST extensions.
Document Properties in XML for Visio. These include file formats with .VDX, .VSX, and .VTX extensions.
Master Keywords Property Set
ID
PropID
Master Keywords
A4790B72-7113-4348-97EA292BBC1F6770
PropID=0x5
MasterDetails
A4790B72-7113-4348-97EA292BBC1F6770
PropID=0x6
This set includes data from:
MasterKeywords In Visio 2002 MasterKeywords are located in the user.visKeywords cell.
MasterDetails, which indexes the data in the following order:
Master name. Derives its information from the masters name, the nameu, or ID cells.
Master prompt. Prompt cell of a master.
Master version. The version of Microsoft Visio that created the file. Supported Visio versions are Visio 5.0/5.0c, Visio 2000, Visio 2002, and Visio 2002 SR-1.
Glossary
access control list (ACL) Contains a list of user IDs or groups and their security permissions. Identifies who can update, modify, or delete an object on a computer or resource on the network.
Active Server Pages (ASP pages) Technology that allows Web developers to combine scripts and HTML code to create dynamic Web content and Web-based applications.
administrative installation point Network share from which users install Visio. Created by running Setup with the /a command-line option; contains all the Visio files.
administrative rights Highest level of permissions that can be granted to an account in Windows NT User Manager. An administrator can set permissions for other users and create groups and accounts within the domain. Required to install the System Files Update.
advertise Windows Installer method for making a feature available to the user without installing it. When the user attempts to use the application for the first time, the application is installed and run. Applications can be advertised by using the /jm command-line option (Windows NT 4.0 and Windows 2000) or by using IntelliMirror software installation (Windows 2000 only). See also assign, publish.
assign Method of installing a feature when using Windows 2000 Group Policy support. An administrator assigns the application to a user, group, or computer. When the application is selected for the first time, Windows Installer installs the application. Assigning places a shortcut for the assigned application in the Start menu. See also advertise, publish.
automatic recovery See rollback.
bucket A folder path within the File Folder Tree where cabinet files for a specific Application, Module, and region of memory are stored.
cache A special memory subsystem in which frequently used data values, such as files that are made available for use offline, are duplicated for quick access.
certificate Set of data issued by a certificate authority to completely identify an entity; issued only after that authority has verified the entity's identity.
certificate authority A mutually trusted organization that issues certificates. Before issuing a certificate, the certificate authority requires you to provide identification information. VeriSign, Inc., is a recognized certificate authority.
chaining, chained package Method used to include additional packages in a Visio installation; chained packages are specified in the Setup settings file.
character entity reference A set of HTML characters that are represented by easy-to-remember mnemonic names.
character set A grouping of alphabetic, numeric, and other characters that have some relationship in common. For example, the standard ASCII character set includes letters, numbers, symbols, and control codes that make up the ASCII coding scheme. See also code page.
child feature A subordinate feature in the Visio feature tree; contained within a parent feature. Setting an installation state for a parent feature can affect the installation state of a child feature.
clear text Unencrypted, non-machine dependent, ASCII text in readable form.
code page Ordered set of characters in which a numeric index (code point) is associated with each character of a particular writing system. There are separate code pages for different writing systems, such as Western European and Cyrillic. See also Unicode.
code point Numeric value in Unicode encoding or in a code page; corresponds to a character. In the Western European code page, 132 is the code point for the letter ; however, in another code page, the code point 132 might correspond to a different character.
complex script Writing system based on characters that are composed of multiple glyphs or whose shape depends on adjacent characters. Thai and Arabic use complex scripts. See also glyph.
configuration property Also known as configuration variable, a property that allows an administrator to control SharePoint Team Services settings.
digital certificate File issued by a certificate authority. Can be used to verify the user's identity for digitally signed or encrypted e-mail messages. Associates the user's identity with a public encryption key.
Digital ID Combination of a digital certificate and a public and private encryption key set.
digital signature Confirms that an e-mail message, macro, or program originated from a trusted source who signed it. Also confirms that the message, macro, or program has not been altered.
Document libraries A folder where a collection of files is stored amid the files often using the same template. Each file in a library is associated with user-defined information that is displayed in the content listing for that library.
elevated privileges In Windows 2000 and Windows NT 4.0, a method of granting administrator rights to an installation program to modify system areas of the Windows registry or password-secured folders of a hard disk. Can be accomplished by logging on with administrator rights, advertising the program, giving administrator rights to all Windows Installer programs, or using Systems Management Server. See also advertise.
encryption Method used to scramble the content of a file or data packet to make the data unreadable without the decryption key.
encryption, 128-bit High level of encryption. Uses a 128-bit key to scramble the contents of a file or data packet to make the data unreadable without the decryption key.
encryption, 40-bit Low level of encryption. Uses a 40-bit key to scramble the contents of a file or data packet to make the data unreadable without the decryption key.
file allocation table (FAT) Common file format of file cataloging for DOS and Windows operating systems; physical method of storing and accessing files from a hard disk. The FAT contains a list of all files on the physical or logical drive.
File Folder Tree A folder tree structure where crash-reporting data from DW.exe is reported. Used as an intermediate storage area so that administrators can review the data before it is submitted to Microsoft.
FrontPage Server Extensions A set of programs and scripts that support authoring in Microsoft FrontPage and extend the functionality of a Web server.
FTP File Transfer Protocol. Protocol used to gain remote access to a Web server.
glyph Shape of a character as rendered by a font. For example, the italic "a" and the roman "a" are different glyphs representing the same alphabetical character.
Group Policy In Windows 2000, allows administrators to manage users' computer configuration, including installation and maintenance of Visio. You use Group Policy to define configurations for groups of users and computers, and you can specify settings for registry-based policies, security, software installation, scripts, folder redirection, and remote installation services.
home page Main page of a Web site. Usually has hyperlinks to other pages, both within and outside the site. One Web site can contain many home pages. For example, the Microsoft home page contains a Products home page, which contains other home pages.
host The main computer in a system of computers connected by communications links.
hyperlink Colored and underlined text or a graphic that you click to go to a file, a location in a file, an HTML page on the World Wide Web, or an HTML page on an intranet. Hyperlinks can also go to newsgroups and to Gopher, Telnet, and FTP sites.
ideographic script Writing system that is based on characters of Chinese origin, where the characters represent words or syllables that are generally used in more than one Asian language.
input locale Sets what language is currently being entered and how to display it. Usually used in reference to the keyboard, code page, and font configuration of an operating system. See also user locale.
Input Method Editor (IME) Software utility that converts keystrokes to characters in an ideographic script (Korean, Chinese, Japanese, and so on).
installation language Locale ID (LCID) assigned to the value entry InstallLanguage in the Windows registry. Also called the default version of Visio. This entry, along with other language settings, determines default behavior of Visio features.
installation state The installation setting applied to a Visio feature; determines whether a feature is installed locally, run from the network, installed on demand, not installed, or not available to users.
IntelliMirror In Windows 2000, a set of tools and technologies that allow administrators to manage users' computer configurations by policy. IntelliMirror includes a software installation and maintenance feature that can be used to install and manage Visio.
Internet The World Wide Web.
intranet An internal Web site for an organization.
JavaScript A cross-platform, World Wide Web scripting language. JavaScript code is inserted directly into an HTML page. JavaScript makes it possible to build Java programs.
keypath A file or registry entry listed as part of a component or feature of Visio. If missing, triggers a reinstall of that component.
LAN Local area network. A computer network technology designed to connect computers separated by a short distance. A LAN can be connected to the Internet and used for intranet Web sites.
local administrators group The group of users who have permission to perform administrative tasks on the local server computer. The permissions for this group are set by using the administration tools for the operating system.
locale ID (LCID) A 32-bit value defined by Windows that consists of a language ID, sort ID, and reserved bits. Identifies a particular language. For example, the LCID for English is 1033, and the LCID for Japanese is 1041.
maintenance mode Configuration mode of an operating system for installing, updating, or removing applications. An important consideration for NT-based operating systems where users require access to secure sections of the registry or a hard disk. See also elevated privileges.
MSDE Microsoft Data Engine (also known as Microsoft SQL Server 2000 Desktop Engine). A data store based on Microsoft SQL Server technology, but designed and optimized for use on smaller computer systems, such as a single user computer or a small workgroup server.
MSI file See package.
MST file See transform.
network domain name A group of users in a network who share a common set of resources, such as server disk drives and printers. A large network may have several domains based on the needs of each set of users.
network place A folder on a network file server, Web server, or Exchange 2000 server. Create a shortcut to a network place to work with files there. Some network places, such as document libraries, have features not available with local folders.
NLS files National Language Support files. Files that extend the ability of the operating system to support multilingual features.
NTFS file system (NTFS) Designed exclusively for use with the Windows NT operating system. NTFS allows for stronger security and more flexible file management methods than does FAT. See also file allocation table (FAT).
package (MSI file) In Windows Installer, a relational database that contains all the information necessary to install a product. The MSI file associates components with features and contains information that controls the installation process.
plug-in language features User interface, online Help, and editing tools that users can install with Visio to run Visio in the users own language and to create documents in many other languages.
private key One of a pair of keys used for encryption. A message encrypted with the private key must be decrypted with the public key. Part of a Digital ID.
public key One of a pair of keys used for encryption. A message encrypted with the public key must be decrypted with the private key. Part of a Digital ID.
publish A method of advertising a feature by using Windows 2000 Group Policy support. A published application is not advertised with shortcuts or Start menu icons. Instead, the application is configured to be installed the first time another application requests it, such as when double-clicking a .doc file from Windows Explorer. See also advertise, assign.
quiet installation Also known as unattended installation. An installation run by using the /q command-line option that runs without generating any user prompts.
right File- and folder-level permissions that allow access to a Web site.
roaming user User who uses more than one computer on a regular basis. Works at multiple sites using multiple computers.
roaming user profiles Account information established for roaming users, usually within a given domain of a network. Automatically configures the computer when the user logs on.
role A named group of user rights. Users are assigned to roles when they are added to a Web site based on SharePoint Team Services.
rollback A method used by Windows Installer to recover from a failed install. Similar to the rollback definition used in SQL. Consists of storing files, folders, and registry settings marked for deletion in a hidden temporary folder. If a serious error is encountered during the installation of new software, the files, folders, and registry settings are returned to their previous settings (as if the attempted installation never occurred).
script In character sets, a set of characters from a particular writing system, such as Arabic, Cyrillic, Hebrew, or Latin.
scripting language A programming language designed specifically for Web site programming. Examples include JavaScript and VBScript.
Secure Multipurpose Internet Mail Extensions (S/MIME) Method of security that allows users to exchange encrypted and digitally signed messages with any S/MIME-compliant mail reader. Messages are encrypted or digitally signed by the sending client and decrypted by the recipient.
Secure Sockets Layer A proposed open standard that was developed by Netscape Communications for establishing a secure communications channel to prevent the interception of critical information, such as credit card numbers.
security labels An Outlook feature that allows you to add information to a message header about the sensitivity of the message content. The label can also restrict which recipients can open, forward, or send the message.
Setup settings file An INI file, such as Setup.ini, read by Setup.exe at the start of the installation process; contains properties that control the installation process.
signed receipts A message receipt that verifies that the recipients recognize the user's digital signature.
SMTP mail server An e-mail server that uses the Simple Mail Transfer Protocol. SMTP is available with Windows NT Server 4.0 and Windows 2000 Server.
SQL Server A network or Web server that uses the standardized query language protocol for requesting information from a database. More commonly, a computer with an installed configuration of Microsoft SQL Server with a configured database that is available from a network location.
system locale In Windows NT and Windows 2000, the setting that determines the code page and default input locale. See also input locale, user locale, code page.
transform (MST file) In Windows Installer, a relational database that contains information about components, features, and Setup properties. A transform is based on a particular package and contains the modifications to apply to that package during installation. You use the Custom Installation Wizard to create transforms for Visio.
traveling user Uses more than one computer on a regular basis, often a portable computer the user takes to different locations. Traveling users might have different language requirements or need access to different configurations of the same application (local or remote). See also roaming user.
UNC Universal Naming Convention. Refers to shared volumes, printers, or files. It takes the format of \\sharedfolder\shared folder.
Unicode Universal character set designed to accommodate all known scripts. Unlike most code pages, Unicode uses a unique two-byte encoding for every character, also known as double-byte character set (DBCS). Unicode is a registered trademark of Unicode, Inc.
URL Uniform Resource Locator. An address that specifies a protocol (such as HTTP or FTP) and a location of an object, document, World Wide Web page, or other destination on the Internet or an intranet. Example: https://www.microsoft.com/.
user locale Setting that determines formats and sort orders for date, time, currency, and so on. Also known as regional settings. See also input locale.
VBScript (Visual Basic Scripting Edition) A subset of the Visual Basic for Applications programming language optimized for Web-related programming. As with JavaScript, code for VBScript is embedded in HTML documents.
vCard The Internet standard for creating and sharing virtual business cards.
virtual server A virtual computer that resides on an HTTP server but appears to the user as a separate HTTP server. Several virtual servers can reside on one computer, each capable of running its own programs and each with individualized access to input and peripheral devices. Each virtual server has its own domain name and IP address and appears to the user as an individual Web site or FTP site.
Web query In Microsoft Visio, a query that retrieves data stored on your intranet or the Internet.
Web server A computer that hosts Web pages and responds to requests from browsers. Also known as an HTTP server, a Web server stores files whose URLs begin with https://.
Windows Installer shortcut A feature shortcut that supports Windows Installer install-on-demand functionality. On Windows NT 4.0, requires the Windows Desktop Update. See also assign, publish, and advertise.
.gif "Cc751057.spacer(en-us,TechNet.10).gif")