How to configure RDS with Windows Server 2022 (2023)

Introduction

In this TechTalk the Microsoft Most Valuable Professional Manfred Helber is speaking about how to configure RDS in Windows Server 2022.
#Microsoft #Server #RDS #Remote #Desktop

Content

Welcome to the tech talk by Mike, Microsoft email today.

Today we will talk about how to configure remote desktop services with Windows Server 2022, so the tech talks.

This is a live stream for your questions.

Also so feel free to put your questions around this topic: remote desktop services in Windows Server into the chat or into the feedback area.

On the streaming platform you are watching and for sure you can ask your questions, you can give feedback and you can leave your comments.

If you think that things should change should be changed, there should be other topics.

My name is Manfred Taylor I'm in Microsoft, most valuable professional in the category cloud and data center, and today we are talking about remote, desktop Services.

I will I have a live demo prepared where we will deploy a remote desktop services in Windows, Server 2022, but we will start with a few words about the architecture of remote desktop services.

So remote desktop Services, maybe you know them as terminal services or terminal server.

This was the previous naming used since Windows Server I think 2012, it's a remote desktop services, so we have the remote desktop Services protocol RDP protocol.

We have the remote desktop Services themselves and we have the RDS licensing.

This is also important.

We will also talk a little bit about the licensing about around remote, desktop Services.

When we deploy a remote desktop services in the live demo.

Later, we will see that there's a component Rd web access, Rd web access, helps us to access the desktops via web page.

It's optional! It's your decision! If you want to have this web access, um yeah option installed and configured.

If you install this component, you need to configure this component.

You need maybe an additional server, it's possible to deploy everything on one machine, but maybe you want to configure this on a dedicated, separate machine, maybe because of scalability the Rd Gateway, the remote desktop Services Gateway.

It's also optional, so I'm using the Rd Gateway for many of my live demo environments where I access the remote connection via the remote desktop Services Gateway.

This helps to ensure that it's not required to publish the RDS session host to external location because you access them via the Rd Gateway and the second Advantage is you don't need a virtual private Network to connect to your network? You only use the RDP Gateway you connect to the RDP Gateway and via the RDP gateway to your RDS session host.

So the rdes session host remote desktop Services session Host.

This is where many people still use the word uh the wording terminal server.

We see two different symbols: RDS on the left, hand, side and RDS.

On the right hand, side remote, desktop Services is available in two different flavors, so you can decide to run a remote desktop Services based on the session virtualization.

This is option number one session.

Virtualization means you have one or several or many RDS hosts and on each RDS host you have several uses.

They work together and um.

They work together on the same machine, but they have their dedicated sessions.

This is important session.

Virtualization means every user that logs on has its own individual session, his own individual environment, but they are sharing a host.

So what are the advantages or different disadvantages of the um yeah session virtualization, the big Advantage I, see in session virtualization is the easy way to standardize this sessions because you have this single host.

Let's imagine you only have one host it's similar if you have several hosts, but now, let's talk about one host, you have one host and on this single host, maybe you have 20 users that are running the individual RDS sessions.

Then you can install an application and the application is available for every user.

You can do some configurations and the configuration changes are available for every user, so this means session virtualization, from my perspective, very easy to handle.

If you have standardized desktops, if you have a similar desktop environments per user or for every User, it's even easy to manage.

If you don't have a dedicated management tool.

The second advantage of the session virtualization is, in my opinion, the costs.

Maybe you have additional ideas, so feel free to bring them up in the chat.

But from my point of view, these are the two advantages: easy standardized sessions with optimized or reduced management effort, and we have the cost reduction yeah based on the optimized management, but also based on the yeah sharing of the resources, because you can imagine, if you have one host with several users on this host, then we can optimize the memory, CPU usage and so on the option number two, the RDS host on the right hand, side is a virtualization based scenario.

Most of you maybe know this as a virtual desktop infrastructure.

Environment vdi in the Microsoft ecosystem means that we build an RDS scenario where our Target machines are virtual.

Windows clients virtualized on hyper-v important, is to know that in this scenario, we have an additional license.

That's called the virtual desktop access license.

This license is available separate as in subscription, and this license is part of the windows 11 Enterprise upgrade with software Assurance.

