Audits. Love them or hate them, system inventories and audits are critical.

enterprise systems management for IT professionals

Knowing and tracking every system and software detail should be simple, efficient and reliable no matter where the devices you’re managing are located. Good data empowers good decision making. Having good data at your fingertips means that you can make better decisions, give better answers and have a better understanding of the current state of your endpoints. Your enterprise systems management audit solution should be able to grab every piece of useful data from your managed machines.

Having comprehensive data allows you to:

  • Close security holes
  • Reduce interoperability issues
  • Examine hardware/software policy issues
  • Inventory computers without interrupting users

You and your IT systems management  team may manage multiple devices in many locations. You’re expected to know each machine by name and category and to be able to provide per-department IT costing and inventory information.

If good data drives good decisions, then it’s crucial to have an enterprise systems management tool that automates the process of running regular audits to collect that data. You should be able to schedule machine audits in any way that you see fit. Clear status reporting would allow you to see when the last audit was completed, when the next one is scheduled and when you last did a baseline audit for your machines.

With Kaseya’s centralized inventory repository, all the data is stored on the server so when you need the details you don’t have to wait for the endpoint. You can:

  • View complete computer summary on one screen
  • Pinpoint failures by manufacturer and model
  • Review changes against the baseline
  • Generate the reports you want, right away

If your network has more than about 20 devices, managing them can become difficult. Enterprise systems management professionals faced with the challenges of tracking IT resources can greatly benefit from a complete hardware inventory, plus a software inventory of the servers, workstations and mobile computers on their network.

Unfortunately, many enterprise systems management professionals end up having one system for inventory, another for remote access and even a separate system just for chassis or serial number tracking. IT systems management automation is the key for transitioning from a reactive environment to a proactive, results-based IT service delivery model.

Learn how to improve your enterprise systems management capabilities. Listen to this webinar, “When Technology IS the Business, Effective IT Management is Critical” for ways you can cost-effectively manage information technology across the enterprise.

2 thoughts on “Audits. Love them or hate them, system inventories and audits are critical.

  1. The kaseya agent system automatically deploys the baseline audit when you first install the agent (even if you remove it from the template), then the latest audit runs always at that same time each day. You can reschedule the latest audit through the auditing manager but…

    There is no way to reschedule the baseline audit. You better hope that the machine is fast enough to run it or you get some very angry customers on the receiving end during a deploy.

    There is no way to schedule deployments of agents using the lan-watch feature, and the baseline audit is automatic: This means I’m looking at deploying 300+ agents in the middle of the night (10pm – 2am), or manually deploying them one at a time throughout the day and hoping that I can disable the baseline audit before it has a chance to kick off.

    Did I mention that no other procedures will run during a latest audit? yeah, all those messages to the user won’t actually be sent until after the audit is ran. So you better schedule the latest audit during downtimes otherwise your announcement to leave the computer on overnight won’t get sent out it time.

    Oddly enough you can schedule a baseline audit from within the audit manager. Seems like this is a feature that hasn’t been fully implemented.

    If only there was some way of having the audit procedures run as a low-priority thread or in some sort of low-IO mode that takes longer to run, but is less invasive on the system.

  2. You are mostly correct, however in regards to your last statement.

    The audit DOES do this.

    I’ve NEVER noticed it slowing down my machine, nor have I ever actually seen the agent using much CPU at all.

    It is amazing how efficient the Kaseya is at auditing a machine. Now, the biggest ‘problem’ is it can take some time to run (because it isn’t running at a high priority!) and upon initial agent deployment this can be bothersome if you have other things you want to do with a machine right away.

    Our KLC processes run on a separate thread, but I’m not sure if the very first remote control attempt to a machine will need the initial audit to complete. I know that subsequent audits can be running concurrently with KLC remote connections to a given agent.

Leave a Reply

Your email address will not be published. Required fields are marked *