Link to home
Get AccessLog in
Avatar of jkimzlg

asked on

RDP in from home creates a new Windows Profile

I'm connecting from home by Dell Netextender client software to a Win 10 laptop at my work.  When I RDP in from home it creates another windows profile ie. jsmith.CONTOSO, when I really want to log into the jsmith windows profile.  How can this be achieved?  I don't think it ever used to do this.  I did notice that there was a windows update last night and my laptop had to do a reboot.
Avatar of John
Flag of Canada image

No issue with Windows 10 any version including V1809 now and all updates.

Do you have a VPN properly installed?   You need that to make connections to the office from a foreign network.
Avatar of David Johnson, CD
John: nexextender is a vpn specific to sonicwall

you can try  SonicWall Mobile Connect for Windows 10 available in the Microsoft store.
Avatar of jkimzlg


I do not have a problem with my connection.

My issue is with RDP.  It creates a different windows profile.  I don't want to be logged into 'plim.SOURCE'.  I want to be logged into 'Plim'

User generated image
You can try a third party VPN tool if you need.  I use NCP Secure Entry.
It is not a Windows problem. It may be an issue with your firewall or the VPN client you are using.
Avatar of jkimzlg


it has nothing to do with the firewall or the VPN client
It is definitely not Windows.  I RDP to my client machine and from a client to my Home Machine.  All Windows 10 Pro.  No issues.

I assume Windows 10 means to you Windows 10 Pro.
this might be worth a try, it's a replacement for windows remote desktop connection.  I havent seen your issue before, but I have had many wonky issues that I don't get using this client, it's free, and it lets you manage and store many connections.

it just has a strange name mRemoteNG

On and it just goes on the client side, not the host.
I have not seen that product. If you try be sure the download site does not have viruses
I htink I got mine off CNet
Two thoughts come to mind, with SonicWALL NetExtender you can either connect to AD and authenticate a user OR with a local user account created on the SonicWALL itself.  If the user account is local to the SonicWALL, I'm wondering if RDP is picking that up as the domain and passing it to the remote PC.  Now the remote PC would need to auth your user account used when RDP'ing into it from AD and it should be putting you into the correct user account on that PC.  Just going down the rabbit hole of ideas to look at.  It would be helpful to see the RDP window with user account info, IE "domain.local\plim"  You can blackout the PC name and other sensitive details.
Avatar of McKnife
Flag of Germany image

Link to home
This content is only available to members.
To access this content, you must be a member of Experts Exchange.
Get Access
If the profile is defective, you usually get informed about the creation of a temporary new profile after the fact, so I don't think that is the case. But it is possible.

The trivial reason for a second profile is, as has been mentioned already, that both a domain and a local account exist with the same name. If you do not provide the domain or machine name together with the username when connecting with RDP, the target machine decides what it uses. So explicitly state what you mean, e.g. MyPC\Plim or MyDomain\Plim.
Hi McKnife, does RDP store credentials in the Windows Credentials Manager?  Or is that just for Outlook and stuff?
Yes - In Windows 10 under Windows Credentials  Default showing is Web Credentials
In the Credentials Manager they are located in Windows Credentials, Generic - but only if you have stored a password with the user, IIRC.
Avatar of jkimzlg


yes McKnife is correct, I'm at work today and when I log back in normally (non-RDP) - it's still using my new profile plim.SOURCE.  My old profile got corrupted somehow.

I did a system restore and now I'm back to normal.  This happened right after I did this windows update:

Security Update for Microsoft Windows (KB4483234) 12/28/18
Avatar of jkimzlg


wow, so I downloaded and installed these two windows updates again, then rebooted, and right after I did so I got a 'Trust Relationship between the workstation and the primary domain failed'.  I rejoined to domain and all is well again, I'm able to use my old profile again.

2018-12 Cumulative Update for Windows 10 Version 1803 x64-based Systems (KB4483234)  -  I suspect it's this one
2018-09 Cumulative Update for Windows 10 Version 1803 x64-based Systems (KB4100347)
I guess the updates are innocent. System restore may break the trust relationship.

Good that it's solved. Happy new year's eve/day, everyone!
same to you McKnife