Installation

Overview of Installation
VingCard VISION is installed in networked environments. It can be installed in

A standard Windows PC network.

OR

An Application Service Provider (ASP) environment using a central remote server

and thin client workstations at the Hotel. Examples of this type of set up are
CITRIX or Windows Terminal Services.

Installation on Standard PC Network

Overview
VingCard VISION can be installed on a single PC or on a system with several PCs
connected together in a network. VISION can either use a dedicated network, or work
over an existing network at the installation property.
In a networked system, the PC that runs the database(s) is referred to as the VingCard
server. All other PCs are referred to as workstations. Each PC has access to its own
locally connected devices and also to all of the networked encoders and printers.
Each PC in the network must have a unique identification. Those identifications are the
computer names as seen from the network. The computer names used by VingCard
VISION are STATION_000, STATION_001, and so on up to STATION_099. The PC
set up as the server is by default STATION_000, although the VISION installation
program allows any computer to be set up as the server.

Locklink

Data

STATION_000

STATION_001

STATION_002
Encoder

Encoder

Ethernet

Printer

Figure 1.
It is recommended that installation of VingCard VISION is carried out in the following
order :

Install and configure the network, first on the server then on each workstation.

Install VingCard VISION on the server (installation program VxxInstall.exe)

If you are making a Multiple Database Installation, run the separate, Multi
database installation program on the server (installation program
VxxMultiDbInstall.exe).
Note : for full details plus an example of setting up a Multiple Database
Installation, see Chapter 12 of the VISION Manual.

Install VingCard VISION on each workstation (installation program

VxxInstall.exe)

Set and Check network access rights and user permissions

Install Microsoft ActiveSync on any PCs that will communicate with LockLink

Enable automatic network logon if required (Windows NT / 2000 / XP only)

Installing the Network

STEP 1: Selection of network PCs and Operating Systems.
VingCard VISION can run under the following operating systems (OS): Windows 98
(not recommended), Windows NT 4.0 or later, Windows 2000, Windows XP, Windows
VISTA.

The VingCard Server in networked systems should use one of the more stable operating
systems (2000 or XP).
STEP 2. Cabling
Connect all workstations with the type of cabling required by your network cards.

STEP 3: Install cards.

If you are using VingCard VISION Workstations (see picture) go to Step 3.

If you have only one PC in your system, go to Step 3.

Otherwise, carry out this step, first on the server, then on each workstation.
If the PC does not have a network card installed, obtain a network card compatible with
Microsoft Network peer-to-peer connections and install it according to the vendor's
instructions. Normally this involves opening the computer enclosure and installing the
card in a free slot, or insertion of a PCMCIA network card in a PCMCIA slot. Restart
the PC and let Windows configure itself automatically (Plug And Play). If Windows is
not able to do this automatically, check the documentation for your network card. You
will probably have to use the Add New Hardware wizard from within Control Panel.
Important note : If you are using network hubs to link one or more PCs in the VISION
network, check that the Duplex settings for your network cards are compatible with
those for your hubs. Mismatches here can cause very slow performance. The Duplex
settings (if present for your adaptor) can be found under:
Start /Settings/Control Panel/Network/Adaptors/Configure/Advanced.
STEP 4: Configure network protocols.
Carry out this step first on the server, then on each workstation.
Each PC running VISION needs

TCP/IP protocol installed

File and Printer Sharing for Microsoft Networks enabled

A unique computer name set. You can either use STATION_000 etc, another
naming convention or simply the existing computer names set up on an existing
network.

A unique IP address. You can either allocate these yourself or allow the network
to set them (via DHCP). In either case, all IP addresses must be on the same
subnet IP addresses can be found by typing IPCONFIG at the command
prompt.

If one or more IPX/SPX protocols are installed, then remove them if you are sure they
are not needed. They are not needed in a VISION only system. You must NOT remove
them if you will be installing VingCard VISION on a system already using Netware
Windows must be restarted before any changes you make to network / TCP/IP settings
take effect. Select Yes if Windows asks if you want to restart your computer.

Installing VingCard VISION

