Hello all,
We recently discovered a "feature" that I'd like to share:
When creating templates in SCVMM, you have the option of specifying a RunAs account to join the resultant VM to a domain. This works fine when deploying a VM from SCVMM. However, if you're using SCVMM as a backbone for Lab Management, and use Microsoft Test Manager (MTM) to Import the template and deploy the VM, you get an error.
It seems that the RunAs account information does not flow from SCVMM to Lab Manager when you import the template. In order to be able to automatically join a deployed VM to a domain, you will need to hand-type the account into every template you create in SCVMM. This is fine for a small Lab Management environment, but can get annoying when you're creating hundreds of templates (which we may or may not have to do).
So, my question is this: Is this a known limitation, an overlooked functionality, or a "feature"? I understand that MTM is extremely limited in its functionality when compared to SCVMM (for obvious reasons relating to scope), but would allowing for the RunAs account to be used in MTM really pose such a risk? Would it be difficult to implement such functionality? Is it a planned addition in R2 (or whatever the next iteration will be)?
On a related note, I tried using Powershell to strip all of our current domain-joined templates of their RunAs accounts and update the DomainJoin accounts, but it didn't take. I don't remember the exact command, but I captured credentials in $cred and used Set-SCVMTemplate with the -DomainJoinCredential switch, passing it the $cred variable. Has anyone used this command successfully?