2.90 C - CURE 9000 Release Note

C•CURE 9000 2.
90 Release Note
March 2023 Document Number: 8200-1950-26
Revision: F
www.swhouse.com
Contents
Installation Media Contents ........................................................................................................................... 4
New Features ................................................................................................................................................ 4
C•CURE 9000 web-based client ............................................................................................................... 4
C•CURE Legacy Web ............................................................................................................................... 4
C•CURE 9000 Dashboard/Home Screen ................................................................................................. 5
Basic Authentication Login Throttling ........................................................................................................ 5
C•CURE ID ................................................................................................................................................ 5
Video Search ............................................................................................................................................. 5
Video Clip Management ............................................................................................................................ 5
Journal Volume Management ................................................................................................................... 5
iSTAR Edge G2 Support ........................................................................................................................... 5
iSTAR driver high activity input detection and suppression ...................................................................... 6
iSTAR Edge to iSTAR Edge G2 conversion tool ...................................................................................... 6
Supported Operating Systems, DBMS, and SQL Collations ........................................................................ 6
Supported Browser and Mobile Operating Systems ..................................................................................... 8
Redundancy and Disaster Recovery ............................................................................................................ 9
Enterprise Considerations and Known Limitations ....................................................................................... 9
Installation and Upgrade Issues ................................................................................................................ 9
Application Layouts on MAS ................................................................................................................... 10
Editing Global Operators ......................................................................................................................... 10
Importing Considerations ........................................................................................................................ 10
Multi-Version Support.............................................................................................................................. 10
General Considerations and Known Limitations ......................................................................................... 11
Intellex Video Server Repairs.................................................................................................................. 11
Upgrading SiteServer appliances to C•CURE v2.90 .............................................................................. 11
DUO Two Factor Authentication ............................................................................................................. 11
Windows Server Core ............................................................................................................................. 11
Windows 10 Operating System Support ................................................................................................. 11
Windows 2016 Operating System Support ............................................................................................. 11
64-Bit Operating System Support with C•CURE 9000 Client ................................................................. 11
SQL Database and Backup..................................................................................................................... 11
Maximum Time for iSTAR Controller Certificate Signature Timeout ...................................................... 11
Editing iSTAR Input Trigger Causes Output to Stay Active .................................................................... 12
Creating an Encryption Key Passphrase After Installing C•CURE v2.90 ............................................... 12
apC Panels .............................................................................................................................................. 12
Restrictions for Cross Panel Events between apC Panels and iSTAR Controllers ................................ 12
Requirement for Adding PIN-only Card from Personnel View ................................................................ 12
Fingerprint Capture Attempt Causes Exception Violation and Locks Administration Client ................... 12
2
Areas ....................................................................................................................................................... 13
Aperio Doors ........................................................................................................................................... 13
Application Layouts ................................................................................................................................. 13
Language Pack ....................................................................................................................................... 13
Maps........................................................................................................................................................ 14
ID Scanner .............................................................................................................................................. 14
C•CURE Kiosk ........................................................................................................................................ 15
Direct Show capabilities after installation................................................................................................ 15
C•CURE Portal ........................................................................................................................................ 15
User-Defined Fields ................................................................................................................................ 15
C•CURE Web Client (Legacy) ................................................................................................................ 16
C•CURE Web Client Classic ................................................................................................................... 16
Reports .................................................................................................................................................... 16
iSTAR Ultra Video ................................................................................................................................... 16
GPS Coordinates in Journal.................................................................................................................... 16
Previous Doors Tab ................................................................................................................................ 16
C•CURE Go Reader................................................................................................................................ 16
Compatibility of Third Party Hardware ........................................................................................................ 16
Compatibility of Third Party Software .......................................................................................................... 18
Firmware Versions for Tyco Security Products Controllers ........................................................................ 18
Enhancements ............................................................................................................................................ 19
Issues Fixed ................................................................................................................................................ 20
Upgrading to Version 2.90 .......................................................................................................................... 26
C•CURE and victor Server Databases May Expand During Upgrade .................................................... 26
Upgrade May Freeze with Out-of-Disk Space Error ............................................................................... 26
Post-Upgrade Steps for C•CURE 9000 v2.90 System on Custom (Non-default) Path .......................... 27
Exported Objects into External XML Documents .................................................................................... 27
SDK Connected Program Drivers ........................................................................................................... 27
Installation of Version 2.90 .......................................................................................................................... 27
Enable Microsoft Media Foundation Server ............................................................................................ 27
SQL Privileges for Local System Account in a Workgroup ..................................................................... 27
Server Requirements Failure Message during Installation on Windows Servers ................................... 27
Installation Completes on Longer-than-15-Character Name Computer but Clients Do Not Connect .... 27
Services/Server Components Manual Start ............................................................................................ 28
victor Temporary License Expiration and C•CURE 9000 Licensed Video Drivers ................................. 28
Installing C•CURE Go Web Service and C•CURE 9000 Web Client...................................................... 28
End of Release Note ................................................................................................................................... 29
3
Installation Media Contents
The installation media includes C•CURE 9000 from Software House and victor from American Dynamics.
These combine for Unified deployments. The installation media also includes supporting Services and
Integration drivers.
Contents:
• C•CURE 9000 Install components (victor Application Server and C•CURE 9000 Client).
• EULA.rtf – End User License Agreement.
• HostIDUtil.exe – HostID Application.
• CC9K-v2-90-RN-8200-1950-25-B0.pdf – the C•CURE 9000 v2.90 release note file (check the
Software House website for the latest revision of the C•CURE 9000 v2.90 release note file).
• CC9K-v2-90-CCUREWeb-RN-8200-1950-37-A0-en – the C•CURE 9000 v2.90 C•CURE web-
based client release note file.
• Unified Quick Start Guide.pdf - the Unified Installer Quick Start Guide.
• C•CURE Quick Start Guide.pdf –the C•CURE Quick Start Guide.
• victor Quick Start Guide.pdf – the victor Quick Start Guide.
• Setup.exe – Executable to launch the installation dashboard.
• Certificates folder containing security certificate files.
• Bin folder containing supporting installers and support files for C•CURE 9000 and victor
products. Installers should be installed through the installation dashboard, not through individual
install files.
• Manuals folder containing the documentation of Software House software and hardware
products.
• Integrations folder containing installers and support files for DSC and Galaxy Intrusion
integration software.
• Prerequisites folder containing prerequisite software requirements for C•CURE 9000 and victor.
NOTE: The Intellex, Video Edge, and HDVR/Exacq video drivers are included with this v2.90 release.
New Features
The following features are new in C•CURE 9000 v2.90.
C•CURE 9000 web-based client

You can use the new C•CURE 9000 web-based client to configure objects in the C•CURE 9000 system
using a web browser. The following features are available in the C•CURE 9000 web-based client:
• Personnel administration
o Personnel management
o Badging
o Credential management
o Clearances management
• Personnel setup
o Personnel view management
o Personnel type management
o Personnel template management
o Web view management
For more information on the new C•CURE 9000 web-based client, refer to the C•CURE 9000 web-based
client Guide.
C•CURE Legacy Web

If you are upgrading the C•CURE 9000 web-based client and need to access legacy features, C•CURE
Web (Legacy) will still be available at “http://localhost/ccureweb” for existing installs only.
4
For more information on C•CURE Legacy Web, refer to the C•CURE v2.90 Legacy Web Guide.
C•CURE 9000 Dashboard/Home Screen

The new C•CURE 9000 dashboard can be customised and frequently used objects and views can be
pinned to the homescreen for convenience. The new dashboard contains a number of new items:
• Tab bar to display multiple Dynamic Views as tabs.
• Recent Tabs section displaying recently opened Dynamic Views or objects.
• Recent Objects section displaying the last views and objects visited.
For more information, refer to the C•CURE 9000 v2.90 Getting Starting Guide.
Basic Authentication Login Throttling

