About adrian_ritz1

dbeckner · ‎Dec 14, 2021

@mfranz Do you know if this SP is compatible with 2019 R2? Either way could you provide it to me?

bruce_giles · ‎Dec 08, 2021

Hi There, thanks so much for the advice that has been posted thus far .. really appreciate it !! As alluded to, it's not as straight forward as we think. Thx Again Bruce

adrian_ritz1 · ‎Dec 08, 2021

Hello, This information if is visible in WebUI then is stored somewhere in the Sql database. The information from beacon is transmitted in a file, with status .bstat which is a xml formatted file. You can catch this file directly on the beacon server or on application server you activate the replication functionality What I did, for one of the customer, I created a simple sql script, that will leverage the SQL send email functionality, it's for a multi tenant implementation, but you can modify it out DECLARE @xml NVARCHAR(MAX) DECLARE @body NVARCHAR(MAX) SET @xml = CAST(( select t.TenantName as 'td',' ',b.BeaconName as'td',' ',b.LastKnownActivityTime as 'td',' ' from Beacon_MT b left join Tenant t on t.TenantID = b.TenantID where b.LastKnownActivityTime < getdate() - 1 FOR XML PATH('tr'), ELEMENTS ) AS NVARCHAR(MAX)) SET @body ='<html><body><H3>Beacon no longer reporting</H3> <table border = 1> <tr> <th> Tenant Name </th> <th> Beacon Name </th> <th> Last Known Activity </th></tr>' SET @body = @body + @xml +'</table></body></html>' EXEC msdb.dbo.sp_send_dbmail @profile_name = 'mail2', -- replace with your SQL Database Mail Profile @body = @body, @body_format ='HTML', @recipients = 'flexera_admin@acme.com', -- replace with your email address @subject = 'Beacon no longer reporting' ; This script will send me on every morning the beacons that are no longer reporting.

adrian_ritz1 · ‎Nov 23, 2021

Hello @JohnSorensenDK , Did t he 2nd VM disappear from the cluster in FNMS? Yes, the 2nd VM is no longer in cluster, also we receive an error that the VM don't have a host, that's why I suspect it was removed 2. Is the inventory date for the 2nd VM after the date when it was removed from the cluster? No idea when it was removed, but also the inventory date is old, I suspect this VM is orphaned and powered off

adrian_ritz1 · ‎Nov 06, 2021

Hello, When I do troubleshooting of the agent or expired inventory I do the following: Start the troubleshooting from the agent upwards because that's the way how Flexera is communicating: Check Flexera log on agents: tracker.log - to see if the inventory is generated and uploaded uploader.log - to see if the upload part is working If you see that the data are going to beacon, then check the beacon server I usually check if in Incoming folder are no inventory queued If are the folders are empty and we are sure that the data are going to app server we need to investigate in the app server If it's an on prem installation, you can activate replication folder https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-configure-replication-to-collect-a-NDI-file-on-the/ta-p/2060 and catch the ndi file, you can check there to see if the inventory are received, or you can check in the sql, FNMSInventory data base to check if you received the inventory there. There are a lot of reason why an inventory is not received.

adrian_ritz1 · ‎Nov 01, 2021

Hello @FrankvH , I can think of several approach for this topic. When you commission a new beacon and create the beacon entry, all agents will receive an updated fail over list, which will contain the new beacon, this is not valid only in case you are using groups that are assigned to a specific beacon. So you can keep some time the old beacon on line, so that all the servers will receive the new policy. After that you can stop the old beacon, and check if you have some left overs, devices that are no longer reporting. Other approach is to configure a DNS alias https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-configure-the-beacon-to-use-a-different-name-or-alias/ta-p/2064 This is better suited at the implementation phase, but can be implemented and afterwards, you instruct the beacon to publish the dns alias, you keep both beacon on line, so that all devices will receive the new policy with the dns alias, and configure the DNS server to point to the new beacon, also after that you need to modify the new beacon to be published with DNS alias, if you are using SSL (port 443) you need to take extra care with certificates to configure them properly. Also don't forget to update all your deployment packages with the new beacon server 🙂

adrian_ritz1 · ‎Nov 01, 2021

Hello @tomaszkosowski , There are several ways to send data to a separate FNMS instances: Replication on FNMS, on the app server you activate the replication and copy all the ndi file to the other Flexera instance. https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-configure-replication-to-collect-a-NDI-file-on-the/ta-p/2060 you can leverage the flexera agent and run ndtrack with uploadlocation https://docs.flexera.com/FlexNetManagerSuite2021R1/EN/GatherFNInv/index.html#SysRef/FlexNetInventoryAgent/topics/PMD-UploadLocation.htm and put your ndi file into your desired location.

adrian_ritz1 · ‎Oct 12, 2021

I used the custom reports from this article: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Virtualization-Discovery-and-Inventory-Details-Custom-Views/ta-p/6025 It will give us the last inventory date for vCenter, I found this report most useful.

a_cutler · ‎Aug 24, 2021

Pardon my ignorance as I haven't done much FNMS work in a long time, but where would I keep the mgssetup.ini with these configuration settings for the agents to utilize when performing the targeted upgrades? Somewhere on the application server I'm guessing?

mfranz · ‎Aug 09, 2021

