IT

S T A N L E Y M A N U F A C T U R E D A C C E S S C O N T R O L

UIDE

T R O L

4 . 2

R’S GUIDER E L E A S E 4

T MANAGER

3

Table of Contents1. Frequently Asked Questions..................................................................................................1

1.1 Stanley PAC Access Control Administration Software.........................................................11.2 SQL Database for Stanley PAC...........................................................................................2

2. Installation................................................................................................................................4

2.1 System Requirements.........................................................................................................42.1.1 Server.........................................................................................................................42.1.2 Client..........................................................................................................................42.1.3 Operating Systems.....................................................................................................42.1.4 Databases..................................................................................................................5

2.2 When to Upgrade the Database Server..............................................................................52.3 Servers and Clients.............................................................................................................62.4 Stanley PAC Server.............................................................................................................6

2.4.1 Prerequisites..............................................................................................................62.4.2 Installation Directories................................................................................................62.4.3 Databases..................................................................................................................62.4.4 Microsoft Windows PowerShell..................................................................................62.4.5 User Accounts and Start-up Tasks.............................................................................7

2.4.5.1 Notes on SQL Server 2005 Express / SQL Server 2008 R2 ExpressDatabases......................................................................................................................72.4.5.2 Notes on SQL Server Databases.......................................................................72.4.5.3 No Manual Editing..............................................................................................7

2.5 Stanley PAC Clients.............................................................................................................82.5.1 Prerequisites..............................................................................................................82.5.2 Installation Directories................................................................................................8

2.6 Connectivity.........................................................................................................................82.7 Regional Options and Time Zone........................................................................................8

3. Uninstallation...........................................................................................................................9

4. Hardware................................................................................................................................10

4.1 The PAC 500 Access and Alarm Server............................................................................104.1.1 Download and Update Times...................................................................................104.1.2 Suppression of Asynchronous Events......................................................................114.1.3 Authenticated Communications................................................................................114.1.4 TCP/IP Port Requirements.......................................................................................11

4.2 The PAC 512 IP Door Controller........................................................................................124.3 The PAC 2000 Series Door Controller using IP Connectivity............................................12

5. Networking and Performance...............................................................................................13

5.1 Network Security...............................................................................................................135.1.1 DCOM / Multiple Clients...........................................................................................13

5.1.1.1 DCOM and Firewall Address Translation..........................................................135.1.1.2 Restricting the Range of TCP Ports.................................................................145.1.1.3 Configuring Your Firewall..................................................................................14

5.2 OEM Interface TCP Port 8658...........................................................................................145.3 Bandwidth Data.................................................................................................................15

5.3.1 Download Data.........................................................................................................155.3.2 Event Throughput.....................................................................................................155.3.3 Minimum Client Bandwidth.......................................................................................15

5.4 Backup File Sizes..............................................................................................................16

P

4

6. Tips..........................................................................................................................................17

6.1 Screen Resolution.............................................................................................................176.2 Multiple Monitors...............................................................................................................176.3 Database Backups............................................................................................................176.4 Reports..............................................................................................................................176.5 PC Name Changes...........................................................................................................17

6.5.1 Finding the Previous PC Name................................................................................186.6 Virtualisation......................................................................................................................186.7 Stanley PAC COM+ Applications on a Domain PC...........................................................186.8 Using Stanley PAC on Windows Server 2003...................................................................226.9 Using Stanley PAC on Windows Server 2008...................................................................246.10 Image Capture Utility in Windows Server 2008 R2.........................................................306.11 Accessing Stanley PAC via Remote Desktop..................................................................306.12 Windows Updates and Hotfixes.......................................................................................306.13 Sending E-mail from Stanley PAC...................................................................................306.14 USB Admin Kit with Windows Vista Business.................................................................30

7. Access Control Schematics.................................................................................................32

7.1 Example 1.........................................................................................................................327.2 Example 2.........................................................................................................................337.3 Example 3.........................................................................................................................34

P

Issue Record

DetailsAuthorDateVersion

Stanley PAC 3.1.JF08/12/2006V1.8

Stanley PAC 3.2.JF31/07/2008V1.11

Virtual server info added.SD23/09/2008V1.12

Stanley PAC 3.3. Updated system requirements; up-dated bandwidth usage; added info on WindowsServer 2008, SMTP, and USB Admin Kit with WindowsVista; updated database information.

SD03/07/2009V1.13

Added frequently asked questions for Stanley PACand SQL, hardware connectivity details; re-editeddocument to present a more logical structure.

JC03/12/2010V2.0

Stanley PAC 3.4. Updated system requirements.SD16/03/2011V2.1

Added information on Image Capture and installingWindows PowerShell; updated references to databaseserver requirements.

SD27/07/2011V2.2

Stanley PAC 4.0. Updated system requirements; up-dated PC name changes and virtualisation.

SP18/10/2012V2.3

Stanley PAC 4.2. Updated system requirements.SD25/04/2013V2.4

Applicability

VersionDetailNameProduct Code