Operator accounts using Basic Authentication are temporarily locked if an incorrect username or
password is used a certain amount of times without a certain time period.
For more information, refer to the C•CURE 9000 v2.90 Software Configuration Guide.
C•CURE ID
C•CURE ID has been updated with the following printing and badging features:
• The Fargo HDP6600 printer is supported in v2.90.
• You can now use barcodes in the GS1 Datamatrix and QR Code formats in the C•CURE ID
badge designer.
• Gemalto ID scanners are supported in v2.90.
• C•CURE ID supports the AssureID SDK to auto-detect fields in scanned IDs.
For more information, refer to the C•CURE 9000 v2.90 C•CURE ID Guide.
Video Search
You can perform video searches in C•CURE v2.90. You can search for analytic alerts, such as motion
detection, in any analytic-enabled camera’s recorded video.
NOTE: The analytics available depends on the camera and the NVR (VideoEdge, Exacq etc) it is
connected to.
For more information, refer to the C•CURE 9000 v2.90 Monitoring Station Guide and the C•CURE 9000
v2.90 System Maintenance Guide.
Video Clip Management

You can create a video clip storage folder in C•CURE v2.90. When you create snapshots or video clips,
you can now save them to this clip storage folder as an alternative to storing them on the NVR that you
access through C•CURE.
For more information, refer to the C•CURE 9000 v2.90 Monitoring Station Guide and the C•CURE 9000
v2.90 System Maintenance Guide.
Journal Volume Management

The Server Configuration Application now contains a new tab for Journal Volume Management.
Administrators can create multiple empty journal volumes for later use, reducing the need to grant full
SQL privileges to other users and strengthening security.
For more information, refer to the C•CURE 9000 v2.90 System Maintenance Guide.
iSTAR Edge G2 Support

C•CURE 9000 v2.90 supports the new iSTAR Edge G2 Linux-based PoE 4-door controller.
5
iSTAR driver high activity input detection and suppression
The C•CURE 9000 v2.90 iSTAR driver can detect high activity inputs and automatically reduce the input
state change journal rate and object update rate to mitigate performance issues caused by high activity
iSTAR inputs. The iSTAR driver counts input active state change and supervision error change as high
activity inputs and writes to the Journal when high activity input is detected. The iSTAR driver Active
Status in the C•CURE 9000 Status List window changes to “High Activity”.
There are 2 new iSTAR driver system variables to help manage this feature:
• High activity input detection period
• High activity input threshold
You can set the detection time period using this system variable. The default value is 5 minutes. Setting
this to 0 minutes disables detection. You can set the input threshold for high activity (Input active state
change and supervision errors count as high activity inputs). The default value is 500 input object change
counts. Using the default values, the iSTAR driver will suppress high activity input status changes and
journal messages when the input object change count is greater than 500 within a 5 minute time period.
iSTAR Edge to iSTAR Edge G2 conversion tool

You can use the iSTAR Edge to iSTAR Edge G2 conversion tool to convert iSTAR Edge panel to iSTAR
Edge G2 panel within the C•CURE Administration Client. The conversion process converts an iSTAR
Edge panel to iSTAR Edge G2 panel within the C•CURE database. The conversion retains the iSTAR
Edge’s name, and the object GUIDs of the iSTAR, boards, doors, readers, events, actions, and any
associated objects. You do not need to create new objects, edit events, or map icons. C•CURE also
retains the iSTAR Edge’s journal history.
For more information, refer to the C•CURE 9000 v2.90 Hardware Configuration Guide.
Supported Operating Systems, DBMS, and SQL Collations

Table 1: Microsoft Operating Systems for Server and Client
Server Series L/M/N/SAS Supported Version
Windows 10 Professional* 64-bit
Windows 10 Enterprise* 64-bit
Windows 11 Professional 64-bit
Windows 11 Enterprise 64-bit
Windows Server 2016 Standard 64-bit
Windows Server 2016 Datacenter 64-bit
Server Series P/Q/R/R+/S/S+/T/SAS Supported Version
MAS Server Supported Version
6
Client Supported Version
*NOTE: Windows 10 must be v1809 or higher. Ensure that Microsoft Windows Media Foundation Server
is enabled in your Windows environment.
Table 2: Microsoft DBMS

Server Series L/M/N/SAS Supported Version
SQL Server 2014 Express SP2 or higher (64-bit)
SQL Server 2016 Express SP1 or higher (64-bit)
SQL Server 2016 Standard SP1 or higher (64-bit)
SQL Server 2016 Enterprise SP1 or higher (64-bit)
SQL Server 2017 Express* All Service Packs (64-bit)
SQL Server 2017 Standard All Service Packs (64-bit)
SQL Server 2017 Enterprise All Service Packs (64-bit)
SQL Server 2019 Express All Service Packs (64-bit)
Server Series Standalone P/Q/R/R+/S/S+/T Supported Version
SAS Server Series P/Q/R/R+/S/S+/T Supported Version
SQL Server 2017 Standard SP1 or later (64-bit)
MAS Server Supported Version
7
*NOTE: SQL Server 2017 Express supports C•CURE v2.80 to v2.90 upgrades on SiteServer.
Table 3: SQL Server Collations Supported

Windows Locale Default Collation
Arabic (Saudi Arabia) Arabic_CI_AS
Chinese (PRC) Chinese_PRC_CI_AS
Chinese (Taiwan) Chinese_Taiwan_Stroke_CI_AS
Czech (Czech Republic) Czech_CI_AS
Danish (Denmark) Danish_Norwegian_CI_AS
Dutch (Netherlands) Latin1_General_CI_AS
English (United Kingdom) Latin1_General_CI_AS
English (United States) SQL_Latin1_General_CP1_CI_AS
French (France) French_CI_AS
German (Germany) Latin1_General_CI_AS
Greek (Greece) SQL_Latin1_General_CI_AS
Hungarian (Hungary) Hungarian_CI_AS
Italian (Italy) Latin1_General_CI_AS
Japanese (Japan) Latin1_General_CI_AI
Korean (Korea Dictionary Sort) Korean_Wansung_CI_AS
Polish (Poland) Polish_CI_AS
Portuguese (Brazil) Latin1_General_CI_AS
Russian (Russia) Cyrillic_General_CI_AS
Spanish (Spain) Modern_Spanish_CI_AS
Swedish (Sweden) Finnish_Swedish_CI_AS
Turkish (Turkey) Turkish_CI_AS
Supported Browser and Mobile Operating Systems

Table 4: Browser and Mobile Operating Systems Supported
IIS Versions 2.90
IIS Web Server v8 or later
C•CURE Go
Android v7 or later
iOS iOS13 or later
C•CURE Go Reader
Android v7 or later
C•CURE 9000 web-based client
Microsoft Edge (Chromium-based) v83 or later
Google Chrome v83 or later
Mozilla Firefox v77 or later
Apple Safari Supported
C•CURE Portal Visitor and Access Management
Microsoft Edge (Chromium-based) v83 or higher v83 or higher
Google Chrome v83 or higher v83 or later
Mozilla Firefox v77 or higher v77 or later
Apple Safari Supported
Visitor Kiosk App (iOS) Supported
C•CURE Kiosk
Android Not Supported
iOS iPad only
8
Redundancy and Disaster Recovery
The following table shows the redundancy and disaster support software that is supported for C•CURE
v2.90.
Table 5: Redundancy and Disaster Recovery Software Supported

