I/A Series® System

RemoteWatch
V4.1 Release Notes

*B0860RK* *A*

B0860RK

Rev A
March 19, 2014
Invensys, Foxboro, I/A Series, and the Invensys logo are trademarks of Invensys plc, its subsidiaries, and
affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 2014 Invensys Systems, Inc.

All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Contents................................................................................................................................ iii

Figures..................................................................................................................................... v

Tables.................................................................................................................................... vii

Preface.................................................................................................................................... ix

1. Overview ........................................................................................................................... 1

2. Enhancements ................................................................................................................... 3
2.1 RemoteWatch Server Applications ...................................................................................... 3
2.1.1 LocalWatch Application .............................................................................................. 3
2.2 RemoteWatch I/A Series Data Acquisition Software (DAS) ................................................ 3
2.2.1 70 Series RW DAS for I/A Series V6.3 thru V8.4 ....................................................... 3
2.2.2 70 Series RW DAS for I/A Series Versions 8.5, 8.6, 8.7, 8.8 and 9.0 ........................... 3
2.2.3 RW 50 Series DAS ...................................................................................................... 4

3. Operational Recommendations ......................................................................................... 5

3.1 RW 50 Series Data Acquisition Software (DAS) ................................................................. 5
3.2 70 Series RW DAS for I/A Series V6.3 thru V8.4 ............................................................... 5
3.2.1 RW_WinExec_Service ................................................................................................ 5
3.2.2 distribute_mbxCfg.vbs File Not Found Error .............................................................. 5
3.2.3 Operating System Resource Usage Data ...................................................................... 5
3.3 70 Series DAS RW for I/A Series V8.5 thru V9.0 ............................................................... 6
3.4 Station Access Manager ....................................................................................................... 6
3.5 Invensys File Services .......................................................................................................... 6
3.6 LocalWatch ......................................................................................................................... 6
3.7 NextNine Virtual Service Engineer ..................................................................................... 6
3.7.1 Adding Devices (I/A Series Workstations) to NextNine .............................................. 6
3.7.1.1 Creating the Device List ...................................................................................... 6
3.7.1.2 Configuring Devices ............................................................................................ 8

4. Installation Notes ............................................................................................................ 11

4.1 RW 50 Series Data Acquisition Software (DAS) ............................................................... 11
4.2 70 Series RW DAS for I/A Series V6.3 thru V8.4 ............................................................. 11
4.2.1 Set the Default Scripting Interface to CScript ............................................................ 11
4.2.2 70 Series RW DAS V3.0/3.1 for I/A Series V6.3 thru V8.4 Uninstall Notes ............. 12
4.3 70 Series RW DAS for I/A Series V8.5 thru V9.0 ............................................................. 14
4.3.1 70 Series RW DAS 3.0/3.1/4.0 for I/A Series V8.5 thru V9.0 Uninstall Notes ......... 14

iii
B0860RK – Rev A Contents

4.4 Invensys File Services ........................................................................................................ 15

4.5 LocalWatch ....................................................................................................................... 15
4.6 Station Access Manager ..................................................................................................... 15
4.7 NetSight Server/Console Application ................................................................................ 15

5. Problems Resolved .......................................................................................................... 19

5.1 RemoteWatch Server Applications .................................................................................... 19
5.1.1 Station Access Manager ............................................................................................. 19
5.1.2 LocalWatch ............................................................................................................... 19
5.1.3 Invensys File Services ................................................................................................. 20
5.2 RW I/A Series Data Acquisition Software (DAS) .............................................................. 21
5.2.1 RW 70 Series DAS for I/A Series V8.5 thru V9.0 ..................................................... 21
5.3 RW Windows Software Update Service (WSUS) Installation Tool ................................... 21

iv
Figures
3-1. NextNine I/A Device Configuration Window .............................................................. 7
3-2. VSE - Device List .......................................................................................................... 9
4-1. CScript Confirmation ................................................................................................. 12
4-2. After Installation Dialog .............................................................................................. 13
4-3. Finish Admin Install Dialog ........................................................................................ 13

v
B0860RK – Rev A Figures

vi
Tables
1-1. Release Media for RemoteWatch 4.1 ............................................................................ 1
1-2. Release Documentation for RemoteWatch V4.1 ........................................................... 1

vii
B0860RK – Rev A Tables