This is included um, the virtual desktop access license, and this means that in a session sorry in an um virtual desktop scenario in a vdi scenario, we have the situation that every user that connects to this RDS environment receives a dedicated, desktop um with on a dedicated machine.

So the advantages we have the full flexibility of a full featured virtual Windows client foreign that we have to manage either of these clients.

But for sure you will then use some management tools on premises or cloud-based tools like InTune from Microsoft or endpoint manager.

That includes in tune, and the maybe second small disadvantage is that you need more resources, because I think you can imagine a dedicated virtual machine per user needs more resources based on the dedicated OS installation compared to the session sharing, on the left hand, side the big advantages that we have more flexibility in providing individual environments so for sure, also in the session based scenario number one.

Every user has this individual session, but in the virtual desktop based scenario, the advantage is that every user has its own machine, so every user can install his individual software applications.

Um compared or in combination with discrete device assignment, we have even in RDS, based on session virtualization, more flexibility in the direction of computer-aid design, video rendering and so on.

What you can see on the right hand, side are the um, the yeah licensing options, so the RDS licensing server is also a server role or a dedicated server that is installed and the file storage.

And then, when we are thinking about users, every user that has an user profile, needs some storage where the files are stored, and we can configure this here flexible and we have the Rd connection broker.

The Rd connection broker is the component that ensures that our connection that maybe was closed or was lost, is reconnected to our initial session.

So this is the connection broker.

It's always in combination with active directory for authentication, so starting with Windows Server 2012 R2.

It was not any longer supported to run um RDS scenario.

When you have user-based licensing without an active directory domain in previous versions of Windows Server, it was possible to run in work groups.

Now you really should have an active directory domain.

It can also be a hybrid deployment we use here.

What we see is the minimum configuration requirement for sure this can also be a hybrid scenario.

Clients can be Windows, iOS, Android, Mac OS, so every client that provides RDS or RDP compatibility can be used here.

Foreign, if you have questions regarding the architecture, feel free to ask them, because this is exactly what we will build later in the live demo.

So I um will expect in the live demo that you have heard already this definitions and you understood what the different roles are for before we start with the live demo.

We should should talk a little bit about the licensing options, because in the session based virtualization scenario, we only need the RDS client access license in the virtual desktop infrastructure based scenario.

We need Additionally the virtualist of excess licenses and for sure we can use the Remo desktop services to provide full desktops.

This is what I explained or described, but we can also publish remote apps.

So it's not um required that the user always starts a full desktop session on the RDS host.

The RDS host can also be used to provide single applications to the client machines, the services and the licensing can be done per device or per user.

We are always looking at the accessing objects, so when we license per user, it's relevant for us how many users access the RDS host.

When we look at the per device option, it's important to know how many devices will access the RDS host um, depending on the option we have chosen, for example, per device, we can revoke a percentage of RDS calls to um free them for new devices um.

We have temporary calls for a specific period of days when a new device enters the environment, but we cannot over allocate the RDS line access license in the per user scenario.

Here's important it cannot be tracked within a work group, so it will not work in a work group scenario.

Um.

We have the situation that we cannot revoke the RDS calls, so they are connected to the specific user object.

Um.

We don't have any temporary uh RDS client access licenses, but um we have the situation that we can over allocate the RDS user client access licenses.

Important is yes.

Maybe you will violate the license agreement, but maybe you will not violate it because um here we can read.

Rds calls are assigned to use in active directory yeah, but the user is an um individual person.

So if you haven't um active directory object like um yeah sales or um yeah support or um sales sales, we had sales already support management or things like this.

Then it's not okay to use the user calls for this shared accounts, so it's always connected to a real person.

So it's a personal per user client access license.

So the wording here is not absolutely correct, so this is the technical way how it works so for each individual for each individual person that wants to use the remote desktop Services, we need a per user call if we use this licensing option and the assignment is done by the active directory user objects.

So if we have different versions of remote desktop Services, then it's important to know that the later client access licenses and I had this situation a few weeks ago.

This is the old table.

There's also a 2022 client access license.

Here.

We can verify this when we go to the um matching web page here.

I can show this to you here.

We have the latest version and we have here also the Windows Server 2022 client access license.

Here we have the situation that the newer RDS Cal version is also or can also be used to access the previous RDS session hosts it's similar to the client access licenses in Windows Server.

If you have a newer client access license version of Windows Server, you can use this Cal to access previous Windows Server versions, but the difference is the Windows Server.

