When the installation starts, it will verify your Windows version to ensure it is a supported version. It also will look for the Microsoft VC++ 2010 runtime libraries, which are required to run the Universal Agent. If either of these checks fail, the installation will finish.
 
If all installation pre-requisites are satisfied, the Welcome dialog displays. Click Next to proceed to the next dialog in the installation sequence. Select Back to return to any previous dialog. Select Cancel to terminate the installation (no system changes are made until the Progress dialog displays).
 

After the Welcome dialog, the Installation Directory dialog displays. Enter the desired installation location or select it using the ... button. If the specified installation directory does not exist, the installation will create it.
 

 
In the example above, the user mode installation will reside under the C:\Users\DAN~1.MOR\AppData\Local\Temp\universal folder.

Click the Next button to display the Universal Broker Service configuration dialog.
 

 
From this dialog, you can choose to run the Universal Broker service as LocalSystem or an existing Administrative account. If the account does not exist, the installation will not issue an error here. Instead, the installation will fail when it attempts to create and configure the Broker service.
 
The Universal Broker service's display name and service name also can be specified from this dialog. The installation will ensure that the service name is unique.
 
The port upon which the Universal Broker service accepts incoming connections is specified in the Listen on port field. Note that the installation will not check whether another process is already accepting incoming connections over the specified port. It is your responsibility to ensure that the port is available.
 
The value specified here is used to set the service_port option in the Universal Broker configuration file, .\conf\ubroker.conf. 100 is added to this value to set the component_port option in ubroker.conf. The Broker accepts external connections over the service_port and uses the component_port to accept control sessions from local Universal Server components. Either of these values can be changed after the installation.

Click the Next button to display the OMS Server Information dialog.
 

 
The option to automatically start the OMS Server is necessary only if local or remote Universal Agents will use this OMS Server to communicate with a Universal Controller. If the Universal Agent will connect using an existing OMS Server, the option can be left unchecked.
 
If the OMS Server will run from this installation, enter a port number upon which it will accept connections from local or remote Universal Agents. This port number must be unique, and like the Universal Broker port, the user mode installation makes no attempt to confirm its availability.

Click the Next button to display the UAG Server Connection dialog.


 
Use this dialog to configure how the UAG Server connects to and identifies itself to a Universal Controller.

One or more local or remote OMS Servers can be specified. The OMS Server is the component responsible for exchanging messages between the Universal Controller and Universal Agent.

The Network ID controls how the Universal Agent is displayed in the Universal Controller. The default setting of OPSAUTOCONF instructs the Controller to assign a unique ID to the Agent. A specific value can be provided here to override this default and customize names for Universal Agents that the Universal Controller displays.

Click the Next button to display the Universal Working Folder dialog. This working folder is shared between the Universal Command Server, Universal Data Mover Server, and Universal Event Monitor Server components. If the directory does not exist, the installation will create it.
 

Click the Next button to begin the installation.
 
The installation first unloads an embedded .cab file that contains the Universal Agent application files and resources. The installation extracts the contents of this .cab file to create the Universal Agent's application directory structure.
 
After the files are placed on the file system, the installation uses values provided in the previous dialogs to configure the Universal Agent. The installation updates configuration and component definition files with these values.
 
Next, the installation creates the Universal Broker service and configures it to run via the Windows Service Control Manager (SCM). The Broker's message source also is registered with the Windows Application event log.
 
Finally, the installation creates two helper scripts: SB_ConfigSetup.bat and ubrsvc.bat.

When the installation finishes, the Complete dialog displays.
 

 
If any errors were encountered during the installation, this dialog is replaced by a Failed dialog.