FAQs

General Software Questions

• Can I use analog cameras with my OnSSI Software?
• What do the lights in Ocularis signify?
• What is Dynamic Archiving?
• What ports are used by the NVR and Client programs?
• What is the Universal Driver?
• What hardware should I use for my NVR?
• What is the difference between MJPEG, MPEG4 and H.264?
• Importance of Frame Size
• What Frame Rate should I use for my cameras?
• Proper use of archiving?
• Where should I record Live Video?

Installation Questions:

• I received an error 1920 when installing the software, what does this mean?
• How do I upgrade my software?
• I installed my software as a 30 day trial, how do I license it?
• I added a new camera but it is not available in the NetGuard Client software
• Why are certain features in the camera settings page unavailable?

How To Questions

• How do I check what version software I am running?
• How to save the NVR configuration for backup purposes or to migrate to another server?
• How to setup and test a Generic Event?
• How do I access my Client viewing software?
• How to Disable User Access Control (UAC) in Windows Vista
• How to add ImageServer Slaves?
• How to setup a Wireshark capture?
• How to use an Event to Trigger NetMatrix Video?
• How to configure the 'Enable Outside Access' in the Image Server for remote NetGuard Clients?
• How is the archive folder structured?
• How to setup a Peformance Monitor Counter?
• How to configure NetEVS to Archive to a Mapped Drive?

1. Can I use analog cameras with my OnSSI Software?

Background: IP cameras are a recent development to the security camera market, as such many locations have analog cameras as well as newer IP cameras.

To use an analog camera in your OnSSI Software a video encoder (video server) is needed to convert the analog signal over to IP. There are many video server manufacturers on the market today, such as Axis, Pixord, Sony, Vivotek and many more. Please check the Supported Devices page to see if a particular model is support. You can find this page at: Supported Cameras List

Top

2. What do the lights in Ocularis signify?

What do the lights in Ocularis signify?

LED 1

Color: Purple
Notification: Event
Duration: Flashes each time an event associated with this camera occurs.

LED 2

Color: Red
Notification: Recording
Duration: Will remain on while the system is recording this camera's feed.

LED 3

Color: Blue
Notification: Motion
Duration: Will remain on as long as there is motion detected on this feed.

LED 4 (After the word “Live”)

Color: Green
Notification: Live feed
Duration: Constant as long as there is a live feed from camera.

Top

3. What is Dynamic Archiving?

Dynamic Archiving is ideal if you have multiple drives available for archiving but do not want to worry about how much space is used on each drive. It will also ensure equal retention of archive video. Dynamic archiving is only possible when you select the Automatic Path Selection check box in the Archive Setup.

Automatic Path Selection

Checking the Automatic Path Selection checkbox lets you select locations for archiving for selected cameras all at once.  This will divide the bottom of the window into two sections. Select cameras for which the archiving function should apply and Select drive for dynamic archives.

When Automatic Path Selection is enabled, you will be able to specify archiving locations for all selected cameras in one step. In the Select drives for dynamic archives section, simply select the box next to each drive required as archives. The drive with the most available space will be used first. If you wish to add a location using its UNC path, click on the 'Add target' button in the Archive setup dialog window and enter a valid UNC path.

Note that it is only possible to select drives; you cannot edit the paths. An Archives directory will automatically be created in each drive.

Notes:
If you use a drive for both recording and archiving, cameras recording to that drive will archive to that drive only. In this case, you should avoid using the same drive for both recording and archiving.

Top

4. What ports are used by the NVR and Client programs?

What is a port? A port is a logical endpoint for data traffic. Networks use different ports for different types of data traffic. Therefore it is sometimes, but not always, necessary to specify which port to use for particular data communication. Most ports are used automatically based on the types of data included in the communication. On TCP/IP networks, port numbers range from 0 to 65536, but only ports 0 to 1024 are reserved for particular purposes. For example, port 80 is used for HTTP traffic which is used when viewing web pages.

Make sure that the following ports are open for data traffic on your network for use with your NetDVMS, NetDVR or ProSightSMB software:

• Port 21 (outbound): Used for FTP traffic. FTP (File Transfer Protocol) is a standard for exchanging files across networks. FTP uses the TCP/IP standards for data transfer, and is sometimes used for downloading events from devices.

• Port 25 (inbound and outbound): Used for SMTP traffic. SMTP (Simple Mail Transfer Protocol) is a standard for sending e-mail messages between servers. This port should be open since, depending on configuration, some cameras may send images to the surveillance system server via e-mail.