Cal is only a piece of paper.

This is not a technical thing that has to be registered for the Windows Server call.

We don't have a license server for the RDS client access license.

We have a license server.

This means that this license has to be activated and there you will see issues if you have a newer, RDS Cal version, but you haven't previous licensing server.

So even if your licensing server is Windows, Server 2019, you will not be able to register the RDS 2022 RDS Cal, so from the licensing perspective.

You're allowed to use this, but from the technical perspective, it's not possible to activate this there.

It is important to understand that there is an service, that's called the Clearinghouse service.

So when you enter the RDS calls in your RDS licensing server, then you are asked if you want to call the Clearinghouse service, and if you have this situation here, then you should call the Clearinghouse service there.

You can provide your RDS 2022 license key and you can downgrade to, for example, 2019 or 2016 or 2012 2012 R2 to use this newer license key within previous RDS licensing server.

This is important to understand because, regarding the usage rights, this is absolutely identical from the Windows Server call and the RDS call, but regarding the handling, the difference is that the Windows Server call has to be.

The customer has to buy the client access licenses.

They have to be documented, but you don't have a technical service where you enter them for the remote desktop Services.

We have this technical service to enter them.

Okay, the RDS calls.

Hopefully this is clear because we will see something about the RDS server in a few minutes in the live demo.

Another important thing is the office compatibility, but I would say: let's talk about this um after the live demo, so first we will go to the live demo and I want to connect to a Windows server and I have already prepared this Windows server.

With a few things.

The server is member of iactive directory domain, so here we can see the d201 as a v14.

It's part of my mhd molapte domain.

It's a Windows Server standard.

This is absolutely fine to use a standard edition for remote desktop services.

In my specific scenario, this is a virtual machine.

This is okay and this is supported, so you can run remote desktop services in Virtual machines um.

This is fully supported for sure.

You also have to plan with the required resources.

Yeah.

Okay, first step is to go to manage, address and features, manage, address and features, and here we'll go to next and in the Second Step.

Usually we click to next for the role-based or feature based installation.

Today we want to have a remote desktop, Services installation.

So there is a dedicated second special option here.

So I will choose this remote desktop Services.

Here you can see on the left hand, side in this grayed out next steps, there's a difference when we select role based or feature-based installation.

We have server selection server roles, features confirmation in the Remo desktop Services.

We can see.

Oh it switches to deployment type deployment scenario, role, Services, Rd connection broker, web access, virtualization host confirmation or completion.

So it's a completely different wizard, so you can also configure remote desktop Services via the first option, role-based or feature-based installation, but you don't have a wizard, then that knows the dependencies between the services, so I would have absolutely recommend you to go to remote, desktop Services installation.

So next, what will we do? A standard deployment standard employment allows you to deploy remote, desktop Services across multiple servers or do I want to choose a quick start.

Quick start allows you to deploy remote, desktop services on one server and creates a collection and publishes remote apps.

So this is interesting because, usually you have an standard deployment.

This is with um pre-configured values and you have typically options like manually, configure or individual deployment, or something like this.

Here we have standard or quick start.

So in the quick start, it's clear I have less configuration, steps or options.

You can see.

On the left hand side.

This is shortened here in the standard deployment.

I will configure this manually.

What I will do with you together? Is we choose the standard deployment, but we build something like the quick start yeah.

So the result will be in our configuration that everything runs on one server: let's go the quick start, sorry, the standard deployment path, then the deployment scenario, the question about session-based deployment or virtual machine based deployment.

So we discussed this when we talked about the lies, sensing and the architecture, and here you have to decide now we have the standard deployment choosing.

We could also build- and let's say, hybrid thing: we could um have some users that use a session virtualization.

It's some users that have a virtual desktop infrastructure based scenario because in yeah the beginnings of remote, desktop Services, the planning guides said: okay, if you have the standard users with their standardized workload, so the typical standard information worker, then this is the typical session based user, with a session virtualization for the users with more individual requirements like developers, maybe managers and so on.

We have the virtual desk of infrastructure scenario and for users that need the full functionality they usually will have their full featured client both is possible.

So in many companies the employees have a full featured client.

