This video explains how to run a script to collect information about assets to keep CMDB up to date.
Video Transcript
So a slightly deeper look into SysTrack–added optimization: as I mentioned before, it’s more or less a script.
Once you’ve imported it, you set up the screen we saw previously, defining where SysTrack is and providing usernames, passwords, and related information.
You then go into the scheduled script execution, where all you really do is specify how frequently you want it to run. In our demo instance, we have it running daily at midnight every night, Pacific Time.
Because it’s ServiceNow, this script will run automatically, make a series of API calls to SysTrack, gather that information, and then drop it into ServiceNow.
In the real world, most people tend to run this weekly, since the information being collected—such as CPU specifications, disk, and memory—doesn’t change very often, making nightly runs somewhat overkill.
Weekly is generally sufficient for most environments, but as shown in the screenshot, you can also choose to execute it immediately and force it to run manually if something needs to be updated right away.
The value of this is that it keeps CMDB information up to date, eliminating the need for manual checks and record updates, and if devices aren’t already in the CMDB, it will populate the information needed for SysTrack Assist for ITSM.
We’ll explain those requirements shortly, but as you can see, the information collected from SysTrack and written into the CMDB is primarily inventory data—things like serial numbers, operating systems, and CPU types—which typically do not change very often.