This message was deleted.
# citrix-vads
Slackbot
07/19/2022, 1:10 PMThis message was deleted.
n
Nick Panaccio
07/19/2022, 1:18 PMWhile our controllers are running S16, I don't think we'd change the specs when we move to S22 - 4 vCPU/8GB.
a
Andrew Gresbach
07/19/2022, 1:19 PMawesome thanks ! we also currently are using the 2 server names of our current controllers in the registry for each VDA so i'm thinking for this we'll need to change that to a DNS name to make the switch easier, then setup the 2 new servers w/ 2203 and then figure out how to connect our existing DB to that and cut over (not sure how that process works yet)
r
Rob Zylowski
07/19/2022, 1:19 PMYoure fine with that Andrew just make sure to configure your cpu with 1 socket 4 cores so the sql db lhc mode uses can use all the cores.
a
Andrew Gresbach
07/19/2022, 1:20 PMoh cool thanks for the tip!
n
Nick Panaccio
07/19/2022, 1:21 PMI can't even recall the last time I saw a VM configured as 4/1 and not 1/4.
r
Rob Zylowski
07/19/2022, 1:21 PMVmware defaults to 2x2
n
Nick Panaccio
07/19/2022, 1:21 PMXenServer does, too, actually
Nick Panaccio
07/19/2022, 1:22 PMBut it's like the first thing we change
a
Andrew Gresbach
07/19/2022, 1:22 PMthis is our current setup so i think we're good
r
Rob Zylowski
07/19/2022, 1:23 PMThats cause you are you. Most orgs dont.
a
Andrew Gresbach
07/19/2022, 1:23 PMthats how we have our VDA's as well (i cpu/multiple cores)
r
Rob Zylowski
07/19/2022, 1:23 PM✅
a
Andrew Gresbach
07/19/2022, 2:20 PM@Rob Zylowski is there any documentation on how we would approach a cutover from 2 existing controllers on 1912 (server 2012 r2) to 2 new controllers on server 2022? wasn't sure if it was better to setup the 2 new controllers on 2203 LTSR and do a cutover from the old 1912 to 2203 or if it was smartest to install 1912 on the 2 new controller servers, add them to the existing site, then remove the 2 old and then upgrade (the kicker is doesnt look like you can install 2203 on server 2012 so have to go to newer otherwise i'd just upgrade
r
Rob Zylowski
07/19/2022, 2:22 PMIts actually a full migration to a new site. If you need to upgrade the infrastructure sevrers oses there is no other way as we dont support inplace os upgrades.
a
Andrew Gresbach
07/19/2022, 2:24 PMso what you're saying is best option is to leave the current 1912 (server 2012) site alone.....and seperately setup 2203 (server 2022) as a new site and do a full cutover/migration when ready?
r
Rob Zylowski
07/19/2022, 2:30 PMThat what most customers do becasue they are looking to reset every once in a while. For the ddcs what you could do is create a new ddc with an updated os, then remove the old ones, then upgrade that in place. then add another new one. since you use persistent machines that may be a better option. For Stiorefornt you woudl just create a new server group.
💯 1
n
Nick Panaccio
07/19/2022, 2:31 PMWe did that with 7.15 (jumping from 7.6ish), created new sites entirely. We're on 1912 right now, but will be upgrading to 2203 eventually on the same sites.
r
Ray Davis
07/19/2022, 3:45 PMI did that as well many times. The biggest issues is when a company has high security and you have to open all the ports ect/cross reference everything.
a
Andrew Gresbach
07/19/2022, 5:51 PMso you're saying in our situation the smart route might be setup the 2 new controllers on server 2022 with 1912 (to match current environment), add to the current site (so we'd temp have 4 ddc's instead of 2), then remove the 2 old DDCs (on 2012 r2) and then do the inplace 1912 to 2203 upgrade?
l
langsbr
07/19/2022, 6:05 PM1912 to 2203 for us was an easy peasy upgrade, not sure I'd make it a site migration for only 500 VDAs.
a
Andrew Gresbach
07/19/2022, 6:38 PMcool ya hoping to make this as painless as possible. those old 2012 r2 servers are the kicker here so wondering if what i mentioned a little above is the best approach (if i'm understanding Rob correctly)
2 Views