• Port 80 (inbound and outbound): Used for HTTP traffic between the surveillance servers and cameras, Client programs, and the default communication port for the surveillance system's Image Server. HTTP (HyperText Transfer Protocol) is a standard for exchanging files across networks; widely used for formatting and transmission of data on the world wide web.

• Any other port numbers you may have selected to use, for example if you have changed the Image Server's port from its default port number (80) to another port number.

When using NetEVS, the following ports must be open for data traffic on your network:

• Port 21 (outbound): Used when recording servers listen for FTP information; some devices use FTP for sending event messages. FTP (File Transfer Protocol) is a standard for exchanging files across networks.
   
• Port 25 (inbound and outbound): Used when recording servers listen for SMTP information. Also, some devices use SMTP (e-mail) for sending event messages and /or for sending images to the surveillance system server via e-mail. SMTP (Simple Mail Transfer Protocol) is a standard for sending e-mail messages between servers.
   
• Port 80 (inbound and outbound): While not directly used by NetEVS, port 80 is typically used by the IIS (Internet Information Services) Default Web Site for running the NetEVS Management Server service.
   
• Port 1024 and above (outbound only): Used for HTTP traffic between cameras and servers.
  NOTE: The following ports above Port 1024 need to be open for both inbound and outbound traffic.



• Port 5432 (inbound and outbound): Used when recording servers listen for alert socket/TCP information; some devices use TCP for sending event messages.  



• Port 7563 (inbound and outbound):  Used for handling PTZ camera control commands, and for communication with access clients.
   
• Port 8844 (inbound and outbound): Used for communication between failover servers.
   
• Port 9993 (inbound and outbound): Used for communication between recording servers and the Management Server.
   
• Port 11000 (inbound and outbound): Used by failover servers for polling (i.e. regularly checking) the state of recording servers.
   
• Port 12345 (inbound and outbound): Used for communication between NetEVS and NetMatrix recipients.
   
• Any other port numbers you may have selected to use. Examples: If you have changed the IIS Default Web Site port from its default port number (80) to another port number, or if you have integrated NetDVMS servers into your NetEVS solution, in which case a port must be allocated for use by the NetDVMS Image Server service.

Top

5. What is the Universal Driver?

The Universal Driver is able to detect any device that responds to ARP requests, however this is
not enough – each device must be configured before video/audio can work.

API documentation and/or using tools such as WireShark to ‘sniff’ the specific device are
necessary in order to set up the device using the Universal Driver.

For more information please see our Unversal Driver PDF.

Top

6. What hardware should I use for my NVR?

Background: When recording video…you truly can't do more with less! ONSSI has performed extensive testing with our NVR software and established recommended hardware platforms that we strongly ask all users to follow closely.

After you have calculated your total frame for your Server / Workstation platforms we strongly recommend adding an additional 10 percent for the HDD storage space and 20 percent for the CPU processors required. This will provide you with a preferred selection of the recommended hardware

Choosing the correct hard drive configuration for your NVR system is critical. Not having adequate hardware can lead to computer sluggishness, loss of video, not getting the desired frame rates, and even hard drive failures.

Please refer to our NVR Hardware Calculator for assistance on selecting the correct hardware for your NVR.

Top

7. What is the difference between MJPEG, MPEG4 and H.264?

Background: When implementing an IP video surveillance system; the video compression utilized is very important. Some compression schemes utilize resources more efficiently while others are more suitable for evidence gathering. In the IP video industry the three primary compression codecs are MJPEG, MPEG4 and H.264.

MJPEG (Motion JPEG) is a video compression technique that compresses every frame to a preset level and then streams the compressed data. Because MJPEG is frame based if your bandwidth to the camera is limited you will continue to get frames, just at a slower rate. MJPEG is very well suited for video surveillance implementations as data sent from the camera can easily be broken down into individual frames for forensic examination.

Pro's:

• Very good compression scheme for evidence and forensic examination.
• Very low latency
• When bandwidth is limited, image quality is not compromised, rather fewer frames are sent. Easy to project bandwidth and disk space requirements.

Con's:

• Consumes more bandwidth at higher frame rates then object oriented compressions (i.e. MPEG4).
• Larger disk space requirements then object oriented compressions.

MPEG4 is an object-oriented compression. The camera detects "objects" in the frame and sends out information when there is a change in the frame. The complete frame is sent out for resynchronization after a fixed period of time.

Pro's:

• Very bandwidth efficient.
• Requires less disk space then a frame-based compression.

Con's:

• Higher latency as software/hardware needs to combine frames from the camera to display video.
• If network connection to the camera is temporarily lost, video may be lost till the next key frame is received.
• Bandwidth and disk space utilizations are hard to predict, because it is heavily dependent on the amount of motionin the camera's view.

H.264 is an object-oriented compression. The camera detects "objects" in the frame and sends out information when there is a change in the frame. The complete frame is sent out for resynchronization after a fixed period of time.

Pro's (versus MPEG4):

• Better Quality at the same bit rate.
• Or the same quality as MPEG4, but using a lower bit rate.
• Lower latency as well as better quality at higher latency.

Top

8. Importance of Frame Size

Background: Images larger than a 40Kb frame size (640x480 resolution) merely provides more color depth to each frame. This is something the human eye can barely detect. Since video surveillance is primarily designed to identify an object or set of objects from the position of historical review (sets of stills). The following suggestion would be suitable for most implementations.

The frame size can be configured through the Camera Settings within the Administrator. From here you select Image Quality and click Preview Image and adjust accordingly.

Top

9. What Frame Rate should I use for my cameras?

Background: Motion picture frame rate is equal to 24 FPS (Frames per Second). Since video surveillance is primarily designed to identify an object or set of objects from the position of historical review (sets of stills) full motion frame rates is not an essential requirement in almost all video surveillance implementations. By default the ONSSI program assigns a frame rate of 8 for each camera added. In most cases a lower frame rate is ideal.

Example FPS's are (2 or 3 FPS for parking lots) with a wide Field of View, (5 FPS for a school hallways) and (12 to 15 FPS for a cash register).

Remember that camera positioning is important: If traffic to the camera position is mostly vertical (towards the camera) then this requires fewer FPS since the cameras will gather a lot more detail as it gets closer. (i.e: person walking down hallway towards a camera). If traffic to the camera position is horizontal (from left to right or right to left) then this may require a bit more FPS so that the cameras capture more frames in acquiring detailed images of the objects.

Please keep in mind that unnecessarily increasing the frame rate merely wastes Network Bandwidth, CPU processing power and Hard Drive space. To modify the frame rate on each camera, go to the Cameras Settings page within your NVR Administrator.

Top

10. Proper use of archiving?

Background: Most surveillance implementations require historical archiving, and OnSSI's products support this feature in an easy and simple way. The benefits include better disk management and better database maintenance options. The database has a capacity of 600,000 records or 40 GB of data, archiving starts a new database and allows for unlimited retention of video as long as there is disk space capacity.

While the user can control video storage by setting the number of Min/Hours/Days after which video content is deleted (this is done by selecting 'Delete records older than' in the Camera Settings page within the Administrator, this is not a recommended control method, since the number of frames may still exceed 600,000. Once each database reaches this 600,000 frames limit the system will begin to delete the oldest image and record the newest image (FIFO).

In almost all cases the proper software configuration is to leave the cameras database to it's default (Max records in database) and to enable archiving for the amount of days required.

Please use our Hardware and Storage calculator to help you in determining the proper amount of storage your system shall require.

Top

11. Where should I record Live Video?

Background: Data streaming such as video transmissions places extremely large demands on your computers resources. When determining if your system/network is being utilized properly, it is crucial that your live video recording location be setup correctly.

Although video can physically be recorded anywhere it is highly / strongly recommended that the live video be recorded to local/physically attached drives. Writing live video to 'Network Attached Storage' devices can lead to major operational problems as the system needs to write video in real time and network-attached drive(s) are subjected to network latency which can cause database or even system crashes.

Please Note: It is perfectly fine to archive the video to any storage device such as a NAS or SAN or any other network drive.

Top

1. I received an error 1920 when installing the software, what does this mean?

Background: Error 1920 means the ONSSI Image Server is not able to start because:
a) The Port the Image Server wants to run on is already in use.
b) The service does not have adequate permissions to run on this machine.

To resolve this error, do the following:

• With the error message remaining on the screen go to the desktop and locate the Image Server Administrator. Open it and change the port number to 8081 (port rarely in use). Click retry on the error message.
• If error message remains, we need to change the login rights of the ONSSI Image Server. To do so, open up your computers services page (start >> run >> services.msc) and locate the ONSSI Image Server.

• Right click on the service and select properties.
• Select the Log On tab and click This account.

 



 

• Using the browse button locate and select the user who is currently logged onto your machine.