Versions v2.70 v2.80 v2.90
Stratus everRun MX 7.4.2 7.4.2 7.7
Stratus everRun Enterprise 7.4.2 7.4.2 7.7
Stratus everRun Extend Supported Supported Supported
NOTE: Only the latest available versions of Stratus everRun MX and Enterprise are qualified on each
C•CURE 9000 release. Stratus everRun MX and Enterprise will be qualified on C•CURE 9000 v2.90 SP1.
Enterprise Considerations and Known Limitations

Installation and Upgrade Issues
Using SQL Server Express with SAS Server L/M/N Upgrades

SQL Server Express is supported for upgrades of SAS Servers Series L/M/N but for best performance,
use SQL Server Standard/Enterprise with C•CURE 9000 v2.90. SQL Server 2017 Express supports
C•CURE v2.80 to v2.90 upgrades on SiteServer. For more information, refer to the datasheet for the
applicable SQL Server versions compatible with C•CURE 9000 v2.90.
SAS and Licensing

You cannot convert a SAS to standalone by changing the license after initially installing and licensing it as
a SAS.
Relation between SAS and its MAS

You cannot point an existing SAS to a different MAS. Ensure you perform a system backup of the MAS
before adding each new SAS in case you have to revert the enterprise to the setup before the SAS was
added.
Upgrading MAS before its SAS

You must upgrade the MAS before you upgrade the SAS systems to the same version. If you upgrade
your SAS systems first, the SAS systems must be restarted again after upgrading the MAS.
Synchronizing Journal before Upgrading from v2.30/2.30 R2/2.50 to v2.90

Prior to upgrading your MAS and SAS systems from v2.30/2.30 R2/2.50 to v2.90, you should verify that
any scheduled Journal Synchronization from SAS to MAS has been completed.
Caution: Close the ‘CrossFire Server Component Framework Service’ prior to performing this last
synchronization. If you do not synchronize before upgrading to v2.90, unsynchronized journal messages
from v2.20/2.30/2.30 R2 never sync to the MAS. For more information about the Application Server
Synchronization tab, refer to Chapters 4 and 10 in the C•CURE 9000 Enterprise Architecture Guide.
Upgrading SAS While Server Not Configured/Running Correctly May Fail

Do not upgrade a SAS when the server is non-functioning as the upgrade may fail. Run a repair, and
ensure the repair is successful before performing the upgrade.
Converting a Standalone C•CURE 9000 System with UDFs to a v2.90 SAS

You cannot automatically convert a C•CURE 9000 system with User Defined Fields (UDFs) to a SAS. For
detailed instructions, refer to Chapter 2 of the C•CURE 9000 Standalone to SAS Migration Utility User
Guide.
9
Upgrading Enterprise System with SAS Once Standalone C•CURE 9000 to v2.90
If you are upgrading an Enterprise System with a SAS that was once a Standalone system to v2.90, you
may need to do the following after the SAS is upgraded and fully running: stop and then re-start any
running Administration/Monitoring Station applications connected to the MAS. This allows the application
to access certain Enterprise functions, such as Synchronization Conflict Views.
Uninstalling MAS with Server Management Application Open Causes Error

Ensure the Server Management Application is closed before uninstalling a MAS. If you uninstall a MAS
without closing the Server Management Application, a message is displayed asking you to close the
Server Management Application. The uninstall will complete unsuccessfully and displays a fatal error
message.
Application Layouts on MAS

Do not edit the 3 pre-defined Application Layouts on the MAS (Default View 1/Default View 2/Default
Application Layout). Create, and assign, a new MAS Application Layout to all Operators to avoid the need
to edit pre-defined layouts.
Editing Global Operators

Do not edit Global Operators if you are logged into the system as a Local Operator as Application Layouts
will not save correctly.
Importing Considerations
• For performance reasons, imports should be done on the server that owns that Object’s partition.
Example:
Global data should be imported on the MAS, and Local data should be imported on the SAS that owns it.
• Very large imports can cause the MAS performance to significantly degrade when synching with
the SAS. Importing personnel records with attached documents and/or images can use significant
amounts of memory during replication. Software House recommends you keep imports down to a
total of 400MB, including both Image and Document data.
Example:
3000 personnel with 500KB Documents for each personnel record = 1.5GB of memory to
process.
Multi-Version Support
C•CURE 9000 provides Multi-version support. This is the ability for SAS systems not yet upgraded to the
version the MAS is running to connect to the MAS, synchronize records, and identify conflicts, and attach
clients to the MAS to configure and monitor the Enterprise. From the MAS perspective, a Global Operator
has the ability to attach to both upgraded and non-upgraded SAS systems, with some limitations due to
the version differences.
The Multi-version process begins with an Enterprise where the MAS and every SAS is currently at the
same version, and the MAS is upgraded. Therefore, only two versions of C•CURE 9000 can be involved:
• The new version to which the MAS has been upgraded.
• The previous version at which all SAS systems were operating.
If an Enterprise currently has a MAS at one version and SAS systems with differing versions, it is
necessary to update all SAS systems to be at the same version as the MAS to establish a common
baseline, prior to beginning to upgrade the MAS to take advantage of Multi-version support.
The intention still is to proceed with upgrading every SAS to match the new MAS version. The difference
is that until that point, all the SAS systems can participate in the Enterprise, within version-specific
limitations.
To enable upgraded clients to communicate with previous version SAS systems, during the upgrade a
copy is made of the C•CURE 9000 client applications from the previous version so that these applications
can be launched when needed if the upgraded client detects it is running in a Multi-version Enterprise.
10
For a complete list of Multi-Version Support limitations, refer to the C•CURE 9000 Enterprise Architecture
Guide.
General Considerations and Known Limitations

Intellex Video Server Repairs
If you are unable to create Intellex Servers, navigate to the Intellex API in Windows Programs and
Features and click Repair to repair the Intellex API.
Upgrading SiteServer appliances to C•CURE v2.90

SiteServer appliances cannot upgrade to C•CURE v2.90 using the current C•CURE v2.90 installation
image. SiteServer appliances can only be upgraded to C•CURE v2.90 using a SiteServer-specific
upgrade image.
DUO Two Factor Authentication

Double-swipe functionality does not function on DUO-enabled doors.
Windows Server Core

Windows Sever Core Edition is not supported on v2.90.
Windows 10 Operating System Support

C•CURE 9000 supports client and server installation on:
• Windows 10 Professional and Enterprise.
The following limitations exist when running a C•CURE 9000 Client on these operating systems:
• Digi International WatchPort/V2 USB Camera - Not supported.
• Penware 100 signature tablet - Not supported.
• Bioscrypt - The VeriAdmin application used to configure Bioscrypt readers does not support
Windows 10. You can configure the readers using a separate workaround.
• Edge browser – the Windows 10 EdgeHTML browser is not supported.
NOTE: Edge Chromium is supported.
• Third party integrations – check with the vendor for Windows 10 client support.
Windows 2016 Operating System Support

C•CURE 9000 supports client and server installation on:
• Windows Server 2016 Standard and Enterprise.
The following limitations exist when running a vAS on these operating systems:
• Digi International WatchPort/V2 USB Camera - Not supported.
• Penware 100 signature tablet - Not supported.
• Edge browser – the Windows 10 EdgeHTML browser is not supported.
NOTE: Edge Chromium is supported.
64-Bit Operating System Support with C•CURE 9000 Client

The Tango Magiccard 32-bit setup cannot be run on a C•CURE 9000 Client on a 64-bit operating
system.
SQL Database and Backup

The hard drive partition you install the C•CURE 9000 database on requires a minimum of 80 GB free
space.
Maximum Time for iSTAR Controller Certificate Signature Timeout

