Hi,

I'd like to integrate InstallShield builds into an Azure DevOps pipeline, and want to clarify the licensing setup before proceeding.

My situation:

• I have an existing InstallShield IDE node-locked license, activated on my personal/local machine.
• My plan is to register that same machine as a self-hosted Azure DevOps agent, and run the InstallShield build (via
• IsCmdBld.exe
• or the Standalone Build tool) as a pipeline step on that agent.

My questions:

1. Can my existing InstallShield IDE node-locked license be used to drive automated/headless command-line builds from a CI pipeline (Azure DevOps) running on the same licensed machine, or does automated/unattended building require a separate license (e.g., Standalone Build/SAB)?
2. If Standalone Build (SAB) is required for CI builds, is that a separate purchasable entitlement from the IDE license, or is it included with certain InstallShield subscription tiers?
3. Since a node-locked license is tied to a Host ID, is there any restriction on running it through a Windows Service-based agent (as opposed to an interactive desktop session) on the same machine?

Any clarification — including pointers to relevant documentation — would be much appreciated.

Thanks!