NetXMS Support Forum

Sorry, I didn't read the guide carefully. In the description, you can use parameters to select all three choices on the first screen like an installation wizard, such as,

/MERGETASKS="fspermissions,sessionagent,useragent"

This problem does not exist

When I use the Unattended installation of netxms5.1.1, after installation, 
start /wait "" "nxagent-5.1.1-x64.exe" /SILENT /SUPPRESSMSGBOXES /SERVER=serverip /CENTRALCONFIG /SUBAGENT=UPS
 /SUBAGENT=FILEMGR /SUBAGENT=LOGWATCH /SUBAGENT=PING /SUBAGENT=WMI /SUBAGENT=netsvc /SUBAGENT=winperf
 /LOGFILE=C:\NetXMS\log\netxms.log /FILESTORE=C:\NetXMS\var
it does not add nxuseragent.exe and nxsagent.exe to the startup folder of windows like directly using the installation file, although the services of both will be installed and executed normally,
but the Unattended installation is used because there is no automatic activation project in front,
As a result, "Take Screenshot" and "FileManager" cannot be used normally when using NXMC,
but the Edit Agent configuration on NXMC is normal

Of course, if I manually add a shortcut to nxuseragent.exe and nxsagent.exe in the Windows startup directory, it will all be back to normal again.

Is there some problem here?

Quote from: Victor Kirhenshtein on November 22, 2024, 01:54:31 PMAgent reads registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to get list of installed products.
I tested WMI query on Win32_Product on my Windows servers, and it seems to work, but is very slow (usually more than 10 seconds). Normally agent command timeout is less than that, so data collection end up in error.
Could you use System.InstalledProducts table instead?

Best regards,
Victor

hi
After receiving your tip, I immediately looked for the agent timeout settings. 
Sure enough, I found agentcommandtimeout in the server configuration. 
The default value is 4000. For testing, I increased it to 20000. 
After restarting the service, it worked magically. The content of the data table is displayed normally.
Although I don't know the reasonable value of timeout, 
I will continue to pay attention to the difference in the increased timeout value.
thx victor

Although the operation of the action is executed under the system account by default under the agent, 
it is invisible under the Windows session of the user currently logged in, 
which is a great advantage for background system management, 
but it is not necessary for the operation that needs to be known to the user at the front desk. It is not easy to achieve, such as the agent's "send user support application notification", 
other front-end operations such as opening a browser to connect to a website, 
and the execution of programs that require GUI display.

It would make netxms more complete if ACTION had an execution option for now logged in user session.

Although the previous wmiquery problem cannot be solved, 
but I want to use DCI to list the requirements of the software installed on the computer, 
in the built-in DCI TABLE source NETXMS.AGENT can be set in the METRIC System.InstalledProducts,
the table will list the software installed on the computer

Quote from: uldis on November 19, 2024, 11:49:53 AMHi, so I will be treading carefully here as all based on Google research. There is an indication that Win32_Product is not query optimized class and thus query on this class runs a consistency check and performs silent repairs. This would probably require for agent to have admin rights on Windows server(?).

Here is Microsoft guidance to use an alternative method and that is to query registry - https://learn.microsoft.com/en-us/troubleshoot/windows-server/admin-development/windows-installer-reconfigured-all-applications.

Please let us know if that works for you.

hi
According to the link guide you provided, the Win32reg_AddRemovePrograms mentioned also has the same result as Win32_Product. I had also suspected that it was an issue with administrator rights, but I found that other queries with more system confidentiality and security, such as Win32_Process, Win32_Service, and Win32_UserAccount, could all be queried normally. Maybe as the page explains, Win32_Product was not done properly. For general queries, Microsoft also requires that you try not to use this.
Finally, I want to know how NetXMS can successfully obtain software inventory from the agent? I want to implement it on DCI.

The query SELECT * FROM Win32_Product was unsuccessful.
 I checked the agnet log and found that in addition to the 500 error,
 there was also WMI: call to CoInitializeSecurity failed. 
It seems to be a security issue. Is there any solution?

The following is the log record. Although errors have occurred, 
we can still see the table data queried.

