This message was deleted.

Not hard at all. I have some notes I can send.

You mean the PVS service in Azure, or just running PVS devices in the Citrix Cloud control plane? The latter is hardly different from the traditional way at all

Yea, good point. So running Citrix PVS on premise but hooking it into DaaS(Citrix cloud) or Setting up PVS in Azure to DaaS? Azure side I have not done yet.

PVS hooking into DaaS pretty straight forward. Integration has also got better recently.

I have a doc I made, but it's not finished. I can send it to you to get you going. But remember it's not finished.

@Ray Davis it is time for a blog 🙂

@Ray Davis doc has all steps it's just missing you have to change the licensing to Citrix cloud on PVS farm properties as well as install a special license SKU on your on prem license server

I used a script to generate the devices, create the VM‘s and configure DHCP reservations. After that I used the new export wizard in the PVS console to add the devices to a machine catalog. I plan to write a blog about it.

Yeah we need that blog @Dennis lol

Hey Guys, sorry for the late response. thank you for all of your feedback! i'll review it over the weekend and also look for other articles! Thanks so much! i hope i can repay you guys in the future with same type of feedback!

Here is the option John referenced “cloud” tick box. I will finish this doc and release a blog soon. No need for a payback man, we are all helping each other out in this space. Like @Webster Webster did for us when we were wet behind the ears many years ago. :)

Just as a note it's not "required" to change an existing PVS server licence to a cloud one if you are already licenced with traditional licences. But something worth keeping in mind is "if I remember correctly it's been a couple of years", once you install the SDK into PVS you cannot use the xendesktop setup wizard for traditional on prem ddc's. It's cloud or on prem not both.

Install pvs console on another machine to manage on prem vms if not moved to daas yet. Then pvs servers with updates sdk manage daas

Did they change the sdk requirement recently and that’s no longer needed?

why would anyone still do PVS? unless snapshots replication is an issue, I don't see much reasons for PVS.

“I’ve always done it this way” is what I always get or “we tried it in 5.x days and didn’t like it so…”

still a lot of folks that just don't like MCS.

Amazing notes @Ray Davis. You're always very disciplined with your doco.

Thanks man. That's because I can remember nothing lmao. But I document things so I have my own little repository

@Jonathan Pitre, that could be the topic for a really cool and fun debate at an in person event.

I will say, I am liking MCS a lot more now. Especially in AHV setups. I have PVS in my lab, and I looked at it this morning, and I was a bit slow doing things. I am liking MCS a lot more now than ever. I would like to get on on the event @Jeremy Saunders if you guys decided to do it.

@Jeremy Saunders definitely Couples of MCS Advantages on top of my head -No Sysprep to run -No Reverse Image to do for VMware tools updates for instance -No possibility of Windows Updates of breaking the network connectivity -No Extra SQL BD to manage -No dependency on licensing server -No extra agent to maintain -No extra legacy MMC console to maintain -Manageable through a web console! -Same RAM Cache mechanism as PVS as long as you install MCS IO -etc

No E1000 hack either for VMware Tools install (quicker that than reverse image) Reduce Infrastructure footprint (no PVS servers) No TFTP/BDM and DHCP setup Helpers needed.

@Jonathan Pitre music to my ears

new pic

Don’t have to worry about networking impacting your images streaming…

It's a lot less faff on, I avoid PVS where possible now

the only pro for PVS I can think of is easy VHDX replication

Depending on your environment, that can be easy. Especially with some stuff we are doing with AHV templates.

Easy with Nutanix indeed

And it will be getting better

I'm over here like..

@Jonathan Pitre, aside from... -No Extra SQL BD to manage -No dependency on licensing server ...the rest are all minor and irrelevant in my opinion if you've got a good automation tool in place. Have been using MDT for 13 years, so this stuff is just so simple for me. But yes, for those that struggle with the items you list, I take your point...BUT you will never win the debate! 😂