This message was deleted.
# citrix-vads
Slackbot
05/19/2023, 1:33 PMThis message was deleted.
j
James Rankin
05/19/2023, 1:35 PMSo they're using Server 2022 with the "/SERVERVDI" switch to make them dedicated persistent one-to-one instances?
James Rankin
05/19/2023, 1:35 PMThe main gotcha you probably need to remember is there is no RDSH in the mix, so things like RDSH timeout policies won't work, you'll have to use the Citrix policies instead
James Rankin
05/19/2023, 1:38 PMAlso I'd be concerned about the potential Office licensing removal as things move forward (which they might well change, but hey-ho)
j
John Gallacher
05/19/2023, 1:38 PMThanks for the feedback @James Rankin. I think that's how they have tested it. We are looking to support the build of a new on-prem DC (other bits in AWS) and manage this official build/deployment of the new VDI workloads.
j
James Rankin
05/19/2023, 1:39 PMWe ran devs with one-to-one instances of Server 2016 in AWS though, and it worked fine
j
John Gallacher
05/19/2023, 1:39 PMYeah, the office is a slight concern I was going to call out... Im not even sure if they have the right licensing in AWS, that could be in breach but yet to confirm, cheers
j
James Rankin
05/19/2023, 1:39 PMMight need some significant retest when Server 2022 gets that awful Windows 11 GUI though
j
John Gallacher
05/19/2023, 1:39 PMGood call.. I will voice these points bud 🙂
d
Daniel Marsh
05/20/2023, 1:30 AMOffice is supported on Server 2022 through to 2026 if that helps.
https://learn.microsoft.com/en-us/deployoffice/endofsupport/windows-server-support
m
Matt Nation
05/26/2023, 1:44 PMI'm working on something similar now with a couple dev teams but using win10. First thing i determined was a standard performance tier disk is the biggest bottleneck. easy fix though.