They have some remote desktop options, because the advantage of this remote desktop thing is that between the clients or the end point and the RDS host, we only transfer encrypted um yeah picture information, it's encrypted a graphic stream um, so the workload runs on the RDS host environment so on the sessions or on the virtual machines inside the RDS host environment, and this means that we can ensure that the content and the workload itself and the data is in an environment that is secure based on our security policy and the endpoint only receives the video stream.

So not the data itself, not the um content, not the documents and so on, and so both is a it's.

A good choice.

We want to select the session based deployment, because this is what we typically understand when we talk about the remote desktop services, so we will choose the session based desktop deployment.

Let's go to next and now we can see.

Okay, we have several components.

We have the connection broker.

We talked about this in the overview we have the web access and we have the session host.

The session host is the central component, so the session host provides the sessions or the applications I'm always talking about sessions, but this can also be published.

Applications.

Okay, let's go to next, so the first question is which server will be the connection broker? Okay, I will use the server 14.

so which, when you are wondering how can I get here additional servers if you want to have a deployment where you say: okay, the connection broker is server 14.

The web access is server 15 and the session host server 16.

Then you can add this additional servers here on the all servers list.

I can show this to you when we have finished this wizard here um.

So then we have a question.

What are you thinking about? The changes Microsoft has announced around the Windows Server 2022 and Office 365 or Microsoft 365 apps I have this topic with me, so we will talk about this um in um, 10 or 15 minutes, or if the deployment takes longer.

I will pick up this topic when we are waiting for the deployment here so um in a few minutes.

We will talk about this uh things here.

Okay, so if we want to have different servers, we can add them on all servers.

I will show this to you when we finish the wizard here.

So the next step is the Rd web access.

So and here I have a check box.

Install the early web access raw service on the Rd connection broker server.

I can also add this server, so there are different options where I can say: Okay I want to have the same server.

Okay, let's go to next select the server from the server pool which to install the Rd session host.

If more than one server selected, the Rd session host raw service will be deployed on all of them.

This is a farm, and this is very interesting on the remote desktop services to decide not only around one server but several servers- and this is usually also the advantage I see if I have a standard deployment, not the quick start, because if I run, the quick start, I always have the situation that the connection broker and Gateway is on one of the nodes for sure I can extend by session hosts, but I would always recommend the standard deployment then I go to next, and then we have the confirmation and I have a warning here that says: uh.

Okay, the session host server will restart.

Okay, I cannot avoid this I want to have the automatic, restart and I want to deploy these rules.

Now I have a wizard with three steps.

Actually it's still pending now, then it's deploying the remote the broker service.

Actually, this is installing Rd connection broker all service.

We then will have a deployment of the Rd web access role, service and so on and so on.

So it will configure this step by step.

If we have several servers, then it will also include this additional servers, and this is a perfect uh time.

I think it's not so interesting to to wait for this uh for this installation.

Uh progress bar here so I will switch to this topic where we already had question about uh in the chat so uh.

What's about the support for the Microsoft or Office 365, apps and remote desktop services.

So when we look at this Matrix here we can see we are actually installing the Windows Server 2022 and the Windows Server 2022 is end of support in October, 2031.

I think you know this.

We have the end of support for Windows, Server, 2012 and 2012 R2 in October next year, and we have the support and for Windows Server 2022 in October 2031 so from today in nine years and on Windows Server 2022.

When we are running office for sure we have a support for office 2019.

This was the previous office version and we have a support for office ltsc.

So the new office version um in the volume licensing environment is called office ltsc for long-term servicing Channel.

You can and I usually also do this at the version.

2021, so I always speak about office, 2021 ltsc and there will be an office I assume.

This is not an announcement by is but I assume.

When we look to the Past, then it was 2016 2019 2021.

Maybe there will be an office 2023 or 2024 um rtsc also so the LTC.

This is not the home and business, but this is a volume license version of office to be allowed to use office in RDS scenarios you need office based on the volume license Channel and the office is not licensed for the terminal server.

It's not licensed for the RDS host, but the office is licensed for the accessing device, so the office 2019 or office 2021 ltse.

If we have 10 devices that access an RDS host, we need 10 of these office 2021 ltse licenses.

So we have 10 devices that access an RDS host.

We need 10 of these licenses, not 11.

We don't need an additional license for the RDS host, but it's also not okay.

To only have one license for the RDS host no licenses for the accessing clients, because when we look at the licensing terms, there's no license for the RDS host itself.

