Skip to content

Commit 4db1889

Browse files
authored
Merge pull request #9956 from sdabbiru/patch-13
Update device-management-faq.md
2 parents da3d064 + 9b2aecc commit 4db1889

File tree

1 file changed

+10
-14
lines changed

1 file changed

+10
-14
lines changed

articles/active-directory/device-management-faq.md

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -40,35 +40,31 @@ ms.reviewer: jairoc
4040
**Q: I registered the device recently. Why can’t I see the device under my user info in the Azure portal?**
4141

4242
**A:** Windows 10 devices that are hybrid Azure AD joined do not show up under the USER devices.
43-
You need to use PowerShell to see all devices.
43+
You need to use All devices view in Azure portal. You can also use PowerShell [Get-MsolDevice](/powershell/module/msonline/get-msoldevice?view=azureadps-1.0) cmdlet.
4444

4545
Only the following devices are listed under the USER devices:
4646

4747
- All personal devices that are not hybrid Azure AD joined.
4848
- All non-Windows 10 / Windows Server 2016 devices.
4949
- All non-Windows devices
5050

51-
---
52-
53-
**Q: Why can I not see all the devices registered in Azure Active Directory in the Azure portal?**
54-
55-
**A:** You can now see them under Azure AD Directory -> all devices menu.
56-
You can also use Azure PowerShell to find all devices.
57-
For more details, see the [Get-MsolDevice](/powershell/module/msonline/get-msoldevice?view=azureadps-1.0) cmdlet.
58-
5951
---
6052

6153
**Q: How do I know what the device registration state of the client is?**
6254

63-
**A:** For Windows 10 and Windows Server 2016 or later devices, run dsregcmd.exe /status.
55+
**A:** You can use the Azure portal, go to All devices and search for the device using device ID. Check the value under the join type column.
56+
57+
If you want to check the local device registration state from a registered device:
6458

65-
For down-level OS versions, run "%programFiles%\Microsoft Workplace Join\autoworkplace.exe"
59+
- For Windows 10 and Windows Server 2016 or later devices, run dsregcmd.exe /status.
60+
- For down-level OS versions, run "%programFiles%\Microsoft Workplace Join\autoworkplace.exe"
6661

6762
---
6863

69-
**Q: Why is a device I have deleted in the Azure portal or using Windows PowerShell still listed as registered?**
64+
**Q: I have deleted in the Azure portal or using Windows PowerShell, but the local state on the device says that it is still registered?**
7065

7166
**A:** This is by design. The device will not have access to resources in the cloud.
67+
7268
If you want to re-register again, a manual action must be to be taken on the device.
7369

7470
To clear the join state from Windows 10 and Windows Server 2016 that are on-premises AD domain-joined:
@@ -119,7 +115,7 @@ Please evaluate the conditional access policy rules and ensure that the device i
119115
---
120116

121117

122-
**Q: I see the device record under the USER info in the Azure portal and can see the state as registered on the client. Am I setup correctly for using conditional access?**
118+
**Q: I see the device record under the USER info in the Azure portal and can see the state as registered on the device. Am I setup correctly for using conditional access?**
123119

124120
**A:** The device join state, reflected by deviceID, must match with that on Azure AD and meet any evaluation criteria for conditional access.
125121
For more details, see [Get started with Azure Active Directory Device Registration](active-directory-device-registration.md).
@@ -148,7 +144,7 @@ For more details, see [Get started with Azure Active Directory Device Registrati
148144

149145
**Q: Why did my attempt to join a PC fail although I didn't get any error information?**
150146

151-
**A:** A likely cause is that the user is logged in to the device using the built-in administrator account.
147+
**A:** A likely cause is that the user is logged in to the device using the local built-in administrator account.
152148
Please create a different local account before using Azure Active Directory Join to complete the setup.
153149

154150
---

0 commit comments

Comments
 (0)