About joan_mckinley

joan_mckinley · ‎Mar 30, 2021

Thank you Markward! I checked with my DBA and he confirmed that is the correct port the DB instance is listening on. Thanks, Joan

joan_mckinley · ‎Mar 29, 2021

Our network team found FNMS XenApp Agent is using port 53571. It was blocked on the firewall so they opened it up as a test and the data was able to transfer to the database. I have searched the documentation for that port and I don't see it referenced. I had told them port 80 and 443 We found this article: Solved: FNMS Multi-Server Ports Configuration - Community (flexera.com) They wanted me to verify the FNMS is supposed to be using this port?

joan_mckinley · ‎Mar 29, 2021

Thank you @rwiltshire!

joan_mckinley · ‎Mar 29, 2021

We use this command line to force a policy request for the FNMS Agent on the Windows side: C:\Program Files (x86)\ManageSoft\Policy Client\mgspolicy.exe -t machine What is the equivalent on the Unix/Linux side? I can't find it in the documentation (probably just missed it). Thanks!

joan_mckinley · ‎Mar 25, 2021

Thank you @jdempsey. The customer doesn't want the approvers to receive the email separately since it will be harder determine who is going to work on that approval. There will be some follow-up for the request (expensive software) before any of the approvers can approve. If it was one email to the DL, they could easily reply "I am working this request", so multiple people don't call the user.

joan_mckinley · ‎Mar 25, 2021

We would like to send one email to all approvers in a AD Distribution List group at once instead of each approver receiving an email individually. In the To: Field we expected it to show the Distribution List name but it shows each individual email address in separate emails. We have played with all the different workflow types but they are still receiving individual emails. Can we do this without creating a utility mailbox that they would have to monitored?

joan_mckinley · ‎Mar 09, 2021

Regarding FNMS Application Usage Metering, we are trying to understand why the default settings have: UseMSI = True as the default UseAddRemove = False as default Is there a reason why the UseAddRemove is set to False? Can we have both set to true without any issues? Thanks, Joan

joan_mckinley · ‎Feb 09, 2021

Thank you Markward for the information! We are going to heed your advice and will recreate all the adapters, imports and mechanics to come *hopefully* to the same result as production.

joan_mckinley · ‎Jan 28, 2021

We would like to mirror our production databases in our development environment so we have valid data to test. We would like to synchronize the data on a monthly basis. Has anyone done this successfully?

joan_mckinley · ‎Sep 16, 2020

@jdempsey, thank you for the suggestions! I think we will look at the first option: Allow approvers to accept requests. We actually do have a Check Status in Actions. Osa helped us set it up a couple years go when we first installed App Portal. But we hadn't thought of it using it in the manner you suggested below. Even the last one is a good suggestion. We had thought of something similar - we created a distribution list of just a few SAM members that would be grabbing tickets and only send the approval email to them rather than the entire team. We added that AD group as approvers via "User Groups" in the "Approval Groups" then applied that to a Workflow. We will definitely achieve what we want between all these ideas. Thanks!

joan_mckinley · ‎Aug 27, 2020

@JohnSorensenDK Thanks for the question. This is just a one time scenario for us and Remedy Self-Service Catalog is $$$. 🙂 The rest of the approvals can be done via email or the portal. Thanks, Joan

joan_mckinley · ‎Aug 25, 2020

Thanks for the reply jdempsey! The reason why we want to do this is because we are creating a Remedy ticket "On Submit" for that catalog item. That ticket is being passed the "View Details" variable which has the link for approving the request. When there are enough licenses for that software, the Software Asset Management team will click the link from the ticket to approve, rather than go into App Portal "Approve/Reject" page or an email. The reason why they want email turned off is because a team of people would receive the emails and not know how needs to work on it. If the Software Asset Management representative grabs the ticket from Remedy with the link to approve in it, we aren't spamming people needlessly. Thanks!

joan_mckinley · ‎Aug 25, 2020

We just upgraded to App Portal 2019 R1. We were hoping we would find a way to turn off email notification for an individual catalog item. It looks like it is still only a global option in the Site Management\Settings\Email section. Is there some way of turning it off that we are not seeing? Thanks! Joan McKinley

joan_mckinley · ‎Aug 07, 2020

Thanks Aamer for the reply and the information. Flexera helped us. We did not realize we needed to update the BeaconEngine.config on the old beacon and new beacon. Even after we did that we still had issues. We discovered that some of our clients are working (sending inventory successfully to our new beacon instance). So it is just some of our systems that are still reporting to the old FNMS server even though they have the new beacon information in the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\DownloadSettings\{6a31f65a-1df0-4ce2-a229-2e148fd36df2} key. It still had old information in this key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\DownloadSettings\BeaconServer We wrote a script to update the BeaconServer key and when we apply that, the clients start sending inventory to the new beacon. Thanks, Joan

joan_mckinley · ‎Aug 06, 2020

We are migrating to a new beacon and was told we could use a DNS alias or change a setting in the BeaconEngine.config. The DNS alias isn't working for us so we are testing modifying BeaconEngine.config in C:\Program Files (x86)\Flexera Software\Inventory Beacon\DotNet\conf on the existing Beacon. We added the server name (FQDN) of the new Beacon to networkName="" It changed some settings in the registry on the clients when they check in but the inventory files are still going to the old server. Not all the settings in the registry are getting updated in particular HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\DownloadSettings\Bootstrap Server 1 and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\DownloadSettings\BeaconServer. We can see in the tracker.log that is is uploading to the old server. We used this technote: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-configure-the-beacon-to-use-a-different-name-or-alias/ta-p/2064 Not sure if there is anything else we need to do besides updating the BeaconEngine.config.

Online Status	Offline
Date Last Visited	‎Mar 23, 2023 10:35 PM

Re: Port 53571 Used for FNMS On Premises

Port 53571 Used for FNMS On Premises

Re: Command Line for Unix FNMS Policy Update

Command Line for Unix FNMS Policy Update

Re: Send One Approval Notification to all Users in a DL

Send One Approval Notification to all Users in a DL

FNMS Application Usage Metering

Re: Mirror Production FNMS Databases to a Dev Environment

Mirror Production FNMS Databases to a Dev Environment

Re: Turn off approver email for one catalog item in App Portal

Re: Turn off approver email for one catalog item in App Portal

Re: Turn off approver email for one catalog item in App Portal

Turn off approver email for one catalog item in App Portal

Re: Migrating to a new becaon

Migrating to a new becaon

Re: Bulk Update Catalog Items Actions

Bulk Update Catalog Items Actions

Re: App Portal Database Schema Question

Re: App Portal Database Schema Question

App Portal Database Schema Question

FlexNet Inventory Agent Support for MacOS 13.0 Ventura

Re: My Apps Keep Selection Questions

Re: My Apps Keep Selection Questions

My Apps Keep Selection Questions

Re: Request Variable not translating in “My Apps - Alert Email Notification”