VisualGDB license trouble in the cloud

[hvbill]

Our IT department want us to move our Jenkins build node into the cloud, to a server were only personal windows accounts is allowed to log-on, not a mutual(?) account for that computer, used by all developers.

This will give us a problem with the VisualGDB license that then must be running with the credentials of the user that installed it.

Is there a way to install the VisualGDB license to the Local System account, or is there another better solution to this problem? I have tried to search for it but not found any solutions.

Thanks in advance

Daniel

• This topic was modified 1 year, 3 months ago by hvbill.
• This topic was modified 1 year, 3 months ago by hvbill.

[support]

Hi,

You might be able to get VisualGDB running under the local system account by manually copying the files and registry keys, however it is not officially supported. There is some information here, however it may not work, or may work differently dependent on your configuration.

A better approach would be to use a floating license for the build server. It will count the number of simultaneously active machines instead of concurrent installations, so you can have as many computer/user combinations as you need without needing to activate them separately. Feel free to contact our sales if you would like to switch your license into a floating one.

[hvbill]

Update.

I have successfully updated a static license to a floating one. It was easy and it works great. Thanks for that.

But still the problem remains with the installation that is user specific and not available for all users of the computer, including the Local System account.

Next step will probably be to try to install VisualGDB as Local System account using Microsoft psexec tool.

[support]

Hi,

The Local System account has a few things different from the regular accounts, so it may break many things you would normally not expect to break (e.g. in MSBuild itself).

You can try installing it by following the steps on this page, but it may still not work as expected, or require non-trivial troubleshooting.

That said, normally you should not need it – the VisualGDB installer integrates it directly into the VS installation, so it should be visible to all user accounts on the same machine (you may need to specify the floating license key via HKCU registry for each of them though).

[hvbill]

Good to know about the floating license key in the registry.
But what about the BSP:s when there is more than one user on the computer? Aren’t they installed in C:\Users\UserName\AppData\Local\VisualGDB\EmbeddedBSPs\ and then personal?

[support]

Hi,

No problem. You can easily override the normal EmbeddedBSPs directory via HKCU\SOFTWARE\Sysprogs\VisualGDB\BSPEngine\BaseDirectory. E.g. setting it to C:\BSPs will place the BSPs in C:\BSPs\EmbeddedBSPs.

[Author]

Posts