Vico Office Installation Guide

VICO OFFICER6.8 MR1 INSTALLATION GUIDE

6.8.83.774November 2020

Vico Office Installation Guide

General process for installing Vico Office:

1. Check the system requirements for installation.

2. Decide which configuration will work best for you.

3. Install the Vico components.

4. Set up the license server.

Vico Office Overview

The Vico Office system consists of components that can be installed in various configurations.

The three main components are:

l Vico Office Client (VOC)

l Vico Project Server (VPS)

l Vico License Manager (VLM)

Vico Office Installation Guide Page 2

Vico Office Client (VOC)

The Vico Office Client is the main program in Vico’s integrated solution for construction planning,controlling and constructability analysis and is needed for all users who will interact with projectdata.

The VOC provides a basic set of functions needed for creating, viewing and reporting of projects.Vico Office modules are task-specific programs that run in the VOC. A module is activated when alicense for it is available on the user’s system or via a license server.

Vico Project Server (VPS)

The Vico Project Server manages the access and storage of project data. The VPS creates new data-bases for each new project and maintains the master list of projects that is visible in the Vico Officeapplication. A VPS can be installed together with the VOC or separately on a remote server.

Note: To use Vico Office, a VPS must be installed somewhere (locally or on the network).

Vico License Manager (VLM)

Vico licenses can be installed locally (single user licenses) or remotely (floating licenses). Floatinglicenses must be installed on a host with a VLM. The VLM cannot be installed on a host where theVOC has been installed. For more information, see "Licensing Process" on page 27.

Single User Licenses (SUL)

Single user licenses are installed locally on a host where the VOC has been installed.


Floating Licenses (FL)

Floating licenses are installed on the host where the VLM has been installed. The VOC systems pulllicenses from the pool of installed licenses on the VLM.

Licenses installed on a license server can be managed using the License Server Administration utility,which is accessed as a webpage (Startmenu > Vico Software > Vico License Manager> ServerAdministration).

System Requirements

These are the current system requirements for Vico Office, along with our recommendations for theconfiguration.

Minimum RequirementsRecommended MinimumConfiguration

OperatingSystem

Microsoft Windows® 10 64-bit Microsoft Windows® 10 64-bit

CPU Intel® multi-core processorEqual to or greater than Intel® Core™i7 Quad-Core (or equivalent) processor3.0 GHz Clock Speed recommended


Memory 8GB Equal to or greater than 16GB

Disk

10GB of free space on driveC: on client computers

Disk space requirement onthe VPS depends on thenumber and size of theprojects

Equal to or greater than 10GB of freespace on drive C: on client computers(SSD)

Disk space requirement on the VPSdepends on the number and size of theprojects (SSD)

Display 1600x1080 or higherEqual to or greater than 1920x1080 orhigher

Video CardHigh-end OpenGL card withat least 1GB onboard videomemory (ATI or NVIDIA)

Equal to or greater than high-endOpenGL card with at least 4GB onboardvideo memory (ATI or NVIDIA)

Note: There is a noticeable difference in performance between the minimum requirements and therecommended minimum configuration.

Note: Windows 7 and Windows 8.1 are supported but not recommended.

Note: Vico Office installed on a Mac system (Windows installed or virtualized) is NOT supported)

General Requirements

The Vico Office Client (VOC) can interact with a remote Vico Project Server (VPS) over a local networkconnection (not a WAN). For optimal performance of the system, the network connection shouldhave the following characteristics.

Item Requirements

Low Latencyl The recommended maximum valuefor latency is 20ms.


Item Requirements

High Bandwidth

l Project data must be transferredfrom the VPS to the VOCcontinuously and in high volume.For good performance of the VicoOffice views, a high bandwidthconnection between the VPS andVOC is therefore required.

Note: A high bandwidth and lowlatency connection alone is insufficientfor providing good performance; thephysical proximity between the VOCand VPS is also important. WANconfigurations are therefore notsupported, even with a highbandwidth and low latency connection.

Firewall Exceptions

l The VOC communicates with theVPS and the Vico License Manager(VLM) over a TCP/IP connectionusing dedicated ports.

l Firewall exceptions are required inWindows firewall and, if applicable,in additionally installed softwareand/or hardware firewalls.

Vico Office Client (VOC) Requirements

These are the requirements for the correct installation of the VOC.

Item Requirements