You will need your installation CD and License codes (delivered with VISION).
STEP 1 Run the Version xx installation program, VxxInstall.exe
Carry out this step, first on the server, then on each workstation. For PCs already set
up with different levels of Windows user, make sure you log on with Administrator
rights before running the install program.
Follow the instructions presented by the installation program and select appropriate
options.
NOTE 1: Upgrading old VISION installations

Pre Version 3.1installations

When installing on a server with an existing Version 2, Version 3.0 or Version
3.01 VISION installation, you must first convert to Version 3.1. First make a
backup of the existing (v2, 3.0 or 3.01) database, then run the VISION 3.1
installation program V31Install.exe, selecting Keep Database when prompted.
You do not need to install any V3.1 Service Releases.
Once your database is at Version 3.1, the Version 5.0 installation program can
automatically convert it.

Version 3.1 through to Version 5.x installations

When your VISION installation is one of the above, you can upgrade directly.
Select Keep Database when prompted and the database will be upgraded in
line with latest VISION requirements. It is strongly recommended that a backup
of the old database is taken before installation.
Special Note when Upgrading from Version 3.1
After selecting Keep Database you will be prompted to select a default Lock

Type (for example 9V Classic or 9V Presidio Combo). If your property uses

more than one of the lock types listed, you should select the most common lock
type as a default and then, after installation is complete, use VISION > Setup >
Locks > Lock Groups > Change Existing in order to allocate the other lock
types to the relevant doors.
You will then be asked to select a default Card Family, either mag-stripe,
memory card or smartcard. You should select the type of keycard that your
property will predominantly use. If your property will use more than one of the
card family types listed, you should select the most common type as a default
(normally but not always mag-stripe) and then, after installation is complete, use
VISION > Setup > User Groups > Change Existing in order to allocate the
other card families to the relevant user groups.
smartcard : a card which uses a memory chip to store information and
additionally has built in processing power.
memory card : a card which uses a memory chip to store information but has
no built in processing power.
Note that VingCard dual reader (Combo) locks can read mag-stripes, memory
cards and smart cards. User groups that need access to these locks should be
assigned either the mag-stripe or the smartcard card families.
There are a small number of VISION locks (Marketed as VC3000 Smart Card)
that can only read memory cards not smartcards. The only time a user group
should ever be allocated the memory card card family is when the property is
equipped with these locks and mag-stripe access is not desired.

Changing a previous server to a workstation

When installing on a workstation that was previously a server, any old version
databases found are deleted.

DaVinci installations
DaVinci databases are NOT automatically converted by VISION installation.

NOTE 2: When prompted for the installation type

For the server, select the appropriate type:

Peer Server: the server will contain the database and the VingCard VISION
program.

Database server: the server will contain the database only. In this case, VISION
cannot be run on the server, only remotely via workstations.

Workstation: the VISION program will be installed, configured to access the

database on the VISION Server.

NOTE 3: When installing on a Workstation

In order that VISION can access the data base on the VISION Server you will be
prompted to enter the name of the VISION Server PC. If upgrading the entry will
default to the VISION Server name previously used. For new installations, you must
know and type the Computer Name of the VISION Server PC. The method of viewing
or changing a Computer Name is operating system dependant. Refer to Windows help
from the start menu and look up Computer Name.

NOTE 4: Installing a Construction database

The initial installation (construction) at a Hotel can be done with a pre-programmed
construction facility code and can be based on simple pre-made database, sufficient
for use at the construction stage.
The construction database can be selected (as an alternative to Demo or Empty)
from the VISION installation program. When VISION is operating with a Construction
database, indication is given on the Log In Screen. You will not need to enter any
License codes. These will be delivered at a later date at which point VISION must be
re-installed using them.
***** New feature in Version 5.0 *****
When operating with a Construction Database, VISION gives you the opportunity to
make Construction Keys. Go to Special Cards module after installing VISION. There
are two options available : make master keys (where the same cards work in all locks)
or make individual keys for each lock.
The Construction Keys you make will work in newly delivered 4.5V locks. To use
them, power up the newly fitted lock and insert one of the Construction Keys a
master or individual key depending on whether you want the lock to have its own key
or not. The lock will learn the special Construction Key code on the card and flash
green. After this, this key will work in the lock UNTIL THE LOCK IS
PROGRAMMED WITH REAL DATA USING LOCKLINK
When VingCard provides the final facility code you need to reinstall VISION and
LockLink using this facility code. Then you can set up the final database and
OVERWRITE the locks with the new data (including facility code), without the
necessity to disconnect a battery for resetting the lock.
To utilize the Construction OVERWRITE functionality you must check the
construction lock check box on the system tab of LockLink.
When the check box is checked, locks with the Construction Facility Code will be
updated with the new Facility Code (the one newly uploaded from VISION to locklink).

