Microsoft Office Tutorials and References
In Depth Information
Monitoring targets
Operators
Report users
Monitoring targets
We identified the technologies that need to be monitored earlier in this chapter. We now
need to identify the actual monitoring targets. Monitoring targets are the actual things we
want to monitor. For example, these can be devices, servers, operating systems, and
network segments. Anything that can disrupt access to Office 365 should be a monitoring
target. Sometimes, a monitoring target might even be a sub-component of a system, such as
a server's hard disk. After all, if a server is dependent upon a disk, we need to monitor the
disk to ensure the disk does not ill up, thereby resulting in a server outage.
Deploying the SCOM infrastructure and importing the
Office 365 Management Pack
In this section, we'll take you through the deployment of System Center 2012 Operations
Manager. We will assume you have an existing server running Windows Server 2012 with
SQL Server installed, and thatthe SQL Server and SQL Server Agent services are running
and set to start automatically. The server should be a member server in the AD domain that
is associated with your Office 365 tenant.
Installing the System Center 2012 Operations Manager
Service Pack 1 prerequisites
The following list shows the prerequisites that must be met prior to installing Operations
Manager. Most, but not all, of the roles and features are installed by means of the Server
Manager Add Roles and Features Wizard:
IIS with the following role services:
IIS 6 Metabase Compatibility
Windows Authentication
Request Monitor
HTTP activation under the .NET Framework 4.5
ASP.NET 3.5 – This is installed through Microsoft Updates on Windows Server
2012, not through the Add Roles and Features Wizard
Microsoft Report Viewer 2010 Redistributable Package
Search JabSto ::




Custom Search