Skip to content

Commit 73af96d

Browse files
authored
Merge pull request #108639 from MicrosoftGuyJFlo/patch-4
Update troubleshoot-device-dsregcmd.md
2 parents 503926c + 7568613 commit 73af96d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/devices/troubleshoot-device-dsregcmd.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ This section lists the status of various attributes for the user currently logge
131131
- **CanReset:** - Denotes if the Windows Hello key can be reset by the user.
132132
- **Possible values:** - DestructiveOnly, NonDestructiveOnly, DestructiveAndNonDestructive, or Unknown if error.
133133
- **WorkplaceJoined:** - Set to “YES” if Azure AD registered accounts have been added to the device in the current NTUSER context.
134-
- **WamDefaultSet:** - Set to “YES” if a WAM default WebAccount is created for the logged in user. This field could display an error if dsreg /status is run in admin context.
134+
- **WamDefaultSet:** - Set to “YES” if a WAM default WebAccount is created for the logged in user. This field could display an error if dsreg /status is run from an elevated command prompt.
135135
- **WamDefaultAuthority:** - Set to “organizations” for Azure AD.
136136
- **WamDefaultId:** - Always “https://login.microsoft.com” for Azure AD.
137137
- **WamDefaultGUID:** - The WAM provider’s (Azure AD/Microsoft account) GUID for the default WAM WebAccount.

0 commit comments

Comments
 (0)