chillipepper

I don't think enabling the DMI agent at this point ( especially when bash exploit exists) is a good idea even though it works

I had a ticket open with Solarwinds the case was transferred to Application development team as the tech support was not able to solve the issue. The App dev team found a potential bug in custom properties where the upsize_ts was holding the value while the node was being synced between NCM and Core by deleting the values…

We are running 7.3 and it still does not work.

Yes that was the 1st step i tried but the issue is i dont see any nodes in there to sync no matter if i choose vendor or any other option from the left it doesnt find anything all it sync's are the old 20 nodes that existed before we upgraded to 7.1.1

We fixed the issue today, in 7.2 the account that NCM uses to write the archive config to specific location also needs full admin access on the machine in addition to the write access on the share. Not sure why this was changed from previous version and to me it makes no sense.

I guess its something more than just permission issue, just got off call with Solarwinds they couldnt figure it out as well. As per them if it was permission issue then it should not be able to validate either which is not the case though. They have sent this to the their dev team hopefully we get some response. Will…

Case # 512177 is open with Solar winds, when we upgraded to 7.2 the account was specified the path to the share is validated as well. Not sure how to integrate Job with windows task scheduler i guess when a scheduled job was created in 7.1 it created a windows scheduler itself. If i manually download the config it writes…

If any one has issues related to Scheduled Job execution after upgrading to 7.2 please open a case with Solar winds and have them check the Job services and job scheduler services running on the NCM server. With the new version 7.2 job service v2 is a new service that is responsible to write any configs to the specified…