Microsoft's Operations Management Suite is a cloud-based service, so there is almost nothing to install except...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
management agents, if necessary. It integrates with other management systems, such as Microsoft System Center. The majority of the process involves creating an account and management workspace, and then connecting the elements that you want to manage.
Start by signing into Microsoft Operations Management Suite (OMS) through the "Sign in" button or "Try for free" button at the bottom of the page. Log in using your existing Microsoft account, such as your Outlook account, or other business account. Now, enter a unique workspace name -- this workspace holds your management data and allows organization of teams and data. Finally, link the workspace to a new or existing Azure subscription, if desired.
Next, select the services, or intended tasks, and connect the desired servers to be managed by OMS. This usually starts by clicking "Get Started" in the overview tile. Administrators can select from a variety of Microsoft OMS choices that include site recovery, malware assessment, backups, system update analysis, automation and change management. Simply check any desired tasks and click "Add Selected Solutions" to continue.
Now, choose how to connect OMS to your environment. This can be accomplished through System Center Operations Manager (SCOM), such as SCOM 2012 SP1 or SP2, your Azure account setup with a Windows or Linux VM extension, or manage servers using agents -- omitting System Center. Administrators can download and install management agents on desired x64 systems, but agents require Windows Server 2008 SP1, Windows 7 SP1 or higher. Agents can be installed in bulk using scripts or other software distribution tools. You'll need the Azure Operational Insights workspace ID and key -- where you downloaded the agent file -- to complete the installation, and it may take up to 10 minutes for all agents to communicate with OMS.
Once the connection is established, you must create at least one log to capture the management data. Typical logs include Internet Information Services web servers or event logs for information, warnings, errors and other events.
Administrators can also opt to connect systems to Microsoft OMS using SCOM, rather than the OMS portal. This is normally accomplished by logging into the SCOM console, choosing Administration and drilling down to Operational Insights Connection. Selecting the "Register to Operational Insights" link will start a registration wizard, and administrators can then click "Add a Computer/Group" and add selected computers or groups to Operational Insights under Azure and OMS. It may take up to 10 minutes for systems to connect and share data with Microsoft OMS.
How OMS integrates with management systems
How to use SCOM 2012 to manage Azure
What's new in System Center 2016?
Dig Deeper on Windows Operating System Management
Related Q&A from Stephen J. Bigelow
VSAN 6.6 and 6.6.1 boast new features, such as vSAN Configuration Assist, integration with vROps and a streamlined upgrade process to improve storage...continue reading
For enterprises that require powerful security and resiliency, vSAN 6.6 presents an array of features, such as encryption and stretched clusters, to ...continue reading
Certain versions of the Linux kernel offer more complete and uniform support for paravirtualization than others due to the open source nature of ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.