About DerekMac

DerekMac · ‎Jun 16, 2022

Not sure what you mean. I was troubleshooting messages found in the Rule Execution Details. This Summary message "VMware server has not been discovered on this device" (which is listed by filtering for "VMwareNotDiscovered") on multiple Beacons, but is successful on the Beacon we intended. So why is it running on other Beacons. I thought the Beacon was decided by the Beacon specified in Subnets. The logs confirm that vCenter was attempted.

DerekMac · ‎Jun 16, 2022

Chris, sorry for the late response. Meant to reply before taking some time off. The Discovery log didn't provide exactly what I was looking for, although I did notice listing of the "is in scope" named Targets, which helps for something else. I do not see a Subnet that points to the extra Beacon. In the Discovery Log I see this message, but do not have a Subnet defined for this, so I assume the messages below come from the Target where we point to this IP. 2022-06-08 23:01:14,119 [ets.SubnetRangeBuilder|rules-50] [INFO ] Authorizing IP range '100.97.82.209/32' 2022-06-08 23:01:14,119 [ets.SubnetRangeBuilder|rules-50] [INFO ] Including IP range '100.97.82.209' Below messages are specific to this extra discovery, but why this Beacon? 2022-06-08 23:02:12,120 [iscoveryActionExecuter|DNSLookup] [INFO ] Successfully performed DNS discovery for device 'mdcvenglabvc'. 2022-06-08 23:04:10,800 [iscoveryActionExecuter|IPScan] [INFO ] Device 'mdcvenglabvc' is in scope: All vCenters-Known vCenter or OVM Manager servers-Services Discovery - All Sites-vCenter Targets - East Coast 2022-06-08 23:04:10,800 [.DiscoveryTaskExecutor|PropertyDisco] [INFO ] Skipping Device Property Scan discovery for device 'mdcvenglabvc': Device is not discovered in the current rule execution. 2022-06-08 23:04:10,800 [.DiscoveryTaskExecutor|PropertyDisco] [INFO ] Performing VMware discovery for device 'mdcvenglabvc'

DerekMac · ‎Jun 08, 2022

Is there a SQL query or something to find out why a particular Beacon is selected to run vCenter Introspection? We have many Beacons and sometimes a vCenter will try to execute on multiple Beacons, working on one and failing on another, but I don't see any pertinent Subnets pointing to the failed Beacon, only the good one.

DerekMac · ‎Mar 20, 2020

I am talking about during the install process, so I did not think ndtrack would have run yet. I would need to do testing on a fresh install. Thanks for the info on ndinit.exe! So something like this CMD (for Windows only): @echo off tasklist /fi "imagename eq ndinit.exe" |find ":" > nul if errorlevel 1 (echo "ndinit.exe is OK") else (echo "ndinit.exe is not running") exit

DerekMac · ‎Mar 18, 2020

We have a deployment tool, Ansible, install the FlexNet agent on servers. Does anyone have an fairly instant and automated way to confirm the agent installed OK and can upload an ndi file? Looking for a command with feedback. I didn't see a good way to get "success" feedback using ndtrack, which doesn't even pause while it executes. Only things I can think of is testing the web access to the upstream FlexNet server's ManageSoftRL site, or set a delay in the script and check the logs, like: Select-String -Path C:\Windows\Temp\ManageSoft\uploader.log -Pattern "Upload successful".

DerekMac · ‎Feb 12, 2020

Thanks Murray, That was my understanding, but you stated it well. I'm still curious how this value gets passed, apparently buried in the application code. I tried to find the user running the agent by checking the Event Viewer > Applications and Services Logs > ManageSoft, but on the server I have access to, it says User = N/A, which I hope just means it is the system account. My server writes to Windows Temp. Anyway, on the server in question, I got a Webex session setup and low and behold, the logs were there in C:\Windows\Temp\ManageSoft. So I guess I will try sleuthing next time they are not there. : / Thanks again, Derek MacIntosh

DerekMac · ‎Feb 10, 2020

Sometimes our Windows Engineers cannot find the agent log files, even for servers still reporting in. They are not in C:\Windows\Temp\ManageSoft. They are not found by doing: Start > Run > %temp% … which BTW does not show C:\Windows\Temp\ManageSoft. Registry entries point to Logfile = $(TempDirectory)\ManageSoft\tracker.log … but TempDirectory is not an Environmental variable, and is not stored anywhere in the Registry. Also not in C:\Program Files (x86)\ManageSoft\mgssetup.ini. So where can I find the value for $(TempDirectory)? If possible, a way we can automate a script to do a log read or extract.

DerekMac · ‎Oct 02, 2019

Yes, now I know what "backported" means, thank you for the explanation. The hotfix failed, so I was trying to figure out if there was a prerequisite, but apparently not, other than having right release. I guess the failure is an issue for a Flexera Support case.

DerekMac · ‎Oct 01, 2019

Example: The Readme for “FNMS-66867 - Inventory Chasis Blank” says “This fix is a backported hotfix for FNML-4189 against FNMS 2018 R2”. Not sure exactly what that means, but think it means FNML-4189 would have to be installed first (prerequisite). How can we tell? FYI, we have 2018 R2 on-premises.

Online Status	Offline
Date Last Visited	‎Aug 17, 2022 08:59 PM

Re: How to determine vCenter Rule Execution Beacon

Re: How to determine vCenter Rule Execution Beacon

How to determine vCenter Rule Execution Beacon

Re: Agent install verification

Agent install verification

Re: What is the value of $(TempDirectory) for logs?

What is the value of $(TempDirectory) for logs?

Re: Can we list our updates and hotfixes applied in FlexNet?

Can we list our updates and hotfixes applied in FlexNet?

Re: How to determine vCenter Rule Execution Beacon

Re: How to determine vCenter Rule Execution Beacon

How to determine vCenter Rule Execution Beacon

Re: Agent install verification

Agent install verification

Re: What is the value of $(TempDirectory) for logs?

What is the value of $(TempDirectory) for logs?

Re: Can we list our updates and hotfixes applied in FlexNet?

Can we list our updates and hotfixes applied in FlexNet?