Team! Depending on how the environment is addressed, I have found tagging devices with a custom location tag pretty handy. Note that you should NOT use the tag key "Location", as that is already default tag key in the system. I usually call tag key something like "Customername-Area" and the tag value is the location. If the customer has their environment broken into subnets-supernets you can filter the assets page on the subnet octets and bulk apply tags 100 at a time. For larger or more complex environments, you can use the tag upload feature and filter your .csv import on the subnetting scheme. Example - 192.168.x.x  all get a tag key of Area and a tag value of NCDC                      10.10.1.x       all get a tag key of Area tag value of SCDC These device level tags will be visible in various reports in the platform, and also in your detailed application dependency report.  -Brooks   ... View more

Hi Mark, thx for your reply. Will try & keep you aware thx again Hervé ... View more

Hi bzeunert, Licenses are used only to collect performance data and is independent of all of the Portal features. You will have access to the features such as tagging and reporting for the lifetime of the Subscription that was used to create the assessment. Please let me know if you have questions. Thank you, Mark Jamison Flexera Support Team ... View more

Hi ektaverma, When a device is discovered as virtual-unknown, this means the device was reported through VMware it, however, none of the support protocol ports were seen as open.  For more information on the various device types, please see the online documentation link below. https://docs.flexera.com/foundationcloudscape/help/FCGlossary_DeviceType.htm When validate collection results is showing an ICMP failure, this means that the RN150 virtual appliance sent a ping request to the device, however, the device did not respond back. ICMP can be blocked at the network level or locally on the device. The RN150 must be able to ping and receive replies back for a device to be successfully discovered. I recommend reaching out to the device administrators and/or the network team for more information regarding the ICMP failures. Please note, device dependency data (netstat and process data) is only collected from the operating system. A limitation of VMware is that netstat and process data cannot be provided. Any device that is a virtual-unknown is not properly discovered at the operating system level. Once the ICMP failure issue has been resolved, please request a rescan from the RN150 main Dashboard. Please let me know if you have questions. Thank you, Mark Jamison Flexera Support Team   ... View more

Hi Felipepandolfi, Will you please open a Support case so that we can further look into this issue. When opening a case, please included the name of the assessment in which the issue is regarding. Thank you, Mark Jamison Flexera Support Team   ... View more

Thank you @ChrisG I have one question. I did try the validation option for the servers we are getting errors, Validation collection is successful for that server. However, this server is still listed in the summary of collection errors. ... View more

Hi Satya, The RN150 is the virtual appliance used to discover and collect performance data against devices. The FlexDeploy Pod is our on premise offer to our SaaS Portal, that houses the data collected by the RN150. Please note, FlexDeploy is only supported on VMWare ESXi 5.5 or higher, and cannot be deployed to VMware Workstation or VMware Workstation Player. For more information on the FlexDeploy requirements, please see the online documentation link below. https://docs.flexera.com/foundationcloudscape/help/FCFlexDeploy.htm Please let me know if you have questions. Thank you, Mark Jamison Flexera Support Team ... View more

Hi, Will you please confirm if the mentioned servers are joined to a domain or workgroup servers?  The NTSTATUS: NT_STATUS_ACCESS_DENIED - Access denied indicates the account does not have the correct privileges to access the WMI classes on the remote host. Please find the below link to a Microsoft article that will detail the required permissions for enabling an account for remote WMI access: UAC & WMI (Account Requirements) https://docs.microsoft.com/en-us/windows/win32/wmisdk/user-account-control-and-wmi As an option, you can use Wbemtest.exe utility that is included on all Windows systems to confirm the user account has the correct WMI privileges. Please find the below detail on using wbemtest.exe. Below are instructions on using wbemtest.exe to verify the account has the correct privilege level and that the service is running: Wbemtest: 1) In Windows, select start, type wbemtest, select enter. 2) Select 'Connect' in the top right corner Namespace = [file://(computer]\\(computer name)\root\cimv2 - enter this replacing computer name with hostname (or IP address) you wish to test to. Enter the Windows account username and password Select 'Connect' Successful authentication will result in seeing WbemServices and the tabs are no longer greyed out. Failure to authenticate will result in an error message. Once you have resolved the privilege issues please select request rescan in the virtual appliance dashboard to update the inventory. Below is a link to a video on using wbemtest.exe: How to Use wbemtest.exe to validate Windows Credentials: https://youtu.be/ZDyXUZUdEDE   Please let me know if you have questions. Thank you, Mark Jamison Flexera Support Team ... View more

For remote communication with WMI, ports should be open for incoming connections to the computer that the connection is being made to. Incoming ports on the computer that is initiating the connection do not need to be open. ... View more

Thank you for the information. It's helpful.  ... View more