![]() ![]() If you had to do this manually, both asset and your CMDB would be severely out of date in no time unless you were a small org with only a few assets. Then as you make changes to the environment, build new servers or decomm old servers, or change an application to different servers this CMDB gets updated with the current information and allows you to track these changes (change module) with who did what when in an automated tool. S/N can do both with different modules but essentially you have to have the S/N scanners go sniff out all the assets and configurations on those assets and keep it updated on a routine basis (say once a week). To me, a tool like ServiceNow (not cheap for small orgs), would be an example of this.ĭmytro touched on the need to track changes but also assets.
0 Comments
Leave a Reply. |