Hoping to revive this thread. I'm looking at automating SQL Always On Clusters and Availability Groups, and banging my head on the same things discussed here. I came here hoping to find a way to leverage a "Deployment-level payload" that contains all information about all blueprint components deployed that could be passed into a post-machine-build workflow that automates the cluster configuration and related things that need to be automated.
Am I reading that such Deployment-level Payload does not exist? Did anyone find a good solution here? Dynamic Configuration Elements?!? Yuck! (but maybe...?)
sbeaver jadelzein GrantOrchardVMware stvkpln
(hope you guys don't mind the tags -- anyone know of a good KB, blog post, or other doc that discusses managing information about multiple machines in a multi-machine blueprint?