NOTE 5: When prompted to select between standard and batch mode

Batch mode is a specialist mode of operation where VISION creates output files that are
read by third party software in order to make keycards on batch encoder / printers.

Some cruise line companies use batch mode. Only select batch mode installation if you
are installing at one of these installations, otherwise, select standard (the default).
Further details of batch mode are available in Chapter 8 of the VISION Manual.
NOTE 6: Multiple Database Installations
For full details plus an example of setting up a Multiple Database Installation, see
Chapter 12 of the VISION Manual.
STEP 2. Make VISION folder available by Sharing
Carry out this step on the Server only.
Note: For Windows 2000, NT or XP servers, the installation program will carry out this
step for you, granting Full Control access to All Users. If you want to restrict the group
of users with access to the VISION folder you can adjust these settings after
installation.
Double click My Computer on the desktop. Right-click on the icon for the folder
where VISION is installed. Click Sharing. Click Shared as: and fill in Share name:
for your shared folder. The name must be VISION. (The Comment: field is optional.)
Set Sharing permission to Full control for all users that will run the VISION program.
If you encounter problems while setting up Sharing, see Sharing folders in Windows
Help. The window should now look similar to this (example is from Widows NT):

Click OK. Note that the icon for the VISION folder has changed.

STEP 3. Make local printers available over the network

Carry out this step on all stations that are directly connected (serial or parallel cable)
to a printer that you want to be shared by other VISION stations.
Install the printer to the local PC. Go to the Windows printer folder (Start button >
Settings > Printers). Right-click the printer you want to share and then click Sharing.
Select Shared as: and fill in Share name: for your shared printer. The name can be
HewlettPackard 400, for example. (The Comment: field is optional.) Click OK and
the printer's icon will be changed.

Shared drive

Printer
folder

Shared
printer

STEP 4. Set up a default printer for each VISION station

Carry out this step on all stations that you wish to view, save or print VISION reports
from.
Go to the Windows printer folder (Start button > Settings > Printers). Consider the
printer that you want to be the default for the particular VISION station. If it is not
listed, use the Add Printer option to add it. Select the printer from the list of those
available and set it as default (Select from list, right click, Set as default).
STEP 5. Hiding the taskbar
This step is optional. If desired, carry out this step, first on the server, then on each
workstation.
The taskbar (normally at the bottom of the screen) can be hidden clicking Start
button/Settings/Taskbar. Then check the Auto Hide box and click OK.

STEP 6. Autostart of VingCard VISION.

This step is optional. If desired, carry out this step first on the server, then on each
workstation.
After successful installation of a peer server or server, the VISION database server will
start each time Windows is started.
If you want the VISION program to start automatically when Windows is started, you
need to prepare this manually. To do this click Start button/Settings/Taskbar and then

click the Start menu, Programs tab. Click the Add button. In the Command line: field
now type c:\VISION\VISION.exe (or use a different path if you installed to a folder
other than c:\VISION). Click the Next button and now double-click the StartUp folder.
In the field Select a name for the shortcut: type VingCard VISION and then click the
Finish button. Click OK.

Setting and Checking Access Rights and User permissions

Background
Access rights and user permission issues are becoming increasingly significant to the
operation of networked VISION installations as windows networks continue to migrate
towards NT/2000/XP solutions.
The most relevant issues are

Folder sharing and associated permissions

Can prevent access to server files if incorrectly set. Sharing and sharing
permissions are relevant to all Windows versions. For Windows NT and later,
sharing is correctly set during VISION installation. However, it might be
incorrectly changed later. For Windows 98, sharing must be set up manually as
described previously.

Registry Permissions
Can prevent VISION from retrieving and using important path information if
incorrectly set. Registry permission is only relevant to Windows NT and later
and is correctly set during VISION installation. However, it can be incorrectly
changed later.

Network User accounts and permissions

