Single-Tenant Requirements

A single-tenant deployment of NetGovern Archive consist of a minimum of one master server. Worker servers (as well as additional master servers) are optional and may not be required in all deployments.

NOTE
During deployment, you will need detailed information about the items below. You should keep a record of them and have the information available during deployment.

Resource Group

You will need to create a resource group and configure networking in the geographic region where the servers will be used.

Servers

Each client needs its own resource group and each resource group needs its own master server to access the shared infrastructure. These are the minimum requirements for a functional NetGovern deployment in Azure. Additional master servers or worker servers may be required, depending on various factors including:

  • Data size
  • Data types (Microsoft SharePoint, Citrix ShareFile, Egnyte, and so on)
  • Frequency that the data is accessed
  • VM size

Virtual Machine Size

In the Azure deployment templates we have provided, certain default values for VM sizes are recommended to minimize costs. We have determined that standard HDDs are sufficient and that the B2S Backglass servers are the minimum required.

You may want to upgrade to premium SSD of the master server, as well as the pod and worker servers, to achieve an acceptable IOPS level based on the number of clients supported, volume of mail, or if you are deploying in a production environment instead of a lab. You can always change the VM size after deployment.

NOTE
The availability of VM sizes varies depending on the region where they will be deployed; some types may not be available.

NetGovern Licensing

It is imperative that you have the appropriate license before beginning deployment because it is required for operating NetGovern Archive and NetGovern Search afterwards. For example, if you plan on using Federated Search to crawl multiple on-premise and online locations, you will need to deploy at least two archive servers. Plus, if you plan to purchase NetGovern Store, it will affect how you configure storage locations during deployment. Be sure to coordinate licensing with your Support Representative.

NOTE
After deploying NetGovern Archive, you must to update your license within NetGovern Archive—see Updating Your License.

Microsoft Azure Subscription

Obtain a Microsoft Azure subscription that allows for at least 20 CPUs. You can modify the number of CPUs in your subscription at any time.

Virtual Network

Create a virtual network to host the virtual machines.

Network/UNC Share

Before you can deploy NetGovern on an Exchange or Office 365 system, you must create a network/UNC path to the file system where archives will be stored. Refer to the following article for instructions: Windows 10 Tip: Create Direct Shortcuts to Shared Network Folders.

Subnet

Create a subnet with at least 16 IP addresses in the virtual network. To avoid an IP conflict, do not use an existing subnet since the NetGovern scripts use the DHCP function of the subnet, which may create an IP conflict if the VMs are deployed in an existing subnet. You will need the subnet name and address prefix in a later step.

SMTP Server

Create an SMTP server that will communicate with Office 365 and send reports to administrators. The server should be configured to allow relaying from the master server.

Test Account

During the validation phase of deployment, you will be required to archive a test account. For optimal validation results, choose an account with a small amount of mail. This can be a new employee or a resource account, such as a conference room.

Configuration and NetGovern Search

Basic knowledge of NetGovern Search is required. It is crucial for you to understand how to configure storage as well as archiving and indexing jobs. We suggest that you consult the other guides in the IPRO Help Center. You can also arrange to have a custom online training program by contacting Support.

Exchange Service Account and Impersonation Rights

You will need to provision an account in Office 365 that has impersonation rights (also called application impersonation) enabling it to access all mailboxes in the Exchange Online tenant—see Creating a Microsoft Exchange Service Account and Granting Impersonation Rights.