Good morning,
I've done some searching and found multiple posts, but i'm thinking there's a simpler way. I have to put together Windows and Linux packages to deliver to a Cloud OPS team that is putting the FlexNet agent into some AWS AMIs. The way it is set up, the instances that are spun up could talk to one of 3 possible beacons, depending on what zones they come up in. The windows agent was easy enough---i added some extra registry settings to the bootstrap and it worked as figured.
I've done a few deployments with the linux agent before and am familiar with the bootstrap--however i found these posts on adding multiple beacons to check at installation, and it seems a little more involved that it needs to be:
In the sample bootstrap file it says "location(s)" for the download/uploads....does that mean you can feed multiple locations with a comma or semi-colon separator? If so--that would be much cleaner for me to provide to this external team. The documentation is a little lacking in the capabilities of this bootstrap.
Thanks!
Jul 22, 2021 09:53 AM
I believe you are referring here to the MGSFT_BOOTSTRAP_* settings settings often found in mgsft_rollout_response files:
# The initial download location(s) for the installation.
# For example, http://myhost.mydomain.com/ManageSoftDL/
# Refer to the documentation for further details.
MGSFT_BOOTSTRAP_DOWNLOAD=http://beacon.mydomain.com:8080/ManageSoftDL/
# The initial reporting location(s) for the installation.
# For example, http://myhost.mydomain.com/ManageSoftRL/
# Refer to the documentation for further details.
MGSFT_BOOTSTRAP_UPLOAD=http://beacon.mydomain.com:8080/ManageSoftRL/
I believe these settings can indeed take a list of URLs to use for bootstrapping, separated by a ";" or ",". For example:
MGSFT_BOOTSTRAP_DOWNLOAD=http://beacon1/ManageSoftDL/;http://beacon2/ManageSoftDL/
MGSFT_BOOTSTRAP_UPLOAD=http://beacon1/ManageSoftRL/;http://beacon2/ManageSoftRL/
If you have a chance to try this, please post back here to confirm - it would be great to have a positive confirmation that it works as I think it will.
Jul 23, 2021 05:21 AM
I believe you are referring here to the MGSFT_BOOTSTRAP_* settings settings often found in mgsft_rollout_response files:
# The initial download location(s) for the installation.
# For example, http://myhost.mydomain.com/ManageSoftDL/
# Refer to the documentation for further details.
MGSFT_BOOTSTRAP_DOWNLOAD=http://beacon.mydomain.com:8080/ManageSoftDL/
# The initial reporting location(s) for the installation.
# For example, http://myhost.mydomain.com/ManageSoftRL/
# Refer to the documentation for further details.
MGSFT_BOOTSTRAP_UPLOAD=http://beacon.mydomain.com:8080/ManageSoftRL/
I believe these settings can indeed take a list of URLs to use for bootstrapping, separated by a ";" or ",". For example:
MGSFT_BOOTSTRAP_DOWNLOAD=http://beacon1/ManageSoftDL/;http://beacon2/ManageSoftDL/
MGSFT_BOOTSTRAP_UPLOAD=http://beacon1/ManageSoftRL/;http://beacon2/ManageSoftRL/
If you have a chance to try this, please post back here to confirm - it would be great to have a positive confirmation that it works as I think it will.
Jul 23, 2021 05:21 AM
Jul 23, 2021 08:03 AM
Thanks @ChrisG
The semi-colons were the correct delimiter. Thanks again!
Jul 23, 2021 10:17 AM
@ChrisG i have one doubt here regarding SSL Certificate for different beacons.
ie, i normally use deployment package including mgsft_rollout_cert that have all certificate chain used for beacon URL's SSL binding .
Now if we are going with this approach, we will be having more than one certificate chain to include.
How can we achieve that ?
Regards,
Junaid Vengadan
Dec 06, 2021 12:51 AM