Note from Jack: Apparently, Brian (the person, not the website) can’t break abroad from desktop virtualization! Aftermost anniversary he noticed this absorbing account and asked me if he could address about it, so today I’m blessed to broadcast his column as a allotment of our freelance contributor program.
Image Source: jvwithmenow.com
By appointment your claimed information, you accede that TechTarget and its ally may acquaintance you apropos accordant content, articles and appropriate offers.
Microsoft appear a examination body of Windows Server 2019 a few canicule ago, and amidst all the new features, one notable affection is missing: the Alien Desktop Session Host (RDSH) role.
I aboriginal abstruse about this via a cheep from Claudio Rodrigues. I googled to acquisition added details, but all I begin were a few accidental bearding comments from bodies who said they couldn’t install the RDSH role on 2019.
So bygone I downloaded the Windows Server 2019 LTSB examination / 1803 / 17623 body to see for myself.
For some context, the trend from Microsoft is they’re aggravating to move bodies off active a GUI on Windows Server. This makes the images abate and simpler for containerization and virtualization, and, conceivably added importantly, it increases aegis by blurred the advance surface. Affective forward, if you alike appetite an *option* for the GUI, you’ll charge to use the Continued Term Servicing Branch (LTSB). If you accept one of the added Server 2019 releases, like the Semi-Annual Channel (SAC), installing a GUI is not alike an option.
Anyway, I installed the “Windows Server Standard (Desktop Experience)” from the Server 2019 LTSB ISO. Appropriate off the bat I noticed that the accession addendum explain that this advantage alone exists for bequest applications that crave a GUI. It says annihilation about alien users or RDSH.
Next, I added the Active Directory Area Casework role (and aggregate it needed) to set up a new domain.
Image Source: waitressresume.net
Then, appliance the Add Roles and Appearance Wizard, I chose the “Remote Desktop Services” accession blazon which says, “Install appropriate role casework for Basic Desktop Infrastructure (VDI) to actualize a basic machine-based or session-based desktop deployment.” This advantage should automatically install the RD Affiliation Broker, RD Web Access, and RD Session Host.
So far, so good.
The aboriginal two roles installed no problem, but the RD Session Host bootless with an absurdity about RDSH not existing. Added errors in the log declared that “The role, roles service, or affection name is not valid: ‘rds-rd-server’.”
I apperceive in the accomplished there were sometimes issues installing Session Host on the aforementioned apparatus that additionally ran the affiliation broker, so I spun up addition Server 2019 VM, added it to the domain, and approved to install aloof the Session Host role while appliance the Affiliation Agent and Web Admission from the aboriginal server. This install bootless in the aforementioned way.
Finally, I approved to install RDSH from the “Server Roles” astrologer instead of the “Installation Type” wizard. I arrested “Remote Desktop Services” box, but again on the abutting awning I alone saw the afterward sub-options:
No Alien Desktop Session Host.
Based on this, I feel assured authoritative the account that RDSH is not allotment of Windows Server 2019. My assumption is they aloof didn’t abolish this advantage from the Server Manager astrologer yet, back it looks like the 2016 adaptation that was aerial into 2019.
If Microsoft removes RDSH from Windows Server, what does that beggarly for the RDS world? What about XenApp? What about multiwin? What about… everything?
Image Source: bizdoska.com
The accompaniment rumor to Microsoft removing RDSH from Server is that they will be *adding* a multi-user, multiwin-based advantage to Windows 10. (Claudio and a few added bodies mentioned this on Twitter, and I heard about it a few months ago on my own too.)
In added words, Microsoft is demography Terminal Server out of Windows Server and affective into Windows 10.
If true, this is fantastic.
The alone acumen that Terminal Server / Session Host was anytime based on a server OS was that it was created in the 1990s back Windows Server was bare to abutment the assorted processors, huge memory, and server-specific accouterments (SCSI, etc.) that was bare to abutment assorted accompanying users.
The better change of the accomplished twenty years is virtualization. IN 2018, best RDSH / XenApp servers are VMs anyway, and Windows 10 and Windows Server both assignment appropriately able-bodied as a VM.
One of the downsides of appliance a server as a desktop is the almost-but-not-quite appliance compatibility. Best anybody would accede that if there was a artefact like Terminal Server / RDSH that was magically based on Windows client, (and absolutely accurate by Microsoft), that would be great.
The added acumen Microsoft had to stick with RDSH on Server for so continued was their antic applicant licensing restrictions dictating Windows applicant usage, ownership, hardware, RDS CALs, SPLA for Windows client, etc. (I won’t re-rant on that, but readers apperceive I’ve been appealing bright about my thoughts on how Microsoft licenses Windows audience for alien GUI usage.)
In the accomplished year, Microsoft has started to relax some of these restrictions, and the tea leaves are suggesting that this trend will continue.
Image Source: pointrobertsvacationrentals.com
So in 2018/2019, the afterward are true:
In this world, it seems like a breeze to cull RDSH from Windows Server. (Just the Session Host role, of course. It makes faculty to accumulate the added Alien Desktop roles in server, like the affiliation agent and web access, as those are “real” server roles that don’t crave a GUI.)
The alone actual catechism I accept is whether a multi-user Windows 10 is absolutely needed. If aggregate in a datacenter in 2018 is a VM, again what’s the aberration amid a distinct concrete host with a hundred Windows 10 VMs (1 user per VM) against that aforementioned host with ten multi-user Windows 10 VMs (10 users per VM)?
Some of the acceptable “RDSH against VDI” arguments still do administer here, like maybe that multi-user VMs are added efficient, while single-user VMs accommodate added adaptability (per-user suspend, resume, alive migration, resizing, etc.).
The alone added affair I can anticipate of appropriate now is for distinct app publishing / RemoteApp. In a use case area the users are aloof appliance a distinct Windows app, after a accomplished alien Windows desktop, again maybe it is added able to accept multi-user VMs that can circuit up sessions per user instead of abounding VMs per user?
But for rank-and-file alien desktop users, I feel I’d appetite “real” Windows 10, single-user desktop VMs (e.g. VDI) rather than multi-user ones (e.g. Windows 10 sessions).
If all this turns out to be true, again I can cautiously adumbrate that 2019 will be the year of VDI. 🙂
It additionally agency that an beforehand prediction, that my 2015 presentation of “RDSH against VDI” would be the aftermost time I anytime gave that presentation, will about-face out to be accurate as well.
Image Source: myperfectresume.com