In years gone past, I built an automated packaging tool to take a dump of packages from SCCM and convert them one by one to App-V. It worked ok for some apps but left a lot to be desired. Like
I am very fortunate to work for a manager who understands the need for more than one app packaging and delivery product. He understands that each product has its strengths and has suggested nominating a primary solution and a secondary.
This post is titled ‘Using App-V for Legacy TLS’ but could be applied for various different Internet Explorer settings. I picked TLS because I was speaking with a former colleague who was approached by his management about needing to disable
First for the App-V Management Servers, they are just web services that also point to the AppVManagement database. There’s really no need to load balance these but what I do is create a CNAME for these. In this post we
With our publishing servers setup in part 4, we are ready to validate before configuring our load balancing. There’s no sense load balancing if some of your publishing servers are duds. Before configuring load balancing, we will want to test
In part 3, we setup our Management Servers, now we need to setup our Publishing Servers. Go to your MDOP Install Media Explore the media Navigate to App-V–>App-V 5.1–>Server and launch appv_server_setup.exe with run as administrator. Click Install Click I