Note: The logged in user MUST have ADMINISTRATIVE rights to the machine.

• Click retry on the original error 1920 message.

If the error remains please contact ONSSI support for additional assistance.

Top

2. How do I upgrade my software?

Background: In order to take advantage of the latest software available, it is often necessary to perform an upgrade on your NVR software. Below we will discuss how to accomplish this.

Note: This only applies to upgrades done from one version of a software to the next (i.e. 6.0 to 6.5), not from one software to a different one (i.e. NetDVR to NetDVMS).

• Open the Add/Remove Programs dialog in the Control Panel.
• Select your ONSSI NVR, and click Change/Remove.If you want to keep your existing configuration (recommended) and/or databases, make sure the Remove Database Files and Remove Registry Settings options are unchecked. Then click OK.

• If your NVR installation also has the Download Manager installed, remove this as well.
  
• Click Finish and close the Add/Remove Programs dialog and the Control Panel Window.
• Click the Install Software button located on the software installation menu and proceed through the installation.

Example of Installation menu

• Start up the software, all of your old settings will be there, you are now done doing the upgrade.

Important Notes:

• If running the Content Analytics VAP on the NVR machine, please reboot after the upgrade has been completed.
• After upgrading make sure to change the user login rights for the ImageServer and Recording Server Services if using a network drive for Archiving.

Top

3. I installed my software as a 30 day trial, how do I license it?

Background: Before purchasing the NVR software many times customers will install the software as a 30 day trial to test out the functionality. Below we will discuss how to license the software once a purchase has been made:

• Open up your software Administrator, and click on the icon located in the top left corner.

• Select “About Adm..”, on the next page the top line fill in your new NVR Software License Code.
• If the 'Software License Code' field is greyed out either a) pause the Recording Server from the 'Service Manager' or b) shutdown the Monitor Program if the software is installed as an application.

• The software will now prompt you to restart the software, go ahead and do that. Re-start the Administrator,and select ‘import DLK’s’, and browse to the DLK file that has been provided to you. If you do not have the DLK file you can request it at: Software Registration and Device License Keys .

Top

4. I added a new camera but it is not available in the NetGuard Client software

When adding a new camera, please ensure the following steps have been taken to gain access to the camera in the NetGuard Client software.

After adding and configuring the new camera in the NVR Administrator program, you must also make sure that the User(s) has permission to access this camera.

Launch the ‘Image Server Administrator’ and go to the ‘User Administration’ section.
In this section you can select ‘Full access for all users’, which allows access to all cameras and options in the NetGuard software, or, you can select ‘Restrict user access’, which allows selecting specific cameras and options for each user.

If ‘Full access for all users’ has been selected, all the cameras added in your NVR Administrator will be available to all users created in the ‘User Setup’.

If ‘Restrict User Access’ is selected , click on the ‘User Access’ button to select which cameras and options will be available for each user. Select the user using the drop down menu and then drag the desired cameras over to the right hand side. Click on 'Close' when done, and then OK to close the ‘Image Server Administrator’.

Once you have completed configuring the users in the ‘Image Server Administrator', access to the newly added camera should be available in the NetGuard client software. Launch/Login to the NetGuard client software and click on the ‘Setup’ tab. Look in the ‘System Overview’ section for the server and the available cameras. You should see the newly added camera included in the list.

Top

5. Why are certain features in the camera settings page unavailable?

Background: When the Recording Server Service/ Monitor Program are running certain features are disabled from being modified. Examples of these are; the Joystick setup page in ‘General Settings’, the cameras ‘live’ database path in that camera’s settings page’ as well as the ‘PTZ Preset Positions’ page. In order to make these options available for modifying please Pause the Recording Server service from the Service Manager in the Administrator.

Top

1. How do I check what version software I am running?

Background: When contacting OnSSI Support or when checking for the latest software version available, it is necessary to check your current software version as well as your software license code (SLC). The following describes how to accomplish this.

Open up your software Administrator, and click on the computer icon located in the top left corner.

Top

2. How to save the NVR configuration for backup purposes or to migrate to another server?

Whether migrating to a new server, or upgrading the current software, here are the steps to backup the software configuration:

Go to the c:\program files\OnSSSI\’NVR’ directory (NetDVMS/NetDVR/ProSight SMB). This is the default installation location, if the software installed elsewhere please go to that folder location.

