Well some people agreed with my point and other people as i would suspect see the need to document everything. I understand having documentation and I have no problem with that. But the way i look at it the network interfaces of the vmware is not something that needs to be documented, you can just work out from what is already there what you need.
If the building burnt down we would invoke DR which has a completely different environment than the in house esxi and even then if you had that documentation it would not help in a dr situation because the storage is different. If you had to rebuild the entire system from backup tapes and brand new hardware. It would not necessarily have to have the same ip addresses to contact the storage. It would only be important that the storage is presented to the esxi. But in the unlikely event of that occurring it would help to have everything documented.
But for example group policy, it was said that they want to know what group policy is in use and why. I thought this was pointless because if someone does not know how to interpret group policy just by looking at it then i don't think they should be touching it in the first place. ie if you need documentation to help interpret gpo then you don't know gpo. IF they want to keep a backup of gpo that is something different, its already backed up in to the several dc backups we have. Could even do a manual gpo backup and attach it to the docs.
