Welcome to Remote Management Console 2

Managing Intego Software on Multiple Macs

Companies, schools and other institutions have security policies that must be applied and enforced. Intego’s Internet security software provides robust protection from the many dangers of the Internet: protection from viruses and malware, network attacks, unwanted content, and much more. Institutions with large numbers of Macs using Intego software will benefit from centralized administration of software, allowing administrators to establish and deploy their security policy quickly and easily.

Intego Remote Management Console 2 is a software administration tool designed for managing Intego software on multiple Macs. Remote Management Console 2 allows administrators to create and load policies, configure individual settings and functions, and make changes to Intego programs on all managed computers quickly and easily. Policies for these programs can be managed for individual workstations or for groups of workstations.

Remote Management Console allows administrators to manage and configure Intego security software on any number of Macs over a local network or via the Internet. The administrator can contact client computers via a Remote Management Console server and set policies for the following programs:

Deploying Intego Software on Multiple Macs

If you manage a large number of Macs, it's good to know that deploying Intego software on your managed computers is simple. Intego has a white paper called Intego Enterprise Software Deployment Guide that you can download and use to prepare and manage your deployment.

Remote Management Console 2 Features

Remote Management Console 2 lets administrators:

Installing and Setting Up Remote Management Console 2

Remote Management Console 2 consists of four components:

Remote Management Console 2's Console, Server and NetUpdate Proxy components require Mac OS X 10.5 or later, or Mac OS X Server 10.5 or later, running on either a PowerPC or Intel-based Mac. Client components require Mac OS X 10.5 or later, on either PowerPC or Intel-based Macs, and are not supported on Mac OS X Server.

Remote Management Console works with the following versions of Intego software:

Preparing for Installation

Installation of Remote Management Console involves several steps, as you install the different components mentioned above and prepare your workstations for installation of Intego software. These steps are as follows:

  1. You first install the Server component. It is recommended to install the Server component on a computer that is always on and is accessible to all the managed workstations.
  2. You then install the Console component on a Mac which will be used by an administrator.
  3. (Optional) If you want to use a NetUpdate proxy, you can install the NetUpdate proxy component on any Mac. It can be the same computer that runs the Server component or another one. The Mac with the NetUpdate proxy component must be able to connect to the Internet to access the Intego NetUpdate server, and must be accessible to other computers running Intego software so they can access the installation packages for program and filter updates that it hosts.
  4. You use the Remote Management Console 2 application to configure the Server.
  5. You deploy the Client component and the appropriate Intego software on managed workstations.

Installing the Server Component

To install the Remote Management Console 2 Server component, mount the Remote Management Console 2 disk image. If you are not logged in on the server, copy the Remote Management Console Server.pkg installation package to the server. On the server, double-click on the Remote Management Console Server.pkg installation package, then follow the instructions displayed by the Installer.

You can do this using Apple Remote Desktop, or via the command line, if you wish to perform a remote installation.

Installing the NetUpdate Proxy Component

To install the NetUpdate Proxy component, mount the Remote Management Console 2 disk image. If you are not logged in on the server, copy the NetUpdateProxyServer.pkg installation package to the server. On the server, double-click on the NetUpdateProxyServer.pkg installation package, then follow the instructions displayed by the Installer.

You can do this using Apple Remote Desktop, or via the command line, if you wish to perform a remote installation.

Installing the Console Component

The Console component is an application that requires no special installation process. Open the Remote Management Console 2 disk image and drag the Remote Management Console application into the /Applications folder on the Mac where you wish to use it.

Connecting Remote Management Console 2 to Remote Servers

For Remote Management Console to be able to connect to the server, the server must be able to accept connections through port 18133 TCP. For workstations to be able to connect to the server, the server must be able to accept connections through port 18134 TCP. If servers use a firewall, including that which is part of VirusBarrier X6, these ports must be open for the different components to be able to communicate.

Network Ports Used by Server
Connections from Remote Management Console 18133 TCP
Connections from workstations 18134 TCP

Deploying the Client Component

The Client component is installed on workstations that you manage using Remote Management Console. The deployment of the Client component is covered in the Using Remote Management Console section of this manual. Note that each time the Remote Management Console software is updated you must create and deploy a new version of the Client component.

