Hi,
We’ve got a need to be able to build installers on ephemeral instances of Windows server; we’ve gotTEam. These are virtual machines either on an on prem hypervisor or on cloud provider VM’s. What’s more we’ve been directed to try and push for keeping the build instances on docker images.
We current have a set of 5 user licenses Enterprise Subscription licenses. All of the documentation I’ve found for current Advanced Installer current licenses requires internet connection and that it requires a computer ID that is changed if the host machine changes. This presents an issue because our overall strategy for build machines has been to prohibit manual configuration on the machines; they utilize an IaC to construct and deploy the templates. From what I’ve read around that means that if a VM is migrated, destroyed, or created then the computer ID is used and we end up using a seat unnecessarily. This creation / destruction method can happen more then once a day, as we are enabling autoscaling for creation and freeing of compute resources depending on the build demands.
Is there a recommended way of handling this situation for the build machines? I read that it might be possible for the account manager to have a special floating license file generated or that uninstalling advanced installer might be able to release the license from the account. I’m also not 100% sure we will be able to have the build VM’s be able to reach your servers to activate; if it’s a hard requirement then I’ll have to open a discussion about it.
Thanks!
FOLLOW US
Get the latest news in Application Packaging