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
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/computer-groups.md
+6-18Lines changed: 6 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Computer groups in Azure Monitor allow you to scope log queries to
4
4
ms.topic: conceptual
5
5
author: bwren
6
6
ms.author: bwren
7
-
ms.date: 02/05/2019
7
+
ms.date: 10/20/2021
8
8
9
9
---
10
10
@@ -56,32 +56,20 @@ When you configure Azure Monitor to import Active Directory group memberships, i
56
56
> [!NOTE]
57
57
> Imported Active Directory groups only contain Windows machines.
58
58
59
-
You configure Azure Monitor to import Active Directory security groups from **Advanced settings** in your Log Analytics workspace in the Azure portal. Select **Computer Groups**, **Active Directory**, and then **Import Active Directory group memberships from computers**. There is no further configuration required.
60
-
61
-

62
-
63
-
When groups have been imported, the menu lists the number of computers with group membership detected and the number of groups imported. You can click on either of these links to return the **ComputerGroup** records with this information.
59
+
You configure Azure Monitor to import Active Directory security groups from the **Computer Groups** menu item in your Log Analytics workspace in the Azure portal. Select the **Active Directory** tab, and then **Import Active Directory group memberships from computers**. When groups have been imported, the menu lists the number of computers with group membership detected and the number of groups imported. You can click on either of these links to return the **ComputerGroup** records with this information.
64
60
65
61
### Windows Server Update Service
66
62
When you configure Azure Monitor to import WSUS group memberships, it analyzes the targeting group membership of any computers with the Log Analytics agent. If you are using client-side targeting, any computer that is connected to Azure Monitor and is part of any WSUS targeting groups has its group membership imported to Azure Monitor. If you are using server-side targeting, the Log Analytics agent should be installed on the WSUS server in order for the group membership information to be imported to Azure Monitor. This membership is continuously updated every 4 hours.
67
63
68
-
You configure Azure Monitor to import WSUS groups from **Advanced settings** in your Log Analytics workspace in the Azure portal. Select **Computer Groups**, **WSUS**, and then **Import WSUS group memberships**. There is no further configuration required.
69
-
70
-

71
-
72
-
When groups have been imported, the menu lists the number of computers with group membership detected and the number of groups imported. You can click on either of these links to return the **ComputerGroup** records with this information.
64
+
You configure Azure Monitor to import WSUS groups from the **Computer Groups** menu item in your Log Analytics workspace in the Azure portal. Select the **Windows Server Update Service** tab, and then **Import WSUS group memberships**. When groups have been imported, the menu lists the number of computers with group membership detected and the number of groups imported. You can click on either of these links to return the **ComputerGroup** records with this information.
73
65
74
66
### Configuration Manager
75
-
When you configure Azure Monitor to import Configuration Manager collection memberships, it creates a computer group for each collection. The collection membership information is retrieved every 3 hours to keep the computer groups current.
76
-
77
-
Before you can import Configuration Manager collections, you must [connect Configuration Manager to Azure Monitor](collect-sccm.md).
78
-
79
-

67
+
When you configure Azure Monitor to import Configuration Manager collection memberships, it creates a computer group for each collection. The collection membership information is retrieved every 3 hours to keep the computer groups current. Before you can import Configuration Manager collections, you must [connect Configuration Manager to Azure Monitor](collect-sccm.md).
80
68
81
-
When collections have been imported, the menu lists the number of computers with group membership detected and the number of groups imported. You can click on either of these links to return the **ComputerGroup** records with this information.
69
+
You configure Azure Monitor to import WSUS groups from the **Computer Groups** menu item in your Log Analytics workspace in the Azure portal. Select the **System Center Configuration Manager** tab, and then **Import Configuration Manager collection memberships**. When collections have been imported, the menu lists the number of computers with group membership detected and the number of groups imported. You can click on either of these links to return the **ComputerGroup** records with this information.
82
70
83
71
## Managing computer groups
84
-
You can view computer groups that were created from a log query or the Log Search API from **Advanced settings** in your Log Analytics workspace in the Azure portal. Select **Computer Groups**and then **Saved Groups**.
72
+
You can view computer groups that were created from a log query or the Log Search API from the **Computer Groups**menu item in your Log Analytics workspace in the Azure portal. Select the **Saved Groups**tab to view the list of groups.
85
73
86
74
Click the **x** in the **Remove** column to delete the computer group. Click the **View members** icon for a group to run the group's log search that returns its members. You can't modify a computer group but instead must delete and then recreate it with the modified settings.
0 commit comments