viii
Preface
This document provides the release notes for the RemoteWatch (RW) V4.1 software.

Revision Information
This is the initial release of this document.

Reference Documents
In addition to the information presented herein, you should be familiar with the following
I/A Series® documents:
♦ LocalWatch User's Guide (RemoteWatch V4.0/4.1) (B0860AX-B)
♦ LocalWatch Release Notes (RemoteWatch V4.0/4.1) (B0860RJ-B).
♦ RemoteWatch I/A Series Data Acquisition System (DAS) V4.1 Installation and Configura-
tion (B0860BD)
♦ RemoteWatch Server V4.1 Upgrade Guide (B0860BF)
♦ RemoteWatch V4.0 User's Guide (B0860AW)
♦ RemoteWatch V4.1 Station Access Manager V4.1.1 User's Guide (B0860BG).
Most are available on the I/A Series RemoteWatch Electronic Documentation CD-ROM
(CG500FH). The latest revisions may also be available through the Global Customer Support
Center at https://support.ips.invensys.com.

Glossary of Terms
$DAS $DAS is used to abbreviate the folder used as the root of the RW DAS
application. For 50 Series stations $DAS equates to
/opt/fox/bin/remote/tools/DAS. For 70 Series stations $DAS
equates to D:\opt\fox\bin\remote\tools\DAS.

RemoteWatch RemoteWatch is a service that provides a diagnostic and dispatch interface

for Distributed Control System resource usage issues. This service allows
Invensys engineers to remotely troubleshoot issues before they become
more serious problems. In addition, RemoteWatch provides the capability
for end-users to view and report DCS information and resource usage, as
well as the ability to download additional files to be deployed on your
RemoteWatch Server.
The name RemoteWatch supersedes the previous name “Device Relation-
ship Management (DRM).”

RemoteWatch The RemoteWatch Server is the central point of control for the Remote-
Server Watch system at your site. The RemoteWatch Server collects data from an

ix
B0860RK – Rev A Preface

I/A Series system, which are then historized and transferred to the Global
Customer Support Center where RemoteWatch engineers can monitor the
health of the system.
The RemoteWatch Server also provides a connection between GCS and
your site that allows GCS experts to remotely view and troubleshoot issues
from the Global Customer Support Center. Using the remote connection,
it is possible navigate through an I/A Series system to determine and fix
the source of the problem and before it is allowed to escalate.
The name RemoteWatch Server supersedes the previous names “Sentinel
Server”, “Site Server”, and “Plant Sentinel”.

x
1. Overview
This chapter describes the contents of the RemoteWatch V4.1 Software release.
The RemoteWatch 4.1 application release contains DCS resource/asset collection applications
and resource/asset data viewing and reporting applications located on the RemoteWatch server.
The DCS resource/asset collection applications are:
♦ RemoteWatch 4.1 70 Series Data Acquisition Software for I/A Series Versions 6.3 thru
8.4
♦ RemoteWatch 4.1 70 Series Data Acquisition Software for I/A Series Versions 8.5,
8.6, 8.7, 8.8, and 9.0
♦ RemoteWatch 4.1 50 Series Data Acquisition Software (one version for all 50 Series
stations, Versions 6.3 thru 8.4.2)
The RemoteWatch server applications include:
♦ LocalWatch Server and Client applications
♦ Invensys File Services
♦ FERRET Lite
♦ Station Access Manager.

Table 1-1. Release Media for RemoteWatch 4.1

Part Number Description

CG500FP-A RW 4.1 I/A Series Data Acquisition
Software
CG500FT-A RW 4.1 RemoteWatch Server Upgrade
CG500FQ-A RW 4.1 Workstation Remote Access
(Netop Host)
CG500FS-A RW 4.1 Station Access Manager 4.1.1

Table 1-2. Release Documentation for RemoteWatch V4.1

Document Number Description

B0860BD-A RemoteWatch I/A Series Data Acquisition System (DAS) V4.1
Installation and Configuration
B0860BF-A RemoteWatch Server V4.1 Upgrade Guide
B0860BG-A RemoteWatch V4.1 Station Asset Manager V4.1.1 User’s Guide
B0860AX-B LocalWatch User's Guide (RemoteWatch V4.0/4.1)
B0860RJ-B LocalWatch Release Notes (RemoteWatch V4.0/4.1)