Can prevent access to server files if incorrectly set and also problems with time
synchronisation. For multi-user systems, suitable users for operating VISION
must be set up manually.

Indications of User permission problems

User permission problems can show themselves in the following ways in a VingCard
VISION system
Unable To Store Facility Code Message

When starting VISION, a message is displayed: Unable to store facility code. Check
that. VISION continues to partially operate, but certain functionality is unavailable.
For example, attempts to make a Guest key will provoke the message License limit
exceeded
This problem can be caused by problems with

Folder Sharing

Registry Permissions

Network User Accounts and Permissions

VISION Locklink module cannot access lock files

From a workstation, when you select the VISION Locklink module a message is
displayed File Not Found. When you press OK a more detailed error message
appears in red text in the Status panel.
This problem can be caused by problems with

Folder Sharing

Registry Permissions

Network User Accounts and Permissions

VISION does not complete a backup

The error message Error: did not complete the backup!!! is received when attempting
to make a backup or when running an autobackup. Either the backup path cannot be
determined from the registry (due to insufficient registry permission) or the specified
path can be determined but not written to by the currently logged on user.
This problem can be caused by problems with

Folder Sharing

Registry Permissions

Network User Accounts and Permissions

Workstation does not act on Time Synch message

A VISION station (usually the server) issues a time synch command as determined by
set up settings but one or more other stations do not synchronize their time.
This problem can be caused by problems with

Network User Accounts and Permissions

How To Set Up User Permissions For VISION

Folder Sharing

The main VISION folder on the VISION server must be shared.

For Windows NT, 2000 & XP, the share is automatically made during installation.
For Windows 98 sharing has to be set manually. The process for this is described at step
2 of the Installing VingCard VISION instructions.

You can check the share on the VISION server by using Windows explorer / My
Computer, selecting the main VISION folder, right clicking, selecting Sharing and
observing the share properties. They should be as outlined at Step 2 of the Installing
VingCard VISION instructions. If they are not, change them.
Registry Permissions

This is relevant to any PC on the VISION network running Windows NT, 2000 or XP.
VISION automatically sets the correct registry permissions during installation - but it is
important that you were logged on with an administrator password during installation.
You can check and change these settings at the VISION server and at each workstation
as follows:
The following steps assume that all VISION users belongs to the group "Everyone".

Logon to the PC with Administrator access rights.

Select Start > Run.

Type regedt32.exe + <enter> to run the 32 bit Registry Editor.

Select "HKEY_LOCAL_MACHINE"

In the registry key tree, open the "SOFTWARE" key.

Locate and highlight the "Vingcard" subkey.

Select the menu option Security|Permissions...

Check the option "Replace Permission on Existing Subkeys"

Verify that the group "Everyone" is listed in the member group listbox. If not,
press ADD and add it to the list.

Double-click the group "Everyone".

Check the "Full control" radio-button and press OK.

Press OK and select "Yes" to the question to confirm the changes.

Exit the Registry Editor.

Repeat the process for each affected NT, 2000, XP PC running VISION SW.

Network User Accounts and Permissions

This is relevant to any workstation on a VISION network where the server is either
Windows NT, 2000 or XP.
Access to the server

Log on to each workstation using a typical user account for staff that will use VISION.
Use Network neighborhood (or equivalent) to locate the server machine. Highlight and
double click. If you gain access to the machine, then network permission is not a
problem; if you are prompted for a user name and/or password, it may be. In order for
VISION to work you need to log on to the server from the workstation.
If this is the problem, the best way to solve it permanently is to create compatible user
accounts (same username and password) on the server and workstation PCs. In this
way, the username and password that you type to log on to the workstation is also used
to gain access to the server with no additional input required.
There are two basic ways to tackle this:

Set up one account on the server, an equivalent account (same user and
password) on each workstation and always log into each workstation with that
account when using VISION.

Set up multiple accounts on each workstation (in line with the propertys policy)
and mirror each on the VISION server.

