Replay 4- Push Install User Guide

Installing the Replay Agent from a Replay Core

There are two ways to install the Replay Agent on a machine. The first is to copy the Replay install software on the machine itself where it is to be installed. Sometimes, it is easier to remotely install on a machine without first copying the software. This second method can be done by “pushing” the agent install to the machine. This section explains how to do that.

Before you begin to push an Agent install from the Core

Before you can push the Agent install to a remote machine, that machine must be configured in a way to accept a remote install. The prerequisites are described below.

If both computers are in the same domain:

This would be to perform a Push Agent installation from computer A to computer B.

User permissions

• Computer A – User should be in local “Administrators” group.
• Computer B – User should be in local “Administrators” group

Firewall settings

• Computer A – Can be on
• Computer B – Should be enabled “Remote Administration” rule. Please see How to enable Remote Administration.

UAC

• Computer A – Can be on
• Computer B – Can be on

If one machine is in a workgroup and the other machine is in a domain:

This would be to perform installation from computer A to computer B. Computer A in a domain, computer B in work group.

User permissions:

• Computer A – User should be in local “Administrators” group.
• Computer B – User should be in local “Administrators” group

Firewall settings:

• Computer A – Can be on
• Computer B – Should be enabled “Remote Administration” rule. Please see How to enable Remote Administration.

UAC:

Windows 2008/Vista

Go to Control Panel. Open Windows Firewall. Click change settings. Go to Exceptions tab. Check Remote Administration.

Windows 2008 R2/Windows 7
Local Policy

• Click Start, click Run, type gpedit.msc, and then click OK.
• Under Console Root, expand Computer Configuration, expand Administrative Templates, expand Network, expand Network Connections, expand Windows Firewall, and then click Domain Profile.
• Right-click Windows Firewall: Allow remote administration exception, and then click "Properties".
• Click Enabled, and then click OK.

Domain Policy

• Create new GPO in active directory or use current linked GPO, and edit it.
• Under Computer Configuration, expand Administrative Templates, expand Network, expand Network Connections, expand Windows Firewall, and then click Domain Profile.
• Right-click Windows Firewall: Allow remote administration exception, and then click Properties.
• Click Enabled, and then click OK.

Installing the Replay Agent remotely from a Replay Core

How to push the Agent install to a machine

This section will explain how to install Replay agent on a machine remotely.

• Before you begin to push an agent install from the core section prerequisites have been met.
• From the Replay Admin Console, right-click on the Core name in the tree and select Push Agent.

This will bring up a window to choose the machine where to remotely install the agent. The machine name or IP address can be typed into the Choose machine box or selected from the Available Machine(s) list.  To select a machine from the Available Machines list, click on the machine name and select the right arrow. To add a  machine to the Selected Machine(s) list that is not on the Available Machine(s) list, type the name or IP address in the Choose machine: box and then click the right arrow button to the right of the box.

The machine will then move from the Available Machine(s) list to the Selected Machine(s) list.

When you are done selecting machines, click the Next button.  The two machines from the Selected Machine(s) window in the previous wizard page will be in the list of Target Machines.

In order to install the agent on a remote machine, credentials for the machine will be supplied on this page for that machine. There are two options:

• Set Default Credentials for all machines on the list – these credentials will be used for all of the machines selected
• Modify the credentials for each machine

To set default credentials, click the "Set Default Credentials" button. Enter the default credentials and then click Ok.

To set credentials for each machine, click the Modify link in the Change Credentials column next to each machine.  The dialog will display with ‘Use default user credentials’ checked and boxes unavailable for typing.

Click this box to uncheck it and enter specific credentials.  Click Ok. If the machine is not part of a domain, enter the machine name in the domain text box.

Click the Validate link for each machine, or the Validate All link at the end of the machine list. If the credentials are validated, then a green ball with check will display. If validation fails, the ball will be red.  To get an explain of the validation failure, put the mouse pointer on the Validate link.

Click the Next button. The machines on the list that passed validation will be brought forward in the wizard for install.

Browse to the Replay license file

Check whether the machine where the agent is being installed should be booted automatically. Check this box to have it reboot. If the machine is to be rebooted manually at another time, then do not check this box.

Click the Next button.

The next wizard page will show all of the machines that are ready to have the Replay Agent installed.

Click the Install link for each machine individually, or if there are multiple agents to install, click the Install All button.

Once you click the Install link, you will see messages in the Progress column until it is complete, at which point you will see the version of the agent installed or if it was upgraded, then it will show that as the message.

Click the Show summary link and it will display details about machine the agent was installed on, the time to install, status and what version was installed. If will also log if the machine was rebooted, and if not, that it is required.

At this point, click the Finish button.

If they have been booted, the agents with Replay installed successfully are ready to be protected. To do this return to the Admin Console, click on the core name in the tree and then click Protect…