RN-00001 1

C•CURE 9000 Security System Version 2.10 Release Notes – July 2012 This Release Notes file provides important information about C•CURE 9000 Version 2.10. Please read this file before installing C•CURE 9000. Contents

1. DVD Contents 2. New Features and Enhancements 3. Supported Operating Systems and DBMS 4. Configuring IIS for C•CURE 9000 Web Service, C•CURE Mobile, and Auto-Update 5. Enterprise Architecture Considerations 6. Considerations and Known Limitations 7. Compatibility of Third Party Hardware 8. Compatibility of Third Party Software 9. Firmware Versions for Tyco Security Products Controllers 10. SPARs Fixed 11. Upgrading to Version 2.10 12. Installation of Version 2.10 For a list of supported operating systems, see Section 3.

IMPORTANT: Read Before Upgrading to C•CURE 9000 Version 2.10 or Repairing/Uninstalling • Beginning with CCURE 9000 v2.10, the Intellex API will no longer support Policy Manager. Video and

alarms will not work properly when you upgrade to v2.10 if your Intellex application utilizes Policy Manager. You must turn off Policy Manager as detailed below:

1. Go to Setup>Port Addresses on the Intellex unit. 2. Change Managed to Stand-Alone. 3. Reboot the Intellex.

• If you do not stop the services in the following list before upgrading C•CURE 9000 to v2.10 (or repairing or uninstalling the software), an error message listing the open services displays and terminates the C•CURE 9000 upgrade, repair, or uninstall.

o All the CrossFire services o C•CURE 9000-related services: American Dynamics Intellex Server Component, Software

House AutoUpdate Installer, Software House AutoUpdate Service, stunnel, and TycoESS. You turn off the services as detailed below:

1. Click Start>Control Panel>Administrative Tools>Services. 2. Check the status of the relevant services in the list, and if a service has a Status of Started,

right-click the service and click Stop on the context menu that displays. (The service stops, indicated by the dynamic Service Control message box that opens and quickly closes.) NOTE: When you click Stop for the CrossFire Framework Service, a Stop Other Services dialog box appears saying that stopping the Framework Service also stops the other open lower-level CrossFire services and asking if you want to do this.

3. Click Yes. 4. Once all the necessary services have been stopped, close the Services and Administrative

Tools windows and start the C•CURE 9000 upgrade, repair, or uninstall process.

2 RN-00001

1. DVD Contents This DVD includes the C•CURE 9000 software, the latest firmware, and any special files referred to in these Release Notes:

• C•CURE 9000 Install components. The installation program is in the root of the DVD. • English folder with Manuals and Reader folders. The Manuals folder contains PDF (Portable

Document Format) files for the manuals. The Reader folder contains the installation file for Adobe Acrobat® Reader 10.01.

• Web Client folder containing the installation program for the Web Client. • HostIDUtil folder containing the Host ID Utility. • SQL Express folder containing the installation program for SQL Express. • ThirdParty folder containing device drivers. • Certificates folder containing Software House certificates for encryption. • ISSSetupPrerequisites containing prerequisite software for C•CURE 9000 and Microsoft IIS. • 9000_2_10_Relnotes_RN00001.pdf - the C•CURE 9000 v2.10 release notes file. • LanguagePack folder containing the v2.10 Language Pack. The v2.10 Language Pack, included with

this release of C•CURE 9000 v2.10, can be installed with C•CURE 9000 v2.10 or higher and includes PDF (Portable Document Format) files for the manuals.

2. New Features and Enhancements iSTAR Global Antipassback – C•CURE 9000 now allows an Area to cross multiple iSTAR clusters to enforce antipassback decisions. The cluster master controller makes the antipassback decision when it owns the card being swiped. Otherwise, the cluster master controller asks the C•CURE 9000 Server to request an antipassback decision from the cluster master controller that does own the card. (For more information, see Chapter 1 “iSTAR Cluster Areas” in the C•CURE 9000 Area and Zones Guide.) Area Lockout – C•CURE 9000 now allows you to configure an Area in which the presence of Personnel, monitored by the Area's entry and exit Readers, locks these cardholders out of a different designated Area/Group of Areas for a specified period of time. A facility with multiple laboratories or highly sensitive manufacturing environments might require this functionality to prevent cross-contamination and a resultant loss of productivity and/or human injury or life. (For more information, see Chapter 1 “iSTAR Cluster Areas” in the C•CURE 9000 Area and Zones Guide.) Area De-muster – C•CURE 9000 now allows you to designate a Mustering Area where personnel can assemble in case of emergency. Once the emergency has passed, you can manually de-muster these personnel to a configured de-muster Area. If a de-muster Area has not been designated, at de-muster time any Personnel in the Mustering Area will be graced and can go to any Area in the facility. (For more information, see Chapter 1 “iSTAR Cluster Areas” in the C•CURE 9000 Area and Zones Guide.) Report Server Service –C•CURE 9000 now has its Report system implemented as a Windows service that can run in either 64-bit or 32-bit mode. The Report Service executes Reports that are either run on the Server by an Operator or configured to run as an Event Action. (For more information, see Chapter 6 “Reporting” in the C•CURE 9000 Data Views Guide.)

