Vico Office Installation Guide - Vico...

Vico Office Installation Guide

R5.3

April 2016

Vico Office Installation Guide

Table of Contents

Vico Office Installation Guide 4

Installation Checklist 4

Vico Office Overview 4

Vico Office Client (VOC) 5

Vico Project Server (VPS) 5

Vico License Manager (VLM) 5

System Requirements 7

General Requirements 7

Vico Office Client (VOC) Requirements 8

Vico Project Server (VPS) Requirements 9

Vico License Manager (VLM) Requirements 10

Supported Publishers and Importers 13

SystemConfiguration 14

Firewall Settings 14

User Account Control (UAC) Settings 15

Configuration Options 16

VOC and VPS Configuration Options 17

VLM Configuration Options 18

Standalone Configuration 18

LAN Configuration (Recommended) 19

Licensing Configuration - Vico Licensing over WAN 21

Installation Options 23

Licensing Process 25

Vico License Distribution Service Connection Failure 26

Hardware ID (HWID) 27

Setting Up the License Server 27

Connecting to the VLM 28

Sending Crash Reports in a Citrix Environment 30

Troubleshooting 31

Copyright 2016 by Trimble Navigation, Ltd

Vico Office Installation GuideGeneral 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.

Installation Checklist

Use the installation checklist to ensure that you have installed Vico Office successfully and have set itup for optimal use. To view this document, Microsoft Excel must be installed on your machine.

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 Client (VOC)

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

The VOC provides a basic set of functions needed for creating, viewing and reporting of projects. VicoOffice modules are task-specific programs that run in the VOC. A module is activated when a licensefor 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 the VOChas been installed. For more information, see "Licensing Process" on page 25.

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 Requirements Recommended Minimum Configuration

OperatingSystem

Microsoft Windows® 7 32- or64-bit

Microsoft Windows® 7 64-bit

Microsoft Windows® 8

CPU Intel® CPU: Intel Pentium 43GHz processor

Equal to or greater than Intel® Core™ i7Quad-Core (or equivalent) processor 3.0GHz Clock Speed recommended

RAM 4GB Equal to or greater than 16GB

HDD 10GB of free space on drive C:on client computers

Disk space requirement on theVPS depends on the numberand size of the projects

Equal to or greater than 10GB of free spaceon drive C: on client computers

Disk space requirement on the VPS dependson the number and size of the projects

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

Video Card High-end OpenGL card with atleast 512MB onboard videomemory (ATI or NVIDIA)

Equal to or greater than high-end OpenGLcard with at least 1GB onboard videomemory (ATI or NVIDIA)

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

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 should havethe following characteristics.

Item Requirements

Low Latency l The recommended maximum value for latency is 20ms.


Item Requirements

High Bandwidth l Project data must be transferred from the VPS to the VOCcontinuously and in high volume. For good performanceof the Vico Office views, a high bandwidth connectionbetween the VPS and VOC is therefore required.

Note: A high bandwidth and low latency connection alone isinsufficient for providing good performance; the physicalproximity between the VOC and VPS is also important. WANconfigurations are therefore not supported, even with a highbandwidth and low latency connection.

Firewall Exceptions l The VOC communicates with the VPS and the Vico LicenseManager (VLM) over a TCP/IP connection using dedicatedports.

l Firewall exceptions are required in Windows firewall and, ifapplicable, in additionally installed software and/orhardware firewalls.

Vico Office Client (VOC) Requirements

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

Item Requirements

Supported operatingsystems

l Windows 7

l Windows 8/8.1

l Windows Server 2008 R2


Hard disk usage l Full installation: Minimumof 10 GB of free diskspace

Memory l Minimum: 4 GB

l Recommended: 16 GB or more

Video card l A high-end OpenGL card with at least 512MBonboard video memory (ATI or NVIDIA)

Open port requirements Ports 20, 21, 1026, and 1027 (inbound and outboundtraffic to enable crash reports to be uploaded to theVico servers)

For more information, see "Firewall Settings" on page14.

Vico Project Server (VPS) Requirements

These are the requirements for the VPS.

Item Requirements


l Windows 7

l Windows 8/8.1



Hard disk usage l Minimum for the VPS program: 100MB

l Minimumper project: 1 GB (but projects can bemuch larger)

l Shared and master databases: 20 MB

l Certain actions on the VOC computer(s) may requireadditional free space for temporary files. Packing aproject may require 1 to 20 GB of free disk space,depending on the project size.