1
B0860RK – Rev A 1. Overview

2
2. Enhancements
This chapter describes the enhancements for RemoteWatch V4.1 software.
The RemoteWatch 4.1 release enhancement is:
♦ The RemoteWatch Data Acquisition Software is updated to include support for
I/A Series 9.0.
The enhancements are implemented in the following software:
♦ RemoteWatch 70 Series Data Acquisition for I/A Series Versions 8.5 through 9.0
(RW 70 DAS)

2.1 RemoteWatch Server Applications

The updated RemoteWatch Server applications in the RW 4.1 release include:
♦ LocalWatch
♦ Invensys File Services
♦ Station Access Manager
(Reference RemoteWatch V4.1 Station Asset Manager V4.1.1 User’s Guide, B0860BG.)

2.1.1 LocalWatch Application

The LocalWatch Application allows a RWS user to view DCS asset and resource information. In
addition, the LocalWatch application forwards the asset data to the GCS repository. For addi-
tional information reference:
LocalWatch User's Guide LocalWatch User's Guide (RemoteWatch V4.0) (B0860AX-A)
LocalWatch Release Notes (RemoteWatch V4.0) (B0860RJ-A)

2.2 RemoteWatch I/A Series Data Acquisition

Software (DAS)
The enhancements for the I/A Series data acquisition software for the various I/A Series system
software are listed in Sections 2.2.1, 2.2.2, and 2.2.3.

2.2.1 70 Series RW DAS for I/A Series V6.3 thru V8.4

No enhancements.

2.2.2 70 Series RW DAS for I/A Series Versions 8.5, 8.6, 8.7, 8.8
and 9.0
The 70 Series DAS for I/A Series Versions 8.5, 8.6, 8.7 and 8.8 is updated to support I/A Series
Version 9.0.

3
B0860RK – Rev A 2. Enhancements

2.2.3 RW 50 Series DAS

No enhancements.

4
3. Operational Recommendations
This chapter describes the operational recommendations for RemoteWatch V4.0.

3.1 RW 50 Series Data Acquisition Software (DAS)

Currently there are no 50 Series RW DAS operational recommendations.

3.2 70 Series RW DAS for I/A Series V6.3 thru V8.4

3.2.1 RW_WinExec_Service
The RW_WinExec_Service logs events to a flat text log file located in the
d:\opt\fox\bin\remote\tools\DAS\Logs directory and to the Windows® Event Log under
the Application section.
RW_WinExec_Service operational parameters such as its periodic execution rate for the probe
scripts, logging enable/disable, start delay can be adjusted via a flat text INI file that is located in
the d:\opt\fox\bin\remote\tools\DAS\cfg directory. It is strongly recommended that the
Execution_Interval be NO LESS than 60 minutes and the default Run_Interval be NO LESS
than 5 seconds.
RW_WinExec_Service executes probe scripts based on entries in the tasklist.csv file. The
tasklist.csv file is updated to contain an extra field for a time-out value. This time-out value is
used as a watchdog timer such that if the script takes too long (hangs for some reason), it can be
terminated automatically by the service instead of hanging the whole DAS application. If a certain
probe script is constantly timing out, the timer value can be lengthened up to a maximum of 15
minutes.

3.2.2 distribute_mbxCfg.vbs File Not Found Error

The distribute_mbxCfg.vbs program fails with a "File Not Found Error" error message. This fail-
ure occurs when the FistHost.txt file cannot be found in the
d:\opt\fox\bin\remote\tools\DAS\install\mbxCfg folder. If this error occurs, copy the
FistHost.txt file from the d:\opt\fox\bin\remote\tools\DAS\cfg folder to the
d:\opt\fox\bin\remote\tools\DAS\install\mbxCfg folder. This error does not occur on
the station used to install the 70 Series RW DAS software.

3.2.3 Operating System Resource Usage Data

On I/A versions 7.x, 8.0.B, 8.1 and 8.1.1, the operating system performance parameters captured
in the opsys.LETTERBUG.xml (where LETTERBUG is replaced with 70 Series station letter-
bug) may not be accurate. This is caused by defects in the MS WMI interface and in most cases is
solved by insuring that all the MS Patches specified at http://support.ips.invensys.com/content/Secu-
rity/mspatch/XP.ASP are installed. Even with the patches installed the free physical memory value
is not correct.

