About sasikumar_r

sasikumar_r · ‎Apr 08, 2020

if you explicitly want to use setup.exe, i hope below command will work for you.. start /wait setup.exe /W /S /v"/qn ALLUSERS=1"

sasikumar_r · ‎Apr 07, 2020

Hi @AamerSharif , Inventory source is from FNMS only, as i said i tried deleting(both on All Inventory & Discovered devices) a device which is not in AD also. But still the device got recreated. I have attached the a screenshot on which you could see created date is 6th April and the last inventory source as FNMS. Device got recreated again on the compliance and discovereddevices tables. kindly help us how to get this fixed. Thank you Sasi

sasikumar_r · ‎Apr 06, 2020

Hi @kclausen @AamerSharif Thank you for your reply! i have tested by deleting the device with both the below mentioned scenarios. 1. Deleted from All Inventory page 2. Deleted from All Inventory page & All Discovered page But the devices is not getting removed from Inventory DB. After the reconcile the device get recreated on the compliancecomputer & discovereddevice table and it again started appearing on All inventory & All discovered devices page. we would like to perform the device deletion from UI rather than using storedprocedure. As per the links i have shared it looks like the device will be removed from both the DB's and it will not appear again on the UI unless its agent is actively sending the inventory. But unfortunately this is not happening on my environment. Device not getting deleted from Inventory DB and getting created again(no other inventory source, Only default AD connection in place). Even the result is same for non AD devices. Thank you Sasi

sasikumar_r · ‎Apr 06, 2020

Hi, As per FNMS 2017R2 Release Notes, Page No:7 It has been mentioned that deleting the device from All Inventory will delete it from All discovered and Inventory DB as well. Below is the URL & Attached is the screenshot for reference. By any chance,did this changed on the later versions? We are on 2019R2 muti tenant environment, but it is not working like it is mentioned. it is just deleting inventory from compliance DB. No other Inventory source, Inventory is from Agent & Default AD connection. https://docs.flexera.com/fnms2017r2/onpremises/FlexNet%20Manager%20Suite%20Release%20Notes%202017%20R2%20(English).pdf https://docs.flexera.com/fnms2017r2/onpremises/FlexNet%20Manager%20Suite%20Release%20Notes%202017%20R2%20(English).pdf Note: I posted this question on Deleting old inventory records,and seems it is solved already hence creating a new thread. Thank you Sasi

sasikumar_r · ‎Apr 02, 2020

Hi All @kclausen @ChrisG , As per FNMS 2017R2 Release Notes, Page No:7 It has been mentioned that deleting the device from All Inventory will delete it from All discovered and Inventory DB as well. Below is the URL & Attached is the screenshot for reference. By anychance it got changed on the later versions? We are on 2019R2 muti tenant environment, but it is not working like it is mentioned. it is just deleting inventory from compliance DB. No other Inventory source, inventory is from Agent only. https://docs.flexera.com/fnms2017r2/onpremises/FlexNet%20Manager%20Suite%20Release%20Notes%202017%20R2%20(English).pdf https://download.flexnetoperations.com/439214/1169/747/11855747/FlexNet%20Manager%20Suite%20Release%20Notes%202017%20R2%20(English).pdf?ftpRequestID=7663748577&server=download.flexnetoperations.com&dtm=DTM20200402120241ODA3ODQxMTA5&authparam=1585854161_0db60e8342e7d2bb012af6157f0b8aa4&ext=.pdf Thank you Sasi

sasikumar_r · ‎Mar 27, 2020

Can we use these on Multi Tenant environment? Like monitoring the beacons across different tenants by installing it on application server?

sasikumar_r · ‎Mar 06, 2020

Hi, We are using both Mulitenant(Cloud) and On Prem FNMS on our environment. Multitenant is on 14.1 and On Prem is on 14.0.1. So by any chance 2019 R2.1 ( 14.1.0.) - On Premise version will be released? Thank you Sasi

sasikumar_r · ‎Feb 19, 2020