Using the Remote Management Console Assistant

After you've completed the installation of the various components of Remote Management Console, you can launch the Remote Management Console application. The first time you do this, the Remote Management Console Assistant will display to help you complete your setup.

This assistant will give you some information about using Remote Management Console, and will help perform the setup necessary to enable the program. The Assistant presents six screens:

Introduction

The Introduction screen gives you an overview of the three components used by Remote Management Console. Make sure that you have installed the Remote Management Console Server component on your server before continuing. To go to the next screen, click Continue.

Server Address

This screen asks you to enter the name or IP address of the server on which you have installed the Remote Management Console Server component. Do this, then click Continue to go to the next screen. Remote Management Console will attempt to connect to the server.

Authentication

Enter the necessary information to create the first Remote Management Console administrator account. This is different from the accounts already on the server, but you may use the same name and password if you wish. Check Remember this password in my keychain if you want this password stored in your keychain so you don't have to enter it manually in the future.

Enter the necessary information, then click Continue to go to the next screen. Note that this screen may be different from what is shown here if you have already set up a server and are connecting to it from an instance of Remote Management Console that did not set up the server.

Note: you can choose to not enter a password when creating an account in this step, or later from the Remote Management Console application, and instead use key authentication. To learn how to use this, see Appendix: Using Key Authentication at the end of this section of the user's manual.

Serial Number

Enter your Remote Management Console serial number, then click Continue. Note that this screen will not display if you have already set up a server and serialized it.

Your serial number determines how many workstations Remote Management Console can manage. You cannot use the same serial number on more than one server; if you wish to use more servers, contact Intego for an additional license.

Client installation

The next screen lets you create a Remote Management Console Client package, that you can then install on your client computers. This package contains information allowing the clients to securely communicate with your server.

Click Continue to create this client package. You'll be asked to save this package.

After you have created this client package, you must install it on the client computers you are managing. You can do this in three ways:

Summary

The Summary screen shows you that the configuration process has been completed. Click Close to quit the Assistant and use Remote Management Console.

Updating Remote Management Console 2

When updates are available to any of the components that make up Remote Management Console 2, the Console component will display an alert. In such case, the alert will display a link from which you can download a new disk image containing the new versions of all the components. Follow the same installation instructions presented above to install the updates.

For updates, a Console > Server > Client hierarchy should be respected. When new versions are available, if it is not possible to update all clients at once, the Console should be updated first, then the Server, and finally the clients. New versions of the Console will be compatible with older versions of the Server; new versions of the Server will be compatible with older versions of the Client component.

About Your Copy of Remote Management Console

To get information about your copy of Remote Management Console 2, choose Remote Management Console > About Remote Management Console. This screen shows the version number of your copy of Remote Management Console 2.

Technical support

Technical support is available for registered purchasers of Intego products with valid subscriptions from the Intego Support page.

Appendix: Using Key Authentication

When you set up user accounts, you can choose to use passwords, but you can also use key authentication if you wish to limit access to only those users on specific computers that you have authorized. To do so, you need to perform the following operations:

  1. On the Mac where the Remote Management Console application is to be used, note the contents of the ~/Library/Preferences/Remote Management Console/console_host_key.pub file.
  2. On the server, create the following file: /Library/Preferences/Intego/Remote Management Console/Server/authorized_keys.plist. Administrative rights are necessary to do this. This is an XML file which contains associations between user names and keys.
  3. Enter the key copied in step 1 together with the user name; the file should look like this:

    4. Each key should appear only once, but the same user name can be associated with several keys, if you wish to provide access to the same user from multiple Macs.
  4. Now that the key-base authentication has been set up, you can deactivate password-based authentication on the server, if you wish. To do this, edit the /Library/Preferences/Intego/Remote Management Console/Server/UsersList.plist file and delete the PasswordHash entry and its associated <data> entry for the users for whom you have set up key authentication.
  5. Quit the RMCServer process on the server; you can do this from Activity Monitor or via the command line. The process will be automatically relaunched.
  6. From this point on, a user need only enter their user name if they are on an authenticated Mac to connect to the server; they no longer need to enter a password.


    7. Using Remote Management Console ››