Automated re-activation of LabVIEW when deploying an image?

[wiebe@CARYA]

Can't help with the licensing problem, but why do you want to install LabVIEW nnn times in the first place? Except for schools\universities, I don't see any reason to install LabVIEW itself. Have you considered making an application\installer? If you enable debugging, you'd still be able to (remotely) debug the entire application. All you lose is the ability to edit.

I would not be surprised if this cannot be done automatically, because it's not a supported use case of the software. If you have a valid use case, that might eventually change...

[wmyers]

That is actually the exact scenario I'm working with.

I'm currently assisting another tech with their labs while they are out on leave and they have approx ~9 labs with 20-26 systems that have the NI LabVIEW software on them.

We routinely receive requests that make significant enough changes to the software configuration in the labs that they require being reimaged upposed to be updated in-place. The NI products however seem to require a sign-in on each workstation after the image has been deployed, consuming a significant amount of time. 

I'm hoping to find a method to either automate that activation process that's within the scope of my ability. I'm planning to spin up a project to implement a licensing server but that will require involvement from several teams as well as several months.

My plan B would likely be to use autoIT to automate keystrokes/mouse movement and Plan C to employ the help of some peers and go to each station one by one logging in with our account creds.

[wmyers]

it seems that activating the software with the computer ID and then deploying the image prevents the log-in prompt as long as the OS volume serial # is the same.