Simple example: put the server and all workstations on a common workgroup (such as
VingCard). Create a user VISION on the server and assign a password. Now create
user accounts with the name VISION and the same password on all workstations. Log
on to workstations using the VISION accounts. You can also log onto the server with
the VISION account but it is not essential. The important thing is that the server
receives any valid username/password combination from the workstation.
For more complex networks, possibly involving domain servers etc. things may be more
complex. However, the basic theory is the same: try to find or set up a workstation
account that automatically provides access to the shared VISION folder on the server.
The final solution chosen must take account of other User / traceability issues relevant
to the property where the VISION network is installed.
Note that on Windows 98 PCs, you may want to activate multiple users (in order to
automatically supply a username and password to the VISION server). You can do this
via Control Panel > Passwords > User Profiles, check the All users can customize.
Tab. When you restart, use the new username and password to login. This will create
the new user.
Note also that with a Windows XP server, if you set up a user without a password
(which is allowed) and then try and log on and connect through Win 98/NT/2000
workstations using the same username but leaving the password blank, you will not be
connected. Therefore, it is necessary to define and use a non-blank password.
Local Rights necessary in order for Time Synch to work

For the VISION time synchronization function to work each workstation running
VISION must be logged in with sufficient user rights to allow the date / time to be
modified.
You can check this for each relevant user. If you cant change date / time via Control
Panel, then VISION will not be able to change it either. You must then increase User
Rights.

Under Windows 2000, Standard User will work, Restricted User will not.
Under Windows NT, Power User will work, User will not.
Avoid Windows password (Windows 98 only).

For Windows 98 the very first time you start up Windows you might be asked to enter a
password for Windows (as opposed to the network). VingCard VISION is protected by
its own password system, therefore a Windows password is unnecessary.
To disable the windows password you must replace the existing password with an
empty password. To do this click Start button/Settings/Control Panel/Password/Change
Window Password. In this dialog, enter your existing password and leave the fields for
New password and Confirm new password empty. Click OK.

Testing the VISION Network for Correct User Permissions

To test the VISION network for correct permissions.

Log on to the server using the username and password that will normally be
used. Start VISION.

Log on to each workstation using a typical lowest permission user at each.

Start VISION at each PC and check that the Unable to store facility code.
Message is not displayed.

Use setup to send a time synch message from the server to all workstations and
check that they all act on it.

Perform a backup from each workstation (or a representative selection) saving

the backup files on the server machine.

If there is still a problem

If you have checked folder sharing, registry permissions and user access rights but you
still suspect an access / permission problem you can also try the following :
Use server IP address instead of computer name

This can be tried on any operating system and for any version of VISION but only
where the server IP address is fixed (not dynamically allocated using DHCP).
At the workstation, Start > Run > Regedit.
Navigate to HKEY_LOCAL _MACHINE\Software\VingCard\VISION
Change VISIONNetPath value from \\servername\VISION format to
\\Ipaddress\VISION (for example \\172.16.30.100\VISION )

Installing Microsoft ActiveSync.

Any VISION PCs server or workstations that will be used to transfer data to and
from the LockLink need Microsoft ActiveSync to be installed.
Microsoft ActiveSync is delivered along with VingCard LockLink units.

Enabling automatic logon in Windows NT / 2000 / XP.

Automatic logon allows users to avoid the network login after a PC is started. In effect,
this may mean that they avoid having to remember a suitable Windows password that is
different to their VISION password.
Automatic Logon may be needed for users who do not share computers and wish to
quickly log onto a network. Automatic Logon may also be used for networks who have
one default logon for their users.

Setting Automatic Logon Manually

To configure Windows NT / 2000 / XP to automatically login will require the registry
to be edited and the following instructions to be carried out.

Run Regedit32.exe

Open the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon

Within the above key enter the values normally entered into the following
values:
DefaultDomainName
DefaultUserName
DefaultPassword

If DefaultPassword is not present to create a new value click Edit, choose Add
Value. In the Value Name field type DefaultPassword. Select REG_SZ for the
Data Type. In the String field type your password and save changes.

In addition if no DefaultPassword string is specified, Windows NT

automatically changes the value of the AutoAdminLogon key from 1 to 0, thus
disabling AutoAdminLogon feature.

From the Edit menu, choose Add Value. Enter AutoAdminLogon in the Value
Name field. Select REG_SZ for the Data Type, enter 1 in the string field and
save your changes.

Finally if DONTDISPLAYLASTUSERNAME value is set to 1,

Autoadminlogon does not function.

