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!

I assume that is because we changed hosting providers for our servers and now the Installshield licensing system does not recognize the licensed server anymore. How can I get my license for Installshield restored and working on the 'new' machine.

Thanks

When I create a web MSI for IIS (Basic MSI), the folder does not install into the wwwroot directory.

In the General Information section, the INSTALLDIR variable is correctly set to "[IISROOTFOLDER]MyWebSite".

In the Internet Information Services view, under Web Sites, the "Content Source Path [Local or UNC]" property contains the variable "[INSTALLDIR]".

And in System Search, IISROOTFOLDER is correctly retrieved from the registry key "HKLM\SOFTWARE\Microsoft\InetStp\PathWWWRoot". The MinorVersion and MajorVersion variables are also being retrieved.

Am I missing something?

I am using InstallShield 2025 R1 Premier Edition.

I also tried using IISScan.exe to retrieve information about a website, but it returns the error: "The website 'MyWebSite' was not found."

I have 2021 premier license I would like to use rest of them but I couldn't go to the site

Using InstallShield 2025 R1, we can see that Server 2025 is now included as an OS type.in the check box screen.

However, it looks like the SYSINFO.WINNT values haven't been added to in order to support identification of Server 2025 as a valid OS?

Are there plans to add Server 2025 into SYSINFO.WINNT or is there a separate way to identify the OS?

We have tried using 2025R2 but that contains a catastrophic bug with the licensing dialog when stepping through an install created with R2 (this has been raised and confirmed as a valid bug).