Windows 10: RDP to Azure AD joined computer

I am trying to connect to a remote computer that is Azure AD joined. Both the client and host computer are running Windows 10 version 1809. Currently I am connecting without NLA to be able to authentication myself, but I would like to connect with NLA.


According to this article: https://docs.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc this should be possible, providing you use the username format "AzureAD\JeroenDeWit" to connect. However, this results in the following error:




Other guides like https://cloudbuilder.io/documentation/Windows10Pro-RDP-AzureADJoined/ also suggest authenticating without NLA.


Am I doing something wrong or is Microsoft doing something wrong?

:)

 

Disconnecting on prem AD and then joining Azure AD creates new Windows profile?

Hello everyone,

I have a question about joining computers in my firm from on prem AD to Azure AD. When someone new arrives at our firm (new employee), there is a fresh installation of Windows 10. It is easy to join Azure AD
because it is a fresh start, but now we have to migrate all Windows 10 users that are on prem AD to Azure AD. When I disconnect those users from our local on prem AD and join them to Azure AD, whole new Windows 10 profile is created, without any of settings,
data or anything else on that profile (clean profile with few applications that are installed computer-wide). So my question is, is there any solution to keep their profile settings from before they joined Azure AD? Or I will have to simply tell them to backup
everything (essential data).

What I tried so far:

• Tried tools for migration like ForensiT (User Profile Wizard, User Profile Manager and Transwiz, just to see if it is going to work) - not successful
• Tried changing profile path from registry - not successful
• Tried log in with the old credentials example: CONTOSO\user (because after I joined that computer to Azure AD user should log in as *** Email address is removed for privacy ***) - not successful

Is there anything else I can try? Thanks for your answers.

 

Joining a Windows 10 Pro machine to Azure AD without linking/registering an employees email address to that computer

I have been researching for a few weeks now trying to figure out how to join Azure AD for new purchased machines when setting up the machine.

I have two different scenarios that would be joining azure AD.

1. Shipping a machine that has not been setup yet directly to an employee's location. I have to walk through step by step on how to configure settings, join the azure domain, and how to download a program or two. Is their a Microsoft process that I can put
information into that knows that computer needs to join our azure domain? I do not wish to sign in with my credentials to join the azure domain each time we order a new computer.

2. If my company has a windows 10 Home edition machine that we would want to add to our Azure AD, We purchase a windows 10 pro license and activate it under the settings. our next step is going into the settings to join an azure AD domain through a Microsoft
account, however I do not wish to register my account on every computer in our environment. Is their a way to have this computer join azure AD with some sort of a token or activation process? The second issue to this scenario is after joining the azure AD
with my credentials the local admin account is still active and I need to then go through the process of logging in and removing this account.

What would be the best process of joining my environments machines to our Azure AD network without having to register my account with each computer?

 

Image W10 workstations for Azure AD join?


Hi All,

I want to image Windows 10; but more importantly I need to join Azure AD 'Out of the Box'!

I don't have a 'master' Azure AD account. I am not even sure that such a thing exits, e.g.: the Administrator account on a standard Active Directory Domain.

Where should I be looking for configuration, where it comes to Azure AD automatic joining?

My thoughts are PowerShell DST! But that is just a rumour.

Any suggestions would be amazing.

Regards,

Davo