Is there any way to associate a VM with a Service Template _after_ the VM is created?
A common problem I'm running into is a sort of "chicken and the egg" scenario where newly migrated resources to Hyper-V SCVMM already exist yet I'd still like to be able to create services and be able to set the stage for "going forward" configuration for said services. Simple yet common example would be ADDS: everyone has domain controllers and it would be nice to create a service template and join the machines into it ... then be able to control with certainty certain aspects of the farm.
Is there any way to join an existing VM to a service? Or is the only way to completely destroy your old VMs and "scale out" a new service? Basically I'm thinking of something similar:
1. Create a very simple Service template for a service (almost no requirements, just stand alone mid their boxes)
2. Join all machines belonging to the service to it.
3. Work with the client to create revisions to slowly add more and more "completeness" to the service over time so eventually they can achieve a solid one-click scale out.
If we have to create every service from scratch it seems like a bit of an oversight making the feature a bit too daunting to use as every service basically needs to be green-fielded then migrated over the top of existing resources to be leveraged.