- If they are going to use the same name, then yes. If not, then no.
- If they use the same name, there's no need to update anything. If they use a different name, then the clients simply need to download the latest machine policy containing the new CMGs info.
- No, but as noted, they will need to download a new policy if a new CMG name is used.
- No.
- You should always use a cert from a public CA and CName record in your DNS. If you didn't use a CName, you will 100% have to change the name because VM Scale Sets have a different DNS name than VMs in the classic cloud service.
Migrate from CMG Cloud Classic to CMG VM Sets
Hey Everyone!
I have been using CMG Cloud Service (Classic) and SCCM 2107 fine for quite some time but now I understand that CMG Cloud Service is now dead and I should use Virtual Machine Sets .
I would like to take the opportunity to move the service to another Azure Subscription.
I have found some docs online (here and here and here) that can help with the creation of the VM Sets feature however I have a few more questions please:
1. Should I delete the current service before creating the new service as VM Sets?
2. How will the clients at home be updated to look for the new endpoint?
3. Do I need to reconfigure the clients?
4. Is there any networking required on the Azure Subscription VM Net to allow for the new VM Sets?
5. Can I use my public certificate instead of my PKI (Root CA cert)?
Anything else I should be aware of or if anyone has a better step-by-step or YouTube guide that would be awesome?
Many Thanks
1 answer
Sort by: Most helpful
-
Jason Sandys 31,161 Reputation points Microsoft Employee
2021-10-25T03:10:54.97+00:00