Server Build Documentation
-
My boss has asked me to create documentation for each VM we have. He is looking for information like network, hardware, application, user accounts, services, and any other helpful detail.
Is there a way to pull this kind of detail in a good looking report. These are Vsphere 5.5 VMs. I am looking for a free solution.
-
No help for you, but I can commiserate.
I am horrible about taking the time to create documentation. I know it is important, but I always put it off. -
Never done it but does VMware have a way to create a report from an audit of some sort inside the vSphere client/web client?
-
I use Spiceworks. Most of the information is easily available there. However, it's not for everyone.
-
I have PDQ Inventory Pro and I was able to build reports with this information and so much more. I am able to quickly pull reports of useful information including all the basics and:
Windows Features and Roles installed on each server
Scheduled Tasks, next run, successful or not, and what user is running them
Services and user running them
All members of the "administrators" group including local and domain users
IE version and settings
and much more -
@thanksajdotcom said:
Never done it but does VMware have a way to create a report from an audit of some sort inside the vSphere client/web client?
Don't believe so.
-
@nadnerB said:
I use Spiceworks. Most of the information is easily available there. However, it's not for everyone.
This is a good solution when a report is needed. Meraki SM will do this too, but sans reporting. I think you could get a CSV file and make a report that way, but am just guessing.
-
Good luck. My last boss was so confused by VMs. He had never heard of doing it for servers before and though that was only something for testing. And then he would called them VSPs (he mean VPS, but would say and type VSP). Neither of which they were anyway.
-
@thecreativeone91 said:
Good luck. My last boss was so confused by VMs. He had never heard of doing it for servers before and though that was only something for testing. And then he would called them VSPs (he mean VPS, but would say and type VSP). Neither of which they were anyway.
points for trying, reminds me of the pointy haired boss in dilbert though.
-
@thecreativeone91 said:
Good luck. My last boss was so confused by VMs. He had never heard of doing it for servers before and though that was only something for testing. And then he would called them VSPs (he mean VPS, but would say and type VSP). Neither of which they were anyway.
I've given up on trying to explain VMs to my boss. No amount of fancy diagrams, articles, or sitting with him and talking through it has helped. He trusts me enough to make the right decisions when it comes to tech though.
-
What VMs guests are running? Have a look at http://sydiproject.com/home/
I've used it once on my windows server when my boss asked me for all details on that server. Ran Sydi and it gave me an extensive report of that server automatically documented on word.
-
For my own documentation I use excel and fill out a sheet with the basics like that. Good "bus" policy.
X does Y
X's vital stats:
ip
domain
admin account (name, not pw)
who owns it
why does it do Y
dependencies
VM Host name / IPyou get the idea - keep it point form and short. No need to write a saga
-
Check this too www.robware.net
