Freelance News Service

Installation Instructions for the Omniva Policy Manager Enterprise Edition Software

Introduction

These instructions are for use by system administrators installing the Omniva Policy Manager System software in the company network. There are three installation procedures and one enabling procedure. Test protocols are included for all but the Administrator portion of the installation. Testing of the Administrator portion of the installation is covered in the Administrator Configuration section of the Omniva Policy Manager Manual.

In these instructions, illustrations are below the applicable text. Some screens may vary slightly from illustrations.

The Omniva Policy Manager software is composed of four program packages:

• Internal server
• Client
• Policy administrator
• External Server

FUNCTION

Internal Server and Client

The Omniva Policy Manager Internal Server and Omniva Policy Manager Client are installed separately but work together to allow a set of registered users to send and receive policy-controlled messages inside the company firewall. The client software, identical to that which will be installed on all user workstations, is to be installed on a network administrator’s workstation for testing purposes.

Policy Administrator

The Omniva Policy Administrator is the user interface company network administrators use to set different sending and receiving policies used by internal groups. The policy administrator is installed automatically with the internal server and need only be enabled. Variations in policies include length of time messages last and restrictions on forwarding or other duplication efforts. The policy administrator also allows system administrators to monitor system use and make changes to the policy management system.

External Server

The Omniva Policy Manager External Server allows those outside the company firewall to access policy-controlled company email. If the company has chosen to host the external server, it must be installed. If the company has elected to have Omniva host the external server, that portion of the instructions should be disregarded. This server can be accessed by anyone, regardless of email client or computer type.

1.0 Installation of Policy Manager Internal Server Software

1.1 General Network Requirements

Before Installing

Internet Information Services (IIS) must be installed, and a Secure Socket Layer (SSL) certificate for IIS must be provided that is trusted by all client machines.

1.2 Dedicated Server

• A dedicated server must be installed in a Windows domain that trusts, for authentication purposes, all domains in which on-site company users reside. If the policy manager is to be used company-wide, the server should be placed in a resource domain that trusts all internal user domains.
• The server must be accessible via HTTPS by all users inside the company firewall. Access via a proxy server is okay.
• The server must be running Windows 2000 Server and installation of Window Service Pack 2 is recommended for optimum performance.
• The internal server must be upgraded to include the following components:

o Windows Script Engine 5.6 or later, which can be downloaded at
http://download.microsoft.com/download/winscript56/Install/5.6/NT5/EN-US/scripten.exe.

o Microsoft .Net Framework Runtime, which can be downloaded at
http://download.microsoft.com/download/.netframesdk/Redist/1.0/W98NT42KMeXP/EN-US/dotnetredist.exe.

1.3 Internal Client User Parameters

· Individual client computers using the system must be able to resolve the fully qualified domain name of the server via the Domain Name System (DNS).

• All users must be part of the same global address book in such a way that any sender’s computer must be able to discover the Windows domain Security Identifier (SID) or Globally Unique Identifier (GUID) for any internal recipient by querying the global address book. Users may be using the same Exchange site, or directory replication can be established between two or more Exchange sites.

1.4 Installation Set Up

The installer must:

• Be logged in as an administrator on the local computer being used for the installation process.
• Have available the fully qualified domain name for both the internal server and the external server. If the external server is hosted by Omniva, the name can be obtained from the Omniva support personnel assigned to assist with the installation.
• Have available the name of the existing external active domain controller.

1.5 Installing the Internal Server Software

1.5.1 Insert the Omniva Policy Manager CD-ROM into the server’s CD drive.

1.5.2 Use Windows Explorer to open the CD. Double click on Key Server to open that folder. This will display a list of files.

1.5.3 Click the Setup.exe file. Two successive boxes titled “Preparing to Install,” followed by “Welcome to the Omniva Policy Manager Server Components Setup Wizard,” will appear automatically.

1.5.4 Click Next. A dialog box titled “Network location of Key Service host” will appear. Select the radio button for Inside.

1.5.5 Click Next. A dialog box will appear titled, “External Active Directory Domain Controller.” Fill in the name of the existing active domain controller and the normal username and password information required to access the Active Directory.

.

1.5.6 Click Next. A box will appear with a space for an email address to which error messages can be sent. Fill in the desired email address.

1.5.7 Click Next. A dialog box will appear labeled Omniva Service Account Information. Filling in the requested information will allow the Omniva Policy Manager to access general user account information and add users to the Omniva Senders Group automatically.

1.5.8 Click Next. A dialog box will appear titled, “Select Installation Address.” This dialog box will allow the policy manager server components to be saved to a virtual directory other than the default virtual directory named by Omniva.

1.5.9 To check disk space, click the Disk Cost button. A chart showing available drives and their resources will appear. Close this chart to return to the “Select Installation Address” box.

1.5.10 Click Next to accept the default installation address. A scrolling window will appear containing server component information and release notes. Read carefully for information on the server installation.

1.5.11 Click Next. A box titled, “Confirm Installation” will appear.

1.5.12 Click Next. A box titled “Installing Omniva Policy Manager 4.0 Server Components,” will appear and the progress bar will fill several times.

