
joan_mckinley asked a question.
We have a small pilot using Windows 365 Cloud PC in our environment and none of them are reporting user information. In particular, we do not see the associated calculated user or last logged in user.
Does the FlexNet Agent v21.30.726 support Windows 365 PC? Is there something we need to configure for that information to be included in inventory?
The *.ndi shows as: system on computerA.ndi in C:\ProgramData\ManageSoft Corp\ManageSoft\Tracker\Inventories.
Even if the user is logged on at the time the inventory runs, it shows as system on computerA.ndi instead of <username> on computerA.ndi and inside the *.ndi it shows UserName="system"
Any ideas?
Thanks!
Hi Joan,
Could you please check the NDI file content? There should be short user name in the header (inventory attribute) and a long one (including domain) in the "Win32_ComputerSystem" object as a property. Here is an example:
If there's a user name, you may check the "ImportedComputer" table in the Compliance DB next. If the user name is in there, please check the users in your system. I think, FNMS will only map known users.
Best regards,
Markward
Hello Markward,
Thank you for the reply!
We checked the NDI and it shows:
UserName="system"
<Property Name="UserName" Value=".\Administrator"/>Even if someone is logged on the ndi file name is: "system on computerA.ndi".
If we run: "ndtrack.exe -t machine" the ndi file is "john.doe on computerA.ndi" and has the UserName information populated:
UserName="john.doe"
But the other field still shows this:
<Property Name="UserName" Value=".\Administrator"/>Thanks,
Joan
I'm also having this issue. Agent version is 21.0. Would an updated version of the agent resolve this?
Its sounds as a similair issue I had on my Mac agents. The issue is that you dont have a domainname for matching users.
one way to achieve this is to set a variable Computerdomainname on the agent to hardcode a domainname so it matches your users in flexera tables. Search and try to find my Mac agent posts
Hi,
The entry UserName=“System” in the NDI file (line 3 I assume) refers to the user who carried out the ndtrack, i.e. the inventory of the device. This is usually “SYSTEM” for Windows, as the installed agent is executed in the SYSTEM context (NT AUTHORITY\SYSTEM). This is therefore absolutely normal.
I rather suspect that it is a similar problem to the inventory of remote servers, where there is no actual logon to the device, but only access via Remote Desktop. This will also be the case with Cloud PCs, as only a remote connection is established here, but there is no actual user login to a device.
The fundamental question is, does the device or operating system actually register which user is actually logging in remotely? Is the information possibly written to some WMI class, which could then be read out?
Try the following command on the cloud PC and check the results:
wmic COMPUTERSYSTEM GET USERNAME
Good Luck!