4.2Stanley PAC

P

5

1. Frequently Asked QuestionsThe section provides an overview of the system requirements for Stanley PAC and the SQLdatabase, addressing some frequently asked questions. More detailed information can be foundin the following chapters.

1.1 Stanley PAC Access Control Administration SoftwareQ: Are there any particular requirements for the PC / server?

A: Software installation and user administration requires full local administrator rights whenlogged onto the PC / Server. There should be no Group Policy Objects (GPOs) appliedduring software installation.

Q: How is the software deployed?

A: May be installed from the CD provided by PAC, or from a network shared drive.

Q: What is the format of the installer?

A: A Setup.exe file is provided; launches a Microsoft Windows Installer.

Q: Will Stanley PAC run in a locked-down environment?

A: Yes, if installed with local rights.

Q: Can the Stanley PAC software be hosted in a Virtual Machine environment?

A: Yes.

Q: Where are the installation files written to?

A: Installation copies files to the Windows System32 folder, and writes to the WindowsRegistry.

Q: What services or processes will run on the PC / Server?

A: Executables: the Stanley PAC administration software (PACUI.exe) and the PAC ServiceManager.

Services: The PAC Communications Engine, PAC Client Manager, PAC Event Manager,PACDatabase Manager and PAC Remote Client Configuration. The PAC OEM InterfaceService may also be required if Stanley PAC is to be integrated with a Stanley AstrowTime and Attendance software database or a third party application.

Q: What is the database format?

A: SQL Server — see Section 1.2: SQL Database for Stanley PAC.

Q: Does Stanley PAC require e-mail configuration?

A: Stanley PAC can send e-mail messages in response to a system event.The SMTP serveris configured within the application. It may be necessary to configure the SMTP server /firewall — see Section 6.13: Sending Email from Stanley PAC.

6

DestinationPort

Source PortProtocol /Direction

LocationApplication

8085 (configur-able)

Dynamicallyassigned

TCP / OutStanley PAC ServerPAC Client Manager

8086 (configur-able)

Dynamicallyassigned

TCP / OutStanley PAC ServerPAC Event Manager

8087 (configur-able)

Dynamicallyassigned

TCP / OutStanley PAC ServerPAC Database Manager

8086–8096N/AUDP / OutN/ACOM+ / DLLHost.exe

5020–5040DCOM as-signed

TCP /In-Out

Stanley PAC ServerCOM+ / DLLHost.exe(DCOM)

1.2 SQL Database for Stanley PACQ: What is the database format?

A: All data is stored in the SQL database on the host machine. This may be SQL 2008 R2Express, which is included on the Stanley PAC installation CD.

Alternatively, Stanley PAC can use SQL Express 2005, SQL Server 2005 SP3 Workgroup(Standard or Enterprise), or SQL Server 2008 SP 2. SQL Server 2000 is not supported.

Q: Can Stanley PAC be installed on a separate machine from the database server?

A: No. Stanley PAC must be installed on the same machine as the database server.

Q: Does Stanley PAC require a specific SQL instance?

A: No. The Stanley PAC database can be hosted on a SQL Server with other databases,however, it must use the default instance.

Q: What Compatibility Mode is the database hosted in?

A: 80.

Q: Can the database be hosted in a Virtual Machine environment?

A: Yes.

Q: Which collation does your SQL database use?

A: Latin1_General_CI_AS.

Q: Does the Stanley PAC / SQL connection employ Optimistic Locking and ConnectionPooling to minimise connection times, and close connections between calls?

A: Yes. SQL / Stanley PAC can be configured for Optimistic Locking and ConnectionPooling, with minimum connection time.

Q: What is the size of the database at initial installation?

A: Approximately 15 Mb.

Q: Does Stanley PAC have any effect on the tempdb database?

A: No.

Q: What additional SQL Server jobs does the Stanley PAC database create?

A: Backup.

P

7

Q: Does Stanley PAC database require any of the following: Analysis Services, ReportingServices, Full Text Catalogues, SSIS packages?

A: No.

Q: Does Stanley PAC database use Extended Stored Procedures?

A: Yes — Xp-dirtree and xp-fixeddrives.

Q: Do Stanley PAC users require sysadmin access or sa login?

A: No.

Q: Do Stanley PAC users require direct access to SQL Server?

A: No.

Q: Can the system operate with Windows Authentication only?

A: No. An account is created during Stanley PAC installation.

Q: Does Stanley PAC require permissions to be granted / denied to the Public Databaserole?

A: No.

Q: Does Stanley PAC need to be able to create temporary databases?

A: Yes.

Q: Do Stanley PAC users or external support persons require Fixed Server Roles?

A: No.

Q: Does Stanley PAC store any data outside of the SQL database?

A: No.

P

8

2. Installation

2.1 System RequirementsYou must have administrator privilege to install Stanley PAC. It is recommended that you use thelocal Administrator account or any account with administrator privilege that will not subsequentlybe deleted from the PC.

We recommend that the Stanley PAC machine requirements, listed below, for memory andprocessor speed, are exceeded whenever possible.

