A new Flexera Community experience is coming on November 18th, click here for more information.
Hi All,
We need to install FNMS agent on around 250 windows servers out of total 1000 windows server in the customer environment.
Could you kindly advise of any Powershell script we have, or an alternative to perform this, please?
The customer isn't willing to modify the GPO, so it is not an option.
Thanks.
āJul 15, 2022 10:07 AM
Hi
You have two option for windows server
1:-Use SCCM to deploy Agent in Windows devices.
2:-Use Adoption method given by flexera as a fantastic feature. Details documentation is available on below.
https://docs.flexera.com/FlexNetManagerSuite2022R1/EN/WebHelp/PDF%20Documents/On-
Prem/GatheringFlexNetInventory.pdf
āJul 15, 2022 09:14 PM - edited āJul 15, 2022 10:04 PM
Hi
My best recommendation is really GPO/SCCM, those that had other methods usually only solved the current estate and missed out new servers or when they did large migrations. I have attached a script that show how you can trigger a remote process for all devices within an OU, it will not work out of the box and you need to tweak it for your needs.
āJul 17, 2022 02:21 AM
Hi @mag00_75 , Thanks for the script.
The customer is not willing to make the changes across environment and only want a list of servers to update with the package (forcefully).
Currently, in the environment, these 250 server originally mentioned has got corrupted for some reasons and we recommended to re-install the agent. However, the customer advised that their GPO will skip the re-install if it would find the "Managesoft" folder in the 'Program files' (or x86) structure.
So, can we add a command to this so the script check for the version, if below than in the package, it re-installs. Otherwise, it skips.
And, Thanks to all for their valuable responses.
1. Customer doesn't have any 3rd-party tool.
2. the 250 servers have corrupted agent but installed. So, I think, the adoption can't target these again. Can it (I believe, adoption is preferable for new installs only)? However, the customer wont share the rootDomain credentials to store in the beacon. Can service account do this, if so, what are the -
a. Role Based access control?
b. Policies?
required for the service account to install agent into those servers.
3. Manual is the only fall-back option; however because of high number, they are not much supporting us here.
Thanks.
āJul 19, 2022 06:09 AM
Common approaches for installing the FlexNet inventory agent are:
In general option #1 is likely to be the path of least resistance as it aligns with current processes and tooling that exists within an environment. All the other options involve some kind of exceptional process. In most organizations that will end up being more difficult to get approvals for and execute.
If a manual/scripted installation is used, a typical command line for installing an MSI package is normally sufficient:
msiexec /i "FlexNet inventory agent.msi" /qn
āJul 17, 2022 09:53 PM
Hi ChrisG,
Thanks for the reply.
what is the powershell command to install the FNMS Agent on windows.
Thanks
Anjan
āJul 18, 2022 10:28 PM
You can execute msiexec command lines like the one I suggested in PowerShell.
āJul 18, 2022 10:32 PM
Hi ChrisG,
I am using the same command but it is not installing. I think i need to pass some parameters.
when i check Get-Service | findstr "Flex" it dont show any services.
Can you please guide me with the document or the entire command to install the FNMS Agent from powershell.
Thanks
Anjan
āJul 18, 2022 10:37 PM - edited āJul 18, 2022 10:38 PM
For doing a manual install and troubleshooting, try dropping the "/qn" command line option to have Windows Installer display a UI showing details of the installation. It may also help to have Windows Installer write a log file which could tell you more about what is going on. For example:
msiexec /i "FlexNet inventory agent.msi" /l*v install.log
You may find the following page useful to learn about msiexec command line options and how to install Windows Installer packages: https://docs.microsoft.com/en-us/windows/win32/msi/command-line-options
āJul 18, 2022 10:46 PM
Thank ChrisG
Appreciated.
āJul 18, 2022 10:51 PM
Thanks everyone for their valuable responses. @durgeshsingh , @ChrisG, @mag00_75
1. Customer doesn't have any 3rd-party tool.
2. the 250 servers have corrupted agent but installed. So, I think, the adoption can't target these again. Can it (I believe, adoption is preferable for new installs only)? However, the customer wont share the rootDomain credentials to store in the beacon. Can service account do this, if so, what are the -
a. Role Based access control?
b. Policies?
required for the service account to install agent into those servers.
3. Manual is the only fall-back option; however because of high number, they are not much supporting us here.
Thanks.
āJul 19, 2022 06:12 AM
Hi
Even in manual installation/ reinstallation, you will required admin credential. Also check in some server in tracker log & try to find out reason for not reporting. if at all old agent need to remove then you have to follow script, policy for removal.
āJul 19, 2022 06:48 AM
āJul 19, 2022 12:21 PM
User | Count |
---|---|
8 | |
7 | |
3 | |
3 |