This message was deleted.

Had to log a case, this has me beat.

Yes there upgrades seem to go in circles

I had to do the DB upgrade manual to get it to work. The docs seem to be incorrect or I read it wrong. You have to run the Site DB Script, Monitor DB script, then Logs DB script. The enable the services so they register back to the DB. 3rd time was the charm.

@Ray Davis what error did you get?

Out of interest why are you doing in-place upgrades? as opposed to creating new delivery controllers etc.

That link is....... horrible. That`s a messed up upgrade path.....

@Nathan Sperry if I create new deliver controllers, then I have alot of work to move everything over. DG, MC, Applications, STAs, Polices. Is there something you know, that I dont? Please share 🙂 @Rody Kossen @Pflynn yea it is. But isnt to bad. Another thing when you run the disable service Script, then upgrade the DB with scripts, Once you run the Enable script. I had to do line by line. If I didnt it would fail as well.

@Ray Davis That is discouraging, I have a pending 7.15 to 1912 to do so much appreciated on the sharing

yea, I am curious about Nathan apporarch now.

Automation!! We build a new environment (DDC, SF, FAS, NetScaler, New DB’s) in parallel for our customers using DSC, so they have a rolling environment, roll forward or rollback. I asked cos it’s a service we offer (shameless plug), and it’s exactly the reasons you are seeing, that customers stick with their current version and put off the upgrade - hence why I asked

So you have scripts that migrate it all as well?

We don’t migrate, we create the DG, Apps etc that are defined in the DSC configuration. I’m not saying it’s easy, but once you’ve defined the configuration, then you can rebuild over and over again. Here are some of the DSC resource on github https://github.com/VirtualEngine/XenDesktop7

I appreciate the advice, but I am still confused. You build new, and the customer has to move settings over? Sorry just trying to understand.

No, the settings are defined in the DSC configuration I.e. what DC you want, what apps you want published. The environment is built from that. So in your case you’d specify all the settings you have in your existing environment in the DSC configuration, then you’d run it, that would build you an new environment that same as the old. New upgrade comes along, run the same config again, make sure any manual changes (🤨) are again incorporated into the configuration, run again - rinse and repeat and you have a Citrix Evergreen Deployment 😉

damn man, thats nice

That is a very interesting approach. I will take a good look at this, I smell lab time in my future - thanks @Nathan Sperry

Thanks Nathan for showing this. I am going to try this in my DR setup.

I can also build a full Citrix environment in ~1 hour using fast clone, full PowerShell script. You need to migrate your settings after, a PoSh script can import/export.