To bypass the automatic logon in the future press and hold the SHIFT key as the
computer is booting.

Setting Automatic Logon Automatically

It is also possible to set automatic logon using the Microsoft TweakUI program which
can be installed into Control Panel. TweakUI is freely available on the internet and
DOES work with all windows versions up to and including XP. Install TweakUI then
use Help for instructions.

Automatic Logon Security Issues

For Windows 98/NT using auto logon can be a security risk, as the DefaultPassword is
stored in plain text in the registry.
In Windows 2000, if you use the TweakUI program TweakUI Logon tab to set the
registry entries, the DefaultPassword value name is NOT created at the Winlogon key.
Instead, a <NO NAME> value name, using the REG_DWORD data type, is created at
HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\DefaultPassword. This
data value is encrypted and NOT viewable.
In Windows XP the password is also encrypted if you use TweakUI, although not at the
registry location mentioned for Win 2000.

Installation in an ASP environment

General
In an ASP environment (for example CITRIX or Windows Terminal Services), the
workstations known as Thin Clients - are physically located at the Hotel (for example
the front desk) but run applications on the remote ASP server(s). To the user at the
Hotel, the User Interface appears exactly as it would on a normal, local PC.
In all cases we recommend that Network encoders are used and mapped to the
workstations as appropriate.
For PMS, we recommend the use of the TCP/IP interface.

Configurations
VISION database at each location

This is VingCard's preferred configuration. A VingCard server (i.e. the computer

holding the VISION database) is physically located at each Hotel. Whilst this goes
against absolute ASP philosophy (i.e. virtually all processing power moved to the ASP
servers), it has the following advantages

A backup solution (for making keys) in the case of network (WAN) problems
between the Hotel and ASP provider.

A backup solution for making keys in case of internal Hotel network (LAN)
problems. (Only if a non networked encoder is connected to the VISION server).

Local, physical connection to the LockLink unit.

Other configurations are possible. Please contact VingCard Tech Service to discuss.
Remember, the following issues need to be considered.

Making keys in case of network failures (LAN and WAN)

Physical connection of LockLink unit for transfer of data.

The VISION program seen on the thin clients are actually individual instances of
VISION, all running on the ASP server(s). However, the ASP framework ensures that
each instance of the VISION program is assigned a unique identity. This allows each
workstation to be set up (mapped to the correct encoders etc) exactly as for a standard
network where each VISION PC has an individual name.
Each thin client only operates against it's own database. The database selection
dropdown list is never seen at the VISION login screen. It is multiple, single database
installations rather than a multiple database installation.
To install :

At Hotel, install VISION as PEER SERVER, select ASP = No

Set up the database. Set up network encoders in the Hotel. See manual Chapter
7. Check you can cut keys. Set up and run the PMS TCP/IP interface on this
machine.

Install Microsoft ActiveSync on this PCs as it will communicate with LockLink

At ASP server install VISION as CLIENT, select ASP = Yes.

Do not run the multi database install program.

Now you need to co-ordinate with the ASP provider to ensure that
o User accounts are created for VISION workstation users at the Hotel.
o The workstation users have the necessary rights and ability to run the
VISION workstation program you installed on the ASP server.
o Printer and folder mappings for each user (for example to print and save
VISION reports; to make backups) are set up correctly.

Once this is completed, run VISION from each thin client. Check that (VISION
access rights permitting) you can cut keys, print and save reports, change overall
VISION setup, make backups.

VISION multi database installation at ASP server

All databases run at the ASP server. Each thin client can operate against any of the
centralized databases. The database selection dropdown list can be seen at the VISION
login screen but can be filtered to map a specific database to a specific thin client.

To install (summary):

At Hotel, no installation necessary

At ASP server install VISION as PEER SERVER, select ASP = Yes.

At ASP, run multi database installation program

Support for Online Remote Controllers

Vision 5.9 supports online remote controllers.
Both mag card and RFID remote controllers are supported. Each online remote controller connects to
the ethernet network. New software (VC network service) on the Vision server detects and controls
these units.

Online radio
locks

Zigbee
network

Vision server
Vision
Vision
clients
clients

VC
Network
service

Technicians
terminal

Online remote
controllers

Remote Controller
& Relay Box with
Ethernet kit
4821906