Supported operatingsystems

l Windows 10 64-bit

l Windows 8.1 (supported but notrecommended)

l Windows 7 (supported but notrecommended)


Item Requirements

Hard disk usagel Full installation: Minimumof 10 GB offree disk space

Memoryl Minimum: 8 GB

l Recommended: 16 GB or more

Video cardl A high-end OpenGL card with at least1GB onboard video memory (ATI orNVIDIA)

Open port requirements

Ports 20, 21, 1026, and 1027 (inboundand outbound traffic to enable crashreports to be uploaded to the Vicoservers)

For more information, see "FirewallSettings" on page 14.

Note: Vico Office installed on a Mac system (Windows installed or virtualized) is NOT supported)

Vico Project Server (VPS) Requirements

These are the requirements for the VPS.

Item Requirements


l Windows 2019 Server


l Windows 2012 R2 Server

l Windows 10

l Windows 8.1 (supported but notrecommended)

l Windows 7 (supported but notrecommended)


Item Requirements

Hard disk usage

l Minimum for the VPS program: 100MB

l Minimumper project: 1 GB (butprojects can be much larger)

l Shared and master databases: 20 MB

l Certain actions on the VOC computer(s) may require additional free spacefor temporary files. Packing a projectmay require 1 to 20 GB of free diskspace, depending on the project size.

Memory

l For running a VPS for several projectson a dedicated server in a multi-userenvironment:

l Minimum: 16 GB


l For running on a local VPS (when VPSresides on the same computer asVico Office):

l Minimum: 8 GB


Firewall exceptions

(Inbound and outboundrules)

l C:\VERSANT\9\bin\versantd.exe

l C:\VERSANT\9\bin\vserver.exe

l C:\Program Files\Vico Software\VicoProject Server Admin\VPSDaemon.exe

l 5089 TCP/IP port

For more information, see "FirewallSettings" on page 14.

Note:l For good performance, a high bandwidth and low latency connection between the VOC and VPSis required.

l If the VOCs are having trouble connecting to the VPS, youmay need to change the firewall set-tings.


l The VPS cannot be installed on a compressed drive.

In the drive properties (right-click the drive > Properties > General tab), ensure that the Com-press this drive to save disk space check box is not selected.

Vico Schedule Planner Standard (SPS) Requirements

These are the requirements for the SPS, along with configuration recommendations.

MinimumRequirements

Recommended Minimum Configuration

OperatingSystem

MicrosoftWindows® 10 64-bit

Microsoft Windows® 10 64-bit

CPUIntel® CPU: IntelPentium 4 3GHzprocessor

Equal to or greater than Intel® Core™ i7 Quad-Core (or equivalent) processor 3.0 GHz ClockSpeed recommended

Memory 4GB Equal to or greater than 16GB

Disk5GB of free spaceon drive C: on clientcomputers

Equal to or greater than 5GB of free space ondrive C: on client computers

Display 1600x1080 or higher Equal to or greater than 1920x1080 or higher

Video Card No special requirements

Note: There may be a noticeable difference in performance between the minimum requirementsand the recommended minimum configuration.

Note: Windows 7 and Windows 8.1 are supported but not recommended.

Note: Vico Schedule Planner Standard is not supported on a Mac system (either Windows installedor virtualized).

Vico License Manager (VLM) Requirements

These are the requirements for VLM.


Item Requirements




l Windows Server 2012 R2

l Windows 10

l Windows 8.1 (supported but not recommended)

l Windows 7 (supported but not recommended)

Disk space l 2MB

Memory l 3MB


Item Requirements

Open port requirements -Floating licensecommunication

Two ports are required:

l Port 2764 - For establishing a connection to the VLM licenseserver.

l A randomport - For further communication with the VLM licenseserver.

This port can also be specified in the license file (.lic) on thelicense server.

To specify the port in a license file (.lic)

1. Open the .lic file (C:\ProgramData\Vico Software\VicoLM) in atext editor such as Notepad.

2. In the second line of the file, add vico.opt XXXX, whereXXXX is the desired port number.

Note: All license files (.lic) at C:\ProgramData\VicoSoftware\VicoLMmust be edited in the same way.

After editing the file, the license server must be restarted.

3. On the VLM host, start the Server Administration page (Startmenu > Vico Software > Vico License Manager> ServerAdministration).

4. On the Server Administration page, click Shutdown.