• Make a copy of all *.ini files, such as the SurvPro2.ini file
• Make a copy of all *.sch files, such as record.sch
• Make a copy of the RemoteClientViewGroups folder
• Make a copy of the NetGuardEVSClientViewGroups folder

Also go into the ‘Devices’ folder located in the same directory and copy the devices.ini file. This file would be placed in the same location on the new server.

After finishing the new installation, make sure the Administrator is closed and copy in the above listed file and folders. Open the Administrator and your configuration should now be available.

Top

3. How to setup and test a Generic Event?

Important:  Generic Events can be easily triggered by any program (i.e. access control) that can open a raw socket connection and pass on data. Note: It is also important to understand that the Generic Event port waits for the TCP socket connection to disconnect/terminate before the string is processed.

For testing purposes only, we will demonstrate how to test it with a telnet session.

Make sure the Client Application is running, and that the camera for which the event notification was defined is displayed in the current view.

• Click on the Windows Taskbar 'Start' button and select “Run”
• Enter the command: telnet localhost 1234. Click the “OK” button.

You can also test the event from a remote PC; in that case, start telnet on the remote PC by entering the IP address of the NetDVMS server instead of “localhost”. Example: telnet 192.168.1.50 1234.

• Enter the event substring that you defined in the Administrator. In our example we used ‘button’. You might experience echo, which repeats some of the characters, as seen above.
• Close the telnet window by clicking the “X” button. You must close the telnet window for the socket connection to terminate and the command to be sent.
• Observe the view of the camera in the Client Application.
• Verify the event notification indicator is on. (Yellow indicator for NetGuardEVS & Purple indicator for Ocularis Client Lite)

Top

4. How do I access my Client viewing software?

Top

5. How to Disable User Access Control (UAC) in Windows Vista

In order to run OnSSI software on a Windows Vista computer you will need to disable User Access Control (UAC).

• Go to Control Panel - User Accounts - User Accounts.
• Click on "Turn User Account Control on or off".

• Uncheck the "Use User Account Control (UAC) to help protect your computer" check box and click OK. You will be prompted to reboot the computer.

Top

6. How to add ImageServer Slaves?

In larger installations often times more than one OnSSI NVR recording system is necessary. In order to provide seamless integration between systems a Master/Slave Relationship is needed. After the Master/Slave relationship has been setup login to the Master ImageServer to access all of the different NVR systems and their cameras.

• Select which NVR machine should be the master (headend)
• Go to the Master machine and launch the ImageServer Administrator
• Under the Master/Slave Setup Check the 'Designate as Master Server' checkbox
• Click the Slaves button
• When the 'Slave Administration' window opens click 'Add Slave'
• Enter in the DNS Name or IP Address of the Slave machine as well as the port the Slave ImageServer is running on
• Repeat step 6 for each NVR Slave to be added
• Exit the ImageServer Administrator to update the configuration.

 



 

• Important Note: When logging into the Master ImageServer via the NetGuard Clients the Master ImageServer will also attempt to login the user into the slaves. Therefore whatever username/password credentials the user specified for the Master ImageServer must also be valid for the Slaves to be able to login successfully
• Log into the Master ImageServer via the NetGuard Client, go to the Setup Tab, note the different ImageServers.
• Drag in cameras from different NVR machines into the views as needed.

Note about Slaves and their communication with the Master:

If the Image Server is set as a Slave, and video will be accessed remotely (such as the Internet) as part of a Master/Slave relationship, outside access must also be enabled in the Slave’s Image Server Administrator. A path must also be created through the firewall/router to each individual Slave as well as to the Master.

Information on Master/Slaves and how they communicate

• When a client logs into a Master Image Server, the Master tries to authenticate to the Slave. Assuming the login is successful, the configuration from the Slave is then passed to the client.
• When the client tries to view video from a Slave, the Slave requests a token from the Master and then provides the video stream. If the Slave cannot get the token from the Master, video will not be provided.

In a situation where the Master can reach the Slave, but the Slave cannot reach the Master (i.e. the Slave is on a Public IP and Master is on a Private IP), video will not be allowed to stream as the Slave cannot successfully get a token from the Master. If however the Master Image Server has ‘Outside Access’ enabled then the Slave will try that IP:port to request the token.

Top

7. How to setup a Wireshark capture?

Using Wireshark to analyze network communication between a camera and your NVR server

Wireshark is a Network Protocol Analyzer and can be used to see the communication between 2 points on the network, particularly from your server to a camera’s IP address.

To perform a Wireshark capture, please do the following:

Open Wireshark and from the Menu Bar on top, click on Capture - Interfaces. This will show you the available Network Interfaces.

Click on the options button next to the network interface that is being utilized on your system. This will open the Wireshark Capture Options dialog box.

In the “Capture Filter” section, type in: Host (space) then the IP address of the camera.

NOTE:  Before you click on the Start button to enable the capture, please make sure that there are no browser windows open. When using Wireshark to capture communication between the camera and the server, if there are browser windows open you may receive additional/unwanted data in the capture.

Any packets being sent between the device and the server will be captured by Wireshark.

Save the captured data as a .pcap file.

Top

8. How to use an Event to Trigger NetMatrix Video?

Open the NVR Administrator and select the NetMatrix option.

The ‘NetMatrix Configuration’ window has two tabs; the ‘Config’ tab lets you define individual computers on which it should be possible to view NetMatrix-triggered content (such computers are known as NetMatrix Recipients), the ‘Event’ tab lets you associate the triggering of an event with a NetMatrix Recipient. Such events include, a camera input, VMD or a Generic Event.

Add a NetMatrix Recipient:

• Click on NetMatrix in the NVR Administrator
• Enter a Name for the Recipient, IP Address of NetMatrix Machine, Port the NetMatrix is listening on and the NetMatrix Password.

 



 

Note: If the NetMatrix is running in the NetGuardEVS, click the ‘NetGuardEVS’ checkbox.

 

• Repeat Step 2 for additional NetMatrix Recipients.

Associate an Event to a Camera:

In the ‘Event’ tab you will see the defined NetMatrix Recipients.

• Right Click and choose the triggering event
• Right Click on the Event and choose ‘Connect’
• Right Click on ‘Connect’ and select the Camera you want to ‘send’ video to

Note: If a red exclamation mark is displayed (!), this means that the association for the event or the action was not completed.

The next time the event is triggered, a NetMatrix alert will be sent to the NetMatrix Recipient and video will be displayed.

Top

9. How to configure the 'Enable Outside Access' in the Image Server for remote NetGuard Clients?

If there are NetGuard users connecting via the Internet or WAN through a firewall, it may be necessary to configure ‘Enable Outside Access’ in the ImageServer to tell the client software the path to connect to video.

To ‘Enable Outside Access’:

• Open the ImageServer Administrator
• Check the 'Enable Outside Access’ box
• Enter in the ‘Outside IP Address', such as the public address of the firewall
• Enter in the ‘Outside Port’, the port the Firewall is forwarding to the local Image Server

When using ‘outside access’, the router or firewall must be configured so requests sent to the Outside (public) IP address and port are forwarded to the inside (local) IP address and port of the server running the Image Server service.

Note about Slaves: If the Image Server is set as a Slave, and video will be accessed via the internet as part of a Master/Slave relationship, outside access must also be enabled in the Slaves Image Server Administrator as well as a path must be created through the firewall/router to each individual slave as well as the master.

Top

10. How is the archive folder structured?

Top

11. How to setup a Peformance Monitor Counter?

If using Windows Vista/2008 Server click here.

• To run the Performance monitor, click on Start – Run and type in perfmon.exe then hit enter.
• The Performance Monitor will open displaying a graph of the counters that are currently being monitored. Highlight the each counter and delete them.
• Click on the [+] sign next to ‘Performance Logs and Alerts’, then Right-click on ‘Counter Logs’ and select ‘New Log Settings’ then give the counter log a name, i.e. ONSSI Counter.

 



 

• Click on the ‘Add Counters’ button and for ‘Performance object’, choose Process.
• Then in the ‘Select counters from list’ choose Thread Count, Handle Count, Virtual Bytes and Working Set, (hold the CTRL key on the keyboard to select multiple counters).
• Then in the ‘Select instances from list’ choose RecordingServer and click on Add then close.
• Click on the Log Files tab on top and change the Log File Type to ‘Text File (Tab delimited)’.

 



 

• Make note of where the file will be saved to. As a default, it will save the files to the ‘C:\Perflogs’ folder, however, you can click on Configure to specify a location.

Top

12. How to configure NetEVS to Archive to a Mapped Drive?

The following are pre-requisites before setting up the NetEVS to Archive to a Mapped Drive:

• The credentials used to run the NetEVS Recording Server Service (‘VideoOS Recording Server’ Service) must match exactly a username and password defined on the mapped drive machine.
• When defining the archive in the NetEVS – Manager, you must use the UNC path and not the mapped drive letter.

Top