Zigbee
server

Ethernet
Vision.db

Having online remote controllers allows more precise control of which card holders are permitted
access through the associated door. Specifically, keycards that still have a valid time window can be
denied access ("cancelled") without having to visit the door.
card type

action

behaviour in online remote controllers

emp cards

replace individual

the replaced card is cancelled

replace whole user

group

each replaced card is cancelled subject to a grace

time

change

the old (pre-change) card is cancelled

remove

the removed card is cancelled

void

the voided employee card is cancelled

unvoid

the voided employee card can work again

void list

guest / emp
rooms 1

check in

any previous guest cards for the room(s) where

the time window has not yet expired, are
cancelled

replace

the replaced card is cancelled

check out

the guest's card is cancelled subject to a grace

time

A grace time allows the affected card to retain access for a time period. For example to permit access
for 15 minutes after a check out, to allow a guest return to their room to pick up forgotten items, or to
use a car park common door. See also later notes in section 1.1, re Setup, System Parameters.
Online remote controllers can be configured to automatically deliver all lock events back to the Vision
database for use in improved event reports. Live, status information is also available.
In other respects, online remote controllers behave like offline common remote controllers. For
example, they will never permit entry to a card with an invalid time window; they can be set up to
unlock in line with a specified timetable, etc
If an online capable remote controller is offline or loses connection, it operates in order with standard
offline behaviour.

Changes to setup and use of Vision

In general, the changes in setup and use of a Vision system for an installation that
includes online remote controllers has been kept to a minimum. The user interface
follows previous versions with a small number of changes.

Guest & Employee Rooms modules

There are no direct changes to the user interface or use.

Using the PMS interfaces

There are no direct changes to the interface or use.

Employee Keycards module

The user interface has been modified to allow many employees to be removed at once. If you do
this, all the employees are automatically cancelled in online remote controllers.
The verify button has been relocated to the top of the screen.2

Special Cards module

There are no changes to the user interface or use.

Help
Has been updated to cover online remote controller related topics and setup.

the employee rooms actions new, replace, remove work as per the guest functions check in, replace, check out.

In preparation for an extension of online functionality, whereby employees can be temporaily blocked and
unblocked in online doors.

Technician's Terminal
In order to provide detailed technical and setup support for the 'VC Network', a user application called
'Technician's Terminal' is installed. This application is intended for use by VingCard technicians when
setting up or maintaining Vision installations. It can also be used during fault finding by skilled Hotel /
Cruise Ship technical staff under the direction of VingCard personnel.

The Technician's Terminal is not required or intended for use during day to day Vision operation. Any
new online-related functionality and settings that the Hotel / Cruise Ship staff need for day to day
operations are made available through the existing 'Vision' user interface.

You can launch Technician's Terminal from start menu > VingCard > VC Network.

When launched, you will see an icon in the system tray.

Right click on this icon to bring up a menu. You can log in with any Vision password (or username &
password combination) that has access to the Vision setup module.

Use of the Technician's Terminal is described in it's own user manual.

One of the most useful views with regard to Online Common Doors is to go to Vision
Status > Service tab. Here, you can see whether the VC Network Service is running, and
whether it has detected and connected to any Remote Controllers.

VC Network Service
Part of the new VingCard Network software installed is the VC Network Service. This runs
continuously on the Vision server, and manages detection, connection and messaging to the online
doors.

When the service is running, detection of ethernet online remote controllers is automatic. There is no
setup (IP address etc) required. Note that it might be necessary to open the firewall on the host
computer for the service (full name VCNetworkService.exe).
By default, this service is installed as an auto startup service. That is, the service starts when the host
computer is started or rebooted. The service is reliant on the ASA database server, which must also be
run as a service. If the VC Network service is started and the database server is not running, the
database service is automatically started. Similarly, if the database service is stopped, the VC Network
service also stops.

In the windows start menu > VingCard > VC Network, there are shortcuts to start and
stop the service. There are also shortcuts to switch the service between auto and manual
startup modes

Uninstalling VingCard VISION

To uninstall VingCard VISION:
Select Start > Settings > Control Panel > Add/Remove Programs.
Select VISION from the list of installed software, and click Change/Remove.
Follow the instructions in the Uninstall program to uninstall VingCard VISION