Azure AD and OnPrem Windows Server 2016
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
Azure AD can be used as a replacement for AD to join an RDS server, but apparently only if you run your RDS server on an Azure VM. You have to connect it to your Azure Virtual Network. In the video above the Microsoft RDS guy is showing this.
From what I could find, this looks to only be the case if you add an AD server to the mix and have RDS talk to AD rather than to Azure AD.
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
Once I saw server 2016 can join Azure AD I got excited. But it seems it's only currently possible if you run an Azure VM and connect Azure AD on your Azure Virtual Network.
I saw that too, but it looked like it was using traditional AD domains, not Azure AD.
-
That video shows Azure AD AP and Azure AD DS, not straight Azure AD. Azure AD DS is using a real AD Server that is synced to Azure AD to deliver traditional AD, but with Azure AD controlling it. So if that is what you are basing the availability off of, that's actually RDS just on traditional AD, not Azure AD.
-
He talks in the video above about elminating the need for AD servers and shows a cloud-only deployment of RDS, skip to minute 9:55
You maybe right. I'm starting to think about just ordering in a server and running an on-prem RDS. I'm about to attempt a deployment of Azure AD and an Azure VM with RDS and will report back.
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
He talks in the video above about elminating the need for AD servers and shows a cloud-only deployment of RDS, skip to minute 9:55
I watched that. Like all MS videos, I think it's just marketing. Yes YOU don't need to run an AD server, MS runs it for you. That's how they "eliminate" it. But he then shows RDS talking to AD, not Azure AD, as how it works. So I'm pretty sure he just means that it's AD.
-
Or you could use a Linux AD server on Vultr. But that's still old school AD. Just cheaper. This is really a huge limitation of RDS, that's the core problem. It doesn't have Windows 10's authentication options.
-
Once again, you are correct lol. Man
I tried deploying a private network on Vultr last night, an AD vm and a RDS vm.
The AD vm ends up multihomed with an external and an internal interface. Apparently internet access is direct for each VM even when you have a private network, it just adds the private adapter. So you couldn't disable the external interface or you'd lose internet access. (Per tech support).
My last ad deployments on premise was a .local domain. Based on previous feedback here we are back to using split DNS and the actual .com?
Not sure how I would do it all on Vultr and remain secure.
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
So you couldn't disable the external interface or you'd lose internet access. (Per tech support).
Nothing wrong with that, might be the way to go.
-
@scottalanmiller only issue that came to mind was updates.
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
@scottalanmiller only issue that came to mind was updates.
Yup, of course an issue. The solution there, and this isn't that great, is that you either use WSUS for Windows or a local mirror for Linux.
-
Which means another server and more of a pain.
-
@bigbear well another issue, depending on where I store all my data. Do I launch a 3rd server with Vultr BLOB storage and share it to the terminal server, cause that would be another server without internet/updates/backup.
Or do I directly attach a volume with BLOB storage to the terminal server? Which seems odd...
-
@scottalanmiller said in Azure AD and OnPrem Windows Server 2016:
@bigbear said in Azure AD and OnPrem Windows Server 2016:
@scottalanmiller only issue that came to mind was updates.
Yup, of course an issue. The solution there, and this isn't that great, is that you either use WSUS for Windows or a local mirror for Linux.
Yup, so you can maybe see where my hope was to join a 2016 RDS to Azure AD the way Windows 10 clients do (also havent tested this lol).
The cake is a lie!
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
@bigbear well another issue, depending on where I store all my data. Do I launch a 3rd server with Vultr BLOB storage and share it to the terminal server, cause that would be another server without internet/updates/backup.
Or do I directly attach a volume with BLOB storage to the terminal server? Which seems odd...
Do you need the BLOB storage and why would it feel odd to have it be direct but not weird to have it on a different server? What's the benefit to having an extra server for storage?
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
@scottalanmiller said in Azure AD and OnPrem Windows Server 2016:
@bigbear said in Azure AD and OnPrem Windows Server 2016:
@scottalanmiller only issue that came to mind was updates.
Yup, of course an issue. The solution there, and this isn't that great, is that you either use WSUS for Windows or a local mirror for Linux.
Yup, so you can maybe see where my hope was to join a 2016 RDS to Azure AD the way Windows 10 clients do (also havent tested this lol).
The cake is a lie!
Oh it's a great idea. RDS just isn't ready for that yet.
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
Yup, so you can maybe see where my hope was to join a 2016 RDS to Azure AD the way Windows 10 clients do (also havent tested this lol).
Windows 10 works, we use it.
-
@scottalanmiller said in Azure AD and OnPrem Windows Server 2016:
@bigbear said in Azure AD and OnPrem Windows Server 2016:
@bigbear well another issue, depending on where I store all my data. Do I launch a 3rd server with Vultr BLOB storage and share it to the terminal server, cause that would be another server without internet/updates/backup.
Or do I directly attach a volume with BLOB storage to the terminal server? Which seems odd...
Do you need the BLOB storage and why would it feel odd to have it be direct but not weird to have it on a different server? What's the benefit to having an extra server for storage?
I have a few TB of data so I assumed BLOB storage was the way to go. If I had less data I suppose it wouldnt be necessary. Looks like its only available from VULTR in NY/NJC data centers.
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
Looks like its only available from VULTR in NY/NJC data centers.
That's the good datacenter anyway
-
@bigbear said in Azure AD and OnPrem Windows Server 2016:
I have a few TB of data so I assumed BLOB storage was the way to go.
Yes, it would be then. But for RDS, unless you are making more than one RDS server, you'd still want it local (same server.)
-
@scottalanmiller said in Azure AD and OnPrem Windows Server 2016:
@bigbear said in Azure AD and OnPrem Windows Server 2016:
Looks like its only available from VULTR in NY/NJC data centers.
That's the good datacenter anyway
Oh yeah? Ive been deploying voice switches from several of their locations. I do notice occasionally Chicago has a lag.
