This message was deleted.

There is no absolute answer to anything in IT. This needs to be communicated. Why people are always looking for one answer to all their problems, I don't know. 80-20 rule is the best you can do, IMO

That’s a battle we face on a daily basis. Like yesterday, where a physician questioned why our IT department didn’t have the knowledge to put Syngo into Citrix after he found out another hospital runs it that way. All of this is a direct result of covid-19. We’ve been trying to put more apps into Citrix as we intake them, but for vendors who refuse to support Citrix, our own management said to not go that route. Interesting shift. Either way, I look forward to seeing the look on their faces when we give them a quote for two new UCS chassis’, blades, and GPUs.

We find App-V Scheduler ideal for deploying to Citrix. I will do a blog post on it soon. We can actually simply run SCCM packages (that we have for our desktop estate) through the sequencer and 90% of the time it spits out a usable package which we then deploy through the Scheduler (we have no SCCM infra in our Citrix estate)

We’re an App-V shop, as well. I’d say that half of our virtualized apps are App-V delivered through Citrix.

App-V and App Layering? How is that working out?

App-V on the XenApp side of the house. I don’t have the App-V client enabled in my W10 VDA. Our XD image is relatively vanilla, and will likely remain that way since our app strategy is focused on XA, generally.

Sounds like a good strategy :)

It works for us. I’m not sure which direction we’re going to go for a majority of these apps - XenApp installed app or App-V. The smaller, lighter packages make more sense for App-V to me, while the garbage like Siemens Syngo are destined for XA.

I usually use an "App Delivery Matrix" with three or four options for dealing with applications. Fit each app into one of these. If you find something troublesome, just batter it into one of the holes. I've worked with customers before where they've ended up with nine or ten different methods of deploying apps because they've searched for an absolute answer for every single app. Pick a few methods and stick to them. In current project, I use Native Install (Packer) ---> App-V Scheduler ---> Cloudhouse Compatibility Container and have found I can shoehorn every app into one of these boxes

I have never really worked with App-V, I am not seeing that many customers anymore using App-V.

I’m interested in seeing MSIX App Attach, because that looks like it could really come in handy in this realm.

Jim did a session on App Attach for UKCUG but I haven't caught the recording yet. Think it is based on the old FSLogix App Container stuff so should be pretty slick if it works

Yeah, I've seen a few demos of it. Just waiting for it to become a general release so that we can take a look at it. I recall there being an easy way to convert MSI packages to that format, but I'm really interested in seeing if it's possible to somehow repackage an EXE installer to it. My guess is that App Attach isn't meant for that scenario, and that App-V/XA is probably the way to go there.