From aeeb4a1a273e59db4b2e0ff589feac4741177588 Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 8 Oct 2019 18:56:19 -0600 Subject: [PATCH 01/11] Command for adding users into RDP group doesn't work This command works only for the user , who already added into the AADJ device any of the local group (administrators) Otherwise this command throws the below error. For example: for cloud only user --> "There is no such global user or group : Azuread\Shenry" for synced user -->"There is no such global user or group : baz\user2" --- windows/client-management/connect-to-remote-aadj-pc.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index e1365a820c..08cdf8d351 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -44,7 +44,11 @@ From its release, Windows 10 has supported remote connections to PCs that are jo >You can specify individual Azure AD accounts for remote connections by having the user sign in to the remote device at least once and then running the following PowerShell cmdlet: > >`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD. - > + > This command works only for the user , who already added into the AADJ device any of the local group (administrators) +Otherwise this command throws the below error. For example: + for cloud only user --> "There is no such global user or group : Azuread\Shenry" +for synced user -->"There is no such global user or group : baz\user2" + >In Windows 10, version 1709, the user does not have to sign in to the remote device first. > >In Windows 10, version 1709, you can add other Azure AD users to the **Administrators** group on a device in **Settings** and restrict remote credentials to **Administrators**. If there is a problem connecting remotely, make sure that both devices are joined to Azure AD and that TPM is functioning properly on both devices. From 88c8867eb297d093272d1895ad0e425763e9bfcd Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Mon, 14 Oct 2019 11:14:12 -0600 Subject: [PATCH 02/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 08cdf8d351..45e829942e 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -47,7 +47,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > This command works only for the user , who already added into the AADJ device any of the local group (administrators) Otherwise this command throws the below error. For example: for cloud only user --> "There is no such global user or group : Azuread\Shenry" -for synced user -->"There is no such global user or group : baz\user2" + > for synced user -->"There is no such global user or group : baz\user2" >In Windows 10, version 1709, the user does not have to sign in to the remote device first. > From c057ae011778ab2bce62fa68e9a6f6711c4ed026 Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Mon, 14 Oct 2019 11:14:31 -0600 Subject: [PATCH 03/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 45e829942e..c612c76084 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -46,7 +46,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo >`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD. > This command works only for the user , who already added into the AADJ device any of the local group (administrators) Otherwise this command throws the below error. For example: - for cloud only user --> "There is no such global user or group : Azuread\Shenry" + > for cloud only user --> "There is no such global user or group : Azuread\Shenry" > for synced user -->"There is no such global user or group : baz\user2" >In Windows 10, version 1709, the user does not have to sign in to the remote device first. From 66eb555db47a10d909e99bebe308e95c423f1f62 Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Mon, 14 Oct 2019 11:15:11 -0600 Subject: [PATCH 04/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index c612c76084..f741f80e5a 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -48,7 +48,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo Otherwise this command throws the below error. For example: > for cloud only user --> "There is no such global user or group : Azuread\Shenry" > for synced user -->"There is no such global user or group : baz\user2" - +> >In Windows 10, version 1709, the user does not have to sign in to the remote device first. > >In Windows 10, version 1709, you can add other Azure AD users to the **Administrators** group on a device in **Settings** and restrict remote credentials to **Administrators**. If there is a problem connecting remotely, make sure that both devices are joined to Azure AD and that TPM is functioning properly on both devices. From 95496c68f7cb8ad3c0e244844d4c2b84ea37da03 Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Mon, 14 Oct 2019 11:15:22 -0600 Subject: [PATCH 05/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index f741f80e5a..7d283eab8a 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -45,7 +45,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > >`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD. > This command works only for the user , who already added into the AADJ device any of the local group (administrators) -Otherwise this command throws the below error. For example: + > Otherwise this command throws the below error. For example: > for cloud only user --> "There is no such global user or group : Azuread\Shenry" > for synced user -->"There is no such global user or group : baz\user2" > From 2f929f4ecdb0b0d86553113afebba5e078044d81 Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 09:44:10 -0600 Subject: [PATCH 06/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 7d283eab8a..6ebfba5fa3 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -48,7 +48,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > Otherwise this command throws the below error. For example: > for cloud only user --> "There is no such global user or group : Azuread\Shenry" > for synced user -->"There is no such global user or group : baz\user2" -> + > >In Windows 10, version 1709, the user does not have to sign in to the remote device first. > >In Windows 10, version 1709, you can add other Azure AD users to the **Administrators** group on a device in **Settings** and restrict remote credentials to **Administrators**. If there is a problem connecting remotely, make sure that both devices are joined to Azure AD and that TPM is functioning properly on both devices. From 40984f432e3d390bed8936bc30388967f1787beb Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 09:45:06 -0600 Subject: [PATCH 07/11] Update windows/client-management/connect-to-remote-aadj-pc.md Thank you Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 6ebfba5fa3..8fce97a0a4 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -44,7 +44,8 @@ From its release, Windows 10 has supported remote connections to PCs that are jo >You can specify individual Azure AD accounts for remote connections by having the user sign in to the remote device at least once and then running the following PowerShell cmdlet: > >`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD. - > This command works only for the user , who already added into the AADJ device any of the local group (administrators) + > + > This command only works for AADJ device users already added to any of the local groups (administrators). > Otherwise this command throws the below error. For example: > for cloud only user --> "There is no such global user or group : Azuread\Shenry" > for synced user -->"There is no such global user or group : baz\user2" From fbfb5c9526f1e7471b604d7b5b016ec68743803e Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 14:33:50 -0600 Subject: [PATCH 08/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 8fce97a0a4..5585ff163e 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -47,7 +47,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > > This command only works for AADJ device users already added to any of the local groups (administrators). > Otherwise this command throws the below error. For example: - > for cloud only user --> "There is no such global user or group : Azuread\Shenry" + > for cloud only user --> "There is no such global user or group : Azuread\Shenry"
> for synced user -->"There is no such global user or group : baz\user2" > >In Windows 10, version 1709, the user does not have to sign in to the remote device first. From 07aa9914e0f7b26195c751f217439c07a8f61caf Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 14:34:00 -0600 Subject: [PATCH 09/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 5585ff163e..0ab77950b7 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -46,7 +46,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo >`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD. > > This command only works for AADJ device users already added to any of the local groups (administrators). - > Otherwise this command throws the below error. For example: + > Otherwise this command throws the below error. For example:
> for cloud only user --> "There is no such global user or group : Azuread\Shenry"
> for synced user -->"There is no such global user or group : baz\user2" > From 88de3332688b11a2ab5a2a1c1a8fb9b33be8966d Mon Sep 17 00:00:00 2001 From: NagaCSC Date: Tue, 15 Oct 2019 14:34:41 -0600 Subject: [PATCH 10/11] Update windows/client-management/connect-to-remote-aadj-pc.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/connect-to-remote-aadj-pc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 0ab77950b7..6c1b6665b6 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -48,7 +48,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > This command only works for AADJ device users already added to any of the local groups (administrators). > Otherwise this command throws the below error. For example:
> for cloud only user --> "There is no such global user or group : Azuread\Shenry"
- > for synced user -->"There is no such global user or group : baz\user2" + > for synced user --> "There is no such global user or group : baz\user2"
> >In Windows 10, version 1709, the user does not have to sign in to the remote device first. > From ec59ff90d3aa3dc17aa6b3e604356441f57cf605 Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Wed, 20 Nov 2019 12:33:57 -0800 Subject: [PATCH 11/11] Update connect-to-remote-aadj-pc.md --- windows/client-management/connect-to-remote-aadj-pc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/connect-to-remote-aadj-pc.md b/windows/client-management/connect-to-remote-aadj-pc.md index 6c1b6665b6..6359220114 100644 --- a/windows/client-management/connect-to-remote-aadj-pc.md +++ b/windows/client-management/connect-to-remote-aadj-pc.md @@ -47,8 +47,8 @@ From its release, Windows 10 has supported remote connections to PCs that are jo > > This command only works for AADJ device users already added to any of the local groups (administrators). > Otherwise this command throws the below error. For example:
- > for cloud only user --> "There is no such global user or group : Azuread\Shenry"
- > for synced user --> "There is no such global user or group : baz\user2"
+ > for cloud only user: "There is no such global user or group : *name*"
+ > for synced user: "There is no such global user or group : *name*"
> >In Windows 10, version 1709, the user does not have to sign in to the remote device first. >