Hi, Assuming FNMS on-prem, one might change the ManageSoft inventory adapter to join the inventory to AD data and avoid importing inventory without an AD counterpart. While this would not prevent anyone from uploading stuff to the beacon, but it would prevent this data from being imported into FNMSCompliance. Or, perhaps, disabling direct import at the inventory server and using a PowerShell script to filter stuff. Then import. Best regards, Markward

nagaeendra · ‎Jul 29, 2021

Hi @kclausen, as recommended opened a new post https://community.flexera.com/t5/FlexNet-Manager-Forum/FNMS-Inventory-Agent-config-corrupt/m-p/201600#M12399

kclausen · ‎Jul 27, 2021

@adrian_ritz1 - To accommodate these users, could you change your global inventory schedule to run at 9AM or 10AM instead of 8AM?

adrian_ritz1 · ‎Jul 23, 2021

You can do it directly from beacon server, please check following link: https://community.flexera.com/t5/FlexNet-Manager-Forum/AD-group-member-query-business-adapter/td-p/187081 I implemented this to a customer for more than 10 license models, and is working fine.

MANOJKUMAR_K · ‎Jul 16, 2021

Hi Nrousseau If you could possible to clarify me the Powersheel script, where the query you stated below in LMS file extraction. I would like to know and I was confused - what Document Name and File from dbo also you mentioned Document. where document name # Select-Statement for filename & BLOB $SQL = "SELECT [DocumentName], [DocumentFile] FROM [dbo].[Document] WHERE [DocumentName] = 'OracleLMSAuditEvidence.zip'"

bruce_giles · ‎Jun 09, 2021

Hi Everyone, as promised .. I had a discussion with the Flexera Team yesterday regarding their thoughts on how best to migrate or relocate Beacons from one environment to another. During my conversation I mentioned the scenarios identified in this thread leveraging the alias dns names as part of the solution along with some others. Primarily we kicked around 2 scenarios One being able to rebuild the server on the new operating system using the same Server Name and IP address from the hardware / instance perspective, along with using the same "actual" Beacon name currently in the FNMS environment. Just thinking out loud here .. this method would make it easier in terms of proxy bypass settings not having to be changed along with any other specific network type of changes. Other things that would not have to change would be the subnet mappings, discovery rules since the subnet mapping to beacon names remain the same, business adapters could probably remain as well. The messy side would be copying the UID details over as mentioned in this thread and probably a few others things we have not thought of. The other scenario is to build brand new Beacon servers with new Server Name and IP with brand new Beacon names and add these to the existing pool of Beacons doubling the number of current Beacons for a short time until all devices receive updated policies. The upside to this method is that you have both old and new working at the same time to ensure everything is working as expected before deleting/removing the old ones. More effort is required to re assign all of the subnets over the testing period to the new Beacon names but you could control what Discovery Rules along with any Business Adapters you wanted to test by only re assigning those related to the rules or adapters. All the associated Network type of things like proxy bypass rules etc. would have to be updated accordingly. As you can see, lots to think about no matter which way you choose to go and I am sure I am leaving some pieces out but I think you get the idea. The individual I was talking with suggested the second scenario would be a lot cleaner and I think we would all agree .. much lower risk of things going dramatically wrong since the old is still available. Either way, the option of creating a Case to resolve any challenges is always available but as we know is not something immediate so you would want to factor that piece in as well. Me personally, I am still thinking about which way but leaning towards the latter. One other thing to mention regarding the Business adapters, since the xml details are kept on the Beacon of choice, they could be copied from the old server to the new one along with creating new tasks in the task scheduler. He was pretty confident that just copying the xml over would work but again something that would need to be tested in a dev/test environment before attempting in production. Please take this as simply my personal view of how it may be accomplished but by all means submit a Case yourself, if you have any questions or concerns. Lots of things to think about for sure, so take your time and plan things out accordingly. Bruce

Online Status	Offline
Date Last Visited	‎Jan 27, 2023 07:07 AM

Re: FNMS 2020 R1 EvidenceAlerts taking forever

Re: Seeking Clarification from the SSL Certificate Experts --- Setting up Agent HTTPS to Beacon Com...

Re: Where is beacon status logged?

Re: Consumption for Oracle license of "Oracle Processor" type is unclear

Re: Potential FlexNet agent issues - Outdated machine inventory

Re: Update policy config on agent running on server

Re: Import von gescannten Daten von "fremden" Flexera Agents

Re: Last date for vCenter inventory

Re: Automatic Agent Deployment Configuration Changes

Re: Beacon servers on the internet

Re: FNMS Inventory Agent config corrupt

Re: Upload inventory on a different schedule

Re: How To Inventory AD Groups with Users and Assing APP and Licenses

Re: Oracle Instances Inventory Details Custom Views - Oracle Visibility Extensions

Re: Need to Relocate Existing VM Windows Beacon onto another Windows VM Server

Questions regarding Azure inventory

Re: Installing FNMS when the data base is in a different domain

Re: Installing FNMS when the data base is in a different domain

Installing FNMS when the data base is in a different domain

FNMS migration to Azure

Re: Service Now Mid server

Re: Reverse Proxy and URL Hardening for Flexera Inventory

Re: Issue installing FNMS on a development server

Re: Precalc error

Re: Issue installing FNMS on a development server