I like LucD's suggestions very much.
My primary vehicle for automating the VMware environment is Powershell, and in that context here are my suggestions:
- The VITKW Applet CHM is great. It has more or less what I need for applets, although some of the definitions for newbies is very vague: specifically get-module (what is a module), get-view (a view of what - I know now but that was the hardest concept to grasp).
- Although the parameters to the Set- applets gives a hint what properties and methods VITKW objects have, I would have like to have seen a section of the chm devoted to the properties and methods of the VITKW objects. Yes there is Get-Member to see that info, but you can get a better sense of what's possible looking through a document
- It would be nice to have an MSDN-like documentation of the .Net classes in the VITKW.
- I found the SDK website clunky and very frightening at first read. I had a lot of trouble finding a context for many of the classes, again at first read. Once you know the SDK a bit it become much more usable.
If you are asking about general documentation, I would love to see a clear set of documentation about configuring SSL in VI Infrastructure. There is a hodge-podge of somewhat conflicting/confusing KB articles, and they are fairly silent on configuring SSL for Update Manager and Consolidation Manager, especially when the SQL server is elsewhere and we're following your best practice of using SQL logins rather than integrated logins.
The VUM documentation really needs some technical information to assist troubleshooting. EG: What happens under the covers during Update Signatures? vmware-updateDownloadCLI? How big does the VUM database need to be? What happens when the UM service starts?
Right now, each doc is a separate PDF and you have to watch like a hawk to see if a PDF has been updated. Having a single documentation set bundle which is updated when any one component is updated would simplify downloads for people starting off, and for people who haven't downloaded the docs in a while. I would include the SDK and Tools docs in this doc set. I would also include the doc set and toolsets on the VC images.
I tend to prefer chm's for searching and online use, and pdf's for printing. Not sure whether it's feasible to provide both formats. Likely not, and PDF's are universal.
Hope this helps. Generally, I like the VMware documentation. It is reasonably complete and well formatted.