We need a qualifying license on the device that accesses the RDS host.

There's nothing new.

This is we know this since years, but what is interesting and new, and what we should know is that the Microsoft 365 apps- maybe you know about this change of the wording we already had last year, um The Office 365 family um.

That includes um um applications like word excel PowerPoint, Outlook um renamed the package where we have the apps in there, so this office applications from Office 365 apps to Microsoft 365 apps, so we have Microsoft 365 apps for Enterprise and Microsoft 365 Apps for business and the Microsoft 365 apps for Enterprise that previously The Office, 365 apps and this functionalities also included in the Microsoft 365, E3 or A5 plan, and also in the Microsoft 365 business premium, but only from the business family.

Only in the business premium.

This Microsoft 365 apps is very popular popular via the app subscription itself or via E3 E5 plan, the business Premium plan and these um plans that includes the Microsoft 365 apps for Enterprise.

They include include the use strides for RDS scenarios.

This means you are allowed to use with your licensed user the office on up to five personal computer devices, five Tablets five smartphones and on an RDS host it's additionally, it's not a replacement.

It's an additional, because the Microsoft 365 apps for Enterprise include the shared computer activation.

This is the licensing perspective.

When you try to install this Microsoft 365 apps on a Windows, Server 2022 based terminal server, then you will see this works.

This works today.

This worked four weeks ago.

This worked last year, so when Windows Server 2022 was announced or was published when it was General available, this combination worked.

But what does this n a mean? It's not supported.

This here is the support Matrix.

This is not the licensing Matrix.

This is not the what technically Works Matrix, but if you want to have a specific implementation at your customer site, you have to ensure that it works from a technical perspective.

You must ensure that you are allowed to use this regarding the licensing terms and then usually you will ensure.

That is that it is supported by the um by the software vendors so by Microsoft, because if it's not supported the issue is, if anything does not work, and you can't take the Microsoft support, the Microsoft support will say.

Oh sorry, it's not supported.

We cannot help you and we will not help you.

So this is important to understand the Microsoft 365 apps are not supported on Windows Server 2022.

They were never planned to be supported on Windows Server 2022, because when Windows Server 2019 was General available, Microsoft said: oh, we will not support the Microsoft, 365 apps and so those days this were the Office 365 apps.

But then Microsoft said, oh, we heard to the customer feedback and we had many customers.

That said, we need this support.

So Microsoft said: okay, we will provide the support for Windows Server 2019 again and more than one year after Windows Server 2019 was launched.

Microsoft provided the support for the Microsoft 365 apps, but Microsoft said in the next version of Windows server.

We will not do this again.

We will not support the apps, why? Why will Microsoft not support the app? So why has Microsoft this this problem in supporting labs? Let's talk about the the different life cycle: Microsoft, 365 apps.

This is a modern life cycle application.

This means once a month we have a new version of the apps, the Windows Server.

It's a long-term servicing platform.

This means a customer can buy this server and run the server um 10 years without changing the version.

I only have to install the security updates and hotfixes version upgrades it's my decision in the Microsoft 365 apps in the modern lifecycle, application and, for example, also in the windows clients, something like Windows 11.

It's not my choice.

To upgrade to new versions.

When Microsoft publishes a new version, I have a specific time period.

I can use to install this new version.

For example, in Windows 11 we have a new version once a year.

The version 22 H2 was released a few days or weeks ago, and now a Windows 11 Pro customer has 24 months to install this version.

The Enterprise customer has 36 months so two or three years to install this new version, but Microsoft can be ensure that in later three years everybody is on 2020 H2 and if not, this customer is not any longer supported in Windows Server.

We don't have the situation now.

You can imagine that it is difficult to bring an um application that has a modern life cycle together with an OS platform that has a fixed life cycle or long-term servicing Channel life cycle, because when we think about Windows Server 10-year support in this 10 years, we have 120 new version of Microsoft 365 apps and they all have to be supported if Microsoft opens the support for the apps, so I absolutely can understand this limitation from the technical perspective um, but on the other hand the customers are asking for for it.

So the customers don't care about this life cycle things they only say.

Oh, we have an Ras scenario.

We want to run the Microsoft 365 apps there and the first answer was that Microsoft said: okay, then you can license office 2019 or 2021 ltsc, but the customer said yeah, but we bought the Microsoft 365 licenses or we have a subscription for the Microsoft 365 licenses.