1.5.13 Following installation, a box titled “Installation Complete,” will appear.

1.5.14 Click Close to exit the installation procedure.

1.6 Testing Installation of the Internal Server

1.6.1 Open Internet Explorer and type in http://localhost/KeyServ/service.asmx. This goes to the Omniva Service page, which has a number of diagnostic links.

1.6.2 Scroll down and click on the “Ping” link. A new Service page will appear titled, “Ping.” Click the Invoke button near the top of the page.

This will automatically ping the server you have created and will display an IE page with a string including the words “NoError.” This indicates the server has been successfully created and is ready for use.

Should the “NoError” string not appear, save a screenshot of the message that does appear and contact your Omniva representative.

2.0 Installation of Omniva Policy Manager Client Software

These instructions are for installing the client software on a systems administrator computer for testing of the system.

2.1 Workstation Requirements

· Workstation must be running on OS Windows 98, NT, 2000 (ME) or XP.

· Email program must be Outlook 98, 2000 or XP.

· Workstation must be a member of a Windows domain that is trusted by the domain in which the internal server resides. In the case of those work stations with OS Windows 98, users must log on to such a domain as part of starting up and logging in to Windows.

· Workstation must be configured such that it trusts the authority that issued the SSL certificate to IIS on the Omniva Internal Server (see General Network Requirements, above). Trust of Verisign is built into most Windows operating systems.

· Installer must log in as Administrator of the individual workstation to install the software.

· Previous versions of the Omniva Policy Manager client software should be uninstalled via the standard Add/Remove Microsoft utility accessible via Start>Settings>Control Panel>Add/Remove Programs.

2.2 Installation of the Omniva Policy Manager Client Software

2.2.1 Close all other programs.

2.2.2 Insert the Omniva Policy Manager CD-ROM into the workstation CD drive.

2.2.3 Click on Start>Program>Accessories>Windows Explorer.

2.2.4 Click on the address line pull-down and select My Computer to display disk drive choices.

2.2.5 Double click on the disk drive labeled “Omniva Installer” and open the folder marked “Outlook Client.”

2.2.6 Click on the file marked Setup.exe.

2.2.7 Click Next. A box titled Omniva Policy Server Host Name will appear.

2.2.8 Type the name of the fully qualified domain name for the internal server into the Policy Server Host Name box.

2.2.9 Click Next to display the Virtual Directory and the Port window.

2.2.10 Click Next to accept the defaults provided for the Virtual Directory and the Port. A progress box will appear, and when installation is complete, a final box will appear.

2.2.11 Click Close to exit.

2.3 Testing the Omniva Policy Manager Client Installation

2.3.1 While still signed on as Administrator, open Outlook. The first time Outlook is opened following the installation there will be a short pause while the client software caches information from the internal server.

2.3.2 Click New to create a blank email template. Note there is a new tool bar on the Outlook template with three options, plus a “Send with Policy” button below the regular “Send” button.

2.3.3 Address the message to yourself, type “Test” in the subject line, and from the new “Expiration” pull-down window, select Quick Destroy (1 Hour). Click the Send with Policy button. Go to your Inbox to ensure you can read the message. If the message does not appear normally, contact your Omniva Representative. Check the message in an hour to ensure it has expired.

2.3.4 Open another new message screen and send a message to yourself after selecting “Do not forward” from the “Allow Forwarding” pull-down menu. Click the Send with Policy button. Ensure you can read the message and that it cannot be forwarded, by attempting to forward it to another email address.

2.4 Testing the “Universal Viewing” Component

The Universal Viewing component is that part of the Omniva Policy Manager system that allows those who do not have Omniva client software installed to read protected messages.

2.4.1 Ensure the Universal Viewing software is working by repeating steps 2.3.3 and 2.3.4 above, substituting the email address of a co-worker who does not have Omniva Client software installed, but who is within the same global address book, for your own.

2.4.2 Confirm that the recipient can read the messages. For the message sent under “Do not forward,” the recipient may be required to type in their domain logon information.

If any of the tests should fail, contact your Omniva Representative.

3.0 Enabling the Omniva Policy Administrator

3.1 General

The Omniva Policy Administrator component is used to define special retention policies tailored to company needs. All of the software components of the policy administrator were installed with the internal server and it needs only to be enabled.

3.2 Enabling the Policy Administrator

3.2.1 Open MMC by clicking Start>Run, type MMC in the dialog box and click OK.

3.2.2 Click on Console of the outermost MMC window.

3.2.3 Select Add/Remove Snap-in, and the Add/Remove Snap-in Screen will appear.

3.2.4 Click Add to bring up the Available Standalone Snap-ins choices.

3.2.5 Scroll down to Omniva Policy Administrator and double click on it to transfer it to the Add/Remove Snap-in Standalone folder.

3.2.6 Click OK, then, click Close to return to the Console windows.

3.2.7 Click on Console of the outermost MMC window, select “Save As,” and save this console as Omniva Policy Administrator.

3.3 Testing Omniva Policy Administrator

See Configuration of the Omniva Policy Administrator for testing of the Administrator installation.
4.0 Installation of Omniva External Server Software