5. On the Server Administration page, click Reread/RestartServers.


Item Requirements

Open port requirements -License server webpageadmin

l Port 9000

If needed, you can change this port to a custom port number inthe XYNTService.ini file.

To change the port to a custom port number

1. In Notepad, open the XYNTService.ini file.

2. Edit the port number.

The server webpage admin should now refer to the sameport number.

Note:l Licenses are stored in this location: C:\ProgramData\Vico Software\VicoLM

l Single user licenses and floating licenses cannot be installed on the same system.


Supported Publishers and Importers

Vico Office is an award-winning suite of products designed specifically for general contractors andowners. Vico Office is the first integrated construction management solution with a unique BIM-neutral environment. This means that users can publish, combine, coordinate, and augment Revit,Tekla, Archicad, and even SketchUp and IFC files with 4D scheduling and 5D estimating data.

The current publishers include:

l Autodesk Revit 2019, 2020, and 2021 (Architecture, MEP and Structure)

l Tekla Structures 2018i, 2019, 2019i and 2020

l Archicad 22, 23, and 24

l Bentley is not supported in Vico R6.1 and later. (To continue to use this publisher, youmust useVico R6 or earlier)

The current importers include:

l Sketchup: versions up to 2020

l IFC2x3 and IFC4

l Trimble Connect for SketchUp 2013 + IFC2x3

For example, you can synthesize the architectural model from Revit, the structural steel model fromTekla, and the MEPmodel fromCAD-Duct (via IFC). You can coordinate the models, fix any problemsbefore construction starts with streamlined constructability issue handling, and then perform a com-prehensive quantity takeoff. The coordinated construction-caliber quantities results in a more pre-cise schedule and estimate. And if at any time the design changes, the model is updated, and thequantities automatically reflect the changes so the schedule and estimate are also up-to-date.

You can investigate various scenarios of the 5Dmodel. For example, what happens if the facade ischanged to glass? What happens to the schedule if a parking garage is added? What happens if adifferent material is used? The model shows in real-time what happens to the schedule and thebudget.


System Configuration

Firewall Settings

The Vico Office Client (VOC) communicates with the Vico Project Server (VPS) via the TCP/IP protocol.This communication takes place through dedicated ports, which should be open on both the VOCsystem and the VPS system.

The Vico Office installer attempts to make required changes in the Windows firewall. Any addi-tionally installed firewall software should be configured manually.

The Vico License Manager (VLM) and the Vico Crash Reporter also require specific ports to be open.In addition to the systems on which the software is running, the VLM and Crash Reporter mayrequire ports to be open on installed firewalls on routers and modems. This allows them to com-municate respectively with the Vico Software license administration system and the Vico CrashReport server.

The table below provides an overview of all open port requirements and program exceptions.

Note:l For the 5019, 5088, and 6000-6200 ports/port range, we recommend setting the exception forthe related .exe process.

l The path (for example, C:\VERSANT\9\bin) changes as the Versant version (for example, 8)changes. This applies to all programs that use the VERSANT path.

Port Process Component Open on Router/Modem

5019 VersantD.exe(C:\VERSANT\9\bin)

Vico ProjectServer

No

5088 VPSDaemon.exe(C:\ProgramFiles\VicoSoftware\VicoProject ServerAdmin)

Vico ProjectServer

No


Port Process Component Open on Router/Modem

5089

(Creating and deleting projects,packing/unpacking)

VPSABackupService(C:\ProgramFiles\VicoSoftware\VicoProject ServerAdmin)

Vico ProjectServer

No

6000-6200 vserver.exe(C:\VERSANT\9\bin)

This can be definedusing anenvironmentvariable calledVERSANT_SERVER_PORTS.

Each project uses adedicated port;therefore, a rangeis used.

Vico ProjectServer

No

20, 21, 1026, 1027 chilkat.exe Vico Office

(CrashReportUploader)

Yes

2764 and additional randomport

(or specified explicitly asdescribed in 9)

Vico LicenseManager

No

(Yes in case of WAN access tolicense server)

9000 Vico LicenseManager

No


User Account Control (UAC) Settings

Windows UAC can block the VPS to VOC communication in the specific case where:

l UAC is active.

—And—

l The user account does not have administrator rights.

If it is not possible to deactivate UAC or to provide the user with an administrator account, you canstart Vico Office in elevated mode.

