In the Remote Ops Mgr deployment guide, you'll notice we've given guidance to help you plan your Remote Operations Manager deployment. A standard Remote Ops Mgr deployment is very similar to a multiple server, single management group Ops Mgr deployment, but there are a few differences I want to point out.
First, you'll need a least a Root Management Server to create the management group. For fault-tolerance you can cluster the Root Management Server. You'll also need a database server which also can be hosted on a SQL 2005 cluster for fault-tolerance. Next, you'll need to use an internet-facing gateway management servers for communication between the root management server and each Essentials server at your customer sites. Again, to provide fault tolerance you can use multiple internet-facing gateway management servers, configuring the Essentials server to failover from a primary gateway to a backup in case of failure.
Optionally, you can install a web console server to provide live monitoring views for your customers if they desire this capability.
To scale your Remote Ops Mgr deployment, you'll need to add additional management servers and internet-facing gateways. A management server can monitor a maximum of 2000 agents; once your Remote Ops Mgr management group reaches this threshold, you'll need to add additional management servers. An internet-facing gateway can monitor a maximum of 530 agents (which is also the maximum number of computers that can be managed by one Essentials server.
Take the example that you are managing 20 customers who each have 200 computers. To support this Remote Ops Mgr deployment, you'd need at least two management servers and eight internet-facing gateway servers, but for fault-tolerance you should consider having additional management servers and gateways available as failover servers in case of an outage.
To reduce the amount of hardware needed to support the required gateway, you could run the gateway management servers in a virtual server. Since Remote Ops Mgr is licenses through the Service Provider Licensing Agreement, adding additional management servers does not increase the incur additional licensing costs.
Maximum number of agents that can be monitored through one management server: 2000
Maximum number of agents that can be monitored through one gateway management server: 530
Maximum number of agents managed by an Essentials server in service provider mode: 530 (30 Windows Servers and 500 Windows clients)
To assist with modeling the required infrastructure for a Remote Ops Mgr deployment, you'll also be able to use the soon-to-be-released System Center Capacity Planner to plan for your Remote Operations Manager deployment.
"Management Servers" (Management Server 1, Management Server 2) scale to 2000 agents?
How does the Root Management Server scale, can this role be combined with Management Server above?
Gateway Server 1 & 2 appear to be outside of the MSP firewall, but I assume would be in a DMZ scenario.
Can the reporting server be combined with the other databases?
What is the scaling limitation on the gateways servers, obviously a software limitation(?).
From a licensing perspective, what is required on the MSP side, is it all SPLA (Windows Ops Mgr, SQL)? What is included in the SPUR for Remote Ops Mgr for the MSP, all needed components of Ops Mgr? In other words what are our usage rights for the $x/per client $x/per server.
Yes, the Root Management Server is a Management Server and can manage up to 2000 agents.
Gateway 1 & 2 could be in the DMZ
Yes, the reporting server database can be installed on the same SQL server, but you should refer to the Operations Manager 2007 deployment guide for full guidance.
With Remote OpsMgr 2007 RTM a gateway can manage up to 530 agents.
On the MSP side, Remote Ops Mgr is licensed through SPLA, SQL and the Windows Server OS is not. Please check with your MS account rep to read the latest SPUR.
Remote Operations Manager 2007 is a partner solution to provide remote managed services to small and
Dustinj i have a question:
Must the Gateway be a member of the Domain?
This is not clear for me?
The internet-gateways should not be a member of any domain.