{"id":2056,"date":"2014-05-06T08:00:54","date_gmt":"2014-05-06T14:00:54","guid":{"rendered":"http:\/\/www.jumpcloud.com\/?p=2056"},"modified":"2024-11-08T17:16:39","modified_gmt":"2024-11-08T22:16:39","slug":"audit-servers-10-minutes","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/audit-servers-10-minutes","title":{"rendered":"How to Audit Your Servers in 10 Minutes"},"content":{"rendered":"\n
Auditing servers is never easy, it\u2019s almost always a time-consuming manual process. And, it\u2019s a process that for the ones auditing the servers is considered time wasted when they\u2019d rather be doing almost anything else. Auditing is needed for inventory purposes, budget planning, capabilities analysis, disaster recovery, security, compliance and a host of other reasons. If you\u2019re in IT, you know this well, and have the scars to prove it.<\/p>\n\n\n\n
Depends on who\u2019s asking, but the kinds of things you\u2019re asked for varies a bit:<\/p>\n\n\n\n
As far as server location (#1), this is really dependent on where your server is hosted. If it\u2019s hosted in a local data center, the IP address of the server may be sufficient to tell you where it is. If it\u2019s hosted by a cloud provider, the combination of the fully qualified domain name and\/or IP address may help. If you need a more specific location, such as rack and bay number, there are systems that help with that type of asset management<\/a>.<\/p>\n\n\n\n But, for a quick and dirty assessment of hundreds or thousands of devices, nothing beats a script that runs a few commands and gets info out of \/proc. So, when I look at items 2-7 (and to a degree, number 1), my first thought is, I can write a script for that. It looks like:<\/p>\n\n\n\nQuick and Dirty Server Assessment Scripts<\/h3>\n\n\n\n