AdminStudio client install Best Practices
So as part of the great Wise -> AdminStudio migration, I'm interested in finding out how other people have their systems setup. Using Wise we currently have a server running the database and with an instance of the client installed (typically unused). Our packagers then install the Wise client on their packaging VMs and complete all their work on those (captures, edits and so on).
Running up AdminStudio I've installed it on the server, but realised that will probably burn up a licence. I've also installed the client onto a VM and while that's functioning for Repackager, InstallShield, Tuner etc. it doesn't look like it'll be the best way to run Automated Application Converter for example.
Also, this AdminStudio page (http://www.flexerasoftware.com/pl/8967.htm) suggests installing Repackager on a physical box and running it from the packaging VMs.
So - how do people have their AdminStudio setup? Installed on the server? Used from the server? Installed on each packaging VM? Installed only on desktops?
I'm working with Wise at the moment but have worked alot with Installshield over the past few years. The setup was usually to have a central network location containing the repackager tool, and one (physical) machine for each packager that had an install of AdminStudio on it. Then we each had a bunch of clean VM's used for software captures. So the capture of software was done on the VM infrastructure using the network install of the repackager, the actual build of the packages on another machine.
Installshield licensing policy dictates that you need one license per packager. You can easily return a license to the pool when uninstalling, but that's why we had actual physical build machines for each packager.
Have you tried this..
We honstly just install adminstudio/installshield on each packager laptop/PC.
We then use the standalone repackager on VMs to capture legacy ->MSI conversions. Please note, we just use the repackager to create the initial irp, we then use the full adminstudio on our own machines to edit irp and build ism/msi as needed.
You can run the repackager from a share, but I have found it pretty easy to just use the standalone repackager instead of messing with shares and network access etc.