iSTAR eX/Edge/Pro controllers use five minutes as the maximum time for “Controller Certificate Signature
Timeout.” Thus, if you do not approve certificate requests when changing to controller-based encryption
mode, the iSTAR reboots at five minutes—even if you configure a timeout period greater than five
minutes.
11
Editing iSTAR Input Trigger Causes Output to Stay Active
If you configure and save a trigger for an iSTAR Input that uses the Armed status value to activate an
Output and you edit the trigger to change the Armed status value after the Output has been activated, the
Output stays active. To change the trigger so the Armed status value for the trigger updates properly, you
need to delete the trigger and re-create it with the new value for Armed status.
Creating an Encryption Key Passphrase After Installing C•CURE v2.90

You can create an encryption key passphrase after installing C•CURE v2.90 if you opted to postpone
creating one during the installation process. Open the Encryption Key Manager Utility from the following
location and follow the on-screen instructions to create the passphrase: C:\Program Files
(x86)\Tyco\CrossFire\EncryptionKeyMgr\netcoreapp3.1\EncryptionKeyMgrWindow.exe
apC Panels
apC Panel Limitations with Timed Actions

Under certain circumstances, apCs do not behave the same as iSTARs when they lose communication
with the host. The host to apC connection supports a limited timed Action capability that works well for
locking/ unlocking Doors, activating/deactivating Outputs, etc. If, however, there are overlapping or
conflicting timed Actions at the apC when power or communication is lost, the results are indeterminate.
Example: If there is a manual Door lock timed Action for an hour and a scheduled host-based Event to
unlock the Door during that time, the host will sort it out. On the other hand, if the host is not
communicating, the apC may or may not restore everything correctly. Software House recommends that
you keep apC timed Actions simple—to avoid overlapping conflicting Actions.
Scheduled Events on apC Door, Input, and Output Groups

Events configured to unlock an apC Door Group, arm an apC input Group, or activate a group of apC
outputs according to a Schedule do not work if the apC panel is offline.
Event Activation Delay Time and/or Minimum Activation Time Ignored if apC is Offline
In offline mode the apC does not support Activation Delay Time and Minimum Activation Time.
Consequently, if an Event configured with Activation Delay Time and/or Minimum Activation Time
activates while the apC is offline, the action will be performed immediately when the apC comes back
online.
apC Event Action Activation Message Not Reported under Certain Circumstances
Timed Actions that occur when the apC is offline may not report (display on Monitoring Station) when the
apC comes back online.
apC Connected to a different server needs to be reset before Clearance download.

If an apC is connected to a new C•CURE 9000 Server, the panel must be reset in order to correctly
download Clearances.
Restrictions for Cross Panel Events between apC Panels and iSTAR Controllers
You can configure an apC Door or Input Trigger to activate an iSTAR Event, but if the Event is configured
with the Download to compatible controller option, it will not activate. Either of the following will work:
• Configure the apC Door/Input Trigger to activate a host-based Event that in turn activates the
iSTAR Event.
• Do not select the Download to compatible controller option for the iSTAR Event.
Requirement for Adding PIN-only Card from Personnel View

If you want the capability to add a PIN-only Card from a Personnel View, you must ensure that the Auto
Generate button in the PIN Credential box on the Personnel View is not hidden.
Fingerprint Capture Attempt Causes Exception Violation and Locks Administration Client
If you are using Bioscrypt, before trying to capture a fingerprint follow the workaround directions.
Workaround: Copy the BII_V1100.dll file from the Bioscrypt install directory to the Client \Badging
directory.
12
Areas
Using Escorted Access with Muster/De-muster

If you are using the Escorted Access feature with Muster/De-muster, make sure that the De-muster Area
does not have the “An Escort must always be present in Area with Escorted Visitors” check box selected.
Offline Transactions Cause Host Occupancy Counts to be Unreliable on iSTARs

A Cluster member iSTAR that goes into communications failure may still try to make occupancy
decisions. When communications are restored, delivery of the delayed transactions invalidates the area
counts at the host. This situation is made even worse if the “Always Track Personnel” system variable is
set to ‘True’.
Remove All Personnel from Area Command Does Not Remove Personnel from Area
The ‘Remove All Personnel from Area’ command from the iSTAR Area Context Menu changes the
Personnel records in the host, setting their ‘Area’ to a zero value. In addition, a Dynamic View of
Personnel who were in the Area no longer shows a value in the Area column, and the ‘Show Personnel in
Area’ command for the Area displays an empty Dynamic View. However, the iSTAR controllers do not
change the location of Personnel in that Area, so an Operator may have to grace Personnel for them to
be granted access when swiping their cards. This is true if Antipassback is configured. In addition, the
Personnel count for the Area is not reset in the iSTAR controllers, requiring an operator to use the ‘Clear
Area Counts’ command on the Area to update the counts.
Aperio Doors
Aperio Doors Do Not Re-lock on Access Completion

Aperio Doors do not re-lock, as other iSTAR doors do, after being opened and then closed. They re-lock
at the expiration of the unlock time.
Workaround: Configure the Doors to shunt for the full shunt time regardless of the Door lock/relock
status.
Aperio Doors Become Disabled by the All Doors Group Unlock Manual Action
If you perform an Unlock Manual Action on the All Doors Group, Aperio Doors in the Group will be
disabled—reading presented Cards, but not unlocking the Door. Software House recommends that you
not perform manual actions on the ‘All Doors Group’.
Aperio Doors Lock/Unlock Limitations

• Aperio Doors do not support Lock/Unlock/Momentary Unlock Manual Actions on the Web Client.
• Aperio Doors containing Aperio v3 readers support Lock/Unlock/Momentary Unlock Manual
Actions on the Monitoring Station.
• Aperio Door containing Aperio v2 readers do not support Lock/Unlock/Momentary Unlock Manual
Actions on the Monitoring Station.
NOTE: Aperio v3 Readers are: IN 100 v3, H100 v3, C100 v3, L100 v3, KS100 v3. Any Aperio readers
configured prior to 2.80 SP2 are Aperio v2 readers.
Application Layouts
Legacy application layout objects can be edited in v2.90 but you cannot create new instances of these
legacy application layout objects in C•CURE v2.90.
Language Pack
Language Pack Upgrade and Repair Requirements

If you are upgrading your C•CURE 9000 to v2.90 and currently have the C•CURE 9000 Language Pack
installed, you must also upgrade the Language Pack. Make sure that during the upgrade process the
Language Pack option on the Dashboard Integration and Services Screen remains selected (checked).
13
In addition, if you are repairing a C•CURE 9000 with an installed Language Pack, you also must repair
the Language Pack.
Language Pack Installation

If you rename dynamic views using the same names as the default names the language pack may not
install as expected.
Maps
Legacy Maps
Legacy maps can be viewed but cannot be edited in C•CURE 9000 v2.90. You must convert legacy maps
before editing.
Maps Backward Compatibility

You cannot import Maps containing any icons from a C•CURE 9000 system running v2.70 or older to a
C•CURE 9000 v2.90 system. In Enterprise Multi-version systems, Maps from SAS machines running
v2.70 will display on MAS systems running v2.90 but icons will not update with state changes.
ID Scanner
OS support
The Accuant IDScanners Snapshell R2 and Snapshell Passport are only supported in Windows 8, 8.1
and 10. Windows Server does not support these ID Scanners.
Hologram logos on the front side of driver’s licenses and passports may interfere with scanning
Due to the variation in layouts of driver's licenses and passports, the hologram logo on the front side of
the ID may interfere with the ability of the ID scanner to scan information. It is recommended that you
configure the ID scanner settings to scan on both sides.
Delay of 5-10 seconds when performing ID Scanner

There is a 5-10 second delay between performing an ID Scan and receiving data from the ID Scanner.
Performing ID Scan on two Administration Stations simultaneously may result in a failed scan
If users perform an ID Scan simultaneously on two Administration Stations on the same machine, a failed
scan may occur because the ID Scanner SDK can only be used on one Administration Station at a same
time.
AssureID Scan SDK