Memory l Minimumper concurrently used project: 300 MB

l Master database: 40 MB

l Shared database: 40 MB

Firewall exceptions

(Inbound and outboundrules)

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

l C:\VERSANT\8\bin\obe.exe

l C:\Program Files\Vico Software\Vico Project ServerAdmin\VPSDaemon.exe

l 5089 TCP/IP port

For more information, see "Firewall Settings" on page 14.

Note:

l For good performance, a high bandwidth and low latency connection between the VOC andVPS is required.

l If the VOCs are having trouble connecting to the VPS, you may 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 License Manager (VLM) Requirements

These are the requirements for VLM.

Item Requirements


l Microsoft Windows® 7

l Microsoft Windows® 8



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 VLMlicense server.

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, where XXXX isthe 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 same portnumber.

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-neut-ral environment. This means that users can publish, combine, coordinate, and augment Revit, Tekla,ArchiCAD, CAD-Duct models, and even IFC files with 4D scheduling and 5D estimating data.

The current publishers include:

l Autodesk Revit 2015 and 2016 (Architecture, MEP and Structure)

l Tekla Structures 21.1 and 2016

l ArchiCAD 18 and 19

l AutoCAD 2015 and 2016 (Architecture and MEP)

l Bentley AECOsimDesigner 8.11.09.593 and 8.11.09.747

The current importers include:

l Sketchup: versions 6, 7, 8, 2013, 2014, 2015, and 2016

l CAD-Duct - the support is via an XML file

l IFC2x3 and IFC4

l Trimble Connect for SketchUp 2013 + IFC2x3

So for example, we can synthesize the architectural model from Revit, the structural steel model fromTekla, and the MEPmodel fromCAD-Duct. We can coordinate the models after running an element-based clash detection, fix any problems before construction starts with streamlined constructabilityissue handling, and then perform a comprehensive quantity takeoff. These coordinated construction-caliber quantities drive a much more precise schedule and estimate. And if at any time the designchanges, the model is updated, and the quantities automatically reflect the changes so the scheduleand estimate are also up-to-date.

Now you can start "asking questions of the 5Dmodel." What happens if we change the facade toglass? What happens to the schedule if we add a parking garage? What happens if we substitute thismaterial for that material? In real-time, the model provides the answers of what happens to the sched-ule and what happens to the budget.


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 VOC sys-tem and the VPS system.

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

The Vico License Manager (VLM) and the Vico Crash Reporter also require specific ports to be open. Inaddition to the systems on which the software is running, the VLM and Crash Reporter may requireports to be open on installed firewalls on routers and modems. This allows them to communicaterespectively with the Vico Software license administration system and the Vico Crash Report 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\8\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\8\bin)

Vico ProjectServer

No

5088 Pre 5.0:NotificationDaemon.exe(C:\VERSANT\8)

5.0 and later:VPSDaemon.exe(C:\Program Files\VicoSoftware\Vico ProjectServer Admin\Wow64\)

Vico ProjectServer

No

5089

(Creating and deleting projects,packing/unpacking)

VPSABackupService(C:\Program Files\VicoSoftware\Vico ProjectServer Admin)

Vico ProjectServer

No

Port Process Component Open on Router/Modem

6000-6200 Obe.exe(C:\VERSANT\8\bin)

This can be definedusing an environmentvariable calledVERSANT_SERVER_PORTS.

Each project uses adedicated port;therefore, a range isused.

Vico ProjectServer

No

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

(CrashReportUploader)

Yes

2764 and additional randomport

(or specified explicitly asdescribed in "Vico LicenseManager (VLM) Requirements" onpage 10)

VicoLicenseManager

No

(Yes in case of WANaccess to license server)

9000 VicoLicenseManager

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, andthen click OK.

Configuration Options

The Vico Office Client (VOC), Vico Project Server (VPS), and Vico License Manager (VLM) can be installedin 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, whichmeans that the same computer is both server and client. Project databases, the master database, andthe 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 system isset up as the Vico Project Server (VPS), and work stations with the Vico Office Client (VOC) installed con-nect to the VPS over a local area network. Multiple users can access the same project at the same 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 the office,and this can be achieved by placing the license server computer inside a DMZ. Floating licenses are typ-ically 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 available.For more information, contact the Vico Office Support team.

Installation Options

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