RN-00001 3

C•CURE 9000 Server as a 64-bit application – C•CURE 9000 server now runs as a 64-bit application if installed on a supported system with a Microsoft 64-bit operating system (Windows 7 or Windows Server 2008 R2). The following components can run as 64-bit applications:

• C•CURE 9000 Server • Server Configuration Application • C•CURE 9000 License program • Software House CrossFire iSTAR Driver Service • Software House CrossFire Report Server • Software House CrossFire Import Watcher

NOTE: All of the above programs run as 32-bit applications when in a 32-bit environment. In addition, C•CURE 9000 client programs (Administration Client and Monitoring Station), as well as most driver services, remain 32-bit applications. Support for Active Directory 2008 – C•CURE 9000 now supports Active Directory Services 2008—the Windows Server 2008/Windows Server 2008 R2 version of Active Directory. C•CURE 9000 supports data import of Active Directory 2008 content as an LDAP Import source. (For more information, see Chapter 3 “LDAP Data Import” in the C•CURE 9000 Software Configuration Guide.) Customer Field Label Editor – C•CURE 9000 now includes a Customer Field Labels Editor that allows you to change the labels of fields on the Personnel Editor Customer Fields and Customer Extended tabs. (The new editor, accessed from the Options and Tools pane, replaces the functionality of the former Design button on the Personnel Customer Fields tab.) Any field labels you customize are stored in the C•CURE 9000 database and preserved when C•CURE 9000 is updated or upgraded. (For more information, see Chapter 11 “Changing the Labels on Customer Fields” in the C•CURE 9000 System Maintenance Guide.) Server Configuration Application – C•CURE 9000 now provides a new Server Configuration Application. This program allows you to enable, start, and stop C•CURE 9000 services; enable Application and Network Settings; and access C•CURE 9000 Licensing. (For more information, see the C•CURE 9000 Server Configuration Application Guide.) Save Dynamic View contents as an Excel file – C•CURE 9000 now provides a button on the Dynamic View toolbar that allows you to save the data displayed in the current Dynamic View as a Microsoft Excel (.XLSX) file. (For more information, see Chapter 3 “Dynamic Views” in the C•CURE 9000 Data Views Guide.) Generate a Unique Random Card Number – C•CURE 9000 now provides a button on the Personnel Editor Credential tab that allows you to generate a unique random card number for an access credential. This card number contains up to the maximum number of digits for the CHUID format chosen for the credential. (For more information, see Chapter 2 “Personnel” in the C•CURE 9000 Personnel Configuration Guide.) Configure Application Layouts to Open in Separate Monitoring Station Instances – C•CURE 9000 now provides an option on the Operator Editor Layout tab that lets you configure an Operator's Application Layouts to open in separate instances of the Monitoring Station—potentially improving performance. For example, if an Operator has nine Application Layouts, you can configure these to open in three Monitor Groups. Then when the Operator starts the Monitoring Station, three Monitoring Station instances open. Each Monitoring Station displays the Application Layouts assigned to it. If the Operator's system has multiple

4 RN-00001