2024.11.17 15:11:56.163 *D* [comm.cs.1          ] Received message CMD_GET_TABLE (324)
2024.11.17 15:11:56.163 *D* [comm.cs.1          ] Requesting table "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")"
2024.11.17 15:12:00.164 *D* [comm.cs.1          ] Message dump:
  ** 000000 | 00 03 50 00 00 00 00 10 00 00 01 45 00 00 00 00 | ..P........E....
  ** code=0x0003 (CMD_KEEPALIVE) version=5 flags=0x0000 id=325 size=16 numFields=0

2024.11.17 15:12:00.164 *D* [comm.cs.1          ] Received message CMD_KEEPALIVE (325)
2024.11.17 15:12:00.164 *D* [comm.cs.1          ] Sending message CMD_REQUEST_COMPLETED (ID 325; size 32; uncompressed)
2024.11.17 15:12:00.164 *D* [comm.cs.1          ] Outgoing message dump:
  ** 000000 | 00 1D 50 00 00 00 00 20 00 00 01 45 00 00 00 01 | ..P.... ...E....
  ** 000010 | 00 00 00 1C 00 00 00 00 00 00 00 00 00 00 00 00 | ................
  ** code=0x001D (CMD_REQUEST_COMPLETED) version=5 flags=0x0000 id=325 size=32 numFields=1
  ** 000000: [    28] INT32      0

2024.11.17 15:12:00.165 *D* [comm.cs.1          ] Message dump:
  ** 000000 | 00 F5 50 00 00 00 00 50 00 00 01 46 00 00 00 01 | ..P....P...F....
  ** 000010 | 00 00 00 55 07 00 00 00 00 00 00 33 57 4D 49 2E | ...U.......3WMI.
  ** 000020 | 51 75 65 72 79 28 72 6F 6F 74 5C 43 49 4D 56 32 | Query(root\CIMV2
  ** 000030 | 2C 22 53 45 4C 45 43 54 20 2A 20 46 52 4F 4D 20 | ,"SELECT * FROM
  ** 000040 | 57 69 6E 33 32 5F 50 72 6F 64 75 63 74 22 29 00 | Win32_Product").
  ** code=0x00F5 (CMD_GET_TABLE) version=5 flags=0x0000 id=326 size=80 numFields=1
  ** 000000: [    85] UTF8-STRING "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")"

2024.11.17 15:12:00.165 *D* [comm.cs.1          ] Received message CMD_GET_TABLE (326)
2024.11.17 15:12:00.165 *D* [comm.cs.1          ] Requesting table "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")"
2024.11.17 15:12:00.165 *D* [                  ] WMI: call to CoInitializeSecurity failed
2024.11.17 15:12:00.165 *D* [                  ] WMI: query "SELECT * FROM Win32_Product" in namespace "root\CIMV2" failed
2024.11.17 15:12:00.165 *D* [comm.cs.1          ] GetTableValue(): result is 500 (INTERNAL_ERROR)
2024.11.17 15:12:00.165 *D* [comm.cs.1          ] Sending message CMD_REQUEST_COMPLETED (ID 326; size 32; uncompressed)
2024.11.17 15:12:00.165 *D* [comm.cs.1          ] Outgoing message dump:
  ** 000000 | 00 1D 50 00 00 00 00 20 00 00 01 46 00 00 00 01 | ..P.... ...F....
  ** 000010 | 00 00 00 1C 00 00 00 00 00 00 01 F4 00 00 00 00 | ................
  ** code=0x001D (CMD_REQUEST_COMPLETED) version=5 flags=0x0000 id=326 size=32 numFields=1
  ** 000000: [    28] INT32      500