To start Vico Office in elevated mode

1. Right-click the Vico Office program shortcut, and then click Properties.

2. On the Compatibility tab, select the Run this program as an administrator check box, and


then clickOK.

Configuration Options

The Vico Office Client (VOC), Vico Project Server (VPS), and Vico License Manager (VLM) can beinstalled in various configurations.


VOC and VPS Configuration Options


VLM Configuration Options

Standalone Configuration

A standalone configuration is recommended for demonstration and offline work only. Although thisconfiguration can provide maximumperformance, collaboration is a manual process.

In this configuration, Vico Office and Vico Project Server (VPS) are installed on the same system,which means that the same computer is both server and client. Project databases, the master data-base, and the shared database are available without connecting to a server.


Both Vico Office and VPS are installed on the same machine.

Note: The communication between Vico Office and VPS takes place via TCP/IP. Server and clientboth have the same TCP/IP address – this is considered a threat bymost antivirus and firewall soft-ware. If it is not possible to make adjustments to firewall and/or antivirus software, we do not recom-mend a standalone configuration.

LAN Configuration (Recommended)

A LAN configuration is recommended for most use cases. In this configuration, a dedicated systemis set up as the Vico Project Server (VPS), and work stations with the Vico Office Client (VOC) installedconnect to the VPS over a local area network. Multiple users can access the same project at thesame time, which enables work-as-one: parallel work on a project as a team.

Two options are possible for licensing:


1. Locally installed single user licenses

2. A license server and floating licenses


Users pull licenses for the various modules from a pool of licenses installed on the server.

Note: Because of hardware limitations of the server (related to memory usage), a large number ofusers might require additional VPSs to be set up.

Licensing Configuration - Vico Licensing over WAN

A WAN configuration, which only applies to the VLM, provides on-site project teams access to a VLMlicense server that is set up in the office. The license server must be accessible from outside theoffice, and this can be achieved by placing the license server computer inside a DMZ. Floatinglicenses are typically required.


Setting up a license server in the DMZ can provide access to floating licenses from outside the office.

In this configuration, the VPS is local for each user.

Note: Other than for licensing, WAN solutions for Vico Office require virtual desktop/applicationsolutions. Our customers have successfully used Citrix, and supplemental documentation is avail-able. For more information, contact the Vico Office Support team.


Installing Vico Office

Networking

Important: When you use Vico Office in a configuration with separate server and client, make surethat both server and client(s) systems are updated to the latest version of Vico Office.

Administrative rights

Installation of Vico Office requires administrator rights and elevated access rights in cases whereUser Account Controls (UAC) are enabled; UACs may need to be modified, or turned off, via the Con-trol Panel.

When installing Vico Office while connected to a network domain, the user account control settingsmay be different from an offline profile, which can result in changed hardware identification char-acteristics. The changed hardware characteristics may result in a “no valid license found” message.Reinstalling your license will solve this issue.

The versant database

Versant is the backend database used to store and interact with information inside of the Vico Pro-ject Server (VPS). Most local installations of Vico Office will see a folder for the C:\Versant directorystored onto their machine for project storage. The project server can also be installed across a LANfor communal project access. See the installation guide for more details.

BIM connections

In some cases, the installer is unable to detect the folder in which Archicad, Revit and Tekla wasinstalled on your computer. If this happens, the Vico installer allows for selecting the folder manu-ally. All required files will be copied to the specified folder.

To install Vico Office components

The Vico Office installer guides you through the steps for installing Vico Office components.

1. Open the Vico Office setup file.

The Vico Office installer appears.

2. Select the language, and then clickNext.


l The installer checks to ensure that your machine has the required system components. Ifany are missing, it will list them so that when you clickNext, they are downloaded andinstalled. Note that you need Internet access to download these prerequisites.If your machine does not have Internet access, you can use another machine with Internetaccess to download the prerequisites from the Downloads page of SupportLink. Unzipthe downloaded file and place the prerequisites next to the Vico Office setup file. Theinstaller will automatically pick up these prerequisites and install them during the VicoOffice installation.

Prerequisites next to setup file

l If the required system components are up-to-date, the disk space requirements are dis-played.

3. ClickNext.

The license agreement appears.

4. Read the license agreement, select the I accept the terms of the License Agreement checkbox, and then clickNext.

Note: TheNext button is enabled only after you have scrolled to the bottom of the agree-ment.

