This message was deleted.

Yep plenty of methods. Pick your poison. MDT seems to be the popular method but if you have other automation tool then use that.

app layering is popular, i prefer MDT even if you spit that into layering for any reason [5:24 PM] we prefer to stay 2016 vs 2019 since it scales better but either way i'd say MDT/choco kinda of install if you have that you can leverage that solution into othe rproducts if you decide to.

Agree on 2016 vs 2019.

I suppose I should clarify, and likely cause some people to cringe/twitch. I mean we simply layer our changes on over time. Same static base image, years old, with tons of changes. We do log them.

That’s fine as long as you track what changes. Try to incorporate automation though.

Thanks @Jarian Gibson

One thing you’ll have to worry about is image bloat and possible rot.

Yea nothing wrong with what you are doing George. Most are like that or came from that. The automation route is the next evolution. Build it in code, store in version control is the next after that. Environment creation is the usual first constraint. Then testing is next. Not seeing many do automated unit testing to ensure the image works as expected. Most just do a UAT type thing. The tools are getting better for us though. Only a matter of time.

@Jarian Gibson @RSRevord Would you gents happen to have some articles regarding the 2016 v 2019 scaling?

@George Gibson GO-EUC has some good stuff - https://www.go-euc.com/performance-comparison-windows-2016-vs-windows-2019-rdsh/

@Jarian Gibson is that link working for you? I'm now wondering if our filters are messing with it

Yes it works for me

Thanks!

no articles, but i can say from our testing 2019 got about 10-20% fewer people than our 2016 implementation. So since we didn't NEED 2019 we went 2016