2.1.1 Server

• IBM Compatible PC, 1.6 GHz dual core processor — 2 GHz dual core recommended.

• 1 GB RAM — 2 GB recommended if using Windows Vista or later. For increasedperformance, more memory is recommended.

• Minimum 2 GB of free disk space — 10 GB recommended and more may be requiredfor large enterprise systems.

• Celeron or Atom processors not recommended.

2.1.2 Client

• IBM Compatible PC, 1.6 GHz processor — 2 GHz recommended.

• 1 GB RAM — 2 GB recommended if using Windows Vista or later.

• Minimum 2 GB of free disk space.

• SuperVGA 800×600 graphics — XGA 1024×768 recommended, 1280×1024 for alarmworkstations.

• Celeron or Atom processors not recommended.

2.1.3 Operating Systems

The following operating systems are supported:

• Windows Server 2012 Standard edition — referred to as Windows 2012.

• Windows 8 Pro or Enterprise edition, 32 or 64-bit — referred to as Windows 8.

• Windows Server 2008, 32 or 64-bit; or Windows Server 2008 Release 2, 64-bit —referred to as Windows 2008.

• Windows 7 Professional, Enterprise or Ultimate edition, 32 or 64-bit; or Windows 7Professional, Enterprise or Ultimate edition with Service Pack 1, 32 or 64-bit — referredto as Windows 7.

• Windows Vista Ultimate, Business or Enterprise edition, 32 or 64-bit, Service Pack 2required — referred to as Windows Vista.

• Windows Server 2003, 32 or 64-bit, Service Pack 2 required; or Windows Server 2003Release 2, 32 or 64 bit, Service Pack 2 required — referred to as Windows 2003.

• Windows XP Professional 32 or 64-bit, Service Pack 3 required — referred to asWindows XP.

P

9

10

You should also consider upgrading to SQL Server 2008 R2 Workgroup, Standard or Enterprisefor increased performance if the Stanley PAC Server has more than one CPU.

2.3 Servers and ClientsFor optimum performance we recommend using Stanley PAC clients for specific functions. Forexample, using one client as an Alarm Viewer, one as an Enrolment Station, one as an EventViewer, etc.

Server

We recommend the use of a dedicated PC for operation as the Stanley PAC server.

Clients

The Stanley PAC client can be easily operated alongside other applications: there is no need fora client to run on a dedicated PC.

2.4 Stanley PAC Server

2.4.1 Prerequisites

Windows Message Queuing

This is a component of Microsoft Windows, and is installed as part of the Stanley PAC installationprocess.

Microsoft .NET Framework Version 1.1

This software is required and can coexist with any other version of the .NET Framework — thereis no need to uninstall the existing version.

Microsoft .NET Framework Version 2.0 is installed as part of the Stanley PAC installation process.

2.4.2 Installation Directories

The software is by default installed into the %ProgramFiles%\Stanley PAC folder.The installationprocedure also creates folders for storing database backups and event archives.You may changethe folders from the defaults during the installation process.

2.4.3 Databases

If you are installing a Stanley PAC Server and no existing Microsoft SQL Server database instanceis found, the setup program requires you to install SQL Server 2008 Express, which is provided.

If you have an existing SQL Server database, you may still install SQL Server 2008 Express whenyou want to run Stanley PAC in a separate database instance.

See Section 2.1.4: Databases for a list of supported database servers.

2.4.4 Microsoft Windows PowerShell

Before you install Stanley PAC 3.4 using the default SQL Express 2008 R2 database server onMicrosoft Windows XP 64-bit, Microsoft Windows Vista 64-bit, Microsoft Windows Server 200364-bit Standard or Enterprise Edition, or Microsoft Windows Server 2008 64-bit Standard orEnterprise Edition, you must make sure that Microsoft Windows PowerShell is installed on youroperating system.

To install Windows PowerShell:

1. On the Stanley PAC installation disk, locate the PowerShell folder, then locate the installerthat is specific to your operating system.

2. Double-click on the Windows PowerShell installer to run it and follow the instructions onscreen.

3. When Windows PowerShell is installed, start the installation of Stanley PAC.

P

11

guest account should not be remoThe

ver Databases2.4.5.2 Notes on SQL Ser

.R2 Express instanceer 2008ver 2005 Express / SQL Serve full DBA access to the SQL Servwill also ha

wsWindo account in Microsoft Administratory user allocated a standard ault, anBy def•

.kupsthem to restore database bacwroup will allo gAC_DBAPPAe user into the ativadministr- Placing a noninstallation.ingroup created dur user gAC_DBAPPAws user allocated the Windoy anted to anris g

er 2008 R2 Express instancever 2005 Express / SQL ServDBA access to the SQL Ser•

.leskups of these tabm bacorles and perfC tabAPPAyite the data in the Stanleights to read and wr has rcomputerr C_EKA_APPAinstallation.

ing account, which is created durcomputerr C_EKA_APPAanted to the rAccess is g•