C•CURE ID scan uses the AssureID SDK to support the latest scanners. C•CURE V2.90 is qualified with
AssureID SDK v5.2.80 and AssureID_Document_Library_v20.03.10.171.msi.
NOTE: The AssureID integration is for data capture, not document authentication and is supported on
Snapshell Passport, SnapShell R2 and R3, and Gemalto QS1000 and AT9000.
AssureID SDK is not installed by default. Contact Acuant to obtain the SDK and a subscription license for
the scanner using this email address: orders@acuant.com Provide the following information in your order:
• Contact name.
• Company name.
• Billing address.
• Phone number.
• Scanner model to be operated with software.
• Quantity of AssureID Sentinel software licenses required. (if ordering multiples, indicate if you
requires separate keys)
• The software maintenance expiration date.
• Name and email address to assign to the software keys.
• Payment information.
14
C•CURE Kiosk
C•CURE Kiosk generates license error during login despite using correct credentials
If a C•CURE Kiosk session is terminated without performing the correct log-out procedure, the C•CURE
9000 server does not assign the C•CURE Kiosk license the next time an operator attempts to login. Either
of following can be used as a workaround:
• Wait for approximately two minutes for C•CURE 9000 to re-assign the license.
• To release all the licenses back to the C•CURE 9000 server, restart the Internet Information
Services (IIS) server that hosts the victor Web Service.
Visitor registration fails in C•CURE Kiosk if Email settings are not configured in C•CURE 9000
If Email settings have not been configured in C•CURE 9000, or if the Email server has been shut down,
C•CURE Kiosk displays an error message at the end of the registration process to indicate that visitor
registration has failed. For more information about configuring Email settings in C•CURE 9000, refer to
the C•CURE 9000 System Maintenance Guide.
C•CURE Kiosk does not login after initial install

After initial install of the C•CURE Kiosk, there may be login issues where login credentials are recognized
but no Check-in Sites display, and the C•CURE Kiosk reverts to the login screen. To work-around this
issue, you must delete the C•CURE Kiosk application cache in the iPad and login again.
Multi-line user defined fields (UDFs) are not supported in the C•CURE Kiosk
If you assign a Multi-line UDF to a Visit Site, the UDF that displays in the C•CURE Kiosk is a regular text
field that does not have the attributes of the Multi-Line UDF.
Using an XML data import definition to disable multiple languages in a Check-in Site
If you configure an Import definition that uses an XML data source to clear the Use Language in the
Kiosk check box in a Check-in Site, you must assign a blank value to the Translated String in the XML
file.
<TranslatedString> </TranslatedString>
Direct Show capabilities after installation

Not all operating systems have Direct Show capabilities enabled after installation. If you are using a
webcam for capturing portraits, ensure that you have enabled these features on your operating system.
You can enable these features through the Control Panel > Programs and Features.
C•CURE Portal
Web Portal on Internet Explorer does not support up and down arrows for decimal fields
If you are using the Web Portal on Internet Explorer, up and down arrows for decimal fields on the Visit
Details screen do not work as expected.
Maximum of 5 documents for C•CURE Portal and C•CURE 9000 Visit and Visit Sites Editors
The number of documents that you can add to the C•CURE Portal and the Visit and Visit Site Editors in
C•CURE 9000 is restricted to a maximum of 5.
User-Defined Fields
User-Defined Fields in Visitor Management after installing the Language Pack

• After installing the Language Pack, when you create a UDF Label in Visitor Management and
your system is configured in a regional language, CCURE 9000 automatically creates a UDF
label in a corresponding base language available in the Language Pack. UDF Labels created
prior to installation of the Language Pack still display the regional language of your system in
addition to the base language available in the Language Pack.
15
• After installing the Language Pack on a client with a local language, the UDF local language is
removed from the list of available languages in the UDF Editor.
C•CURE Web Client (Legacy)
C•CURE Web Client (Legacy) requires Adobe for download

If you are running a report on C•CURE Web Client without Adobe Acrobat installed on your system, the
screen indicates it is downloading, but no download takes place. You must install Adobe Acrobat on your
system manually.
C•CURE Web Client Classic

C•CURE Web Client Classic does not support Windows Server R2 and 32-bit version operating systems.
Reports
After you upgrade your C•CURE version, an error message appears when you configure an iSTAR
Report with the Basic Configuration sub-type and you select all check boxes in the Class and Field
selectors.
iSTAR Ultra Video

If you plan on upgrading your C•CURE 9000 system to v2.90, and have iSTAR Ultra Video versions
4.90/6.4.3 or 4.93/6.5.3, you need to update your iSTAR Ultra Video to version v5.1/6.6.0 prior to
upgrade.
GPS Coordinates in Journal

You must use a compatible device, such as the C•CURE Go Reader, to take advantage of this Location
field. If you are using a feature of C•CURE that writes to the Location field of the journal, we strongly
recommend that you use SQL Server 2016 for the best performance. If you are using a version of SQL
Server prior to 2016, we recommend that you enable flag 6533 to optimize write performance for
geospatial coordinates. To enable flag 6533, execute the following command: DBCC TRACEON (6533, -
1).
Previous Doors Tab

Due to changes to the Previous Doors tab in the Personnel editor, custom Personnel Views may not
display the Previous Doors tab correctly. To fix this, edit the custom view and include all controls that are
under the “Previous Doors” category in the Fields and Controls pane. The default views: Default
Personnel Edit View and Personnel View with Portrait in Header properly display the new controls
correctly.
C•CURE Go Reader
At the time of release, a C•CURE GO Reader driver is not available for 2.90. Check the Software
Downloads section of www.swhouse.com for availability. Uninstall C•CURE Go Reader prior to upgrading
to 2.90.
Compatibility of Third Party Hardware

The following list includes some of the third-party products compatible with C•CURE 9000 version 2.90.
Table 6: Third Party Hardware Compatibility Table

Equipment Type Vendor Model Model Latest Supported
Version
Digital Video American Dynamics Intellex 5.4
Management System
VideoEdge 5.4
HDVR 1.7, 2.1, 2.2
Exacq ExacqVision 7.8.2.98464
16
Wireless Readers / Schlage AD-30x / 40x AD.A.130
Locks
NDE/LE
Assa Abloy Aperio Hub Hub 6.6.32718
Signature Capture Topaz T-S261-B 3.0.3
Topaz USB T-S261-HSB 4.4.0
PenWare 100 PW100 4.5.0

USB Badging Cameras Video Associates Val Cam 6.1.76.00
VA-3 USB 6.1.76.00
Videology 2x USB 9.0
TWAIN 2.1.18
All brands WIA-compliant (non-TWAIN)

ID Scanners Acuant ScanShell R2/R3 SDK 10.11.04
SnapShell Passport SDK 10.11.04
Gemalto AT-9000-UV 5.2.80
QS1000
IP Cameras AXIS 2400/2401 2.33
Badging Printers Fargo HDP 5000 3.5.4
HDP 6600 01.00.0013
DCT 4500E 2.1.0.3.2
Magic Card 600 2.00
Pronto 2.00
Rio Pro 2.00
DYMO 450 Series
Brother 820-WiFi Printer
QL-820NWB WiFi
VC-500W WiFi
Primera LX500C No WiFi
Smart Card Device SCM Microsystems SDI010 5.21
17
Readers HID HID-USB-5421
5127
Identive 4701F
Innometriks Cheetah 5.2.6
Cheetah SE 2.0.2
Rhino 5.2.6
Compatibility of Third Party Software

