Now that apm 2.0 supports running windows scripts, I was thinking about making a monitor that runs script to scan for installed software on my servers, stores them in a table and alerts if new software has been installed. It would also allow me to make a report that showed new software installed in the last day/week/month/etc.
Would this break anything, or should I create my own database for my table?
It's not that this would necessarily break APM, but we can't promise that we won't break what you've done with an update.
Well I mainly wanted to know if you activelly looked for extra tables and drop them. I added a table Monday, and it's still there and I just didn't want to go to far down the road if it was going to go away when some maintance script runs Friday night or whatever.
I have a cool vbs script that uses odbc to write to a sqlite database. Should be easy to convert it to mssql. And having it a standard monitor that gets added to all monitored servers, would be much easier to maintain, than having to manually run easyaudit or the like.
If anyone is interested if I get it working well, I'll provide the details.
We don't hunt for rogue tables. Dev suggested that you might want to prepend your table name with something unique to elminate the possibilty of our accidentally overwriting your table.
right now, they are PEO_hardware, PEO_software, didn't figure that would ever be used by you guys.
FordCrews:If anyone is interested if I get it working well, I'll provide the details.
I would be interested in seeing the details once you get it working.