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
The guest configuration agent receives improvements on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about:
13
+
The machine configuration agent receives improvements on an ongoing basis. To stay up to date with
14
+
the most recent developments, this article provides you with information about:
14
15
15
16
- The latest releases
16
17
- Known issues
17
18
- Bug fixes
18
19
19
-
For information on release notes for the connected machine agent, please see [What's new with the connected machine agent](../../azure-arc/servers/agent-release-notes.md).
20
+
For information on release notes for the connected machine agent, see
21
+
[What's new with the connected machine agent][01].
20
22
21
23
## Release notes
22
24
23
25
### Version 1.29.48 - January 2023
24
26
25
27
#### New Features
26
28
27
-
- In this release we have added support for Linux distributions such as Red Hat Enterprise Linux (RHEL) 9, Mariner 1&2, Alma 9, and Rocky 9.
29
+
- In this release, we've added support for Linux distributions such as Red Hat Enterprise Linux
30
+
(RHEL) 9, Mariner 1&2, Alma 9, and Rocky 9.
28
31
29
32
#### Fixed
30
33
@@ -33,34 +36,61 @@ For information on release notes for the connected machine agent, please see [Wh
33
36
34
37
### Guest Configuration Linux Extension version 1.26.38
35
38
36
-
In this release, various improvements were made.
39
+
In this release, various improvements were made.
37
40
38
-
- You can now restrict which URLs can be used to download machine configuration packages by setting the allowedGuestConfigPkgUrls tag on the server resource and providing a comma-separated list of URL patterns to allow. If the tag exists, the agent will only allow custom packages to be downloaded from the specified URLs. Built-in packages are unaffected by this feature.
41
+
- You can now restrict which URLs can be used to download machine configuration packages by setting
42
+
the `allowedGuestConfigPkgUrls` tag on the server resource and providing a comma-separated list of
43
+
URL patterns to allow. If the tag exists, the agent only allows custom packages to be
44
+
downloaded from the specified URLs. Built-in packages are unaffected by this feature.
39
45
40
46
## Fixed
41
47
42
-
- Resolves local elevation of privilege vulnerability [CVE-2022-38007](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-38007).
43
-
- If you're currently running an older version of the AzurePolicyforLinux extension, use the PowerShell or Azure CLI commands below to update your extension to the latest version.
The machine configuration service uses the metadata information to automatically create an audit
34
+
resource for definitions with either `AuditIfNotExists` or `DeployIfNotExists` policy effects. The
35
+
resource type is `Microsoft.GuestConfiguration/guestConfigurationAssignments`. Azure Policy uses
36
+
the **complianceStatus** property of the guest assignment resource to report compliance status. For
37
+
more information, see [getting compliance data][02].
40
38
41
39
### Deletion of guest assignments from Azure Policy
42
40
43
-
When an Azure Policy assignment is deleted, if a machine configuration assignment
44
-
was created by the policy, the machine configuration assignment is also deleted.
41
+
When an Azure Policy assignment is deleted, if the policy created a machine configuration
42
+
assignment, the machine configuration assignment is also deleted.
45
43
46
-
When an Azure Policy assignment is deleted from an initiative, if a machine configuration assignment was created by the policy, you will need to manually delete the corresponding machine configuration assignment. This can be done by navigating to the guest assignments page on Azure portal and deleting the assignment there.
44
+
When an Azure Policy assignment is deleted, you need to manually delete any machine configuration
45
+
assignments the policy created. You can do so by navigating to the guest assignments page on Azure
Guest assignment resources in Azure Resource Manager can be created by Azure
51
-
Policy or any client SDK.
50
+
You can create guest assignment resources in Azure Resource Manager by using Azure Policy or any
51
+
client SDK.
52
52
53
53
An example deployment template:
54
54
@@ -79,31 +79,30 @@ An example deployment template:
79
79
80
80
The following table describes each property of guest assignment resources.
81
81
82
-
| Property | Description |
83
-
|-|-|
84
-
| name| Name of the configuration inside the content package MOF file. |
85
-
| contentUri| HTTPS URI path to the content package (.zip). |
86
-
| contentHash| A SHA256 hash value of the content package, used to verify it has not changed. |
87
-
| version| Version of the content package. Only used for built-in packages and not used for custom content packages. |
88
-
| assignmentType| Behavior of the assignment. Allowed values: `Audit`, `ApplyandMonitor`, and `ApplyandAutoCorrect`. |
89
-
| configurationParameter | List of DSC resource type, name, and value in the content package MOF file to be overridden after it's downloaded in the machine. |
|**name**| Name of the configuration inside the content package MOF file.|
85
+
|**contentUri**| HTTPS URI path to the content package (`.zip`). |
86
+
|**contentHash**| A SHA256 hash value of the content package, used to verify it hasn't changed.|
87
+
|**version**| Version of the content package. Only used for built-in packages and not used for custom content packages.|
88
+
|**assignmentType**| Behavior of the assignment. Allowed values: `Audit`, `ApplyandMonitor`, and `ApplyandAutoCorrect`.|
89
+
|**configurationParameter**| List of DSC resource type, name, and value in the content package MOF file to be overridden after it's downloaded in the machine. |
90
90
91
91
### Deletion of manually created machine configuration assignments
92
92
93
-
Machine configuration assignments created through any manual approach (such as
94
-
an Azure Resource Manager template deployment) must be deleted manually.
95
-
Deleting the parent resource (virtual machine or Arc-enabled machine) will also
96
-
delete the machine configuration assignment.
93
+
You must manually delete machine configuration assignments created through any manual approach
94
+
(such as an Azure Resource Manager template deployment). Deleting the parent resource (virtual
95
+
machine or Arc-enabled machine) also deletes the machine configuration assignment.
97
96
98
-
To manually delete a machine configuration assignment, use the following
99
-
example. Make sure to replace all example strings, indicated by "\<\>" brackets.
97
+
To manually delete a machine configuration assignment, use the following example. Make sure to
98
+
replace all example strings, indicated by `<>` brackets.
100
99
101
-
```PowerShell
100
+
```azurepowershell-interactive
102
101
# First get details about the machine configuration assignment
0 commit comments