The following list includes some of the third-party software compatible with C•CURE 9000 version 2.90.
Table 7: Third-Party Software

Company Product Latest Supported Version
Data Dynamics Active Reports 6.2.3681
American Dynamics Intellex API 5.02.32.45
Flexera FLEXNet Publisher 11.10.1
LEAD Technologies LEADTOOLS 14.5.0.68
Infragistics Infragistics 17.2
Microsoft .NET 4.61
SQL Server 3.5 if installing
Windows Installer 4.5
MFC Runtime 9.0 SP1, 10.0 SP1, 11.0, 12.0,

14.0
WIX WiX 3.9 R2
Sequiter Inc CodeBase 6.5
Stratus everRun MX 7.5.1.1
everRyn Enterprise 7.5.1.1
Stunnel Stunnel 5.42
The OpenSSL Project OpenSSL 1.0.2L
Apache CouchDB 1.6.1
Node.js Node.js 0.12.7
Firmware Versions for Tyco Security Products Controllers

18
The following table includes the firmware versions related to C•CURE 9000 v2.90.
Table 8: Firmware for Tyco Security Products Controllers

Component Latest Supported Version
iSTAR Classic 4.4.C
iSTAR Pro 5.2.F
iSTAR Edge, eX 6.2.8
iSTAR Ultra 6.7.0
iSTAR Ultra SE 6.7.0
ISTAR Ultra LT 6.7.0
apC, apC/8x, apC/L 10.7ZF
iSTAR Configuration Utility 6.8.0
iSTAR Edge G2 6.8.0
IP-ACM / IP-ACM 2 6.7.0
Enhancements
Table 9: Enhancements
Category Issue Fix Description
Number
Administration and 554830 Object High Activity Metric can be accessed from the Administration
Monitoring Station Client.
663396 User password for email can be up to 50 characters long.
625325 The About menu now displays the C•CURE service pack version
and build number.
553751 The Floor Selection automatically highlights groups by default when

configuring a clearance with elevators.
475572 Fixed length card numbers can now be generated.
Application Server 527713 Recurring schedules can be applied to Application Server object for
Journal or Audit sync.
Import/Export 464444 Import configurations residing on the MAS can match and update
local SAS personnel records.
Installation and 576705 Selected Settings screen is displayed during upgrades.

Upgrade
Journal 660872 A journal message is created when SAS synchronization state
changes.
664884 A journal message to log maintenance steps is created when
Journal log volumes are automatically set to standby during log
volume management action.
Object Selection 511838 Pulse Duration value can be set using Set Property on the object.
Control
Personnel 659627 Up to the 50 characters can now be entered in the UDF
Enumeration Value box.
520287 All columns of the Personnel editor data grids can be resized.
19
Readers 649051 Reader LCD Message Set can now be applied to multiple iSTAR
controllers at once using a new executor available from the
controller GUI.
Visitor 667053 Journal message has been added to record that an NDA
Management form/document has been read by a visitor at the C•CURE kiosk.
Temporary Credential Assignment Temporary credential assignment through XML import

You can use the C•CURE 9000 import engine to assign and re-
assign temporary credentials to existing Personnel profiles.
Reader LCD Message Bulk Set Reader LCD Message Set can now be applied to multiple iSTAR
controllers at once using a new executor available from the
controller GUI.
Issues Fixed
Table 10: Issues Fixes
Number
Administration and 610086 The Cluster Renaming window contains the correct number of
Monitoring Stations ACM board name entries.
663396 User password for email can be up to 50 characters long.
647412 APC readers remain in same partition as parent controllers, as

expected.
601199 System Variable GUI description for Allow Activation after

Expiration has been updated to indicate an iSTAR driver restart is
required before variable takes effect.
631385 SAS machines which are offline can be removed from a MAS as
expected.
665499 Tooltips have been added to diagnostic buttons.
605648 Updates to Dynamic Views with large numbers of Objects have

been enhanced to prevent client applications from freezing.
642714 Administration station navigation pane configuration is saved, as

expected, between client restarts.
628852 Audit log records removal of custom clearances from records.
663474 Operators with limited privileges can assign or remove clearances

using the context menu, as expected.
610343 Export Report file names with invalid symbols will not save. File
names must not contain special characters or symbols.
660508 Duplicate Doors or Inputs cannot be added to an Intrusion Zone.
655095 Clearances Dynamic View is displayed without unexpected delays.
507786 Personnel records created before a UDF and UDF mask can be
saved, as expected.
20
Number
658619 Event emails send as expected with, or without, text in the
Message Box.
658219 Action pane is rendered correctly when Create Copy is selected on

an event.
676319 "Schedule by Timezone” moves to the same partition as the

schedule when the schedule partition is changed.
667715 An issue which caused passwords which meet the complexity

requirements to be rejected as weak has been resolved.
543755 Doors can be renamed, as expected, when an event has been

added to a door trigger.
576452 Up to 10 windows can be displayed when multiple objects are
selected and Show Associations is selected from the context
menu.
572485 Moving comm ports between hardware folders is now dynamic and
does not require the user to refresh the window.
631014 Credential query Dynamic View can display more than 2500
records when “IsExpired” option is selected.
628848 Freeswitch service is set to manual at installation.
Areas and Zones 631386 Anti-Passback failure mode column displays the last saved mode
(global or local) when the iSTAR cluster editor is used.
662592 An error with a system variable associated with the iSTAR Area
Lockout feature has been resolved.
C•CURE ID 670105 Primary Portrait is set as the default image layout for Fargo
Connect badge printers.
644811 Batch proximity card enrol process has been improved.

654974 Error handling messages between Personnel Search and Editor
are now consistent.
C•CURE Web 678004 Display PIN is respected in the web client.

(Legacy)
Credential 631615 Print Badge and Preview Badge buttons are greyed out when no
layout is defined, as expected.
605601 Removing a temporary credential from one personnel record and

adding it to another personnel record re-activates the original
personnel record’s disabled credential(s), as expected.
CrossFire Server 527286 More detail is provided to users when the message “Unable to
Delete Object” is displayed.
629962 An error within the CompleteUpgrade process which prevented

services from starting after a MultiVersion upgrade has been
resolved.
21
Number
629956 Edits to records, door unlock schedules, and manual actions are
downloaded to iSTAR panels as expected.
676342 An issue which caused CrossFireRestfulService to fail has been

resolved.
601200 An issue which caused the “Allow activation after expiration”

setting to cause credential cleanup to fail has been resolved.
Cybersecurity 631053 SPNs created in an NTLM/Kerberos environment must be deleted

to restore C•CURE client to server connectivity if CrossFire
services are run as a local system.
Events 660023 Renaming Events does not require a system restart.
568241 Events clear from the Locked Causes list, as expected.
661457 Events with “Play Sound” action play the sound consistently, as
expected.
662594 Events with predefined log messages are saved, as expected.
663376 Instructions in the Event Details window are displayed in the

correct order.
676882 Outputs activated by an event follow the event rules consistently.
613933 State changes wait for door Relay Pulse time to expire.
655114 Events can be acknowledged multiple times in the Activity Viewer.
651054 Automatic event culling can be disabled.
Guard Tour 650354 Guard tour report “SWH109 – Guard Tours Completed Without
Errors” does not contain guard tours completed with errors.
HDVR 553240 Importing cameras and then saving cameras on the Exacq HDVR
works as expected.
Import/Export 599335 Error messages are included in the error log file stored in the
import folder when an XML import fails.
670062 Importing events with “Send to Monitoring Station” enabled, forces

the “Send to Journal” property to enable.
656564 Labels are imported correctly when importing Enumerated UDFs.
Installation and 677006 The file process.exe, which caused malware warnings in prior
Upgrade iterations, is not installed in C•CURE v2.90.
666574 A message is displayed to contact customer support for assistance