5
B0860RK – Rev A 3. Operational Recommendations

3.3 70 Series DAS RW for I/A Series V8.5 thru V9.0

Currently there are no operational recommendations for 70 Series DAS for I/A Series versions 8.5
thru 9.0.

3.4 Station Access Manager

Windows XP stations only allow one user to be logged in at a time. When connecting using
Remote Desktop to a Windows XP station, if another user is currently logged in then they will be
logged off and you will resume their session. If this functionality is not desired, Remote Desktop
can be disabled for Windows XP stations in the Configuration Tool found in the Start menu.
When connecting to a Windows XP station with Remote Desktop, the NetOp host application
will stop functioning properly. Any subsequent attempts to connect with NetOp will fail until the
NetOp Host software is restarted on the Windows XP station. This applies to NetOp versions 9.0
and earlier.

3.5 Invensys File Services

Currently, there are no Invensys File Services operational recommendations.

3.6 LocalWatch
Reference LocalWatch Release Notes (RemoteWatch 4.0) (B0860RJ) for LocalWatch operational rec-
ommendations.

3.7 NextNine Virtual Service Engineer

This upgrade requires no NextNine VSE changes.

3.7.1 Adding Devices (I/A Series Workstations) to NextNine

Stations are added to the NextNine installation by creating a comma-delimited (csv) data file and
running a script or manually adding one-at-a-time through the NextNine application. This sec-
tion explains how to add all stations using the provided software.

NOTE
Before device objects may be added, the Global Customer Support Center must
have downloaded the latest rule base (product line distribution). Contact the Global
Customer Support Center RemoteWatch Administrator to ensure that the latest
version has been downloaded to the server.

3.7.1.1 Creating the Device List

Before running the Add_Device application, verify that an entry exists in LocalWatch for each
station that you want to add to NextNine, and then proceed as follows:

6
3. Operational Recommendations B0860RK – Rev A

1. If not logged in as RwsGcsAdmin (or administrator for RWS model codes C15 thru
C18), login as RwsGcsAdmin (or administrator for RWS model codes C15 thru
C18).
2. Open My Computer or Windows Explorer and navigate to:
D:\Program Files\NextNine\SiteServer\Add Device.
3. Right-click Add_Device.exe and select Run as Administrator
(for RWS Models C15 through C18, double-click Add_Device.exe). The Device
Configuration window (Figure 3-1) appears.

Figure 3-1. NextNine I/A Device Configuration Window

4. On the Device Configuration window as shown in Figure 3-1, do the following:

a. For the NextNine version, select either 4.5 or 4.6.
b. For NextNine product line, select Sentinel Manager Dynamic Thresholds
(unless notified by the Global Customer Support Center RemoteWatch Adminis-
trator to do otherwise).
c. Enter the username and password for NextNine.
Contact Global Customer Support for the information.
d. Click Create to output the data file. The file is automatically saved as:
D:\Program Files\NextNine\SiteServer\device_list.csv.
5. Click Exit to close the Device Configuration window.

7
B0860RK – Rev A 3. Operational Recommendations

3.7.1.2 Configuring Devices

The device_list.csv file was created in the previous section. Now, a batch file uses it to con-
figure the devices for NextNine support. There are two versions of the batch file:
♦ add_devices.bat - used for VSE 4.5
♦ add_devices_46.bat - used for VSE 4.6
The procedure for executing either script is the same.
1. In a command window started with the Run as Administrator option, navigate to:
D:\Program Files\NextNine\SiteServer
Depending on the VSE version, run either:
♦ add_devices.bat - used for VSE 4.5
♦ add_devices_46.bat - used for VSE 4.6

NOTE
Ignore any error messages regarding the self-support or self-monitor stations.

2. From the desktop, double-click either the VSE v4.5 Login icon or the VSE v4.6
Login icon and enter the username and password supplied by Global Customer Sup-
port.
3. When the Site Server Device List appears, click Operation/Devices and verify that
the devices have been added, as shown in Figure 4-1.

8
3. Operational Recommendations B0860RK – Rev A

Figure 3-2. VSE - Device List

9
B0860RK – Rev A 3. Operational Recommendations

10
4. Installation Notes
This chapter describes the installation notes for RemoteWatch 4.1.