4.1 General Requirements

Before Installing

As with the internal server, Internet Information Services and an SSL certificate for IIS must be installed on the external server. Since the SSL certificate must be issued to the common name of the internal server, Omniva will provide instructions and assistance in copying the SSL certificate to the external server.

4.2 Dedicated Server

• The Omniva Policy Manger External Server must be running Windows 2000 Server and installation of Window Service Pack 2 is recommended for optimum performance.
• The external server must be upgraded to include the following components:
• Windows Script Engine 5.6 or later, which can be downloaded at
  http://download.microsoft.com/download/winscript56/Install/5.6/NT5/EN-US/scripten.exe.
• Microsoft .Net framework Runtime, which can be downloaded at
  http://download.microsoft.com/download/.netframesdk/Redist/1.0/W98NT42KMeXP/EN-US/dotnetredist.exe.
• The Omniva Policy Manger External Server must reside in an Active Directory domain outside the company firewall. Omniva engineers can assist in setting up an Active Directory domain for the external server.
• An organizational unit (OU) called Omniva External Recipients must be created in the same Active Directory and machine account of the external server must have control of the Omniva External Recipients OU.
• The external server must be accessible via HTTPS by all outside recipients. Access via a proxy server is okay.
• The external server must be able to resolve its fully qualified domain name in DNS.
• The internal server must be able to query the external server via Lightweight Directory Access Protocol (LDAP). If there is a firewall or other restriction on network traffic between these two servers, the servers must be given permission to communicate via TCP port 389.
• The external server and client machines of all recipients must be able to resolve the fully qualified domain name of the internal server so that they are directed to the external server. Setting this up involves creating DNS Views, sometimes known as split, or two-headed, DNS. Omniva engineers can assist with this configuration.
• Once the installation is complete, Omniva recommends installation of Windows 2000 Security Roll-up 1, along with the IIS Lockdown Tool, available from the Microsoft website. Use it to lockdown IIS in Application Server Pages (ASP) mode. Omniva engineers can assist with this configuration.

4.3 Installation Set Up

The installer must:

• Be logged in as an administrator on the local computer being used for the installation process.
• Have available the fully qualified domain name for both the internal server and the external server.
• Have available the name of the existing external active domain controller.

4.4 Installing the External Server Software

4.4.1 Insert the Omniva Policy Manager CD-ROM into the external server’s CD drive.

4.4.2 Use Windows Explorer to open the CD. Double click on Key Server to open that folder. This will display a list of files.

4.4.3 Click the Setup.exe file. Two successive boxes titled, “Preparing to Install,” followed by “Welcome to the Omniva Policy Manager Server Components Setup Wizard,” will appear automatically.

4.4.4 Click Next to accept the licensing agreement. A dialog box titled “Network location of Key Service host” will appear. Select the radio button for “Outside.”

4.4.5 Click Next. A box will appear titled, “External Active Directory Domain Controller.” Leave all spaces blank.

4.4.6 Click Next. A box will appear labeled Omniva Service Account Information. Filling in the requested information will allow the Omniva Policy Manager to access general user account information and add users to the Omniva Senders Group.

4.4.7 Click Next. A box will appear titled, “ Select Installation Address.” This dialog box will allow the external server components to be saved to a virtual directory other than the default virtual directory named by Omniva, if desired.

4.4.8 To check disk space, click the “Disk Cost” button. A chart showing available drives and available resources will appear. Close this chart to return to the “Select Installation Address,” box.

4.4.9 Click Next to accept the default installation address. A scrolling window will appear containing server component requirements and release notes. Read carefully for information on the server installation.

4.4.10 Click Next. A box titled, “Confirm Installation” will appear.

4.4.11 Click Next to continue the installation. A box titled “Installing Omniva Policy Manager 4.0 Server Components,” will appear and the progress bar will fill several times.

4.4.12 Following installation, a box titled “Installation Complete,” will appear. Click Close to exit the installation procedure.

4.5 Testing Installation of the External Server

4.5.1 Open Internet Explorer and type in http://localhost/KeyServ/service.asmx. This will open a link to the Omniva Policy Manager Service page.

4.5.2 Scroll down and click the Ping link. A new Service page will appear titled, “Ping.”

4.5.3 Click the Invoke button near the top of the page. This will automatically ping the server you have created and will display an IE page with a string including the words “NoError.” This indicates the server has been successfully created and is ready for use.

Should the “NoError,” string not appear, save a screenshot of the message that does appear and notify your Omniva representative.

4.6 Testing the External Server

Testing functionality

Test the functionality of the External Server by sending protected and confidential messages to someone outside the organization’s intranet who can help with the test (see section 2.3 of this instruction). Omniva recommends the person helping with the test use a stand-alone email client such as Outlook, Outlook Express, Eudora or Netscape in order to more closely simulate a corporate email recipient environment.

The recipient should confirm that A) they were prompted to register with the Omniva Policy Manager service, and B) that the message was viewable.

This concludes the installation procedures for the Omniva Policy Management Servers, Client, and Policy Administrator.