From what I'm reading, a hyper-v VM needs to have Windows 7, the guest agent, and a saved snapshot.
When I tell it to repackage an MSI (Google Earth 7.1) as an AppV package, it starts up the VM, connects with the guest agent, and then fails with Error -001: Virtualizing package Error loading conversion dll. Does anyone know why this is?
On a side rant, I don't have $2500 to visit training on this product. We have a couple hundred software packages and using Admin Studio seems like I'm writing a scripts to automatically make a package which then needs a script to install anyway. Nearly every package needs to have shortcuts removed and various other customizations. Making AppV packages manually is a relatively quick and straight forward task which this seems to complicate packaging, tripling the work that needs to be done. Perhaps it's great if you want every compatibility issue tested, but at the cost of 3 times the work. I'm quite happy with the manual software store I've created and using OneNote to document the packaging procedure for each package. Having the conversion to AppV automated sounds like a great idea, but not if I have to spend even more time customizing the automated installer. Maybe someone can help me understand how it actually benefits me.
When I tell it to repackage an MSI (Google Earth 7.1) as an AppV package, it starts up the VM, connects with the guest agent, and then fails with Error -001: Virtualizing package Error loading conversion dll. Does anyone know why this is?
On a side rant, I don't have $2500 to visit training on this product. We have a couple hundred software packages and using Admin Studio seems like I'm writing a scripts to automatically make a package which then needs a script to install anyway. Nearly every package needs to have shortcuts removed and various other customizations. Making AppV packages manually is a relatively quick and straight forward task which this seems to complicate packaging, tripling the work that needs to be done. Perhaps it's great if you want every compatibility issue tested, but at the cost of 3 times the work. I'm quite happy with the manual software store I've created and using OneNote to document the packaging procedure for each package. Having the conversion to AppV automated sounds like a great idea, but not if I have to spend even more time customizing the automated installer. Maybe someone can help me understand how it actually benefits me.