4.1 RW 50 Series Data Acquisition Software (DAS)

The 50 Series DAS version 4.1 software is installed without having to uninstall the previous ver-
sion.

4.2 70 Series RW DAS for I/A Series V6.3 thru V8.4

The user should pay close attention to the installation prerequisites in Chapter 2 of RemoteWatch
I/A Series DAS V4.1 Installation and Configuration (B0860BD).
If DAS version 3.0 or 3.1 is already installed on the I/A Series AW70 workstations, it must be
uninstalled prior to installing DAS version 4.1. Refer to “70 Series RW DAS V3.0/3.1 for I/A
Series V6.3 thru V8.4 Uninstall Notes” on page 12 or “70 Series RW DAS for I/A Series V8.5
thru V9.0” on page 14 for the instructions to uninstall DAS version 3.0 and 3.1.
DAS version 4.1 should be installed from a command window with the screen buffer properties
set for 200 characters across and at least 300 lines down. The progress of the installation process
can be followed on the command window. Refer to the document B0860AV under the Chapter
titled “70_Series_RW_DAS Software Installation”. Step 3 of the installation process details the
instructions for setting the screen buffer properties.
The installation process automatically propagates to Version 6.x workstations (from Version 7.x
workstations) without using a separate installation process for Windows NT-based workstations.
It is vital that the Windows Simple File Sharing property be disabled on each 70 Series work-
station that is to have DAS installed. This is described in Chapter 2 of B0860AV as well. If Sim-
ple File Sharing is enabled, the installation process cannot remotely install DAS to other
workstations on the network. The installation script may terminate with a Permission Denied or
Access Denied error.

4.2.1 Set the Default Scripting Interface to CScript

The default scripting engine for the Windows® Operating System is WScript. This must be
changed to CScript for proper scripting operation. For the purposes of the RW_DAS installation,
this procedure only needs to be performed on the workstation where the installation will be initi-
ated.
1. In a command window (Start->Run cmd), enter wscript//H:cscript and press
<Enter>.
2. A dialog box specifying CScript will be displayed, as shown in Figure 4-1.

11
B0860RK – Rev A 4. Installation Notes

Figure 4-1. CScript Confirmation

3. Click OK.

4.2.2 70 Series RW DAS V3.0/3.1 for I/A Series V6.3 thru V8.4
Uninstall Notes
If the 70_Series_RW_DAS software must be uninstalled for any reason, use the following proce-
dure:
1. Insert the CD-ROM (part number CG500EH) into the CD-ROM drive.
2. Open a command window to E:\70_Series_DAS.
3. Execute the script SetScriptMode.vbs
4. Execute the script 70_RW_Uninstall.vbs. This script may take some time to exe-
cute especially if the RW_Winexec_Service is pending on completion of a data acqui-
sition task before it can be stopped and removed.
5. On some 70 Series stations, after the password is entered two additional dialog boxes
are displayed. See Figure 4-2 and Figure 4-3.

12
4. Installation Notes B0860RK – Rev A

Figure 4-2. After Installation Dialog

If Figure 4-2 is displayed, wait 30 seconds and click Next. When Figure 4-3 is dis-
played, ignore the text contained in the dialog box and click Finish.

Figure 4-3. Finish Admin Install Dialog

6. To verify that the un-install operation executed properly, check the Add/Remove
Software applet on the workstations and verify the package
70_Series_RW_DAS_x.x is not present.
This completes the removal of the 70 Series DAS software (Version 3.0/3.1) on 70 Series worksta-
tions with I/A Series software versions 6.x, 7.x and 8.0 through 8.4.

13
B0860RK – Rev A 4. Installation Notes

4.3 70 Series RW DAS for I/A Series V8.5 thru V9.0

The 70 Series DAS is installed using the RemoteWatch I/A Series DAS V4.1 Installation and Config-
uration (B0860BD) document.

4.3.1 70 Series RW DAS 3.0/3.1/4.0 for I/A Series V8.5 thru

