Did you know Operational Insights no longer requires Operations Manager? In this post I'll guide show you how to install and connect an agent to Operational Insights, and show you some of the improvements we've made to it in the past weeks.
So here’s the deal:
You can still connect to Operational Insights through Operations Manager; that hasn’t changed. The difference is that those of you that don’t have SCOM, or don’t wish to connect through it, can now connect servers directly to Operational Insights.
All you need is a computer running Windows Server 2008 SP1 or above.
…And here’s what you need to do:
1. Download the agent setup file from the Operational Insights portal. You can find the download file under "Servers and Usage"–> "Servers connected directly"–>"Configure"
You'll return to this screen during agent installation to copy your Workspace ID and Key.
2. Install the agent in one or more computers: You can install agents one by one, or install in bulk using a script.
After agreeing to the License agreement and choosing your install folder, select that you want to connect the agent to Microsoft Azure Operational Insights.
In the next screen you will be asked for your Operational Insights workspace ID and workspace key.
Your workspace ID and key can be found in the same screen where you download the agent file . We've also added a copy button to each key so you can copy these to your clipboard easily and avoid typos.
In the same installer screen you can click "Advanced" to optionally setup your proxy server and provide authentication information. Click Next to get out of the proxy configuration screen and return to the workspace information screen.
When you click Next, your workspace ID and key will be validated. If we find any errors in this information you can hit Back to make any corrections. Once we confirm your workspace ID and key are correct, you can click Install to complete agent installation.
If you ever need to re-configure your agents, you can re-configure them manually by going to the Control Panel and searching for "Microsoft Monitoring Agent".
In the properties window you will find an "Azure Operational Insights" tab, where you can update your workspace key and ID information. From this screen you can also disconnect an agent from Operational Insights, by unchecking the "Connect to Azure Operational Insights" check box.
You can also configure your agents by using a script like the one below:
$healthServiceSettings = New-Object -ComObject 'AgentConfigManager.MgmtSvcCfg'
$healthServiceSettings.EnableAzureOperationalInsights('workspace id','workspace key')
3. The server summary count in "Servers & Usage" will start updating immediately after the agents communicate with the service. Remember to add Intelligence Packs if you haven't already and note: The Capacity Management and Configuration Assessment IPs are not currently supported by servers connected directly. You’ll still need SCOM if you’d like to use these IPs.
We’re working on making this feature even more easy to use. If you have any feedback, don’t forget to submit it through the Feedback button within the Operational Insights portal.