Skip to content

Commit bffdc59

Browse files
author
Ryan Willis
committed
user rights assignment and crp rp
1 parent 4677644 commit bffdc59

File tree

2 files changed

+13
-0
lines changed

2 files changed

+13
-0
lines changed
110 KB
Loading

articles/azure-arc/servers/prerequisites.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,18 @@ Linux operating systems:
8282
* openssl
8383
* gnupg (Debian-based systems, only)
8484

85+
## Local user logon right for Windows systems
86+
87+
The Azure Hybrid Instance Metadata Service runs under a low-privileged virtual account, `NT SERVICE\himds`. This account needs the "log on as a service" right in Windows to run. In most cases, there's nothing you need to do because this right is granted to virtual accounts by default. However, if your organization uses Group Policy to customize this setting, you will need to add `NT SERVICE\himds` to the list of accounts allowed to log on as a service.
88+
89+
You can check the current policy on your machine by opening the Local Group Policy Editor (`gpedit.msc`) from the Start menu and navigating to the following policy item:
90+
91+
Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Log on as a service
92+
93+
Check if any of `NT SERVICE\ALL SERVICES`, `NT SERVICE\himds`, or `S-1-5-80-4215458991-2034252225-2287069555-1155419622-2701885083` (the static security identifier for NT SERVICE\\himds) are in the list. If none are in the list, you'll need to work with your Group Policy administrator to add `NT SERVICE\himds` to any policies that configure user rights assignments on your servers. The Group Policy administrator will need to make the change on a computer with the Azure Connected Machine agent installed so the object picker resolves the identity correctly. The agent doesn't need to be configured or connected to Azure to make this change.
94+
95+
:::image type="content" source="media/prerequisites/arc-server-user-rights-assignment.png" alt-text="Local Group Policy Editor showing which users have permissions to log on as a service." border="false":::
96+
8597
## Required permissions
8698

8799
You'll need the following Azure built-in roles for different aspects of managing connected machines:
@@ -104,6 +116,7 @@ To use Azure Arc-enabled servers, the following [Azure resource providers](../..
104116
* **Microsoft.GuestConfiguration**
105117
* **Microsoft.HybridConnectivity**
106118
* **Microsoft.AzureArcData** (if you plan to Arc-enable SQL Servers)
119+
* **Microsoft.Compute** (for Azure Update Manager and automatic extension upgrades)
107120

108121
You can register the resource providers using the following commands:
109122

0 commit comments

Comments
 (0)