@DustinB3403 said in Random Thread - Anything Goes:

@PhlipElder said in Random Thread - Anything Goes:

@Dashrender said in Random Thread - Anything Goes:

@scottalanmiller said in Random Thread - Anything Goes:

I didn't scroll down at first to see the comment - so I was like - uh.. what, did they buy a cardboard house?

My thought was that a house could be bought for $25K in some neighbourhoods.

I thought this as well, Detroit anyone?

Same page. There's some neighbourhoods that a complete property could be purchased for that.

Outlying rural areas out here one can buy an 1/8th with a home for about $25K.

@Dashrender said in Random Thread - Anything Goes:

@scottalanmiller said in Random Thread - Anything Goes:

I didn't scroll down at first to see the comment - so I was like - uh.. what, did they buy a cardboard house?

My thought was that a house could be bought for $25K in some neighbourhoods.

@scottalanmiller said in Random Thread - Anything Goes:

Reminds me of my first IAD (Instructor Assisted Deployment) when a buddy of mine challenged me to jump out of a perfectly good airplane.

@pmoncho said in RDS 2019 Setup and RDS License Role:

@PhlipElder said in RDS 2019 Setup and RDS License Role:

@pmoncho

@pmoncho said in RDS 2019 Setup and RDS License Role:

Working on replacing two 2k8R2 TS servers with RDS 2019. These two servers host a LOB application with about 50 users.

Due to a few issues with our current setup and LOB app limitations, my plan is to create two RDS servers holding their own RDSH, RDCB, and RDWA roles. Each server will have their own collection (Containing only itself)

My question is, can these two servers still connect to one RDS License server (which will be located on a DC)? (I don't see why not but figured I'd check)

I know this is convoluted but it will change in the future to a single RDSH server with all roles as we will be upgrading to the new version of our LOB app connecting to a backend SQL Server.

Question answered, but curious, why not have Broker/Gateway/Web roles on their own server/VM then have two collections set up along with their respective session hosts configured on that VM?

That would make things like user profile disks (FSLogix) and load balancing, and certificates, a lot simpler to work with along with getting Single Sign-On configured in AD.

I was not planning on using the RDGW as my user come in via a SSLVPN.

As for the rest, my current issues are, Windows licensing costs (keep them down as I keep trying to move services off of windows), going from 2K8R2 to 2019, we will need to use both old version and new version at the same time, limitations in the old version of our LOB app keeps my configuration options very limited without dorking up the current data, and trying to do this will minimal distraction to my in-house users and our remote clients from a tech side.

Just moving to the new version of our LOB app is going to be a wallop to our users.

This convoluted setup is temporary until the old LOB version dies. Its the best I could come up with based on my research, RDS requirements, licensing costs (Server, CALs, RDS CALs..etc...), LOB and user requirements/limitations.

RDGW provides a layer of protection whether via HTTPS 443 port forwarding, which is the only way to publish RDS Internet facing IMNSHO, or using a VPN of any sort.

Using a single Broker setup would simplify management and ease of connection for users.

One option would be to use one collection session host setup for the user's dedicated desktop and then publish the other session host's software installed as RemoteApps back to those users. That keeps things relatively clean in the user's local profiles.

Using User Profile Disks with FSLogix on a network share makes it even easier.

@pmoncho

@pmoncho said in RDS 2019 Setup and RDS License Role:

Working on replacing two 2k8R2 TS servers with RDS 2019. These two servers host a LOB application with about 50 users.

Due to a few issues with our current setup and LOB app limitations, my plan is to create two RDS servers holding their own RDSH, RDCB, and RDWA roles. Each server will have their own collection (Containing only itself)

My question is, can these two servers still connect to one RDS License server (which will be located on a DC)? (I don't see why not but figured I'd check)

I know this is convoluted but it will change in the future to a single RDSH server with all roles as we will be upgrading to the new version of our LOB app connecting to a backend SQL Server.

Question answered, but curious, why not have Broker/Gateway/Web roles on their own server/VM then have two collections set up along with their respective session hosts configured on that VM?

That would make things like user profile disks (FSLogix) and load balancing, and certificates, a lot simpler to work with along with getting Single Sign-On configured in AD.

@Obsolesce No AD. Workgroup VM.

@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.

@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.

@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 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.