with collation repairs on SQL Server 2012.
22
Number
643072 Third party integration identifier information displayed during the
installation period has been updated.
631240 An issue which caused a duplicate password field to be displayed

when creating a password for the iSTAR diagnostic web page has
been resolved.
651038 High Assurance Enrollment Service performs as expected.
555237 Disabled default personnel views are not re-enabled when the
system is upgraded.
555568 Default administrator and guard operator objects created by an

installer can be disabled or deleted.
569516 / Improved error messaging is displayed if Error #1603 is displayed

607373 during installation.
596948 C•CURE GO web service can be installed with a MAS installation

and can be uninstalled, as expected.
598256 A validation step has been added to the installation process to

prevent users from installing C•CURE on servers using the
Domain\ComputerName server name.
623915 Installer verifies ISO type to ensure features and prerequisites
match the available system before installation begins.
653949 Installation/upgrades run as expected when using a local account

with correct privileges to run SQL service on domain.
iSTAR Driver 665138 GC board serial number status is not written to the Journal.
668107 Inputs function as expected when removed from an Elevator.
653302 Reader LC Message Set naming convention is consistent between

the Hardware Tree and Controller.
667165 Readers come back online as expected when iSTAR driver is
restarted.
665884 An issue which caused the iSTAR driver to run out of memory
during startup has been resolved.
653854 High activity inputs causing performance issues are detected and
suppressed.
669483 An issue which caused the iSTAR driver to run out of memory
during startup has been resolved.
653923 iSTAR driver will stop running if it experiences a timeout during
driver initialization.
669482 Communication status is reported correctly from iSTAR Ultra SE
panels running firmware v6.6.9.
645152 Changes made to an iSTAR controller configuration through a

remote client station save as expected.
23
Number
Journal 608134 If there is no space to write the SQL transaction log for the journal,
the system correctly shuts down.
666737 CrossFire Server shuts down correctly if Unified journal is not

created on startup.
667454 Message date and time corresponds with server date and time, as
expected.
631054 An error with an integration causing an error to be continuously

written to the Journal has been fixed.

654647 Audit sync can continue, as expected, when audit sync tracking
table is missing.
647311 Users cancelling a manual action are recorded in the journal.
647545 “Days per volume” system variable description has been improved.
626821 “Reference Removed” audit message is synchronised to the MAS

audit database when a MAS and SAS reconnect.
660872 A journal message is created when SAS synchronization state

changes.

Licensing 677287 Connection counts are grouped so elasticity does not use up extra
licenses per process.
663510 CrossfireLicense.txt diagnostic file is included in v2.90.
567809 A popup message is displayed when users exceed licensed

limits/features.
Maps 662684 Map icons on maps can be set to not propagate alerts, decreasing
map loading times.
Operators/Privileges 666579 DBManager InstallDiagnosticOperator command completes as

expected.
653920 An issue with privilege and partition handling, which caused server
performance issues, has been resolved.
620660 Smart card templates are available, as expected, to Operators

created in a partition with full privilege in that partition.
Personnel 675731 APB Grace Personnel works as expected.
24
Number
601189 “Limit Replay to X Records” checkbox can be enabled by default.
631189 An error which causes Innometriks High Assurance services to

freeze when adding personnel has been resolved.
663240 When creating a UDF with a MASK, character restrictions are

applied correctly when performing copy, paste, or using the import
function.
Queries/Reports 557715 Queries based on exception objects run as expected.
631012 SWH24 query returns all results, as expected, when PIN field is
selected in dynamic view.
654130 Complex Controller Action queries are handled more efficiently to
prevent timeout on SAS machines.
667388 / Times on custom reports and in query configurations are displayed

631643 in server/client local time.
666120 Export to Excel icon is displayed when configured as an exception,

as expected.
Readers 651086 PIN confirmation works as expected to ensure PIN numbers are
confirmed correctly when first set.
655115 Bulk Update Readers updates the all selected readers, as

expected.
669739 KS100 V3 is included in the drop-down menu for Aperio readers.
SAS Conversions/ 596390 Sound Event Actions and Report Event Actions map to new Object
Migrations IDs after migrating from standalone to a SAS.
SMTP 666042 SMTP sever configuration passwords can be up to 50 characters

long.
SQL 630996 Hardware objects can be edited and saved, as expected.
Swipe and Show 620313 Swipe and Show windows/tabs update without having to click on
the tab first.
590919 Carousel view is displayed as expected in Swipe and Show.
Time Zone 653938 An error which caused error messages in the Trace Logs related
to timezone pairs and audit triggers has been resolved.
victor Web Service 665115 C•CURE authentication session-ID header is formatted correctly.
Video 512242 Analytics alarms for HDVR and Exacq have been added to
C•CURE v2.90.
600992 IP camera video image can be resized to prevent stretching.
25
Number
658314 Fixed duplicate IP addresses can be used between HDVRs.
Visitor Management 645769 Connections between C•CURE Kiosk and server are restored
automatically if the kiosk is shut down during registration.
645778 The correct local time is displayed in the Last Visit Time column of
the visitor record dynamic view.
538236 Visitor Management sends visit-registered email to host, as

expected.
658008 Host search result works as expected.
663586 User message text remains consistent between check-in site and
kiosk.
660027 An issue which caused unexpected errors to occur after importing
personnel through the Visitor Management portal has been
resolved.
667433 Visitor Management sends correct email notifications.
604638 Visit Template settings are consistently copied to Visits created

from that template.
653904 Visitor check-in now works on a MAS.
Upgrading to Version 2.90

Refer to the C•CURE 9000 Installation and Upgrade Guide for information on upgrading your C•CURE
9000 system.
You can upgrade to C•CURE 9000 v2.90 directly from the following earlier versions:
Table 11: Software Version Upgrades

SiteServers, Standalone, and Enterprise Systems
v2.7x to v2.90
v2.80 to v2.90
Be aware that upgrading removes the existing firmware files

(<INSTALLDIR>Tyco\CrossFire\ServerComponents\apC and istar) while adding the new firmware
versions. If you need to keep your existing firmware, save the files elsewhere before you upgrade to
v2.90. Otherwise, you have to re-download these files from the Software House web site.
C•CURE and victor Server Databases May Expand During Upgrade

Ensure you have ample disk space available before upgrading as C•CURE and victor Server application
databases may expand by up to 10GB.
Upgrade May Freeze with Out-of-Disk Space Error

During an upgrade, a message may inform you that there is not enough disk space available.
26
Workaround: Add more disk space on an existing/new drive and run the upgrade again.
Post-Upgrade Steps for C•CURE 9000 v2.90 System on Custom (Non-default) Path
If you are upgrading a system in a custom (non-default) location, once the upgrade to v2.90 completes,
you must verify that the System Variable paths for Import, Export, and Database Backup are correct.
Exported Objects into External XML Documents

If you have exported objects into external XML documents from previous versions of C•CURE 9000, you
may not be able to re-import them directly into C•CURE 9000 v2.90. Object definitions in the database
can change from version to version, so the import may fail or the imported object may not work correctly
in C•CURE 9000 v2.90.
Workaround: If you have any valuable XML documents generated by Data Export in a prior version of
C•CURE 9000, you should do the following prior to upgrading C•CURE 9000 to v2.90:
1. Re-Import the XML documents.
2. Upgrade to v2.90.
3. Export the Objects again.
SDK Connected Program Drivers
SDK Connected Program Drivers and C•CURE 9000 Upgrade

