Windows Agent 2.1.0.3 doesn't report User

Bug #1292020 reported by Travis Elsberry
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OCS Inventory: Windows Agent
Fix Released
Low
Didier Liroulet

Bug Description

My Windows agent is installed on a mix of Windows 8 Pro 32-bit/64-bit and Windows 8.1 Pro 32-bit/64-bit systems reporting back to a Linux 2.1 server. Before upgrading the agents from version 2.0.5 on the same platforms it worked fine with the new server version 2.1 On all of the computers where I upgraded the agent from 2.0.5 to 2.1.0.3 the User is not reported back, but on the remaining computers where the agent is still 2.0.5 it reports the User.

Revision history for this message
Steffen Jeschke (steffen-jeschke) wrote :

Same or better nearly the same problem here. I repost my thread from the forum and if more informations or some tests are needed i will provide them!

"Hi everybody,

i switched from calling OcsLogon from a Logon-User script to using the service. But lots of PCs doesn't collect/ report the username of the logged on user. (INVENTORY => Logged on user ID is <>). It seems to me that sometimes it works and sometimes not and nearly 100% of the not working pcs are windows xp - only one out of 150+ is windows 7.

For deploying the agent i use the gpo-startup-script version"

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi.

When using service, if nobody is logged on when inventory is done, agent send nobody.

If server has in is history "nobody", it leave nobody. Otherwise, it ignore the nobody and leave the previous logged on user.

Perhaps are you in this case...

Could please set DEBUG=1 into ocsinventory.ini file (you must stop service to modify this file), and then wait a few days and send me ocsinventory.ini and ocsinventory.log file generated ?

Cheers

Changed in ocsinventory-windows-agent:
assignee: nobody → Didier Liroulet (dliroulet)
Revision history for this message
Travis Elsberry (tj2718) wrote :

Hello Didier,

Attached are the requested files, zipped. I set debug=1 on all my installations so the files were ready to go.

I do not believe that nobody was logged in is the case. I was logged in to install the software when it did the initial inventory, as well as being logged in when I did a manual inventory from the icon in the system tray.

If there is anything else you need me to send or try, please let me know.

Thanks!

Revision history for this message
Jakub Bitenc (jakubjbitenc) wrote :

Same situation at my workplace. Agent updated to version 2.1.0.3. Computers with Win XP, Win 7 installed, report username correctly. No client out of 55 machines with Windows 8.1 reports user name.

Revision history for this message
Jakub Bitenc (jakubjbitenc) wrote :

I should have added this in aerlier post. OCSInventory.log contains:

AGENT => Launching hardware and software checks
 INVENTORY => Loading Download history
 INVENTORY => Logged on user ID is <>
 INVENTORY => Operating System is <Microsoft Windows 8.1 Pro 6.3.9600 >, description <4/442>
 INVENTORY => Operating System uses 32 bits memory address width
 INVENTORY => Computer domain or workgroup is <mydomain.local>
 INVENTORY => User domain is <>

Revision history for this message
phicel (phi-cel) wrote :

Hi,

Same problem for me...

Some user id is missing in about 30% of machines ( we have about 150 computers here )

All is on Windows 7

No problem with old agent

Revision history for this message
Hans Wurst (coding-v) wrote :

We had the same problem on machines running version 2.1.0.3.

However by using the latest source, the user gets reported correctly again.

Turned out that revision 490 (a fix for https://bugs.launchpad.net/ocsinventory-windows-agent/+bug/1300172) also seems to fix this problem.

--- SysInfo/SysInfo.cpp 2014-03-10 12:55:35 +0000
+++ SysInfo/SysInfo.cpp 2014-04-15 14:11:06 +0000
@@ -630,9 +630,11 @@
  TCHAR szUserName[255];
  DWORD dwUserName = 255;

+/* Don't use this code, it list all users connected on Domain controlers and uses 100% CPU
  // First, try WMI
  if (m_wmiInfo.IsConnected() && m_wmiInfo.GetLoggedOnUser( csUserName))
   return TRUE;
+*/
  // Then, try to find user running explorer.exe process
  if (getUserNameFromExplorerProcess( csUserName))
   return TRUE;

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Ok, this fix will be released in 2.1.1 available soon

Changed in ocsinventory-windows-agent:
status: New → Fix Committed
importance: Undecided → Low
Changed in ocsinventory-windows-agent:
status: Fix Committed → Fix Released
Revision history for this message
lenovo customer service (lenovohelp) wrote :

When using this version I have the same problem with this version, I change it to 2.1.0.1 which work well on this.But there is also some issue with my windows update so I get help from https://babasupport.org/microsoft/windows-customer-service/150 which is really a nice supportive site for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.