Hi @mfranz, No errors logged on the history of the tasks, just have task started,action started,action completed & task completed entries. Thank you Sasi

sasikumar_r · ‎Feb 19, 2020

Hi @mfranz, Yes the old task is the culprit, failed them using fail-tasks command and now the new jobs are getting processed successfully. @adrian_ritz1 - Thank you for the document, it is very helpful. also as i mentioned on my original posts the jobs on the task scheduler are getting failed still now with error 0x2.. configured account has full admin privilege on the server. attached is the screenshot. Thank you Sasi

sasikumar_r · ‎Feb 18, 2020

Hi @mfranz is there any best practices to remove the queued jobs safely without impacting other data? Thank you Sasi

sasikumar_r · ‎Feb 18, 2020

Hi @mfranz , Yes we have updated server name on the batchprocessor table and the compliancesetting table. But still the issue persist. Thank you Sasi

sasikumar_r · ‎Feb 18, 2020

Hi All, We have a multi Tenant environment and recently migrated our all the servers(batch,invnetory,Db & Web) to new servers. After Migration we have upgraded the application to 2019R2(from 2019R1.3). After upgrade, inventory import(also reconciliation) which happens overnight is not starting for any tenants. due to which the devices and its inventory information are not getting updated. Task scheduler jobs on the batch server is getting failed with error 0x2. tried checking on batchprocessor and scheduler logs with no luck. i could see almost 2000+ queued jobs(mostly precalc) jobs listing when i enter the command batchprocesstask console lis-tasks (which is of old date). Kindly suggest where to check and how to fix this issue. Thank you in Advance. Sasi

sasikumar_r · ‎Oct 30, 2019

Hi @wawat68 , For Unhandled exception - check the Regional and Language settings of the server on the control panel. Go to Region and Language Settings, change the language to English (US or Australia). On the Administrative Tab click “Copy Settings”. Restart the Beacon server to apply the changes made,Hopefully it should work after the restart Regards, Sasi

sasikumar_r · ‎Oct 21, 2019

I have figured out Agent id on the Beacon(on registry) and the Agentid on the ndi files that collected for each Vcenter host(Vmware Inventory) are same.Because of the same agent id - Instead of updating the Vcenter host inventory, beacon server's inventory is getting Updated.

sasikumar_r · ‎Oct 15, 2019

Hi @winvarma \all, I hope i have identified the issue on my environment. Agent id on the Beacon(on registry) and the Agentid on the ndi files that collected for each host are same. Because of the same agent id - Instead of updating the host inventory, beacon server's inventory is getting Updated. By anychance does any one faced this issue and have a solution for this? Thank you Sasi

Online Status	Offline
Date Last Visited	‎Feb 03, 2023 11:42 AM

Re: How to run setup.exe to install agent for windows server without human interaction?

Re: Deleting Inventory Devices from All Inventory

Re: Deleting Inventory Devices from All Inventory

Deleting Inventory Devices from All Inventory

Re: Deleting old inventory records

Re: A new way to monitor your beacon environment

2019 R2.1 - On Premises - Will it released?

Re: Inventory Import not happening after Server migration and Upgrade to 2019 R2

Re: Inventory Import not happening after Server migration and Upgrade to 2019 R2

Re: Inventory Import not happening after Server migration and Upgrade to 2019 R2

Re: Inventory Import not happening after Server migration and Upgrade to 2019 R2

Inventory Import not happening after Server migration and Upgrade to 2019 R2

Re: Unhandled exception has occured in your application

Re: FlexNet Manager Suite 2019 R1.2

Re: Vm's were not showing Host details

FNMS Agent executables with different version

Oracle Instance Inventory Failed

Re: How to get Cluster Domain name in Reports

How to get Cluster Domain name in Reports

Incorrect(spelling) Vmhosts name in Flexera

Re: Linux agent installation failed due to missing dependencies

Integrating FNMS with Ivanti Identity management for authentication

Linux agent installation failed due to missing dependencies

Re: Duplicate serial number VM's with no host alert

Duplicate serial number VM's with no host alert