We don't want to have additional licensing costs, so Microsoft said: okay, we heard your feedback again.

Dear customers.

We will have a look at the support for Microsoft 365 apps on Windows server, and the discussion already started at the end of last year, but the first feedback from Microsoft was in September.

So we can see here.

The 6th of September well in Christian wrote.

Okay, we will check if this can be possible.

Then um the on Friday, the 14th October.

We had a new post from Microsoft.

That said, okay, we will add the support for Microsoft 365 apps to Windows Server 2022, but not today, and this is important to understand when we go to the web to LinkedIn Twitter Facebook.

Wherever you are looking for news around Microsoft Technologies, you will read in those days very often Microsoft ads or Microsoft added support for Microsoft 365 apps in um, two um Windows Server 2022, but this did not happen today.

This is important to know so today we still don't have the support.

Microsoft says: support for running Microsoft 365 apps on Windows Server 2022 is currently in preview.

So if the preview shows that there are issues that this will be not possible, then we will not get a support for Microsoft 365 apps Windows, Server 2022, so it's in preview Microsoft is testing this it's not available.

Today.

When you are asking me, when will we have the support for the Microsoft 365 apps, then um? Here we can read, we will provide information which version of Microsoft 365 apps are supported on Windows Server 2022 at a later date later this month later this year somewhere next year.

We don't know this because actually it's in testing.

This means that we have a comment.

Maybe this is not uh perfect for trustworthy.

In my opinion, this is not an issue of trusting in what Microsoft said because Microsoft always says: if you see issues or if you want other things in the products, please give feedback.

There are several feedback platforms for Microsoft and many many customers gave feedback about the Microsoft 365 apps in Windows server from the technical perspective.

If you say: okay, let's don't, let's talk about Microsoft only, let's imagine, there's an OS platform from any vendor that has a long-term channel that is supported for 10 years.

The customer don't want to have any changes in there and on the other hand, we have a modern application.

That brings an update every month and I have to install these updates in a very short time period.

Then everybody that's a little bit familiar with Technics I.

Think I think we'll agree with me that this is difficult to bring this together and, on the other hand, Microsoft has the customers that say, okay, but we want to run this together.

We have the requirement to have this together in Microsoft, listens to these customers, but um.

It's it's no um announcement or anything like this, but think a little bit further.

What maybe can happen in the next step? There will be a new version of Windows server in two or three years, so the release Cadence for Windows server is two to three years, so I assume that we will have a new Windows Server version, maybe in 2025 or something like this um, and we will have again the situation that from the technical development here, it's very very difficult to bring together this new Windows Server release with the Modern Life Cycle applications, and if the customers have more and more demand, what would I do as a software vendor I would say: okay, maybe the customers want to have a modern life cycle server release.

Maybe the customers want to have a new server release every two or three years they have to install within two years and I'm pretty sure that this is absolutely not what the customers want.

So um I I'm, not sure what I should think about this.

So I think there are many modern Technologies like Windows, 365 and Azure virtual desktop that um don't require to run this Modern Life Cycle applications on a Windows Server platform, but for sure, if you are the customer and if you are running RDS for years, you will not be happy with the situation that the modern applications are not supported there um.

We don't want to go too deep into discussion.

If this is good or not good, so I'm I would be happy if you spend some time to think about my words about this compatibility.

That's in my opinion, not a thing of trustworthy or uh.

That Microsoft wants to force us in one or in the other direction um, but um from the technical perspective.

It's really difficult to bring this together so important.

Today, 24th October 2022.

We still have the situation Windows, Server 2022 and the Microsoft 365 apps are not supported together.

So when you run them today, you could have run them half an year ago you could have implemented a terminal server or RDS host with Windows Server 2022 in August September last year.

So today it's still not supported in the future.

It's relatively I'm.

Also relatively sure.

I cannot guarantee this, but it's relatively sure that Microsoft will add.

This support.

Microsoft will not add the support to an unlimited time.

They already announced this.

They will add the support till October 2026., it's comparable to what office ltsc does um, but I'm pretty sure that this will be um.

Yeah realized I'm, pretty sure that this will be um yeah announced, but I cannot guarantee when this will be announced.