.ity is used to access the databaseated SecurrInteg•

ver 2008 R2 Express Databasesver 2005 Express / SQL Ser2.4.5.1 Notes on SQL Ser

.ye kkupDir DBBac, and edit theTIONAL\EKAC INTERNA ATIONAL\EKAAARE\PPACHINE\SOFTWHKEY_LOCAL_MA

vigate to, na avigate toyws RegistrWindoy location, in the kup directorthe baco changeTTo change.yws RegistrWindoC database according to the path set in Ay P PAthe Stanle

k upy to bacuesdaTy ervuns at 15:30 eault, this task r By def.kupyBaceeklCWAPPA•

.vice Managerted — via the Serset to be autostary are Engine) if the.g.vices (et the seruns at boot time to starThis task r.tupCStarAPPA•

.eents to archivvviding there are enough old eent log, provthe eents inve ey to archivy da ay to archivervuns at 18:00 eault, this task r By def.hivecCEventArAPPA•

k.23:00 to synchronise all access controllers with the system clocy thereafter aty daervuns at boot time and eault, this task r By def.kSyncCClocAPPA•

our system:wing scheduled tasks are added to yolloThe f

.roupator to be a member of this goper A user does not need to be an.ivilegey other prdatabase without giving him/her an

or theator fe a user a database administrou to makws yroup alloThis g.AC_DBAPPA•

our system:roup is added to ywing local golloThe f

ust not be changed.andomly and mated ror this account is generord fwpassThe.This is a user account that is used to access the databaseC is installed.APPA

y is the name of the computer on which Stanlecomputerr , where computerr, C_EKA_APPA•

k:orail to wwill fCAy P PAou should not modify or delete it, or StanleYYou should not modify or delete it, or Stanleour system.wing account is added to yolloThe f

asksTt-up 2.4.5 User Accounts and Star

.ating systemsou are using one of these operyerShell ifwows PWindoou should not need to install YYo .ise EditionsprStandard and Enter

er 2008 R2vws SerWindoise Editions and Microsoft pr2003 R2 Standard and Enterervws SerWindoerShell is already installed on Microsoft wows PWindoault Microsoft By def

Note

ved

mou YYou

ual Editing2.4.5.3 No Man

.itten to the MSDB databasekup details are wrail when the bacto appear to fkups, as this could cause bac from the MSDB database

ust not manually editnot update the door controllers

ypasses the front end and does, as this blesy access or MSSQL tab an

.not update the door controllers

12

2.5 Stanley PAC Clients

2.5.1 Prerequisites

Microsoft .NET Framework Version 1.1

This software, required by Stanley PAC, can coexist with any other version of the .NET Framework— there is no need to uninstall the existing version.

Microsoft .NET Framework Version 2.0 is installed as part of the Stanley PAC installation process.

2.5.2 Installation Directories

The Stanley PAC software is by default installed into the %ProgramFiles%\Stanley PAC folder.You may change the folders from the defaults during the installation process.

2.6 ConnectivityThe client PC must be in the same workgroup or domain as the Stanley PAC Server to which it isconnected.

The name of the Stanley PAC Server to which the client is connecting can be specified in eitherthe installation process or on the client login screen.

2.7 Regional Options and Time ZoneEnsure that the correct regional options and time zone for the country or region is specified on theserver and client.

You can set the regional options by choosing Start › Settings › Control Panel and selectingRegional Options, or by choosing Start › Control Panel and selecting Regional and LanguageOptions, depending on the version of your operating system.

Once the Server / Client has been set, check that the correct time zone is set in Stanley PAC bystarting the application and choosing the Tools › Options menu. Look for the Timezone setting.

13

3. UninstallationStanley PAC can be removed from your system using the Add or Remove Programs item in theControl Panel, or running the Setup program from the installation disk. The prerequisite software,i.e. the .NET framework, service packs, SQL Server 2008 R2 Express, etc., are not uninstalledby this process, but can be uninstalled separately if required.

After uninstallation, the following files are (intentionally) left on your system:

• The database. If you are using SQL Server 2005 Express or SQL Server 2008 R2Express, these files are in %ProgramFiles%\Microsoft SQL Server\MSSQL.1 andits subfolders. These files can be reused if you reinstall Stanley PAC.

• Any contents of the database backups directory.

• Any contents of the event archives directory.

If you no longer need these files, you can manually delete them.

P

14

To ensure reliab

ating system.our oper, depending on yoolsTC Ay P PAStanle›ogramsPrAll›tStar or oolsTToolsC Ay P PAStanle›ogramsPr›tStaram in rou can find a link to this progy

ually —net segment and set their IP addresses manC 500s on the local EtherAam to find P PArprogdressvice IP AdConfigure Deou can use the k, yorour netwIf static addressing is used on y

.ydress automaticallObtain IP adace is set to k interforws PC when the netwWindoy aithm used balent to the algorThis is equivon subnet 169.254.0.0, subnet mask 255.255.0.0.

y other hosty any to select an IP address not used b If not, it will trle it will use it.ailabver is avser If a DHCP.e its IP address automaticallyvieC 500 will attempt to retrAer is applied, the P PAwWhen po

.C systemsAy P PAed on all Stanleyemplo, is notoreeatures are required and, therefC fAy P PAvice is required where enhanced StanleThis de

ating system.ws CE embedded operWindo uses the verC 500 Access and Alarm SerAPPAThe

verC 500 Access and Alarm SerAThe P PA4.1

wared Har4.

o ensure reliabT le, error free operation we strongly recommend the use of static IP addressing

Timeswnload and Update 4.1.1 Do

.ANWWANer a ver ovver o Setting up a 500 serTB198:echnical BulletinTTechnical Bulletiner to , refk connectivityorC 500 netwAmation relating to the P PAorther infor furF

ound on its barcode label.of the unit, which can be fumberial n is the sernn , where nC500_APPAC 500 attempts to set its NetBIOS node name to AA P PA

.

wnload.of the dok speed at the timeor, and are reliant upon the netwximatewnload times are approThe do

Note

e updateee load

sholdery-e50,000 K K 11 secs 12 mins / 40kb 14 secs

sholdery-e25,000 K K 3 secs 5 mins / 40kb 8 secs

gaPyholdereK

SizTime /wnload Do

gpayholdereKKe

15

er is using a vC 500 serAor use when the P PAfles ace has a setting that enabThe user interf

onou hr4.1.2 Suppression of Async

This setting must not be enabled

APPAty sheet, select the In the proper2.

, select the modulewaredHarIn the 1.

vents:onous ehro suppress asyncT

connection. when com

dialupThis is intended.entsvs suppression of asynchronous e

us Events

IP connection (via a PSTN modem).

.ventsSuppress async e, then select tabC 500A

.ervC 500 serA e P PA

netC 500 using the EtherAunicating with the P PA mm

C 500 uses authenticated Aault, the P PAy def

unicatiouthenticated Comm.1.3 A

ned off in the userThis can be tur.unications comm

ons

as required.unicationscommyptedUse unencr, then select or deselect tabC 500APPAty sheet, select the In the proper2.

.ervC 500 serA, select the P PA modulewaredHarIn the 1.

unications on or off:o turn authenticated commT

mally recommended., although this is not noraceinterf n the userBy

4

and 8085–8086. 135, 3000–3020,ts):y UDP ports (and if necessarTCP porwing olloaffic to the fmit incoming trerP

wer ClientsVieC Alarm Ay P PAStanle

.C 500s using non-authenticated commsAating P PA7076 when oper•

.C 500s using authenticated commsAating P PA15081 when oper•

ts:TCP porwing olloaffic to the fmit incoming try to perIt is necessar

t RequirementsorTCP/IP P4.1.4

C 500.Amation on the P PAorinfor moreC fAy P PAour installation of Stanley yer to the documents that accompanRef

Note

16

Stanley PAC Intivid VIP DVR

This is only required if the Intivid VIP DVR is being used for CCTV.

Permit incoming traffic to the following TCP ports (and if necessary UDP ports): 5300–5301,5150–5151 and 5400.

4.2 The PAC 512 IP Door ControllerThe PAC 512 IP door controller employs an on-board Lantronix Xport ethernet to serial converterto connect the controller to the network. By default, this device is configured for dynamic IPaddressing and, in the absence of a DHCP server, will auto configure an IP address on subnet169.254.0.0, subnet mask 255.255.0.0.

Static IP addressing is strongly advised. This is performed in the same manner as outlined inSection 4.1.

The Xport device is pre-configured to communicate on Port 8003.

For further information relating to the PAC 512 IP controller network connectivity, refer to thefollowing Technical Bulletins: TB205: Setting up a PAC 512 IP over a LAN and TB200: Setting upa PAC 512 IP over a WAN.

4.3 The PAC 2000 Series Door Controller using IP ConnectivityThe PAC 2000 Series door controllers employ the Lantronix UDS1100 ethernet to serial converterto connect the controller to the network. By default, this device is configured for dynamic IPaddressing and, in the absence of a DHCP server, will auto configure an IP address on subnet169.254.0.0, subnet mask 255.255.0.0.

Static IP addressing is strongly advised. This is performed in the same manner as outlined inSection 4.1.

The UDS1100 device must be configured to communicate on Port 14001.

For full details relating to the UDS1100 configuration, refer to Technical Bulletin UDS1100 Unit 2:Using with PAC 2000 Series Door Controllers — Configuration, or the e-Learning tutorial of thesame name.

P

17

5. Networking and Performance

5.1 Network SecurityThis section describes how to:

• Configure DCOM for multiple Stanley PAC clients support across a firewall. This is toallow the Stanley PAC Server and Clients, which use DCOM, to communicate witheach other.

• Configure firewalls on a WAN. This is required to allow the Stanley PAC Server tocommunicate with PAC IP controllers.

5.1.1 DCOM / Multiple Clients

To ensure maximum security on your network when using Stanley PAC clients over a firewall therange of TCP ports used by DCOM on the clients must be restricted. Section 5.1.1.2: Restrictingthe Range of TCP Ports describes how to do this.

5.1.1.1 DCOM and Firewall Address Translation

You cannot use DCOM through firewalls that perform address translation (NAT) — i.e. where aclient connects to a virtual address, such as 198.252.145.1, and the firewall maps it transparentlyto the server’s actual address, such as 192.100.81.101.

P

18

.er machinevy connect to the SCM on the serumbers when thet night porthe rk up Clients will automatically pic.er machinevou only need to do this on the serRemember that y

.ust createou m, which yyy, which yey k registrosoft\Rpc\InternetCHINE\Software\MicrHKEY_LOCAL_MAw are located under thealues listed belonamed v

All of the.iction functionalityt restry settings that control the DCOM poral registrervThere are se

tsorTCP Pe of 5.1.1.2 Restricting the Rang

ect.e effor them to taksettings in order fywing registrolloy of the fe changes to anou maky time your machine anust reboot ym

ou, y Also.yalue entr named vtsorPy the type required bTI_SZREG_MULLTI_SZt the suppor does not currentlyexedit.ereg to configure these settings;exedt32.eregust use ou mYYou m

Note

DescriptionalueypeName

notshould tsalue indicates which porv namedtsorP, then the Nis set to

alue If this v.DCOM applicationsorts should be used fwhich por

alue indicates named vtsorP, then theYalue is set to If this v

leailabvtsInternetAorP REG_SZ Y .Yys set this to aAlw

tsorP TI_SZREG_MULLTI_SZ

51413000–3020Example:

.ange per linertSpecify one por

.aluemeaning of this named vmine thew deteroptions belo

The.angest rOne or more por

TType V

t.unicates using this porcommare installed on the system whichy other software of anwInstallers need to be a•

k.orer the netwvunicating oace from comments the OEM Interfvwhich preare on the system, a conflict can occury other softwt is also used b If this port 8658.por

TCPace using unicates with the OEM Interf, commw Astro.g., eareOEM client softw•

Issue

t 8658.TCP porunicates using are which commty softwy third-paran, andw Astro.g., eare, OEM client softwaceeen the OEM InterfThere is a potential conflict betw

t 8658orTCP P5.2 OEM Interface

.evange(s) specified abo rtsorPer in the vour seron yy), if necessartsts (and UDP porTCP poraffic from all clients to the mit incoming trerP•

.)t that Microsoft Outlook uses (135 is the Microsoft Exchange por.ervour seron yy)t 135, if necessart 135 (and UDP porTCP poraffic from all clients to mit incoming trerP•

.ervour sernet to yaffic from the Intery all incoming trDen•

ws:ollonet should be configured as fer and the Intervour sereen yall betwwThe fire

wallour FireYYour Fire5.1.1.3 Configuring

tsorUseInternetP REG_SZ N or Y

.applicationsor DCOM be used f

19

Workaround

• It is possible to configure the OEM Interface to listen on a different TCP port; howeverit may not be possible to configure the OEM client software, e.g. Astrow, to use thenew port.Therefore, if a port conflict were to occur, it would be necessary to reconfigurethe third-party software to use a port other than 8658.

• Check the third-party software provider’s documentation and website for instructionson how to change the TCP ports that the third-party software uses.

5.3 Bandwidth DataThe bandwidth data below was measured using 50 PAC 500s running at 20 events per second.

Event throughput stops when a download begins.

The bandwidth usage of a PAC 512 IP is considerably less than that of a PAC 500. TheSerial-to-Ethernet port of a PAC 512 IP is constricted to 57.6 kb/s.

5.3.1 Download Data

Stanley PAC Server to PAC 500 Access and Alarm Server

The download begins with an initial burst of approximately 1,100 kb/s, which is followed bybandwidth usage within the range 300–780 kb/s.

PAC 500 Access and Alarm Server to Stanley PAC Server

The download begins with an initial burst of approximately 980 kb/s, which is followed by bandwidthusage within the range 20–380 kb/s.

5.3.2 Event Throughput

Stanley PAC Server to PAC 500 Access and Alarm Server

Max bandwidth: 480 kb/s (approx)

PAC 500 Access and Alarm Server to Stanley PAC Server

Max bandwidth: 680 kb/s (approx)

5.3.3 Minimum Client Bandwidth

A Stanley PAC client requires a minimum of 512 kb/s (full duplex) connection to its associatedserver.

P

5.4 Backup File SizesThis section describes the size of files created using the backup utilities which accompany StanleyPAC.

Database Backup File Sizes

The following table lists the size of the Stanley PAC backup files with the following databasesettings:

• 100 Areas

• 20 Access Groups

• 20 Time Profiles

Approx DB File Size (KB)Number of Keyholders

16,00025,000

29,00050,000

42,00075,000

Events Backup File Sizes

The following table shows the approximate size of the Stanley PAC events backup file for varyingnumbers of events.

Approx DB File Size (KB)Number of Events

40,600250,000

81,200500,000

162,4001,000,000

Archive File Sizes

The following table shows the approximate size of the Stanley PAC archive file for varying numbersof events. Event archiving is a feature of Stanley PAC v2.2 and higher.

Approx DB File Size (KB)Number of Events

24,900250,000

50,000500,000

99,7001,000,000

21

6.Tips

6.1 Screen ResolutionA screen resolution of at least 1024 × 768 pixels is recommended when using Stanley PAC.

If you are using the Stanley PAC Alarm Viewer we recommend a screen resolution of 1280 × 1024.

6.2 Multiple MonitorsIf you are using Stanley PAC on one PC for multiple functions we recommend the use of twomonitors, e.g. using the Event Viewer in its undocked form on one monitor, whilst using the AlarmViewer in the other monitor.

6.3 Database BackupsWe recommend making backups of the database on a regular basis using the backup tools providedwith Stanley PAC.

6.4 ReportsWhen running reports, we recommend using queries whenever possible to limit the size of returneddata.

If you are using Stanley PAC Clients and Servers, we recommend that you do not run reports onthe Server.

6.5 PC Name ChangesChanging the PC name will cause the installation of Stanley PAC on that PC to stop working. Thissection describes a workaround for this problem.

Workaround

1. Ensure that all Stanley PAC clients are shut down.

2. Change the PC name back to its original value — in Control Panel, open the System itemand use the Computer Name tab.

3. Backup the Stanley PAC database.

4. In Control Panel, use Add or Remove Programs to remove the following programs:

• The Stanley PAC installation.

• The SQL Server 2008 R2 Express installation, called Microsoft SQL Server2008.

5. Change the PC name to its new value — in Control Panel, open the System item anduse the Computer Name tab.

6. Reinstall Stanley PAC and SQL Server 2008 R2 Express, but do not select the Preserveexisting database option during installation.

7. After reinstalling Stanley PAC, choose the Start › Programs › Stanley PAC Tools ›Restore Database command to restore the last database backup.

8. Download the database to the connected door controllers. This may cause disruption todoor access. Make sure all users are aware before performing a download.

9. Ensure that the Server name property of any clients that connect to the server is changedto the new name. This property can be found on the logon screen of the Client.

P

22

http://supporat Micros er to mation reforor more infF

Notes

t.microsoft.com/defa

ent log, the computer name vIn the e

item in the left ha Systemk the Clic2.

, werVieEvent y the This will displa

command a Run›tStarChoose the 1.

io y the PC prmine the name used bo deterTTo deter

vious PC Nam6.5.1 Finding the Pre

kstations are shuorEnsure that all w

, which is locatedticle 281642wledge Base Arsoft Knoault.aspx?scid=kb;en-us;281642

.Computered in the column y e is displa

.vent logsystem ey the nd pane to displa

.w pictured belo

.eventvwr and type

or to the name change:

me

uing.ore continwn bef utdo

.

ents equal to or

, Microsofter

or to the

.um system requiremen better than the minimThe system resources .areVMwHyper-V or

tualisation enun on a virC can be rAy P PAStanle

tualisationVir6.6

.name changevious computer nao locate the preTTo locate the pre3.

oductionIntr

C COM+ Applic AA y P PA6.7 Stanle

System RequiremeSection 2.1: nts — see ust be equal to ortual machine m allocated to the vir

evtual SerVirvironment such as Microsoft n

i ent log to a date prvwn the e, scroll do me

cations on a Domain PC

it is possibin a Microsoft domain, unningou are r If y.vicesvide application serer PCs use Microsoft COM+ to provC SerAy P PAStanle

le for the domain polices to stop the application running

.roup PCskgorlem should not occur on wThis prob

dorwwn user name or passLogin failure unkno

DCOMce: 10004 SourEVENT ID:

ent log:vws eWindowing error messages will be seen in the olloThe fto log into the application.leou will not be abun and yail to r Engine) will f.g.vices (eC SerAy P PA, the StanleOn domain PCs

.

23

Cause

This problem occurs because the Log on as a batch job privilege has not been set for the identityof the COM+ package. When you set a user as the COM+ identity, COM+ adds this privilege foryou.

However, if the user is a domain account and does not have the Log on as a batch job privilegeset in a Group Policy Object (GPO), when the Active Directory performs an update, the identity ofthe COM+ package is reset and the permission is removed.

If you retype the password, COM+ will add the Log on as a batch job privilege again for the localcomputer.

Resolution

To resolve this problem, give the domain account the Log on as a batch job privilege in the GroupPolicy Object in the Domain Controller.

Procedure

1. Ensure that Administration Tools is installed on the local computer from the i386 folderon the Server disc.

2. Choose Start › Programs › Administrative Tools › Active Directory Users andComputers.

3. In the Console tree, right-click on the domain for which you want to set Group Policy.

P

24

4. Choose Properties and select the Group Policy tab.

5. Select Edit to navigate to the Group Policy Object you want to edit.

6. Choose Computer Configuration › Window Settings › Local Policies › User RightsAssignment.

25

7. Double click on Log on as batch job in the right pane.

8. Select the Add User to Group button and specify the Administrator group.

P

26

6.8 Using Stanley PAC on Windows Server 2003By default, a Windows 2003 server disables COM+, thus stopping a client PC from connecting tothe server and generating the following error message:

The component or application containing the component has been disabled

To solve the problem, the network COM+ access and network DTC access must be enabled.

Procedure

1. Choose Start › Control Panel, or Start › Settings › Control Panel, depending on theversion of your operating system.

27

2. Select Add or Remove Programs.

3. Select Add/Remove Windows Components.

4. Select Application Server and choose the Details button.

5. Select the Enable network COM+ access and the Enable network DTC accesscheckboxes and choose the OK button.

6. Choose the Next button to complete the wizard.

7. Choose Finish to close the wizard.

28

6.9 Using Stanley PAC on Windows Server 2008By default, Windows Server 2008 will not let Stanley PAC clients connect. This is due to tworeasons: first, by default Windows Server 2008 is not set up with the role of an Applications Server;second, by default the Windows Server 2008 firewall blocks the ports required by Stanley PACclients to communicate.

The procedure below explains how to set up Windows Server 2008 as an application server. Tofind which ports to unblock on the firewall, see Section 4.1.4: TCP/IP Port Requirements. If youare using the OEM Interface, see also Section 5.2: OEM Interface TCP Port 8658.

Procedure

1. On the Windows 2008 Server, choose Start › Administrative Tools › Server Managerto start the Server Manager.

The Server Manager starts.

P

29

c- and then leftRolesk on clic-Right2.

x in the Add Role The first dialog bo

.d RolesAdk on clic

ou YYou Beginore Bef s wizard ( .) appearsu Begin

) appeaver RolesSelect Serx in the Add Roles wizard (The second dialog bo

.xtNek Clic3.

. ars

30

4. Left-click in the box next to Applications Server so that it contains a tick.

5. Click Next.

An Add Roles Wizard dialog box appears, informing you that in order to install theApplications server role there are features that require installing.

31

6. Click the Add Required Features button.

The third dialog box in the Add Roles wizard (Application Server) appears.

7. Read the information, then click Next.

The fourth dialog box in the Add Roles wizard (Select Role Services) appears.

32

8. Make sure that Application Server Foundation and COM+ Network Access are ticked,then click Next.

The fifth dialog box in the Add Roles wizard (Confirm Installation Selections) appears.

33

9. Review the selections you have made, and then click Install.

The installation will now proceed.

When the installation is complete, the last dialog box in the Add Roles wizard (InstallationResults) appears. For each feature you should see the message Installation succeededdisplayed as below.

10. Click Close and then exit the Server Manager.

P

34

6.10 Image Capture Utility in Windows Server 2008 R2Using Stanley PAC under Windows Server 2008 R2, the Image Capture utility may fail to start.The error message An error occurred in image capture is shown.

To resolve this issue, go to the Server Manager and enable Desktop Experience in the Featuressection. When this feature is installed, restart the PC.

6.11 Accessing Stanley PAC via Remote DesktopYou may experience problems when using several Remote Desktop sessions to access StanleyPAC on a Windows Server 2003 / Windows Server 2008 server. For example, the user of oneRemote Desktop session may only be able to see the log-in screen for another session.

Therefore we recommend that, at any one time, you should have no more than one RemoteDesktop session open to access Stanley PAC on a Windows Server 2003 / 2008 server.

6.12 Windows Updates and HotfixesWe recommend that you keep any PCs that run Stanley PAC up to date with all updates availablefrom the Windows Update website (http://v4.windowsupdate.microsoft.com), to maintain the securityof your system.

Refer to PAC for update recommendations before applying any updates.

6.13 Sending E-mail from Stanley PACStanley PAC connects to the SMTP server using port 25. Depending on the configuration of yournetwork, port 25 may be blocked by anti-virus software, a corporate firewall, or your ISP. If StanleyPAC is not sending e-mail messages, reconfigure your anti-virus software or firewall to unblockport 25 or ask your ISP to resolve the issue. See also Section 5.1: Network Security and Section5.2: OEM Interface TCP Port 8658.

If Stanley PAC is not able to resolve the name of the SMTP server to an IP address, it will not beable to send any e-mail. If Stanley PAC is not sending e-mail messages, try configuring StanleyPAC with the IP address of the SMTP server, rather than the SMTP server name.

6.14 USB Admin Kit with Windows Vista Business

Issue

This section describes an issue that can occur under Microsoft Windows Vista Business whenyou create a direct channel, assign a COM port to that channel and attach a USB Admin Kit to theport. If you disconnect the USB Admin Kit and restart Stanley PAC, an alarm is displayed warningyou that the COM port has not been found.The direct channel is still fully configured, but the COMport has been removed.

Innovation in Access Control

Technical Support 1-800-414-3038