Hi, I need to know witch FlexNet processes run on windows in order to verify that the installation is correct? Thank you
‎Jan 09, 2020 09:04 AM - last edited on ‎Jan 09, 2020 09:39 AM by KPBussey
Hi,
Assuming you install the standard package on windows, installing only the agent and checking the processes will not necessary result that the agent is working correctly. For example if during the installation the ports are closed to the beacon server, agent will be installed correctly but no policy will be downloaded from server, resulting in an agent that is not working.
What I do is that after installing the agent I run the ndschedag -t machine command to see if I have the policy download, if you run this command and receive an empty screen, you need to check the log files to see why the agent is not working.
‎Jan 14, 2020 03:33 AM
Hi Miguel,
I am not sure about processes, but you should see two services running: BatchProcessScheduler and BatchProcessor.
Also you can verify if installation was successful by going to http://localhost/Suite in web browser, this should open FNMS UI.
Jan
‎Jan 09, 2020 09:17 AM - edited ‎Jan 09, 2020 09:19 AM
Some of the things to check:
Verify that the 2 Batch Processor "Services" are running
Within IIS Manager, open up the FlexNet Manager site and verify that all of the Application Pools are installed and running
Within Test Scheduler, open up the FlexNet Manager node and verify that all of the scheduled tasks for FNMS are installed and 'Ready'
Verify that the URL for FlexNet Manager comes up successfully in your browser
‎Jan 09, 2020 09:23 AM
‎Jan 09, 2020 09:32 AM
After the FlexNet Inventory Agent is installed on Windows, you will see two Services being created. For the first server, the name of the server will contain the version number of the installed agent.
Flexera Inventory Manager managed device vxx.xx.xxxxx
Flexera Inventory Manager security service
‎Jan 09, 2020 10:12 AM
Hi,
Assuming you install the standard package on windows, installing only the agent and checking the processes will not necessary result that the agent is working correctly. For example if during the installation the ports are closed to the beacon server, agent will be installed correctly but no policy will be downloaded from server, resulting in an agent that is not working.
What I do is that after installing the agent I run the ndschedag -t machine command to see if I have the policy download, if you run this command and receive an empty screen, you need to check the log files to see why the agent is not working.
‎Jan 14, 2020 03:33 AM