V9.0 Uninstall Notes
If the RW_WinExec DAS software must be uninstalled for any reason, use the following proce-
dure:
1. Login to the proper account for installation:
a. For a secure system, use the IA Installer account. Typically, the name is IAIn-
staller.
b. For a standard system, use the fox account.
2. Open a command window to d:\opt\fox\bin\remote\tools\DAS\install.
3. Execute the script uninstall_70.cmd. This script may take some time to execute
especially if the RW_Winexec service is pending on completion of a data acquisition
task before it can be stopped and removed.
4. On secure I/A Series systems, if the IA Installer account is not named IAInstaller, the
following occurs:
a. A dialog box asks if the I/A Installer account has been renamed.
b. If Yes is selected, another dialog box prompting for the IA Installer account name
appears. Enter the new account name, and click OK.
5. When prompted, select the station(s) to uninstall.
6. If a remote workstation is contained in the list of stations to uninstall, then proceed as
follows:
♦ On a standard I/A Series system, enter the fox account password at the prompt.
♦ On a secure I/A Series system, perform the following:
♦ In the dialog box, indicate whether or not the I/A Services account has been
renamed.
♦ If the IA Services account has been renamed, another dialog box appears.
Enter the new name and click OK.
♦ Enter the IA Services account password and click OK.
7. To verify that the un-install operation executed properly, check the Add/Remove
Software applet on the workstations and verify the package RW_WinExec_Pkg is
not present.
This completes the removal of the 70 Series DAS software (Version 3.0, 3.1, and 4.0) on 70 Series
workstations with I/A Series V8.5 software.

14
4. Installation Notes B0860RK – Rev A

4.4 Invensys File Services

The Invensys File Services software is installed per RemoteWatch Server V4.1 Upgrade Guide
(B0860BF).

4.5 LocalWatch
LocalWatch is installed using RemoteWatch Server V4.1 Upgrade Guide (B0860BF). Reference the
LocalWatch Release Notes (RemoteWatch 4.0) (B0860RJ) for any special installation instructions.

4.6 Station Access Manager

The Station Access Manager (SAM) application utilizes several third-party applications to initiate
remote sessions to other stations. These applications include NetOp Remote Control Guest,
FileZilla FTP Client, and Hummingbird Exceed. It is recommended that these applications are
installed prior to installing the SAM application, although this is not necessary. If any of these
applications are not installed, that functionality will not work in SAM application. They can be
installed at a later time and configured using the Configuration Tool.
NetOp and Exceed require valid licenses to run properly. FileZilla is open software and an instal-
lation package can be found on the SAM installation CD.

4.7 NetSight Server/Console Application

The NetSight Server/Console application, contained on the NetSight Console CD-ROM
(K0174HZ) can be installed on the RWS model codes C15, C16, C17, C18, C20 and C21. Net-
Sight is not supported on RWS models prior to C15.
The NetSight Console application can be installed on an RWS as described in B0700EJ using the
steps for installation on a I/A Series/FCS Workstations (non-security enhanced), with the follow-
ing exception: the Turning Off/Disabling and the Turning On/Enabling Virus Scan steps are
skipped.
The NetSight Console application uses a second network (a network other than the I/A Series
MESH network) to communicate with the NetSight sever located on an I/A Series workstation.
The NetSight Server application requires the RWS to be directly connected to the I/A Series
MESH network for the purpose of communicating with switches on the I/A Series MESH net-
work. This connection is only to be used to communicate with the switches in the I/A Series
MESH network and is NOT to be used for communication between the RWS and I/A Series sta-
tions. This solution is only applicable at customer sites that will allow the connection between the
RWS and the I/A MESH network, some customers may not allow this connection. A customer
can install a firewall (or similar security device) that only allows communications between the
RWS and the IP address associated with switches on the MESH network. The IP address range of
switches on the MESH network is 151.128.81.1 to 152.128.81.254.
Prior to installing NetSight Server application on the RWS, three prerequisites must be com-
pleted:
1. Determine the Ethernet media type between the RWS and the MESH control net-
work, that is, copper or fiber:

15
B0860RK – Rev A 4. Installation Notes