BEFORE UPGRADING C•CURE 9000: If you licensed any of the SDK Connected Program drivers with a
previous release, check the Software House web site (Home>Support>“Software House Connected“>
Compatibility Matrix http://www.swhouse.com/support/SWH_Connected_Compatibility_Matrix.aspx) to
confirm that your integration is compatible with v2.90 BEFORE YOU UPGRADE.
Contact the distributor of the Connected Program driver to get your C•CURE 9000 v2.90 compatible
driver.
NOTE: Client Auto-Update does not update clients with new versions of a Connected Program Driver
product; you must perform Client updates for these products manually at each client.
Uninstalling SDK Connected Program Drivers

If you have a Connected Program Integration from a previous release that you do not intend to upgrade
and wish to uninstall, you must uninstall it before you upgrade your C•CURE 9000 to v2.90. If you
upgrade to v2.90 and then try to uninstall, the uninstall may fail.
Installation of Version 2.90

Enable Microsoft Media Foundation Server
Ensure that Microsoft Windows Media Foundation Server is enabled in your Windows environment before
installing C•CURE 9000 v2.90. For more information on to enable this feature, check your Windows help
documentation.
SQL Privileges for Local System Account in a Workgroup

If you are installing C•CURE 9000 on a Workgroup system that already has SQL Server 2014/2016
Express/Full installed, you must assign the SQL Sysadmin privilege to the Windows account local system.
If you do not do this, the CrossFire Services do not start.
Server Requirements Failure Message during Installation on Windows Servers

If IIS Extension files are not installed on your server system, the Installer reports that IIS is not installed.
You can safely continue installing and install the IIS Extension Files after the C•CURE 9000 install is
complete.
Installation Completes on Longer-than-15-Character Name Computer but Clients Do Not Connect

If you install C•CURE 9000 on a computer with a name longer than 15 characters, the following error
message displays: “The NetBIOS name is limited to 15 characters”. You can continue the install, but the
system name will be truncated. Consequently, Clients will be unable to log in to C•CURE 9000.
Workaround: Change the computer name to match the 15-character truncated version.
27
Services/Server Components Manual Start
After installing C•CURE 9000 v2.90, you must run the Server Configuration Application (Start>All
Programs>Tyco>Server Configuration Application) one time to start the CrossFire Framework and
CrossFire Server Component Framework Services. You cannot access C•CURE 9000 functions until you
start these services.
You also need to enable and start the Extension Service (Hardware Driver) for each type of controller,
video, or network component to be used on the server. The Extension Services [Drivers] are not
automatically started by default because enabling drivers for devices that are not used can affect system
performance. In addition, starting them automatically would trigger a download for apC and iSTAR
controllers. You can view the status of these drivers from Windows Services, but should not configure
them to start automatically from there; startup is managed by the CrossFire Server Component
Framework Service.
For more information, refer to the C•CURE 9000 v2.90 Installation and Upgrade Guide.
victor Temporary License Expiration and C•CURE 9000 Licensed Video Drivers
If you install a C•CURE 9000 + victor Unified system but do not obtain a permanent license for victor,
C•CURE 9000 Video drivers may stop working when the victor temporary license expires.
Workaround:
1. Either obtain a permanent victor license or remove the victor temporary license.
2. Edit, disable, and then save each Video Server on the C•CURE 9000 Administration Station.
3. Edit, enable, and save each Video Server to restore the connection with each server.
Installing C•CURE Go Web Service and C•CURE 9000 Web Client
IP Address Requirements for C•CURE Go Install

You should install the C•CURE Go Web Service application either on a system with a fixed IP address or
on a system that cannot switch from one IP address to another by a simple reboot. Since C•CURE Go
has no way of knowing that the IP address has changed, it cannot distinguish a server IP address change
from the service on the server stopping or the server being shut down.
IIS Version Prerequisite for C•CURE Go Install

An error is displayed on the C•CURE Go Web Service installation screen, not on the final prerequisite
review screen, if the IIS version for the C•CURE Go Web Service is incorrect.
Installing Language Pack for C•CURE Go and C•CURE 9000 Web Client
Install C•CURE Go Web Service and the C•CURE 9000 web-based client on a machine with C•CURE
9000 client and the C•CURE language pack to ensure that C•CURE Go and C•CURE 9000 web-based
client are translated.
C•CURE Go Web Service Installation Not Supported on MAS

C•CURE 9000 MAS systems running as IIS servers are not licensed for, and do not support, C•CURE Go
Web Service.
28
End of Release Note
The trademarks, logos, and service marks displayed on this document are registered in the United States [or other countries]. Any
misuse of the trademarks is strictly prohibited and Johnson Controls will aggressively enforce its intellectual property rights to the
fullest extent of the law, including pursuit of criminal prosecution wherever necessary. All trademarks not owned by Johnson
Controls are the property of their respective owners, and are used with permission or allowed under applicable laws.
Product offerings and specifications are subject to change without notice. Actual products may vary from photos. Not all products
include all features. Availability varies by region; contact your sales representative.
© 2023 Johnson Controls. All Rights Reserved.
29

2.90 C - CURE 9000 Release Note

Uploaded by

Copyright:

Available Formats

You might also like

2.90 C - CURE 9000 Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2.90 C - CURE 9000 Release Note

Uploaded by

Copyright:

Available Formats

C•CURE 9000 2.

March 2023 Document Number: 8200-1950-26

C•CURE 9000 web-based client

C•CURE Legacy Web

C•CURE 9000 Dashboard/Home Screen

Basic Authentication Login Throttling

Video Clip Management

Journal Volume Management

iSTAR Edge G2 Support

iSTAR Edge to iSTAR Edge G2 conversion tool

Supported Operating Systems, DBMS, and SQL Collations

Table 2: Microsoft DBMS

Table 3: SQL Server Collations Supported

Supported Browser and Mobile Operating Systems

Table 5: Redundancy and Disaster Recovery Software Supported

Stratus everRun Enterprise 7.4.2 7.4.2 7.7

Stratus everRun Extend Supported Supported Supported

Enterprise Considerations and Known Limitations

Using SQL Server Express with SAS Server L/M/N Upgrades

SAS and Licensing

Relation between SAS and its MAS

Upgrading MAS before its SAS

Synchronizing Journal before Upgrading from v2.30/2.30 R2/2.50 to v2.90

Upgrading SAS While Server Not Configured/Running Correctly May Fail

Converting a Standalone C•CURE 9000 System with UDFs to a v2.90 SAS

Uninstalling MAS with Server Management Application Open Causes Error

Application Layouts on MAS

Editing Global Operators

General Considerations and Known Limitations

Upgrading SiteServer appliances to C•CURE v2.90

DUO Two Factor Authentication

Windows Server Core

Windows 10 Operating System Support

Windows 2016 Operating System Support

64-Bit Operating System Support with C•CURE 9000 Client

SQL Database and Backup

Maximum Time for iSTAR Controller Certificate Signature Timeout

Creating an Encryption Key Passphrase After Installing C•CURE v2.90

apC Panel Limitations with Timed Actions

Scheduled Events on apC Door, Input, and Output Groups

apC Connected to a different server needs to be reset before Clearance download.

Requirement for Adding PIN-only Card from Personnel View

Using Escorted Access with Muster/De-muster

Offline Transactions Cause Host Occupancy Counts to be Unreliable on iSTARs

Aperio Doors Do Not Re-lock on Access Completion

Aperio Doors Lock/Unlock Limitations

Language Pack Upgrade and Repair Requirements

Language Pack Installation

Maps Backward Compatibility

Delay of 5-10 seconds when performing ID Scanner

AssureID Scan SDK

C•CURE Kiosk does not login after initial install

Direct Show capabilities after installation

User-Defined Fields in Visitor Management after installing the Language Pack

C•CURE Web Client (Legacy)

C•CURE Web Client (Legacy) requires Adobe for download

C•CURE Web Client Classic

iSTAR Ultra Video