aabdul ✭✭✭✭✭

I know this post is too old, but for the sake of others replying to this post so that it might help others. The questions have been answered on another post https://thwack.solarwinds.com/t5/NPM-Discussions/Timezone-Discussion-Remote-pollers/m-p/159719

I agree as well, it is a good feature to have in web console. Here is the thwack page to give a thumbs up https://thwack.solarwinds.com/t5/SAM-Feature-Requests/Schedule-recurring-maintenance-unmanage-for-nodes-and-groups/idi-p/565667

I stumbled across this post and thought reply to this old post so that it might help others solve the queries raised here. Please check out this product blog post Vmware Events is now available in VMAN 8.4 onwards Hope this helps!

It skips the inventory

- please check this post and if that does not help add your vote

I just tested in PM 2.1.7 Sync completed without any errors. I suggest you to try this Success Center

Stumbled across this post, for the sake of helping others. I had a customer with similar error(s) while trying to deploy PM agents via Remote install service on Server 2008 x86 endpoints. The work around was to use Offline deployment of PM agents​ The MAC address retrieval using ARP resolution was not attempted for…

Thanks Jame, it is really helpful

Turns out this is also prevalent on Windows 10 and windows 2016 when used computer explorer and update history check. Will be fixed in PM 2.1.6

You could use one of the reports under 1. Reporting -> Windows Server update Services Analytics report group 2. Choose computer update Summary / Approved update summary reports 3. Select the appropriate data source for that report. Hope this helps.

I had one customer today with same errors, though they were related to MS patches on 2 Server 2016 endpoints and from a previous case last year it the error came up when installing MS KB890830 According to this post the problem might be caused by SHA-2 Code Signing Support requirement for Windows and WSUS

As of release ARM v9.0.821 release, installation along with NPM is not recommended/supported. This is due to some dependent services version incompatibilities. I'm sure this will change in future release at least for small environments.

TCP port 37893-37896 - used for Return traffic from the SolarWinds LEM appliance to SolarWinds LEM Agents, most likely firewall.

Probably a late response - for sake of other users who might be on this post with similar question. SAM has a built in Template called "File Change monitor" which can monitor the file change events including checksum. See for more details.…