displays, each instance of the Monitoring Station can open on a different display. (For more information, see Chapter 10 “Operator” in the C•CURE 9000 Software Configuration Guide. Journal Query Assistant – C•CURE 9000 now allows you to query “Object Changed” states–such as ‘Door Forced’, ‘Door Held’, and ‘Door Open’– in the Journal log , as well as allowing you to query the specific Objects reporting the change. (For more information, see Chapter 6 “Historical Tracking of System Activity” in the C•CURE 9000 System Maintenance Guide.) Acknowledge All and Silence All buttons – C•CURE 9000 now provides optional buttons you can add to the Monitoring Station Event Viewer Quick Action Toolbar that allow an Operator to acknowledge/ silence all Events with one click. You can add these buttons when you drop an Event Viewer into an Application Layout. (For more information, see Chapter 2 “Application Layout” in the C•CURE 9000 Data Views Guide.) Reload Backup Utility – The functionality for retrieving Audit/Journal Log backup files that were deleted from the C•CURE 9000 Backup directory and then archived elsewhere has been moved from the Reload Log Backup tab in the Server Management Application to a separate utility. (For more information, see the C•CURE 9000 Server Configuration Application Guide.)

3. Supported Operating Systems and DBMS C•CURE 9000 does not support the 64-bit editions of Windows XP Professional, Windows Vista, or Windows 2003 Server. There are also limitations on full client support for 64-bit. See Table 1 for Operating System support information and Table 2 for DBMS information. Table 1: Microsoft Operating Systems for Server and Client

Standalone Series L/M/N Supported Version Server or Client Windows 7 Professional (Recommended) 32-bit, 64-bit, SP1 or later server or client Windows 7 Enterprise (Recommended) 32-bit, 64-bit, SP1 or later server or client Windows 2003 Server Standard 32-bit,SP2 or later server or client Windows 2003 Server Enterprise 32-bit, SP2 or later server or client Windows XP Professional 32-bit, SP3 or later server or client Windows Vista Business 32-bit, SP2 or later client only Windows Vista Enterprise 32-bit, SP2 or later client only Windows Server 2008 Standard 32-bit, SP1 or later server only Windows Server 2008 Enterprise 32-bit, SP1 or later server only Windows Server 2008 R2 Standard (Recommended) 64-bit, SP1 or later server only Windows Server 2008 R2 Enterprise (Recommended) 64-bit, SP1 or later server only Standalone Series P/Q/R/R+/S Supported Version Server or Client Windows 2003 Server Enterprise 32-bit, SP2 or later server or client Windows Server 2008 Standard 32-bit, SP1 or later server only Windows Server 2008 Enterprise 32-bit, SP1 or later server only Windows Server 2008 R2 Standard (Recommended) 64-bit, SP1 or later server only Windows Server 2008 R2 Enterprise (Recommended) 64-bit, SP1 or later server only

RN-00001 5

SAS Series L/M/N Supported Version Server or Client Windows 7 Professional (Recommended) 32-bit, 64-bit, SP1 or later server or client Windows 7 Enterprise (Recommended) 32-bit, 64-bit, SP1 or later server or client Windows 2003 Server Standard 32-bit, SP2 or later server or client Windows 2003 Server Enterprise 32-bit, SP2 or later server or client Windows XP Professional 32-bit, SP3 or later server or client Windows Vista Business 32-bit, SP2 or later client only Windows Vista Enterprise 32-bit, SP2 or later client only Windows Server 2008 Standard 32-bit, SP1 or later server only Windows Server 2008 Enterprise 32-bit, SP1 or later server only Windows Server 2008 R2 Standard (Recommended) 64-bit, SP1 or later server only Windows Server 2008 R2 Enterprise (Recommended) 64-bit, SP1 or later server only SAS Series P/Q/R/R+/S Supported Version Server or Client Windows 2003 Server Standard 32-bit, SP2 or later server or client Windows 2003 Server Enterprise 32-bit, SP2 or later server or client Windows Server 2008 Standard 32-bit, SP1 or later server only Windows Server 2008 Enterprise 32-bit, SP1 or later server only Windows Server 2008 R2 Standard (Recommended) 64-bit, SP1 or later server only Windows Server 2008 R2 Enterprise (Recommended) 64-bit, SP1 or later server only MAS Server Supported Version Server or Client Windows Server 2008 R2 Standard 64-bit, SP1 or later server only Windows Server 2008 R2 Enterprise 64-bit, SP1 or later server only MAS Client Supported Version Server or Client Windows 7 Professional 32-bit, 64-bit, SP1 or later client only Windows 7 Enterprise 32-bit, 64-bit, SP1 or later client only Windows 2003 Server Standard 32-bit, SP2 or later client only Windows 2003 Server Enterprise 32-bit, SP2 or later client only Windows XP Professional 32-bit, SP3 or later client only Windows Vista Business 32-bit, SP2 or later client only Windows Vista Enterprise 32-bit, SP2 or later client only

Table 2: Microsoft DBMS Server Series Standalone L/M/N and Client Workstation Supported Version SQL Server 2008 R2 Express (Recommended) 10.50.1600.1 RTM (32- and 64-bit) SQL Server 2008 R2 Standard (Recommended) 10.50.1600.1 (32- and 64-bit) SQL Server 2008 R2 Enterprise (Recommended) 10.50.1600.1 (32- and 64-bit) SQL Server 2008 Express 10.0.4000 SP2 (32- and 64-bit) SQL Server 2008 Standard 10.0.4000 SP2 (32- and 64-bit) SQL Server 2008 Enterprise 10.0.4000 SP2 (32- and 64-bit) SQL Server 2005 Express 9.00.4912 SP4 (32-bit) SQL Server 2005 Standard 9.00.4912 SP4 (32-bit) SQL Server 2005 Enterprise 9.00.4912 SP4 (32-bit)

6 RN-00001

Server Series Standalone P/Q/R/R+/S & SAS Server Series L/M/N Supported Version* SQL Server 2008 R2 Standard (Recommended) 10.50.1600.1 (32- and 64-bit) SQL Server 2008 R2 Enterprise (Recommended) 10.50.1600.1 (32- and 64-bit) SQL Server 2008 Standard 10.0.4000 SP2 (32- and 64-bit) SQL Server 2008 Enterprise 10.0.4000 SP2 (32- and 64-bit) SQL Server 2005 Standard 9.00. 4912 SP4 (32-bit) SQL Server 2005 Enterprise 9.00. 4912 SP4 (32-bit) * SQL Server Express (2005/2008/2008 R2) is supported on upgrades of SAS Servers Series L/M/N. However, Software House recommends using full SQL Server Standard/Enterprise with C•CURE 9000 v2.10 for the best performance. SAS Server Series P/Q/R/R+/S Supported Version SQL Server 2008 R2 Standard (Recommended) 10.50.1600 (32- and 64-bit) SQL Server 2008 R2 Enterprise (Recommended) 10.50.1600 (32- and 64-bit) SQL Server 2008 Standard 10.0.4000 SP2 (32- and 64-bit) SQL Server 2008 Enterprise 10.0.4000 SP2 (32- and 64-bit) SQL Server 2005 Standard 9.00. 4912 SP4 (32-bit) SQL Server 2005 Enterprise 9.00. 4912 SP4 (32-bit) MAS Server Supported Version SQL Server 2008 R2 Standard 10.50.1600.1 (64-bit) SQL Server 2008 R2 Enterprise 10.50.1600.1 (64-bit) NOTE: C•CURE 9000 version 2.10 does not support Oracle as a DBMS.

4. Configuring IIS for C•CURE 9000 Web Service, C•CURE Mobile, and Auto Update You must use the IIS Repair Utility to configure IIS for the following C•CURE 9000 components: Web Service, C•CURE Mobile, and Auto-Update. To use the utility:

1. Find the utility in the following directory: C:\Program Files (x86)\Tyco\CrossFire\tools. 2. To have the proper permissions to configure IIS on Windows 7, Windows Server 2008, and

Windows Server 2008 R2, run the utility as an administrator, as follows. a. Right-click the IIS Repair Utility application. b. On the context menu, click Run as Administrator.

3. On the IIS Repair Utility for CCURE dialog box, select either or both of the component options in the IIS Components box, depending on which C•CURE 9000 components you are using:

a. SWH Auto Update – for Client Auto-Update b. CCURE 9000 Web Service – for Web Service and/or C•CURE Mobile

4. Click the Repair IIS Components button.

5. Enterprise Architecture Considerations 5.1 Installation and Upgrade Issues 5.1.1 Error Message during SAS Upgrade a from C•CURE 9000 v2.02 R2 to v2.10 When you are upgrading a v2.02 R2 SAS on a Windows 2008 OS to C•CURE 9000 v2.10, an error message displays saying that the "Host Process for Windows Services stopped working and was closed". You can safely ignore this message and let the upgrade continue since the problem is fixed later on in the upgrade process.

RN-00001 7

5.1.2 Using SQL Server Express with SAS Server L/M/N Upgrades The use of SQL Server Express (2005/2008/2008 R2) is supported for upgrades of SAS Servers Series L/M/N. However, for the best performance, Software House recommends using full SQL Server Standard/Enterprise with C•CURE 9000 v2.10. 5.1.3 A SAS Cannot Be Removed Once Installed You cannot remove a SAS from a MAS once the SAS has been installed into the Enterprise Architecture System. 5.1.4 SAS and Licensing Once a SAS is successfully licensed and installed, removing the SAS license prevents the SAS from being able to start. Therefore, there is no way that a SAS can be changed back into a Standalone C•CURE 9000 system. 5.1.5 Relation between a SAS and its MAS There is no way to point an existing SAS at a new MAS. Consequently, it is critical to perform a system backup of the MAS after each new SAS is added. 5.1.6 Required Hard Drive Space for Upgrading Enterprise Architecture Systems Upgrading the MAS and SAS requires a significant amount of hard drive space. Please ensure that SQL Server has at least 100G of available hard drive before upgrading to v2.10. 5.1.7 Upgrading a MAS before its SAS When you are upgrading your MAS and SAS systems, you must first upgrade the MAS and then upgrade the SAS systems to the same version. 5.1.8 Synchronizing the Journal before Upgrading from v2.01 or 2.02 R2 to v2.10 Prior to upgrading your MAS and SAS systems from v2.01 or 2.02 R2 to v2.10, you should verify that any scheduled Journal Synchronization from SAS to MAS has been completed. Caution: The Server Component Framework should be shut down while performing this last synchronization. If you do not perform journal synchronization prior to upgrading to v2.10, unsynchronized journal messages from v2.01 or 2.02 R2 will never sync to the MAS. (For more information about the Application Server Synchronization tab, see Chapter 10 in the Enterprise Architecture Guide.) 5.1.9 Converting a C•CURE 9000 to a v2.10 SAS You can convert only a single Standalone C•CURE 9000 v2.01 or v2.02 R2 to be a v2.10 SAS. 5.1.10 Converting a C•CURE 9000 with UDFs to a v2.10 SAS You cannot automatically convert a C•CURE 9000 v2.01 or v2.02 R2 system with User Defined Fields (UDFs) to a v2.10 SAS. Contact the Software House Customer Support Center for the necessary procedure. 5.2 Application Layouts on the MAS You may use the three pre-defined Application Layouts (Default View 1, Default View 2, and Default Application Layout) on the MAS, but should never edit them. Consequently, Software House recommends that you create at least one new Application Layout on the MAS that you assign to all Operators to avoid the need to edit the pre-defined Layouts.

8 RN-00001

5.3 Editing Global Operators You should not edit Global Operators if you are logged into the system as a Local Operator because you will not be able to save Application Layouts correctly. 5.4 Making a SAS Operator Global If a local SAS Operator is currently logged in or was logged in recently and you need to make this Operator Global by changing his/her Partition to Global, the following will take place:

1. After you (acting as a different, high-privileged Operator) make the local SAS Operator Global, this Operator will receive a synchronization conflict and not be able to successfully be made Global.

2. This Operator whom you attempted to make global will neither appear to be Global, nor be able to log in.

3. At this point, changing the Operator’s Partition to Global a second time will succeed in making him/her Global. (Be sure to make this change while logged into the SAS.)

5.5 Importing Considerations

• For performance reasons, imports should take place on the server that owns that Object’s partition. For 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 take up a significant amount of memory during replication. For example, 3000 personnel with 500KB Documents for each personnel record equals 1.5GB of memory to process. For performance reasons, Software House recommends that you keep imports down to a total of 400MB, including both Image and Document data.

5.6 Replication of Images The Enterprise architecture only supports replication of personnel and badge images if the images are 3.75 MB or smaller. Therefore, be sure all your images are smaller than 3.75 MB. If an image larger than 3.75 MB is encountered, no further images will be replicated until that image is removed or resized.

6. Considerations and Known Limitations NOTE: Maps and Intellex 5.0 Video are supported on Client and Server installations on all operating systems even when Data Execution Prevention (DEP) is enabled. If you previously turned DEP off for all programs, you should turn it back on as follows: • For Windows 7, Vista, and Windows 2008/2008 R2 operating systems –

1. From the Start menu, select All Programs, then Accessories, right-click on the Command Prompt shortcut, and choose Run as Administrator.

2. At the Command Prompt, use the following command to enable DEP: bcdedit /set nx OptOut (Be sure to include the spaces when typing the command.)

• For the Windows XP operating system –

o No command; select Computer>Properties>Advanced>Performance>DEP>Turn on DEP for all programs and services except those I select

RN-00001 9

6.1 Vista Operating System Support C•CURE 9000 supports client-only installation on Vista Business (Service Pack 2) and Vista Enterprise (Service Pack 2). The following limitations exist when running a C•CURE 9000 Client on the Vista operating system: • C•CURE 9000 Client Installation only. Server is not supported. • 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 Vista. You

can configure the readers using a Windows XP system as a workaround. 6.2 Windows 7 Operating System Support C•CURE 9000 supports client and server installation on Windows 7 Standard (Service Pack 1) and Enterprise (Service Pack 1). The following limitations exist when running a C•CURE 9000 Client on the Windows 7 operating system: • IP Cameras AXIS 2400/2401 2.33 - Not supported. • 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 7.

You can configure the readers using a Windows XP system as a workaround. 6.3 Windows Server 2008/2008 R2 Operating System Support C•CURE 9000 supports server-only installation on Windows Server 2008 Standard and Enterprise (Service Pack 1) and 2008 R2 Standard and Enterprise (Service Pack 1). The following limitations exist when running a C•CURE 9000 server on the Windows Server 2008 operating system: • IP Cameras AXIS 2400/2401 2.33 - Not supported. • 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

Server 2008. You can configure the readers using a Windows XP system as a workaround. 6.4 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. 6.5 SQL Database and Backup The hard drive partition on which the C•CURE 9000 database is installed should have a minimum of 80 GB free space. 6.6 ISC Controllers 6.6.1 C•CURE 9000 requires ISC Version 2.02 CPU chip (U-18) C•CURE 9000 requires that ISC Controllers have the Version 2.02 CPU (chip U-18 on the CPU board), using at least version 4.05 firmware. Controllers with an older version of this chip will behave in an unpredictable manner, such as points (inputs) activating or deactivating unreliably.

10 RN-00001

6.6.2 Host-based ISC Controller Triggers Activate Output Action, Regardless of Schedule If an ISC state change meets all of the following criteria, then a Host-based ISC Controller Trigger would activate an Output action, regardless of schedule: • ISC state change occurs (e.g. input activation). • State change triggers a host-based action (not controller-based — for example, input / output linkage). • The host-based action triggers a direct controller-based state change (i.e., not via an event). • The action is on a non-Always schedule. This trigger only works if you assign the Always Schedule. The workaround is to configure the initial state change to trigger a host event, not an action. The host event can then be used to trigger an action based on any schedule. 6.6.3 ISC Trigger Cannot Activate iSTAR Output C•CURE 9000 no longer allows you to configure a Trigger on an ISC Input to activate an iSTAR Output. The correct way to configure this functionality is to create a Trigger on an ISC Input to activate a host Event, and have the Event activate the iSTAR Output. 6.6.4 ISC Input Trigger to Unlock /then Relock a Door Some Trigger actions on an ISC Input are not able to relock a door after unlocking it. Using the Trigger ISC Input HW Status: Input Abnormal>Unlock door with the Trigger ISC Input HW Status: Normal>Lock door does not relock the door. Also, using the Trigger ISC Input HW Status: Input Abnormal>Activate Output does not work with a door strike. Instead, to configure an ISC Input (such as a button) to unlock a door, then relock it, use the following Trigger: ISC Input HW Status: Abnormal>Action: Door Unlock Track Link Mode. This mode tracks the state of the Input to relock the door. Alternatively, using ISC Input HW Status: Input Abnormal>Activate Event with an Event that does not require acknowledgement will toggle Active and Inactive when the ISC Input is toggled Abnormal and Normal. 6.6.5 ISC Door Momentary Unlock The Momentary Unlock Manual Action can only be performed on one ISC Door at a time. If you right-click on more than one Door in a list of ISC Doors, the Momentary Unlock action is not available. 6.7 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 iSTAR Event is configured with the Download to compatible controller option, the Event will not activate. Either of the following alternatives will work: • Configure the apC Door or Input Trigger to activate a host-based Event that in turn activates the iSTAR

Event. -or-

• Do not select the Download to compatible controller option for the iSTAR Event.

6.8 Door Trigger Property Double Swipe Status Cannot Activate an Output If you configure an iSTAR Door Trigger using the property Double Swipe Status and set the Action to Activate Output, the Output is not activated by the Trigger. To activate the Output, you need to create an event that activates the Output, and then configure the Trigger to activate that Event. 6.9 Editing an 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

RN-00001 11

stays active. To change the trigger so the Armed status value for the trigger updates properly, you need to delete the trigger and recreate it with the new value for Armed status. 6.10 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. 6.11 Event Activation Delay Time and/or Minimum Activation Time Ignored if apC is Offline The apC in offline mode does not support Activation Delay Time and Minimum Activation Time. If you configure an Event that specifies an Activation Delay Time and/or a Minimum Activation Time, and the Event is activated causing an Action, the apC will still perform the action immediately while the apC is offline. 6.12 Manual Actions on Groups with ISC and iSTAR/apC Objects Leave Some Objects Active Manual Actions performed on groups of objects that include both ISC objects and iSTAR/apC objects can leave some of the objects active with no active cause when these manual actions are cancelled. This is because ISC manual actions are not handled in the same manner as iSTAR and apC Manual Actions. Mixing them in a Group and performing a Manual Action on the Group gives various results. To avoid this problem, do not define Groups with both ISC and iSTAR/apC objects. Or if you define such Groups, do not perform Manual Actions on those Groups. 6.13 Journal Caused to Not Write Messages If your C•CURE 9000 is running on either a Windows 2003 Server or a Windows XP Server and has a NIC card with a MAC address with the left-most digits greater than or equal to 0x80, the Journal will not be able to write messages.

Prerequisites: • If your system is running on Windows Server 2003—before installing C•CURE 9000, you must do the

following: 1. Download and apply a hot fix from Microsoft

(see http://support.microsoft.com/kb/981080). 2. Check the Registry Key called EnableUuidGenSupport to ensure that it has a DWORD with a

value of 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc. If it does not, add it. • If your system is running on Windows XP—you must disable your current NIC and add a NIC to the

system that has a MAC address with the left-most digits less than 0x80 (example: 00-13-72-A7-7E-0F).

6.14 Monitoring Station and Area Status If you had created a default Dynamic View for “Area” in C•CURE 9000 version 2.01 or 2.02 R2, you should recreate this as an “iSTAR Area” Dynamic View when you upgrade to version 2.10. Otherwise, the status list for Areas in the Monitoring Station may not include the correct columns. 6.15 Personnel Import from XML Software House recommends that you not use Card Number (for matching only) for import matching if you are importing an XML file whose records have more than one credential assigned.

7. Compatibility of Third Party Hardware The following list includes some of the third-party products compatible with C•CURE 9000 version 2.10.

12 RN-00001

Table 3: Third-Party Hardware Equipment Type Vendor Model Latest Supported Version ______________________________________________________________________________ Digital Video American Dynamics Intellex 5.0 Management System Network Video American Dynamics *VideoEdge Recorders * VideoEdge is available as an optional Connected Program Integration. See the Software House web site: http://www.swhouse.com/support/SWH_Connected_Compatibility_Matrix.aspx __________________________________________________________________________________ Bioscrypt Bioscrypt V-SMART I CLASS 7.5 Readers Soft. 5.50 V-STATION I CLASS 7.30 Soft. 5.51 __________________________________________________________________________________ Schlage Electronic Schlage AD-400/401 AD.A.13 Locks AD-300/301 AD.A.13 __________________________________________________________________________________ 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 Watchport/V2 301-9010-01 2.55 Video Associates VA – 3 USB Camera 7.7 Videology 24C7.38USB 1.1.115 20K758USB __________________________________________________________________________________ IP Cameras AXIS 2400/2401 2.33 __________________________________________________________________________________ Badging Printers Nisca 5350 5.12 Fargo HPD 600 2.1.3 Fargo DTC 400 2.3.2.1 Fargo DTC 400e 1.3.05 Fargo DTC 550 2.2.2.3 Fargo HDP 5000 3.3.3.0 Fargo DCT4500 1.0.1.31 Magicard Tango 2/2e 1.6.1.0 Magicard Rio 2/2e 1.6.1.0 __________________________________________________________________________________ Smart Card Device SCM Microsystems SWH-SCM-SDI-010 V5.34 SCM Microsystems SWH-SCM-SDI-011 V5.34 Advanced Card Systems ACR-120 1.0.20_A __________________________________________________________________________________ C•CURE Mobile Datastrip DSV 11SG 1.0.63.42 __________________________________________________________________________________

8. Compatibility of Third Party Software The following list includes some of the third-party software compatible with C•CURE 9000 version 2.10.

RN-00001 13

Table 4: Third-Party Software Company Product Latest Supported Version __________________________________________________________________________________ Data Dynamics Active Reports 5.3.1436.2 __________________________________________________________________________________ American Dynamics Intellex API 5.01 *VideoEdge API * VideoEdge is available as an optional Connected Program Integration. See the Software House web site: http://www.swhouse.com/support/SWH_Connected_Compatibility_Matrix.aspx __________________________________________________________________________________ EMC AutoStart Version 5.4.0 HF-cumu Replistor Version 6.4 SP2 HF5 __________________________________________________________________________________ Flexera FLEXNet Publisher 11.9.1 __________________________________________________________________________________ LEAD Technologies LEADTOOLS 14.5.0.68 __________________________________________________________________________________ Infragistics Infragistics 11.1 __________________________________________________________________________________ Microsoft .NET 4.0 3.5 required for certain third-party components Windows Installer 4.5 MFC Runtime 8.0 SP1, 9.0 SP1, and 10.0 SP1 Silverlight 5.0.61118.0 __________________________________________________________________________________ Acresso Software InstallShield Version 2010 SP1 __________________________________________________________________________________ Sequiter Inc CodeBase 6.5 __________________________________________________________________________________ The OpenSSL Project OpenSSL 0.9.8g __________________________________________________________________________________

9. Firmware Versions for Tyco Security Products Controllers The following list includes the firmware versions for the controllers for C•CURE 9000 version 2.10. Table 5: Firmware for Tyco Security Products Controllers Controller Latest Supported Version __________________________________________________________________________________ iSTAR Classic 4.4.C __________________________________________________________________________________ iSTAR Edge, Pro, eX 5.1.7 __________________________________________________________________________________ ISC 4.1 __________________________________________________________________________________ apC, apC/8x, apC/L x.7ZF __________________________________________________________________________________

10. SPARs Fixed SPAR # 25814 – The confirmation message that appears on the Log Volume Management dialog box when you select the ‘Delete Selected Volumes From Database’ option has been reworded for clarity. SPAR # 25823 – The C•CURE 9000 Repair Install now prompts for IIS appropriately, in the same way as a new Install.

14 RN-00001

SPAR # 25860 – Maps now load as quickly for viewing by an operator with limited privileges as for an operator with full privileges. SPAR # 26158 – When you create an Event template, the options and actions you select and save are now being kept and reappear correctly when you re-open the template. SPAR # 26844 – Admit and Reject messages translated in the MUI Editor now display in the correct translated language at the Monitoring Station. SPAR # 26984 – On partitioned systems, reports that sort by partition name no longer return an error. SPAR # 26985 – C•CURE 9000 no longer allows users to create user-defined fields with the same names as existing database fields, thus resolving potential problems with templates. SPAR # 27663 – The system now properly prevents duplicate Event Actions from being imported. SPAR # 27734 – Reports and queries now display all door and schedule pairs associated with a clearance, including doors from door groups. SPAR # 27836 – When an operator's privilege is disabled, the system no longer generates an error indicating that the operator record was disabled. SPAR # 27911 – Personnel imports no longer fail if the database includes user-defined fields that were named using SQL reserved keywords, such as ‘Check’. SPAR # 28335 – The Advanced tab for Quick Search now includes a scroll bar if the queries list is longer than the window space can display at one time. SPAR # 28458 – The functioning of the ODBC Import time stamp has been improved. SPAR # 28462 – You are now able to successfully run the ‘Valid Admit’ or ‘Door Alarm’ reports without receiving any errors. SPAR # 28515 – The new badge print date no longer gets incorrectly applied to a previous credential record when you add a new credential to a personnel record that already has one credential with an assigned badge layout, assign a badge layout to the new credential, and then print the new badge. SPAR # 28643 – The system now checks to make sure that the Windows user account configured to run CrossFire has full privileges, ‘System All’. If not, the system displays an informative error message and then shuts down. This prevents unstable and unpredictable behavior. SPAR # 28687 – A new system variable in the Monitoring section, Skip Old Activity Messages, defines the number of hours that can elapse between the time a message was generated and the time it was received by the Monitoring Station; this prevents messages from hardware panels generated before the specified time interval from displaying on the Monitoring Station after the Cross Fire server has rebooted and reconnected to the hardware. SPAR # 28715 –Controller status no longer displays as ‘online’ immediately after driver startup before the controllers are actually communicating; the status now displays as ‘unknown’ until the controllers connect or lose communications. SPAR # 28929 –Startup time for systems with a large number of iSTAR controllers has been improved. SPAR # 28931 – Running a Repair on a SAS that was renamed and its IP address reassigned no longer creates a new SAS on the MAS, abandoning the original SAS. Instead the Repair correctly updates the SAS’s name, IP address, and URL. SPAR # 28935 – The system now prevents bad XML (non-printable) characters from being stored in database records. SPAR # 28947 – Using the Add or Remove Buttons menu to change the display of the Function buttons on the C•CURE 9000 Administration Station Navigation pane now works correctly. SPAR # 30001 –The error messages that display in the Window System Event Log and the C•CURE 9000 journal when a C•CURE 9000 system exceeds its licensed capacities have been reworded for clarity. SPAR # 41233 – Double-byte characters no longer display as question marks in exported reports. SPAR # 41873 – Intrusion Zone arm/disarm status changes, such as 'Mode Changed Method' changed from 'Card' to 'Event', are no longer tracked in the Audit Log— inappropriately.

RN-00001 15

11. Upgrading to Version 2.10 The C•CURE 9000 Installation and Upgrade Guide includes step-by-step instructions for upgrading your C•CURE 9000 system. The upgrade chapter explains the steps you need to take prior to upgrading, the database updates that are performed when you upgrade, and the tasks you need to perform after the upgrade is completed. Please refer to the C•CURE 9000 Installation and Upgrade Guide for more information. CAUTION: Before upgrading to C•CURE 9000 v2.10, see the Important Note on Page 1 of this Release Notes file. You can upgrade to C•CURE 9000 v2.10 directly from the following earlier versions:

• V2.01 • V2.02 R2

NOTE: If you are using any of the C•CURE 9000 components—Web Service, C•CURE Mobile, or Auto-Update, see Section 4 in these release notes. 11.1 Language Pack Upgrade for C•CURE 9000 v2.10 When upgrading from the C•CURE 9000 v2.02 R2 Language Pack, the installation must temporarily disable the network adapter. A dialog box appears stating the following: “In order to properly upgrade the installed product, the installation must temporarily disable the

network adapter. It will be re-enabled automatically. Do you want to proceed? Yes/No” • Click Yes to continue the upgrade process. The network adapter is automatically re-enabled when

the installation completes. - or -

• Click No to cancel the upgrade.

12. Installation of Version 2.10 NOTE: If you are using any of the C•CURE 9000 components—Web Service, C•CURE Mobile, or Auto-Update, see Section 4 in these release notes. 12.1 Microsoft Powershell 1.0 You must manually install Microsoft Powershell 1.0 or higher for Windows Server 2008 32-bit before you begin installing C•CURE 9000. If you are installing C•CURE 9000 on a Windows XP system, under certain circumstances you may receive a message saying that the Powershell 1.0 Prerequisite failed to install. You may safely ignore this message as Powershell 1.0 is actually installed. 12.2 Server Requirements Failure Message during Installation on Windows Servers If IIS Extension files are not installed on your server system, the Installation program reports that IIS is not installed. You can safely continue the installation and install the IIS Extension Files after the C•CURE 9000 installation has completed.

16 RN-00001

12.3 SDK Connected Program Drivers PRIOR TO UPGRADING C•CURE 9000: If you have licensed any of the SDK Connected Program drivers with a previous release, please check the Software House web site under Home>Support>“Software House Connected“>Compatibility Matrix (http://www.swhouse.com/support/SWH_Connected_Compatibility_Matrix.aspx) to confirm that the integration you have is compatible with v2.10 BEFORE YOU UPGRADE. Contact the distributor of the Connected Program driver to get your C•CURE 9000 v2.10 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.

12.4 Hardware and Video Driver Manual Start After installing Version 2.10, you must run the Server Configuration Application (Start>All Programs>Software House>C•CURE 9000>Server Configuration Application) one time to enable and start the Server Component Service (Hardware Driver) for each type of controller and video, or network component that will be used on the server. (The Server Component Services [Drivers] are not automatically started by default because enabling drivers for devices that are not used by the server can affect system performance. In addition, starting them automatically would trigger a download for apC, ISC, and iSTAR controllers.) See the C•CURE 9000 Installation and Upgrade Guide on the product DVD for specific instructions. You can view the status of these drivers from Windows Services, but you should not configure them to start automatically from there; startup is managed by the CrossFire Server Component Framework Service. 12.5 Installing C•CURE 9000 on Non-English Operating Systems If you are installing Microsoft SQL Server on a non-English version of Windows XP with Service Pack 3 loaded, you may encounter an error message telling you that it is unable to overwrite a file. You can ignore this message and continue on as it does not affect the operation of C•CURE 9000. 12.6 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.10. Object definitions in the database may change from version to version, so the import may fail or the imported object may not work correctly in C•CURE 9000 v2.10. 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 Version 2.10:

1. Re-Import the XML documents. 2. Upgrade to Version 2.10. 3. Export the Objects again.

End of Release Notes 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 Tyco International Ltd. 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 Tyco International Ltd. 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. Copyright © 2012 Tyco International Ltd. and its respective companies. All rights reserved