Okay, and if you are looking for these new things like Windows 11 in combination with Microsoft 365 apps, you can do this in an virtual desk of infrastructure scenario.

You can do this in Windows 365.

You can use this in Azure virtual desktop and you you can use this in Azure virtual desktop on Azure stack HCI, so there are many new options.

This is my recommendation to have a look at this, but if you prefer to run the RDS the traditional way, then you will have the support late in 2022 or 2023.

There's no final date in the list, but always keep in mind.

Today.

It's only for testing, it's not supported for production, environment, okay, let's have a look at our deployments, so we had enough time to wait for the server restart.

I will look on to the RDS host.

I will use the administrator at mhdmolab.de and we'll enter the password Here and then, let's check what the configuration did now, it's completing the configuration here on the machines we needed the restart for the session host.

Now the role service implementation is still in progress.

Um to fill the time till this installation finishes.

Let's go to another machine here here.

This is another Windows Server the servers in the work group.

So let's take this one here, foreign, let's take this machine, so this is a Windows Server 2022.

Also it's a data center, but this is not relevant, and here we can see remote desktop is disabled on the server 12.

different server, different scenario.

If you enable This, Server remote uh the the remote desktop access remote desktop on this computer, then we have the situation.

We don't have an RDS Host.

This is only a remote desktop connectivity for administrative tasks, so this RDP or Rd remote, desktop Services enablement.

Here is only for admin.

No licensing Administration, only no RDS call required no RDS call included.

This is important because when you enable remote desktop here, you have three sessions, One console session and two remote sessions, but this does not mean that you have three RDS client access license included.

This only means that you can use Remote Desktop to manage this server for administrative tasks.

It has nothing to do with the role administrator.

So if you are an administrator and active directory, this does not mean that you can do anything on this server if you use the server.

So if my user man, for it is part of the domain administrators and I'm, connecting This Server to run a locally installed word or explore PowerPoint to do my preparations here, then I need RDS calls for me and the other users that are using this machine.

So this is important.

This configuration here only for administrative tasks.

This is not an RDS Host.

This is only for management.

No RDS calls included.

We don't need RDS calls here on the deployment on the server 14 that has finished now I can close this year now.

Here we have an RDS configuration, and here we can see.

Okay this machine has an web access server it's a little bit untypical that this icon is gray usually would expect some colors.

But this is the default visualization.

Here we have the connection broker.

We don't have a virtualization host, because we did it decided for the Rd session host, and now.

We can add the Gateway and the licensing via clicking on this plus the Gateway is optional.

Yeah it's my decision.

The licensing has to be installed within 120 days after deploying the RDS host, so for the first 120 days, we don't need a license.

Server from the technical perspective from the licensing perspective, we have to be licensed.

Already now so here we can see the servers in the list and in the collections, we have our sessions.

We provide here.

We can configure a session collection.

And I, could say, okay, I, have a new session collection? This is in session collection.

Zero! One, for example, and I can decide for my session collection host.

I can decide for the user and groups.

I could say: I have also the domain admins um.

Usually you would use your own groups, but I want to have this in a short time.

We only have three minutes left, so I will add my domain administrators I can decide if I want to use a user profile.

Disk I can confirm this.

Then I will have a session collection here and then I can add the applications to the session collection.

So here I have the um session collection, zero.

One and I could add the remote app programs and the published desktops.

So it depends on what I want to provide here.

Okay.

So, as I mentioned, we are already at the end of the time of this Tech talk.

If you have any questions about remote, desktop Services feel free to bring them up in the chat.

Also, your feedback is welcome, also critical feedback.

We have this feedback about trustworthy and the support life cycle, and if you have more questions about different topics, not only your remote desktop services but for sure also remote desktop Services then feel free to join tomorrow.

The tech talk um there.

We have a take talk support hour, also at 11 30, where I have one hour for all your questions on the October 31st so next week, Monday again at 11, 30 Charming time so the time in your time zone where you joined, we will talk about how to install and configure active directory three domain services and for for or on Windows Server 2022.

So, hopefully you will find time to join tomorrow.

The tech talk q, a and next week, Monday the tech talk about active directory domain services and DNS now feel free to bring up your feedback to the chat.

I will close this session now say.

Thank you for your time.

Thank you to Microsoft Emir for supporting the tech talks and see you tomorrow at 11, 30 for the tech talk, q, a bye.