Has anyone ever used AppVentix with an exisiting App-v deployment ??

@Bram Wolfs might be able to help…

Thanks i dropped the AppVentix support guys an email

@Patrick van den Born just implemented this recently

Green feild implementation of Appventix i am ok with as used AppV Scheduler in past. This project is a migration away from the exisiting App-v infrastructure and to replace it with AppVentix so they wont need the App-v infrastructure servers. I have setup Appventix content/config shares and machines groups and just about to install the Appventix agent but the PVS image already has the App-v client installed and the publishing server and app-v client configuration are both configured via registry keys on the image and all the App-v packages are fully cached and mounted in the default cache location (C:\Programdata\App-v). My question is what cleanup do i have to do before installing the Appventix agent and migrating? i presume i have to remove the existing App-v publishing server from registry and the App-v publishing tasks scheduled tasks but what about the existing mounted/cached App-v packages ? (get-appvclientpackage -all | remove-appvclientpackage) will get rid of them but do i need to get rid of them ? Any registry cleanup required as package info/guids are still in registry?

I’ll have to doublecheck, but I’m pretty sure removing the app-v publishing server from registry is sufficiënt. The AppVentiX agent will take of the rest.

Hi John, we will provide you with all the needed information on monday morning 👍

Perfect cheers 👍