2024.11.17 15:12:03.645 *D* [comm.cs.1          ] GetTableValue(): result is SUCCESS, value contains 471 rows
2024.11.17 15:12:03.645 *D* [comm.cs.1          ]    AssignmentType|Caption|Description|HelpLink|HelpTelephone|IdentifyingNumber|InstallDate|InstallDate2|InstallLocation|InstallSource|InstallState|Language|LocalPackage|Name|PackageCache|PackageCode|PackageName|ProductID|RegCompany|RegOwner|SKUNumber|Transforms|URLInfoAbout|URLUpdateInfo|Vendor|Version|WordCount
2024.11.17 15:12:03.645 *D* [comm.cs.1          ]    1|Office 16 Click-to-Run Extensibility Component|Office 16 Click-to-Run Extensibility Component|||{90160000-008C-0000-1000-0000000FF1CE}|20241101|||c:\program files\microsoft office\root\integration\|5|0|c:\WINDOWS\Installer\fbc3.msi|Office 16 Click-to-Run Extensibility Component|c:\WINDOWS\Installer\fbc3.msi|{C765E232-FFB0-4E0C-ABE2-57538949FC70}|C2RInt.16.msi||||||||Microsoft Corporation|16.0.18129.20100|0
2024.11.17 15:12:03.645 *D* [comm.cs.1          ]    1|Office 16 Click-to-Run Localization Component|Office 16 Click-to-Run Localization Component|||{90160000-008C-0404-1000-0000000FF1CE}|20241101|||c:\program files\microsoft office\root\integration\|5|1028|c:\WINDOWS\Installer\fbf3.msi|Office 16 Click-to-Run Localization Component|c:\WINDOWS\Installer\fbf3.msi|{9C80BB02-55A3-428E-8044-3556FB56F9B6}|C2RIntLoc.zh-tw.16.msi||||||||Microsoft Corporation|16.0.18129.20100|0
2024.11.17 15:12:03.645 *D* [comm.cs.1          ]    1|Office 16 Click-to-Run Licensing Component|Office 16 Click-to-Run Licensing Component|||{90160000-007E-0000-1000-0000000FF1CE}|20241101|||c:\program files\microsoft office\root\integration\|5|0|c:\WINDOWS\Installer\fbfc.msi|Office 16 Click-to-Run Licensing Component|c:\WINDOWS\Installer\fbfc.msi|{29F8FAA5-EBBF-4EA4-81CB-C0629F26D29C}|SPPRedist.msi||||||||Microsoft Corporation|16.0.18129.20116|0
2024.11.17 15:12:03.646 *D* [comm.cs.1          ]    1|SQL Server 2017 Full text search|SQL Server 2017 Full text search|https://go.microsoft.com/fwlink/?LinkId=154582||{C37AD300-12CF-4911-9019-A05D66055EB4}|20241115|||C:\SQLServer2017Media\ExpressAdv_CHT\x64\setup\|5|1033|C:\Windows\Installer\1b46f21.msi|SQL Server 2017 Full text search|C:\Windows\Installer\1b46f21.msi|{CE06E25F-15DC-4D18-889C-34CF07054C9E}|SQL_FULLTEXT.MSI|||||:SqlRun01.mst;:InstID01.mst;:InstName01.mst|||Microsoft Corporation|14.0.1000.169|0
2024.11.17 15:12:03.646 *D* [comm.cs.1          ]    1|Microsoft .NET Framework 4.5.1 Multi-Targeting Pack|Microsoft .NET Framework 4.5.1 Multi-Targeting Pack|||{6A0C6700-EA93-372C-8871-DCCF13D160A4}|20200313|||C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.4.5.1.TargetingPack,version=4.5.50932.1\|5|1033|C:\Windows\Installer\1bfbac2.msi|Microsoft .NET Framework 4.5.1 Multi-Targeting Pack|C:\Windows\Installer\1bfbac2.msi|{D6098F6F-BA25-46AC-8358-CEBEA010E3BA}|netfx_451mtpack.msi||||||||Microsoft Corporation|4.5.50932|0
2024.11.17 15:12:03.646 *D* [comm.cs.1          ]    1|SQL Server 2017 Advanced Analytics|SQL Server 2017 Advanced Analytics|https://go.microsoft.com/fwlink/?LinkId=154582||{826DA700-7B76-49BA-8A83-E55F5FA1301E}|20241115|||C:\SQLServer2017Media\ExpressAdv_CHT\x64\setup\|5|1033|C:\Windows\Installer\1b46f06.msi|SQL Server 2017 Advanced Analytics|C:\Windows\Installer\1b46f06.msi|{D51BE933-FA08-415D-965A-C04006F87189}|SQL_EXTENSIBILITY.MSI|||||:SqlRun01.mst;:InstID01.mst;:InstName01.mst|||Microsoft Corporation|14.0.1000.169|0
2

