Most users typically deploy the Advanced Remote Management (ARM) server in an enterprise network to facilitate the communication between the various components.

Without Load Balancer

This sample diagram is a typical deployment without the use of a load balancer.

Remote Management without Load Balancer

1. Queue RM Command

6. Request Remote Management Session URL .

2. Queuing Command to Connect to RMS

7. Admin Joins Remote Management Session

3. Confirm Command .

8. Device Joins Remote Management Session

4. Create Remote Management Session .

9. Send Commands/Get Frames .

5. Send Session URL .

 

With Load Balancer

This sample diagram is a typical deployment that includes a load balancer. For more information, see Integrate a Load Balancer to Your Deployment.

Remote Management with Load Balancer

CAP Servers contain Core Services, Application Services, and Portal Services and can be load balanced.

CP Servers cannot be load balanced with the F5 since they use built-in software load balancing.

1. Queue RM Command

6. Request Remote Management Session URL .

2. Queuing Command to Connect to RMS

7. Admin Joins Remote Management Session

3. Confirm Command .

8. Device Joins Remote Management Session

4. Create Remote Management Session .

9. Send Commands/Get Frames .

5. Send Session URL .