It seems the "devOpsSetupRunbook" is contingent on the "WVDTestUsers" group being present for it to be successful. In my existing test AD environment, AD Connect is not syncing everything in the directory, so it couldn't find WVDTestUsers after the next sync and the runbook eventually fails on this step. Something to check if you're trying to use this deployment with your own AD environment. Maybe tweak the pre-req for people using existing AD/ADConnect configurations? Awesome, great work!
It seems the "devOpsSetupRunbook" is contingent on the "WVDTestUsers" group being present for it to be successful. In my existing test AD environment, AD Connect is not syncing everything in the directory, so it couldn't find WVDTestUsers after the next sync and the runbook eventually fails on this step. Something to check if you're trying to use this deployment with your own AD environment. Maybe tweak the pre-req for people using existing AD/ADConnect configurations? Awesome, great work!