From ec59ff90d3aa3dc17aa6b3e604356441f57cf605 Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Wed, 20 Nov 2019 12:33:57 -0800 Subject: [PATCH] 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. >