Recently, I started to use wmi query seriously in my working environment USING NETXMS 5.1.0 .
I added a DCI tableB in node and used agent as the data source. 
When setting METRIC to WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product"), 
It was found that it had no effect. The DCI was blank and had no field name, 
but the DCI did not automatically DISABLE. However, 
when I changed the query command to the following 
SELECT * FROM Win32_OperatingSystem
SELECT * FROM Win32_Process
SELECT * FROM Win32_Service
SELECT * FROM Win32_BIOS
SELECT * FROM Win32_NetworkAdapterConfiguration
SELECT * FROM Win32_UserAccount
All values in table format are displayed normally.
I just want to change the built-in NODE function 「SOFTWARE INVENTORY 」of NETXMS
to be used on DCI TABLE, but I found that the built-in functions are all normal,
except that I cannot reproduce it on DCI.
Get-WmiObject -Class Win32_Product | Select-Object Name, Version, Vendor | Format-Table -AutoSize On the tested NODE, it is normal to use POWERSHELL to test.
What is the cause of this problem?
The following is what I excerpted from the DEBUG LOG. ERROR=500 RESULT =5 appears.


2024.11.16 23:12:57.099 *D* [dc.agent          ] Node(YMXXXX)->getTableFromAgent(WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")): error=500 result=5
2024.11.16 23:12:57.099 *D* [client.session.0  ] Sending message CMD_NOTIFY (48 bytes)
2024.11.16 23:12:57.099 *D* [client.session.0  ] Message dump:
  ** 000000 | 00 12 50 00 00 00 00 30 00 00 00 00 00 00 00 02 | ..P....0........
  ** 000010 | 00 00 00 17 00 00 00 00 00 00 00 22 00 00 00 00 | ..........."....
  ** 000020 | 00 00 00 5C 00 00 00 00 00 01 1E 68 00 00 00 00 | ...\.......h....
  ** code=0x0012 (CMD_NOTIFY) version=5 flags=0x0000 id=0 size=48 numFields=2
  ** 000000: [    23] INT32      34
  ** 000010: [    92] INT32      73320

2024.11.16 23:12:57.099 *D* [client.session.0  ] Sending message CMD_NOTIFY (48 bytes)
2024.11.16 23:12:57.099 *D* [client.session.0  ] Message dump:
  ** 000000 | 00 12 50 00 00 00 00 30 00 00 00 00 00 00 00 02 | ..P....0........
  ** 000010 | 00 00 00 17 00 00 00 00 00 00 00 22 00 00 00 00 | ..........."....
  ** 000020 | 00 00 00 5C 00 00 00 00 00 01 1E 68 00 00 00 00 | ...\.......h....
  ** code=0x0012 (CMD_NOTIFY) version=5 flags=0x0000 id=0 size=48 numFields=2
  ** 000000: [    23] INT32      34
  ** 000010: [    92] INT32      73320
2024.11.16 23:27:01.926 *D* [obj.dc.queue      ] DataCollectionTarget(YMXXXX)->QueueItemsForPolling(): item 143083 "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")" added to queue
2024.11.16 23:27:01.926 *D* [dc.collector      ] DataCollector(): processing DC object 143083 "WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")" owner=73320 sourceNode=0
2024.11.16 23:27:05.928 *D* [dc.agent          ] Node(YMXXXX)->getTableFromAgent(WMI.Query(root\CIMV2,"SELECT * FROM Win32_Product")): error=500 result=5

Quote from: Alex Kirhenshtein on November 12, 2024, 10:48:36 AM

Quote from: hmjvaline on November 10, 2024, 01:59:29 PMNew NXMC already has mib file upload feature ,
There is no need to pull the mib file from the server side
another The jar file used in the report server also needs to be added to the server.
If it can be uploaded directly to the server through nxmc on the client, it will become very convenient to maintain or update.

Just use built-in file manager to delete jar file and upload new version to definitions directory.