5. Select the desired installation option(s).

6. ClickNext.

Note that Vico License Manager cannot be installed at the same time as Vico Office.

7. Select which features will be installed.

When you click a feature, its description appears below the item.

8. ClickNext.


http://support.vicosoftware.com/

9. Read the Trimble Solution Improvement invitation. You are encouraged to participate in theprogram.

When you select 'Yes', a crash report is automatically sent to Trimble. Only necessary inform-ation required by developers to help them understand why a crash occurred is included inthe report.

When you select 'No', a crash report is NOT automatically sent to Trimble. However, you canstill send this report manually. A prompt will be available on the UI after the crash hasoccurred.

Important: If you are installing Vico Office in a Citrix environment, the option to send crashreports is not available. To enable this feature, see "Sending Crash Reports in a Citrix Envir-onment" on page 32.

Important: Administrators: If you previously added the registry setting CrashReportSettings:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Vico Software\Report settings

Please remove it or set it to <empty>. Otherwise, this setting might prevent crash reportsfrom being sent to Trimble.

10. ClickNext.

The screen displays a confirmation that all the required information has been provided.

11. ClickNext to install selected options and features.

This may take several minutes. When the process is completed, you must restart your com-puter. To view the ReadMe, you must have a PDF reader.

12. ClickRestart Now or Restart Later.

Upgrading

The Golden Rule of Upgrades - Back up all existing projects

It is fundamentally important that all existing projects get backed up before upgrading to a newinstallation of Vico Office. Deployment environments can vary greatly and the safest way to mitigateany data loss occurring during an upgrade is to back up all of your projects before any new install-ation of Vico Office.

Reverting to Earlier Versions of Vico Office

If you need to revert back to a previous Vico Office release on your machine, some files have to beremoved manually, as the Vico Office database files are not backward compatible. See Reverting(Rolling Back) to a Previous Vico Office Version section in this document for further information.


Vico WinEst Integration

If you are using GC Estimator (Vico and WinEst), you will need to download the latest plugin fromVico SupportLink. Select the Vico WinEst plugin for your version of Vico Office and WinEst.

Disk cleanup precautions

When running standard Windows Disk Cleanup, or other similar applications to free up disk space, itis almost certain that all .log files will be deleted from your system. While most Windows .log files areexpendable, the Versant database logs are not. Permanently deleting them from your systemwilldestroy your Vico Office projects. You must ensure that Versant .log files are excluded from the DiskCleanup.

Anti-virus software

Some Anti-Virus software blocks or slows down the communication between Vico Office and theVico Project Server. Exceptions should be added to the Anti-Virus software settings to prevent this.See Firewall Exceptions for a list of executables and TCP/IP ports.

Licensing Process

The licensing process for Vico software consists of the following steps:

1. Receive a license installation utility file (.liu).

This can be a new license or an existing license that is reassigned using the Customer Portal.

2. Copy the .liu file to the target computer.

For single user licenses, this is the VOC computer. For floating licenses, this is the VLM com-puter.

The VOC or VLM installation must be completed before continuing with license installation.

3. Initiate the license generation process by double-clicking the .liu file.

The License Installation Utility (part of Vico Office) connects with the Vico License DistributionService and generates a hardware-specific license file.

The resulting license file (.lic) is stored in the following location: C:\ProgramData\Vico Soft-ware\VicoLM

Vico License Distribution Service Connection Failure

If a Vico License Distribution Server connection fails, the License Installation Utility displays a mes-sage and automatically generates a license request file for 'offline' license installation.


http://support.vicosoftware.com/

To receive a license file

1. In the Vico Software License Request Problemmessage, clickOK to save the license requestfile.

2. Attach the license request file to an empty email, and send it to [email protected].

Important: The request file should be the only attachment to an otherwise empty email. Ifthe email is edited or additional attachments are added, the automatic process will fail.

After the request file is received, an email with the license file is automatically sent by the VicoLicense Distribution Service.

3. Save the license file on the target computer.

4. To finish the installation, double-click the file.


mailto:[email protected]

Hardware ID (HWID)

Vico licenses are hardware-dependent, which means that a unique HWID is generated and copiedto the license file during installation. This ID is compared to the one that is generated when a Vicoproduct is started. If theymatch, the license can be checked out.