Tip: To determine where to install the Vico Office Client (VOC), Vico Project Server (VPS), and VicoLicense Manager (VLM), see "Configuration Options" on page 16.

Option Description

Vico Office (VO) Installs the VOC and the required components to communicatewith the VPS.

Note:

l The VOC and VPS can be installed on the same computerfor a standalone configuration. Otherwise, if the VOC isinstalled without the VPS, you can specify the VPS thatwill contain projects by entering a network IP address ora computer name in the Vico Office dashboard (after theinstallation is completed).

l The VOC cannot be installed on the same system as theVLM.

Vico Project Server (VPS) Installs the Vico Project Server.

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

Vico Office Web Services (VOWS) Installs aWindows Communication Foundation (WCF) servicethat lets clients access Vico Office data through a unifiedinterface.

Note: Only install the Vico OfficeWeb Services if you knowthat you want it.

Schedule Planner Standard Installs Schedule Planner in standalonemode, which is used forlocation-based flowline scheduling, without a connection to theVPS or BIMmodels required.


Option Description

Vico License Manager (VLM) Installs the VLM, which is required for floating licenses that can beused by other computers that are connected via LAN orWAN.

Note:

l The VPS can be installed on the same computer as theVLM.

l The VOC cannot be installed on a systemwith VLMinstalled because Vico Office requires a single userlicense for the VOC. Single user licenses cannot beinstalled on VLM.

Document Controller Standard Installs Document Controller in standalonemode, which is usedfor 2D documents, 3D models, and in a hybrid mode.

To install Vico Office components

1. Open the Vico Office setup file.

The Vico Office installer appears.

2. Select the language, and then click Next.

l If the required system components are not installed or updated, the screen displays thecomponents that will be installed or updated when you click Next.

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

3. Click Next.

The license agreement appears.

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

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

5. Select the desired installation option(s).

6. Click Next.

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. Click Next.

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 in thereport.

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

Attention Users in Citrix Environment: If you are installing Vico Office in a Citrix environment,the option to send crash reports is not available. To enable this feature, see "Sending CrashReports in a Citrix Environment" on page 30.

Attention 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.

10. Click Next.

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

11. Click Next to install selected options and features.

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

12. Click Restart Now or Restart Later.

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 Software\VicoLM

Vico License Distribution Service Connection Failure

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

To receive a license file

1. In the Vico Software License Request Problemmessage, click OK 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 copied tothe 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 virutal 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 select Vico 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, click Reread/Restart Servers, and then click Reread/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.

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

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.

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 able tocheck 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.

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


Sending Crash Reports in a Citrix Environment

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

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.

Attention 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 from beingsent to Trimble.

Citrix Users

1. When a crash occurs while using Vico Office, a warning icon will appear on the top-right cornerof the window.

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

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

Citrix Administrators

1. Start Registry Editor and locate the following:

Computer\HKEY_CURRENT_USER\Software\Vico Software\Vico Office

2. Change the CrashReportSendData value to 'AutoSend'.

Troubleshooting

Problem Cause/Notes Resolution Test for Problem

Vico Officecannot connectto local ornetwork VPS(Versantdatabase).

Antivirus or firewallblocks theconnection.

Note: Multiplefirewalls/antivirus canbe present on amachine

Versant database isnot installedproperly/’versantd’service is not running

Set exceptions for the following files:

n C:\VERSANT\8\bin\versantd.exe(TCP/IP port 5019)

n C:\VERSANT\8\bin\obe.exe (TCP/IPport range 6000-6200)

n C:\VERSANT\8\NotificationDaemon.exe(TCP/IP port 5088)

Reinstall VPS/start ‘versantd’ service

itest –v <SERVER_NAME>

(DOS commandline function)

Check the ControlPanel ->Administrativetools -> Services -> VersantD

Vico Officecrashes duringstartup

TCP/IP networking isnot set up properly(DNS nameresolution).TCP is broken orthere is no networkadapter in themachine

Set up TCP/IP networking (ask youradministrator)

ipconfig

(DOS commandline function)

Vico Officedrops E7031error duringstartup

User must havepermissions to writeVersant DB directory(usuallyc:\Versant\db)

Set proper rights on the Versant DBdirectory in Windows Explorer(C:\Versant\db)

Run the followingcommands inCommandPrompt:

makedb testdbcreatedb testdb

Vico Office Installation Guide - Vico...

Documents

Transcript of Vico Office Installation Guide - Vico...