I think the really operative phrase in this article is: "Once you have assembled the list of scriptlets you need – printed, laminated and guarded by a fire ele

I think the really operative phrase in this article is: "Once you have assembled the list of scriptlets you need – printed, laminated and guarded by a fire elemental as in days of old – you can make the 2012 stack of Microsoft software sing." My biggest issue with using windows server 2012 is the cognitive dissonance encountered when using the product. Are they trying to go more like unix and use command line scripts (e.g: powershell)? It sure seems that way. However, they also bolted on the most horrid and inappropriate UI ever onto the product. Is there some reason a hierarchical menu system doesn't make sense for an admin? Do they adopt a sensible convention of making all the configuration text editable? Is built in remote command line administration present (e.g: ssh?) It doesn't seem like it. As a competent linux admin and novice windows server admin it seems very confusing. And don't get me started on hyper-V. I really tried to use and spent almost a day of investigation. However, there really is nothing for documentation. With ESXI you download it, install, connect vmware fusion, and start working. Done. Couldn't figure out how to do that hyper-V.