Note: Changes to the hardware or operating systemmay result in a new HWID, which invalidatesexisting licenses. HWID generation is affected by the following:

l Hardware changes on the host computer

l OS upgrades on the host

l UAC settings

l For virtual machines:

l OS upgrades on the virtual machine

l Virtualization software upgrades (potentially)

l Migration to a new host

Setting Up the License Server

To set up a license server

1. Decide which computer will act as the license server.

2. Open the Vico Office setup file, and selectVico License Manager (VLM) to install the VLM onthat machine (server).


3. To install the floating licenses on the server computer, open the .liu license installation files andwait for 15 to 20 seconds.

Example license names are:

l VO R5 Takeoff Manager

l VO R5 Cost Planner

l VO R5 Cost Explorer

Note: The .liu files should be associated with the Vico License Installation Utility (LIU). If thefile association is missing, download and install the License Installation Utility separately.

4. To start the Server Administration page on the license server, click the Startmenu > Vico Soft-ware > Vico License Manager > Server Administration.

5. On the left, clickReread/Restart Servers, and then clickReread/Restart.

The license server should be up and running.

Connecting to the VLM

To install the VOC and connect to the VLM

1. Install the VOC on each user's computer.

We recommend that you restart your system after the installation.

2. To install the VOC license on the client computer(s), execute the license installation file (.liu fileattached to license notification), and wait for 15 to 20 seconds.


ftp://sftp.vicosoftware.com/public/Downloads/License_Utilities/liu_setup.zip

3. On the Dashboard in Vico Office, set the connection to the VLM in the VLM Server field, andrestart Vico Office.

When you start Vico Office, it will check out the Vico Office Client license locally and should be ableto check out the module licenses from the server.

To install Schedule Planner Standard and connect to the VLM

1. Install Schedule Planner Standard on each user's computer.

2. On each user's computer, download and install the Vico Office Utility, which is available on theDownloads page of SupportLink.

3. On the License server access step, enter the name or IP address of the server computer duringinstallation. The VLM connection information is stored in an Environment Variable that you canalso create manually.

Reverting (Rolling Back) to a Previous Vico Office Version

If you need to revert back to a previous Vico Office release on your machine, some files have to beremoved manually, as the Vico Office database files are not backward compatible. Please followthese steps to avoid any database conflict.


http://support.vicosoftware.com/FlareFiles/SupportLink.htm#SupportLink/Downloads.htm%3FTocPath%3D_____2

To revert to a previous Vico Office version

1. Back up your database.

2. Uninstall Vico Office and all related components (Vico Project Server, Schedule Planner Stand-ard).

3. Delete the Vico Office installation folder:C:\Program Files\Vico Software

4. Delete the Versant installation folder:C:\VERSANT

Important: This step will permanently remove all Vico Office projects from your machine.Please proceed only If you have backups for the projects you would like to keep.

5. Delete the following database profile files:

l C:\osc

Note: This folder is hidden by default. To display hidden folders, select this option 'Show hid-den files, folders, or drives' (File Explorer > Organize > Folder Options > View).

l C:\Users\<CURRENT_USER>\osc

Note: Your user profile folder might be set to a different (network) drive. If you type%HOMEDRIVE%%HOMEPATH% in File Explorer, it will point you to the user profile folder.

Sending Crash Reports in a Citrix Environment

During the Vico Office installation, you are invited to participate in the Trimble Solution improve-ment program. This program is available only to the system administrator who installed Vico Office.Due to the nature of a Citrix environment, this program is not automatically available to the rest ofthe Citrix users.

There are two ways to participate in the program: one will require Citrix users participation and theother will require the Citrix Administrator to modify the registry settings.

Important: Administrators: If you previously added the registry setting CrashReportSettings:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Vico Software\Report settings

Please remove it or set it to <empty>. Otherwise, this setting might prevent crash reports frombeing sent to Trimble.

Citrix Users1. When a crash occurs while using Vico Office, a warning icon will appear on the top-right corner

of the window.


2. Click on the warning icon. A 'Send Error Info' dialog appears.

3. Click on the 'Send and don't askme before sending in future.'

Citrix Administrators1. Start Registry Editor and locate the following:

Computer\HKEY_CURRENT_USER\Software\Vico Software\Vico Office

2. Change the CrashReportSend Data value to 'AutoSend'.


Date post:	23-Oct-2021
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Vico Office Installation Guide

Documents