Are you talking about installing AGNET on the server, using filemgr.nsm in the agent, 
and using 「 file manager」 command on the node? Other commands, 
such as 「upload file 」on NODE, throw the server's files to the agent client, 
and others like There is no way to see the JAR file I have uploaded to C:\NetXMS\var\nxreportd\definitions using TOOL->UPLOAD FILE TO SERVER or CONFIRUATION->SERVER FILE MANAGER.

I tested again and found that the problem may not be a capitalization issue. 
After we set snmp.codepage to utf-8, after I restarted the service and restarted the windows server,
 I found that it began to be unable to parse text normally again 
until I pressed the edit codepage again in the server configuratione, 
but did not modify it directly After saving, it returned to normal, 
so I think the settings of snmp.codepage may not be properly accessed when the service is restarted, 
but only take effect when the settings are saved.

A while ago, in order to get the name of the interface from snmp,
 because the name encoding uses UTF-8, I set UTF-8 in the setting option of SNMP.Codepage, 
and found that it had no effect.SNMP.Codepage


Later, it wasn't until I thought of changing UTF-8 to utf-8 that it started to work normally. 
Should this input be changed to mainly uppercase, 
or should it be made directly case-insensitive?

New NXMC already has mib file upload feature ,
There is no need to pull the mib file from the server side

another The jar file used in the report server also needs to be added to the server.
If it can be uploaded directly to the server through nxmc on the client, it will become very convenient to maintain or update.

Quote from: Victor Kirhenshtein on November 06, 2024, 04:22:49 PMIf you represent educational or non-profit institution, feel free to contact us directly and I'm sure we can find a solution.
Best regards,
Victor

I think I need your support, how should I contact you ? 
as before I upgraded to 5.1.0 without thinking carefully, now I can't downgrade to 5.0.8 so that I can continue working with netxms, the worst I also lack a backup of the database and cannot see the complete steps for downgrading the database. How can I get myself back to the normal working state as quickly as possible?

Quote from: Victor Kirhenshtein on November 06, 2024, 04:07:38 PM

Quote from: hmjvaline on November 06, 2024, 03:03:35 PMI am shock netxms 5.1 is limited to 250 nodes  
It reduced my enthusiasm for NetXMS and even gave up on it because it is no longer so open and free. Although I have never needed the company's institutionalized services, I feel discouraged by this new restriction.

You know, even open source developers need money for living. And purchasing support contract for using open source product pre-built for Windows platform is not a big ask in my opinion. 250+ devices is not a small deployment, so likely organization is not that small either, and do not hesitate paying license fee for Windows servers.

Thank you very much for your long-term contribution to NETXMS. I know that the sustainability of anything requires money to support, and the changes in NETXMS are not the only example. 250 node maybe for small commercial company is not too small and may have enough funds to support it, but for me as a school worker, this may not be too easy. The school I serve is There are not only hundreds of servers and switchs , not to mention more than 500 computers or notebook or  pad. Maybe this sounds a bit scary, but in the future, netxms may consider the plight of users in educational institutions.Finally, I would like to thank netxms and you all.

Quote from: Alex Kirhenshtein on November 06, 2024, 03:29:31 PM

Quote from: hmjvaline on November 06, 2024, 03:03:35 PMI am shock netxms 5.1 is limited to 250 nodes  
It reduced my enthusiasm for NetXMS and even gave up on it because it is no longer so open and free. Although I have never needed the company's institutionalized services, I feel discouraged by this new restriction.

Hi
Well, product is still open and free. Only official build for Windows Server is restricted now. You have following options:
- purchase support contract from us (any support tier will give you license for unlimited number of nodes)
- built it yourself
- migrate server to Linux

Thank you for your immediate explanation of possible alternatives. I will try to remain unrestricted and try these methods, but I am an enthusiastic supporter and user of Windows, mainly because of the closeness to work use and convenience. Many years ago, in order to be able to run under Windows I found an open source, free, and easy-to-use NMS. I  spend time looking for suitable software and learning. Maybe users under WINDOWS are destined to be restricted or charged in the end. However, under LINUX, there will be more OPEN AND FREE NMS to choose from. NETXMS maybe was not that special under linux, but NETXMS has always been special under WINDOWS.