♦ If the media type is fiber, then a fiber network adapter and a fiber cable need to be
ordered and installed in the RWS. The fiber network adapter part number is
P0923LU.
♦ If the media type is copper and the RWS has an available (unused) Ethernet
adapter port then only the interconnect cable is required.
♦ If the media type is copper and the RWS does not have an available (unused) eth-
ernet adapter, then a P0924FD, copper network adapter, must be installed in the
RWS and an interconnect cable is required.
2. Determine if the 151.128.191.254 IP address is in conflict with an IP address used
by an I/A station. The last two octets for I/A Series stations are contained in the
d:\usr\fox\sp\IIF.prm file and are specified in the ADRIP1 parameter for each
station (without the "." between the octets and leading 0s added). The simplest
method to check for an IP address conflict is to use grep as follows:
a. Open a cmd window on any of the I/A Series System AWs.
b. Select the d: drive.
c. Change directory to d:\usr\fox\sp
d. Enter the following grep command; grep 191254 IIF.prm"
If the grep command results in output, then the IP address is in use by I/A, contact
Global Customer Support Center at http://support.ips.invensys.com to
determine what IP address to use for the RWS.
If the grep command results in no output, then there is no IP address conflict and the
151.128.191.254 address can be used for the RWS. Continue with the configura-
tion of the network adapter.
3. Next, configure the network adapter on the RWS that is being used for connection to
the I/A Series MESH network as follows:
a. Open the properties for the network adapter.
b. Deselect (uncheck) all protocols except for Internet Protocol (TCP/IP).

NOTE
Some protocols like Broadcom Advanced Server Program Drive, and so forth, can-
not be unchecked, this is normal and the configuration can continue.

c. Click the Internet Protocol (TCP/IP) and then click Properties.

d. On the General tab, select Use the following IP address.
e. Enter 151.128.191.254 as the IP address.
f. Enter 255.255.0.0 as the Subnet mask.
g. Leave the Default gateway blank.
h. Then, click the Advanced… button.
i. Select the WINS tab.
j. On the WINS tab:
♦ Uncheck Enable LMHOSTS lookup.
♦ Select Disable NetBIOS over TCP/IP.

16
4. Installation Notes B0860RK – Rev A

♦ Next, click OK.

k. On the Internet Protocol (TCP/IP) Properties dialog box, click OK.
l. Click the Configure button.
m. Select the Advanced Tab.
n. Select Speed & Duplex and set to 100Mb Full.
o. Select Flow Control and set to Disabled.
p. Click the OK Button.

Once these three prerequisites are completed, the NetSight Server application can be installed as
described in NetSight Console for the MESH Control Network (B0700EJ) using the steps for instal-
lation on a I/A Series/FCS Workstations (non-security enhanced), with the following exception:
the Turning Off/Disabling and the Turning On/Enabling Virus Scan steps are skipped.
The connection between the RWS and the MESH network is ONLY to be used for NetSight
communication with MESH control network switches. This link MUST NOT BE used for com-
munications between the RWS and I/A Series stations connected to the MESH network.

17
B0860RK – Rev A 4. Installation Notes

18
5. Problems Resolved
This chapter describes the problems resolved for the RemoteWatch 4.1 release.

5.1 RemoteWatch Server Applications

The RemoteWatch Server applications identified in the following sub-sections contain software
changes to correct issue identified in a CAR.

5.1.1 Station Access Manager

SAM discovery tool (CAR:1093321)

