Installing Windows 10 without a Microcoft account

[IRJ]

I would be interested to compare a default windows 10 install with Azure's Windows 10 VDI. I wonder how much extra shit is on with standard windows 10 that they wont run on their own hardware

https://azure.microsoft.com/en-us/services/virtual-desktop/

[Dashrender]

@IRJ said in Installing Windows 10 without a Microcoft account:

I would be interested to compare a default windows 10 install with Azure's Windows 10 VDI. I wonder how much extra shit is on with standard windows 10 that they wont run on their own hardware

https://azure.microsoft.com/en-us/services/virtual-desktop/

Well - I assume that their VDI is using Windows 10 Enterprise - so it should be the same in their VDI or your personal hardware, at least for the most part.

[Obsolesce]

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

[Dashrender]

Enterprise and Education don't have all that extra crap (the games) that home and Pro do - I don't understand at all why they include that shit in Pro... it's not like anything sold at typical retail has Pro on it, with the exception of Surface Pro devices (which are sold at retail).

[PhlipElder]

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

[IRJ]

@Dashrender said in Installing Windows 10 without a Microcoft account:

@IRJ said in Installing Windows 10 without a Microcoft account:

I would be interested to compare a default windows 10 install with Azure's Windows 10 VDI. I wonder how much extra shit is on with standard windows 10 that they wont run on their own hardware

https://azure.microsoft.com/en-us/services/virtual-desktop/

Well - I assume that their VDI is using Windows 10 Enterprise - so it should be the same in their VDI or your personal hardware, at least for the most part.

If you were MS and you were running let's say 100,000 VDIs (probably low number) on your hardware, I would think you would 100% optimize. Not doing so would be foolish and expensive.

I would bet that it isnt just Windows 10 Enterprise, but that is just my best guess based on cost of not doing it.

[Obsolesce]

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

[Dashrender]

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

I've made file shares work using AAD creds... so I am kinda surprised RDP wouldn't work with AAD creds.

[PhlipElder]

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

[black3dynamite]

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

For standalone non-domain, isn't it MicrosoftAccount\UserName is that only for personal Microsoft account only?

[PhlipElder]

@black3dynamite said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

For standalone non-domain, isn't it MicrosoftAccount\UserName is that only for personal Microsoft account only?

Not in this case. No permutation worked.

I have the VM and the AAD account on my desktop here. I'll try again. Let's see if it works...

[Obsolesce]

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

What's the exact command you used, because it works for me.

[PhlipElder]

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

What's the exact command you used, because it works for me.

Nope.

[black3dynamite]

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

What's the exact command you used, because it works for me.

Nope.

Not sure if this will work but include AzureAD\ has part of your username.

[PhlipElder]

@black3dynamite said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

What's the exact command you used, because it works for me.

Nope.

Not sure if this will work but include AzureAD\ has part of your username.

Tried that among other permutations.

[Obsolesce]

@black3dynamite said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

What's the exact command you used, because it works for me.

Nope.

Not sure if this will work but include AzureAD\ has part of your username.

Yes that has to be included.

The error messages says something about the credentials, so no idea. Does it work if you add it to the local Administrators group?

Other than that, I'm not doing anything different and it works with any AAD account on any AAD device, so I've not had to troubleshoot it.

[PhlipElder]

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@black3dynamite said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Obsolesce said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@PhlipElder said in Installing Windows 10 without a Microcoft account:

@Dashrender said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

I use this guide to walk customers through setting up a machine nearly weekly.

I'm curious why you push them away from using a MS account?

If the machine is pulled in to Azure AD by signing in with a MS AAD account, one cannot use that account to RDP into that endpoint. Something be broken there.

Better to set up a local account and bind the Azure AD/MS Account in the OS settings.

Interesting - didn't know that.

So what - you setup a local account, then under that local account, join it to an MS AAD, then login as the MS AAD account? Then you can RDP into the computer using the MS AAD account?

You can RDP into an AAD joined Win10 PC with an AAD account. I do it all the time.

Perhaps that account isn't added to the local Administrators group, or the one that allows RDP.

Log on process?

Domain\UserName & Password

or

[email protected] AAD account?

For standalone non-domain joined OS VMs/PCs [email protected] AAD does not work.

Yes [email protected].

On a device that is joined to AAD, try adding AzureAD\[email protected] like this:

net localgroup Administrators AzureAD\[email protected] /add

Otherwise something is misconfigured in AAD. There are a lot of variables in this.

I ran the gamut of trying to get it to work both in CompMgmt.msc and CMD.

AAD is vanilla. No changes.

What's the exact command you used, because it works for me.

Nope.

Not sure if this will work but include AzureAD\ has part of your username.

Yes that has to be included.

The error messages says something about the credentials, so no idea. Does it work if you add it to the local Administrators group?

Other than that, I'm not doing anything different and it works with any AAD account on any AAD device, so I've not had to troubleshoot it.

Nope.

[Dashrender]

I wonder if a cached credential is required.

@PhlipElder have you logged into this VM as [email protected] before?

[PhlipElder]

@Dashrender said in Installing Windows 10 without a Microcoft account:

I wonder if a cached credential is required.

@PhlipElder have you logged into this VM as [email protected] before?

Yeah, I log on using the Hyper-V Console. PITA that as I can't use Enhanced Session Mode since that is riding on RDP too.

Just tried with the account in the local administrators group and same result.

[black3dynamite]

Temporary turn off Network Level Authentication and try to again.