NStar Build 648
Release notes NStar Build 648
Overview
These release notes contain the information that is specific to NStar Build 648:
• New features
• Special Software Considerations
• Known Anomalies
• Remote Client/Server Configuration
New Features
NStar Build 648 adds the following changes since NStar Build 45.2 and the International Build 47. The build numbering sequence is reflecting a fundamental change. NStar now uses a Unicode based code (allows functional operation in multi-bit languages such as Chinese). The demo mode of operation is no longer time sensitive. The new Demo mode operation will allow no more than 10 cards to be entered and if the NSOPT1 option is used, printing of badges is not
allowed. Registering NStar will remove the Demo mode restrictions.
• Added operating system support for Windows Vista Business, Windows XP Pro SP3.
• SQL Server 2005 Server Express Edition is the default database engine • Supports existing SQL Server 2005
• Card Holder Locate button in the tool bar • Card Database display
• NStar Scheduler now allows Database Backup as an option • A Restart button has been added to the NStar Services New features have added to the option set – NSOPT1
• Fusion DVR support
• VISTA Intrusion (VISTA 128FBP or VISTA 250FBP) • Galaxy Intrusion (G3 and Classic)
• Card Holder Biometrics tab now has the same look as WIN-PAK SE/PE
Special Software Considerations
When upgrading a previous NStar, the “Registered SQL Server Properties” tab will prompt the user to enter a Login ID, Password and Instance name. Typical installations use the default Login ID “sa” and a blank (empty) password and instance name. Unless you know this information is different, leave the defaults as seen on the screen and select “Next”. NStar will not change the existing database engine.
For Windows Vista, the NStar Service Manager can be launched by right clicking and selecting “Run as administrator”. This setting can also be adjusted in
Windows from the right click/Properties/Advanced and select Run as administrator.
Known Anomalies
1. You must right click on the Backup and Restore utility and select “Run as administrator” once to complete registration of components (Windows Vista installations only).
2. Schedule Database back up feature will not support backup on Tape drive and Network drives.
3. MSDE 2000 will be not be automatically upgraded to SQL Server 2005 Express when upgrading to NStar Build 648 from any previous releases of NStar such as Build 45, 47,19 etc.
4. NStar Builds 19 - 47 using a hardware key option (NSOPT1D – dongle) is not supported by NStar Build 648. A new NSOPT1D can be ordered.
5. Tutorials are not current to this release.
Upgrading Anomalies and Work-Arounds
1. Where the UI is a member of the Domain, the user is unable to login after upgrading the system to NStar Build 648.
Workaround - Change the logon property of the NStar services.
2. Action group priorities for NS2 panel & RS-232 Port may show zero after upgrading.
Workaround – It can be changed manually from Action Groups.
3. Configure some operators before up gradation from NStar Build 45 to NStar build 648. After upgrade these operators are not listed in operator report.
Workaround – Edit and save the operators in operators list view – no data needs to be changed, just open the operator record and click on “OK”.
(Hourly may be required in some systems). This will keep the Vista time in sync with NStar. This is schedule is automatically created when the QSW is used. If you do not use the QSW, you will have to manually add a Schedule Server in the Device Map and a Schedule to the Time Management->Schedule. Virtual
keypad can also be used to set the appropriate Time/Date from NStar. 5. In Windows Vista all the NStar utilities have to be run as administrator mode.
Workaround – On the Utility, Right click/Properties/Advanced and select Run as administrator.
6. Play back speed for recorded video for Fusion DVR is not correct. Workaround –Adjust the speed accordingly in the control bar.
Intrusion Application Notes
VISTA - If there are more than 8 Vista devices generating fault activities,
communication to NStar will be interrupted until there are fewer than 8 devices in the fault condition.
It is therefore recommend to use smart sensor devices as they will not report faults when bypassed. This will then minimize the number of faults being reported.
Galaxy – Galaxy Dimension panels are not supported.
Remote Client/Server Configuration
NStar works both in Domain and Workgroup environment.
• The user can set the option as per the requirement. However, by default, the option is set to DOMAIN Environment.
• This setting needs to match between all Servers and all clients.
Domain Environment
In order to work in a Domain Environment, you need to create the users and start the NStar Servers.
Preparing Domain User to start NStar Servers (Services)
Create Domain Users
1. Login to the system as Administrator where NSTAR Servers are installed. 2. Open Computer Management window through Control Panel ->
Administrative Tools -> ComputerManagement.
Note: In case you have installed Windows 2003/XP Operating System, switch to Windows Classic view in for control panel option.
3. Select Groups from System Tools->Local Users and Groups folder and open Power Users properties.
5. Enter Domain & User Name in the format ‘DOMAIN\USER NAME’ and click OK button.
6.
7. 8.
Setting up NSTAR Server Log On Settings
After adding domain user to local system Administrator or Power User group. 1. Open Services window from Control Panel -> Administrative Tools ->
Computer Management -> Services and Application.
By default, NSTAR Servers ‘Log On As’ property will be the Local System.
2. To set NSTAR Server Log On property, double click the required server from right side pane of services window.
3. In Server Properties window, select ‘Log On’ tab.
4. In this tab ‘Log On As’ property will be set to ‘Local System Account’. Set this to ‘This account’ and give Domain user account, which was added previously to System Administrator/Power user group and enter the password.
5. Click OK to save changes.
6. Follow these steps to set Log On As property of all other NSTAR Servers. 7. Restart the System to affect changes.
Note: User can login to NSTAR System using any account either local or
domain.
Unblocking the NSTAR services on Windows XP SP2, Windows XP SP3 or Windows Vista Business.
NSTAR services should be unblocked only if the status of Windows Firewall is
'On'. You can check this setting in the Windows Firewall dialog.
1. Open the Control Panel window through Start-> Setting-> Control Panel and select 'Windows Firewall'. (Windows Vista Start-> Control Panel->
Security – Allow a program through Windows Firewall go to step 3 below)
2. Check the status of ‘Windows Firewall’ through Windows Firewall dialog
-> General tab.
3. Select ‘Exceptions’ tab from ‘Windows Firewall’ dialog and click ‘Add
The illustration below displays the procedure of adding NSTAR Database server (NCICore.exe) to Exceptions tab.
4. Select the required program by browsing the location in ‘Add a Program’ dialog and click OK. The service will now be available in the Exceptions Tab.
6. Repeat Steps 2 to 4 to unblock all other NSTAR Services running on the current system.
7. Click OK to save changes.
8. Restart all Services once if required.
Disabling the Firewall in 2003 Server
To access NSTAR services, the Windows Firewall should be disabled. You can check this setting in the Windows Firewall dialog.
Steps to Disable Windows Firewall settings
1. Right-click 'My Network Places' -> Properties to view the Local Area Connection.
3. Select the 'Advanced' tab from Local Area Connection Properties window.
WORKGROUP Environment
1. Select the WORKGROUP Environment radio button to set the option to Workgroup Environment.
2. NSTAR services should be unblocked before proceeding further. Refer to "Unblocking the NSTAR services on Windows XP", if the NSTAR
Comparison of DOMAIN vs. WORKGROUP configuration
DOMAIN Environment WORGROUP Environment
Communication Communication
Servers and Clients communicate using Secure RPC connection. Servers and Clients communicate using Secure RPC Security. Anonymous communication method is used.
Services Configuration Services Configuration
Will require Domain User and password for Server Services. Will not require Domain User Login for running the UI client.
Windows Firewall Configuration Windows Firewall Configuration
Will require Domain all NStar Servers and client to be added to the Exceptions in Windows Firewall (via Control panel.
Note: In Windows Server 2003, the Firewall Exceptions are not allowed and hence the Firewall will have to be disabled to allow DOMAIN connectivity.
Will require Domain all NStar Servers and client to be added to the Exceptions in Windows Firewall (via Control panel.
Note: In Windows Server 2003, the Firewall Exceptions are not allowed and hence the Firewall has to be disabled to allow WORKGROUP connectivity.
Legacy Comments
Operates similar to NStar Build 19 to 48 in Domain Operates similar to NStar Build 19 to 48 in Domain
No change from NStar Build 19 to Build 48 in Domain environment. Servers and Client will work as in previous legacy builds (as in Builds 19 through 39) in WORKGROUP environment. Note: Ensure that the Microsoft default value for Windows XP Service Pack 2 for Restricting Remote Clients is actually retained. RPC_RESTRICT_REMOTE_CLIENT_DEFAULT
NStar VISTA Integration
When the NSOPT1 or NSOPT1D option is used a single VISTA 128FBP or VISTA250FBP panel can be added to NStar. Supported feature include: Alarm Monitoring; Controlling Vista panel from Control Map; Partition Arm/Disarm; Zone Bypass/Unbypass; Output On/Off; Virtual Keypad; Video Pop-up on Vista Alarms.
Section Index
A. Equipments Required
B. Connections For Home/Facility Automation Control C. Summary of programming commands
D. Programming for the ADEMCO 4100 SM Procedure E. Configurations
A. Equipment Required
• VISTA 128FBP or VISTA 250FBP – Recommended is Version 3.0; Minimum is Version 2.0
• ADEMCO 4100SM Serial Interface Module • Serial to IP converter (optional)
Communication settings are 1200-baud, 8 data bits, no parity, and one stop bit.
B. Connections for Home/Facility Automation Control
12 34 5 6 7 8 9 J2 CONNECTOR BLACK GREY YELLOW RED GREEN BROWN BLUE VIOLET
4142TR CABLE (SUPPLIED WITH 4100SM)
C. Summary of Programming commands
• Find out the installer code. For 128/250 FBP it is 5140 by default. • To enter into program mode
o Enter installer code + [8] + [0]+ [0] +[0]
o Installer code can be modified *00 option once entered into program mode.
o Installer code must be provided in NStar from HA port page.
• To set engineering defaults, enter *96 (may be required with Version 2 firmware) o If this is performed then you must do a *97 to set standard defaults. • To set defaults, enter *97
o 1 to load ADEMCO defaults; 2 to load ADT defaults; 0 to exit without changing programming
• To change to next page of program fields, press *94 o Press *94 to move to 2nd page, (fields 1*01 – 1*76)
Press *99 to move back to 1st
page
o Press *94 to move to 3rd page, (fields 2*00 – 2*88) Press *99 to move back to 2nd
page
o Press *94 to move to 4th page, (fields 3*00 – 3*85) Press *99 to move back to 3rd
page • To return to previous fields, press *99
D. Programming for the ADEMCO 4100 SM Procedure • 0*05 System Notify Event
o Enter 1 to view all zone faults/restores. • 0*14 Trigger on RS232 input
o Enter 1 for Home Facility Automation Control • 1*70 Enable event log type
o Enter 1.1.1.1.1.1 for all 6 types • 1*78 Extended Home Control Event Report
o Enter 1
• 1*79 Home Control Event Report Types o Enter 1.1.1.1.1.1 for 1-6 zone types • 2*30 Pager Installed
o Enter 0
• 3*19 Enable J2 Header Printer Port
o Enter 1 for Home Automation Control
Optional
Turn off if unused 971 (Bell 2) and 974 (Dialer 1) alarms • Log in with installer code
• *93 is used to set the alarm functions and prompts for “Zone Prog” press 1 for Yes
o “Set to Confirm” press 0 for No o “Enter Zone No” press 971*
o Press * until you see “Enter Zone No – 000 = Quit 972” press 000* to Quit or continue by pressing * to change 974
o Press * until you see “974 Zone Type – 24Hr TROUBLE” change from 19 to 00
o Press * until you see “Enter Zone No – 000 = Quit 975” press 000* to Quit o “Quit Menu Mode” press 1 for Yes
o *99 until you exit the programming mode
Disable Periodic Self Test • 0*27 Periodic test
o Enter 0.0.0.0 to turn test off (default is 0.0.2.4 (every 24 hours)).
E. Configurations
• Number of partitions can enabled from 2*00 programming option o Create Partition ADVs accordingly in NStar.
• Zone information can be configured from programming options given in 0*93 o Create Zone ADVs accordingly in NStar.
• Output information can be configured from programming options given in 0*93 o Create output ADVs accordingly in NStar.
• Assign keypad to partition-1.
• Create a Master user that should be able to Arm/Disarm partitions, Bypass/Unbypass zones, etc. Assign all the partitions enabled.
o Tip: For adding user 002 with user code 1234, enter [5140][8][002][1234] o Master user code must be provided in NStar from HA Port page. It will
