You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Scenario: Runbooks go into a suspended state on a Hybrid Runbook Worker when using a custom account on a server with User Account Control (UAC) enabled
105
77
106
78
#### Issue
@@ -411,38 +383,6 @@ This error occurs when you attempt to use a Run As account in a runbook that run
411
383
If your Hybrid Runbook Worker is an Azure VM, you can use [runbook authentication with managed identities](../automation-hrw-run-runbooks.md#runbook-auth-managed-identities) instead. This scenario simplifies authentication by allowing you to authenticate to Azure resources using the managed identity of the Azure VM instead of the Run As account. When the Hybrid Runbook Worker is an on-premises machine, you need to install the Run As account certificate on the machine. To learn how to install the certificate, see the steps to run the PowerShell runbook **Export-RunAsCertificateToHybridWorker** in [Run runbooks on a Hybrid Runbook Worker](../automation-hrw-run-runbooks.md).
412
384
413
385
414
-
### Scenario: Set-AzStorageBlobContent fails on a Hybrid Runbook Worker
415
-
416
-
#### Issue
417
-
418
-
Runbook fails when it tries to execute `Set-AzStorageBlobContent`, and you receive the following error message:
419
-
420
-
`Set-AzStorageBlobContent : Failed to open file xxxxxxxxxxxxxxxx: Illegal characters in path`
421
-
422
-
#### Cause
423
-
424
-
This error is caused by the long file name behavior of calls to `[System.IO.Path]::GetFullPath()`, which adds UNC paths.
425
-
426
-
#### Resolution
427
-
428
-
As a workaround, you can create a configuration file named `OrchestratorSandbox.exe.config` with the following content:
Azure Maps Search also provides some batch query APIs. The Reverse Geocoding Batch API sends batches of queries to [Reverse Geocoding API](/rest/api/maps/search/get-reverse-geocoding) using just a single API call. The API allows caller to batch up to **100** queries.
For more information on using Search v1, see [Azure Maps Search client library for .NET](https://www.nuget.org/packages/Azure.Maps.Search/1.0.0-beta.5). For more information on using Render v1, see [Azure Maps Render client library for .NET](https://www.nuget.org/packages/Azure.Maps.Rendering/1.0.0-beta.3).
Copy file name to clipboardExpand all lines: articles/azure-monitor/vm/monitor-virtual-machine.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,8 @@ The following table lists the different steps for configuration of VM monitoring
44
44
| Step | Description |
45
45
|:---|:---|
46
46
|[Deploy Azure Monitor agent](monitor-virtual-machine-agent.md)| Deploy the Azure Monitor agent to your Azure and hybrid virtual machines to collect data from the guest operating system and workloads. |
47
-
|[Configure data collection](monitor-virtual-machine-data-collection.md))| Create data collection rules to instruct the Azure Monitor agent to collect telemetry from the guest operating system. |
48
-
|[Analyze collect data](monitor-virtual-machine-analyze.md)| Analyze monitoring data collected by Azure Monitor from virtual machines and their guest operating systems and applications to identify trends and critical information. |
47
+
|[Configure data collection](monitor-virtual-machine-data-collection.md)| Create data collection rules to instruct the Azure Monitor agent to collect telemetry from the guest operating system. |
48
+
|[Analyze collected data](monitor-virtual-machine-analyze.md)| Analyze monitoring data collected by Azure Monitor from virtual machines and their guest operating systems and applications to identify trends and critical information. |
49
49
|[Create alert rules](monitor-virtual-machine-alerts.md)| Create alerts to proactively identify critical issues in your monitoring data. |
50
50
|[Migrate management pack logic](monitor-virtual-machine-management-packs.md)| General guidance for translation the logic from your System Center Operations Manager management packs to Azure Monitor. |
51
51
@@ -90,4 +90,4 @@ See [Design a Log Analytics workspace architecture](../logs/workspace-design.md)
90
90
91
91
## Next steps
92
92
93
-
[Deploy the Azure Monitor agent to your virtual machines](monitor-virtual-machine-agent.md)
93
+
[Deploy the Azure Monitor agent to your virtual machines](monitor-virtual-machine-agent.md)
0 commit comments