Description: Configuration of the Station Access Manager (SAM) is still largely com-
pleted by hand. The Discovery tool used to automatically configure SAM
has to be run on each individual system and in case of Windows based sta-
tions, each individual station. This makes configuring SAM extremely
painful on large systems.
Solution: The SAM discovery of I/A Series stations can be based on the I/A Series
workstations contained in the LocalWatch database, using the new Auto-
matic Update feature (Refer to B0860BG section "Using Automatic Sta-
tion Update").

5.1.2 LocalWatch

Links for Contact Invensys and Invensys Customer feedback do not work (CAR:1181319)
Description: The LocalWatch selections under the Help Menu are broken for Contact
Invensys and Invensys Customer feedback.
Solution: Fixed reported issue.

LocalWatch on the RWS 4.0 server crashes with the error Object reference not set to
an instance of an object when the program is opened. (CAR:1172916)
Description: The issue is with Expansion FBMs. Since Expansion FBMs do not have
their own letterbug, the LocalWatch service class is failing when loading
Expansion FBMs. This action is causing the entire LocalWatch application
to fail on startup.
Solution: Fixed reported issue.

19
B0860RK – Rev A 5. Problems Resolved

5.1.3 Invensys File Services

Import of historian tags from stations containing a station prefix (CAR:1179568)

Description: Installed DAS software from CG500FD_C. Edit the
d:\opt\fox\bin\remote\tools\DAS\cfg\dasFiles.cfg file to have StationPrefix
= BL4_. On the RemoteWatch 4 machine XML2Import.exe fails and
d:\resource_das\wrk\histcfgupdates show only 6 letter XML files. Example
dbvu.BL4_OL.xml, while the full name on the AW70 running the DAS
software is dbvu.BL4_OLIVIA.xml. It seems that xml2import.exe is hard-
coded to 6 character files, and does not support the station prefix. We need
station prefixes to support multiple sites per RemoteWatch server.
Solution: The Xml2InSql.exe and Xml2Import.exe programs, which are responsible
for creating historian tags, have been updated to correct this issue.

When Site Prefix is specified, collected FERRET data does not contain the site prefix.
(CAR:1172918)
Description: RemoteWatch 4.0 is monitoring multiple systems where a Host letterbug is
used multiple times. System 1 has AW7001; System 2 has AW7001; Sys-
tem 3 has AW7001. RemoteWatch does allow us to use the Site prefix to
make save the host data for the host with a unique file name
(Site_System1_AW7001, Site_System2_AW7001, etc). FERRET data col-
lected does not use the Site Prefix in the file name but has it embedded in
the file, making sure data always gets populated to the correct LocalWatch
DB. However, in the Ferret_ Archive for all the collected fer files, files get
overwritten. AW7001.fer is always the last one written. Please add support
the Site_prefix for the archive so we have correct audit trail of all the differ-
ent for files collected.
Solution: The srvc_mvferret.exe program used by the ISDBService which processes
the FERRET data files is updated properly to handle site prefixes. The site
prefix was not part of FERRET data file name in RW 4.0 DAS for 70
Series (both versions, i.e. 7.0 thru 8.4 and 8.5 though 9.0). In the RW4.1
DAS for 70 Series (both versions) now provide the site prefix as the part of
the file name. The updated srvc_mvferret.exe handles both of these condi-
tions correctly.

20
5. Problems Resolved B0860RK – Rev A

5.2 RW I/A Series Data Acquisition Software (DAS)

5.2.1 RW 70 Series DAS for I/A Series V8.5 thru V9.0

Installation should prompt for Site Prefix (CAR:1179578)

Description: When installing the DAS 4.0 software with CG500FD_C the installer
does not ask for a StationPrefix during the installation. Also, during the
installation, the first Ferret gather is run and transferred to the Remote-
Watch server. This data does not have a station prefix. After the installa-
tion, the StationPrefix is added to the configuration and new data is sent to
the RemoteWatch server that does contain the station prefix. Now the
RemoteWatch server has multiple directories with and without station pre-
fix for the XML data, for the Ferret archives, for the InSQL tag database,
etc. That is very difficult to clean up. An option is needed to setup that Sta-
tionPrefix before the 1st data is gathered and send to the RemoteWatch
server.
Solution: The software installation of the 70 Series DAS for I/A 8.5 thru 9.0 is
updated to allow for the station prefix (also known as the site prefix) to be
specified during installation. This will eliminate the reported problems,
multiple directories, multiple InSQL tag database, etc.

5.3 RW Windows Software Update Service (WSUS)

Installation Tool

Update Registry for WSUS (CAR:1182201)

Description: Part of the Release of RWS 4.0 is enabling WSUS. To enable client stations
of a WSUS server, there will be a need to make Host file entries, Registry
Changes/additions, and verify Automatic Updates is enabled/running. All
of this combined opens multiple location to configuration problems. With
Registries, one bad entry could cause major malfunctions within the OS.
We would like to create a program that will detect the OS, ask for the
entries of the WSUS Server, WSUS IP address, and make all needed
changes to a station to allow Automatic Updates.
Solution: The RW 70 Series DAS for I/A Series Versions 8.5 through 9.0 contains a
utility to allow the person adding WSUS support using the RWS as the
source for the Window Updates, to programmatically update the Windows
registry for use during Window Updates configuration procedure. Refer-
ence CG800DZ, RemoteWatch Services WSUS Site Implementation (this
document is available from the Global Customer Support).

21
Invensys
10900 Equity Drive
Houston, TX 77041
United States of America
http://www.invensys.com

Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Website: https://support.ips.invensys.com