---
title: "RIG AntiVirus and Windows Update Guide"
slug: "rig-antivirus-and-windows-update-guide-1"
updated: 2022-06-06T21:00:47Z
published: 2022-06-06T21:00:47Z
canonical: "support.nectarcorp.com/rig-antivirus-and-windows-update-guide-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.nectarcorp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# RIG AntiVirus and Windows Update Guide

## Overview

This document discusses Nectar Best Practices for running AntiVirus (AV) software and applying Windows updates to the Nectar Remote Intelligence Gateway (RIG).

### About this Guide

This guide provides the following:

##### [Best Practices](/docs/rig-antivirus-and-windows-update-guide-1#_bookmark9)

##### [IP Ports/Protocols](/docs/rig-antivirus-and-windows-update-guide-1#_bookmark13)

### Audience

This guide is intended for Nectar partners and engineers who have system administration access and technical knowledge of the Nectar Unified Communications Management Platform (UCMP).

### Supported Software Versions

- Nectar UCMP v8.7

### 

## Best Practices

This section includes the following:

##### [Antivirus Protection](/docs/rig-antivirus-and-windows-update-guide-1#_bookmark10)

##### [Windows Updates](/docs/rig-antivirus-and-windows-update-guide-1#_bookmark11)

### Antivirus Protection

Nectar recommends installation of a quality antivirus product on the appliance. Nectar recommends excluding the Apps/ directory from real-time scanning. At a minimum, for performance and data integrity, the RigDB directory MUST be excluded. Though the installation directory may vary, this is the default:

#### Apps/nectar/rigDB

### Windows Updates

Nectar recommends manually installing Windows Updates during a monthly or quarterly service window. This is preferred over automatic updates to avoid any server reboots interfering with an active Nectar process, potentially corrupting the database and/or generating false alarms.

Follow these steps to apply Windows updates **when the Services’ names are known**:

1. Connect to the RIG as you would normally.
2. Navigate to **RIG > Admin > Command Line**.
3. Issue the following command to stop the **Backup** Service:

**net stop**

***Note***

*The Backup RIG name may differ based on partner branding.*

1. Issue the following command to stop the **Primary** Service:

**net stop**

***Note***

*The RIG name may differ based on partner branding.*

1. Close the connection to the RIG.
2. Apply the Windows updates.
3. Restart the server as Windows requests.

The Nectar services will automatically restart after the server reboots. You can view this within Windows Services.

***Note***

*Nectar client access is the last item to become operational. Depending on the system size and database compression settings (how long historical data is stored), it may be 10-15 minutes before you can log into the Nectar application.*

Follow these steps to apply Windows updates **when the Services’ names are unknown**:

1. Connect to the RIG as you would normally.
2. Navigate to **RIG > Admin > Command Line**.
3. Issue the following command:

#### net start

The system will return a list of possible services. Usually the service contains the text **RIG** in its name.

1. Note the name of the Primary and Backup Services.

***Note***

*If there is a space in the Service name, you must quote the Service name, for example:*

***net stop “my service RIG”***

1. Issue the following command to stop the **Backup** Service:

**net stop**

***Note***

*The Backup RIG name may differ based on partner branding.*

1. Issue the following command to stop the **Primary** Service:

**net stop**

***Note***

*The RIG name may differ based on partner branding.*

1. Close the connection to the RIG.
2. Apply the Windows updates.
3. Restart the server as Windows requests.

The Nectar services will automatically restart after the server reboots. You can view this within Windows Services.

***Note***

*Nectar client access is the last item to become operational. Depending on the system size and database compression settings (how long historical data is stored), it may be 10-15 minutes before you can log into the Nectar application.*

## 3.IP Ports/Protocols

The Nectar RIG requires access to the following IP ports/protocols:

###### SRSTP (TCP:443)

###### HTTP (TCP:80)

###### NTP (UDP:123)

###### DNS (UDP:53)

###### SMTP (TCP:25)

These ports are in addition to the ports required for monitoring/administering client devices and applications. For more information, see the *Ports and Protocols Guide*.