Oct 01 2020 11:15 AM
We're migrating our CM infrastructure to Azure, as we make progress on that we have both an OnPrem instance running and an Azure instance, does any one know of a way to keep task sequences in sync between the two?
Thanks,
Jamie
Oct 02 2020 01:39 AM
@Jamie Hosley If you're actually building a new site in Azure and migrating everything to that, you should use the built-in migration functionality. Check Migrate data between hierarchies in Configuration Manager to get started. However, why wouldn't you just move your current site to Azure using the procedure described in Extend and migrate on-premises site to Microsoft Azure ?
Oct 02 2020 11:46 AM
@Michiel Overweel so a migration was done to get the Azure instance configured initially, but there are still parts being looked at by our infrastructure before the final move to it, during the interim then there is OSD TS dev happening on the on-prem side because it's still handling production, so the OSD team was looking to see if there were any option to keep it in sync, or even something as simple as say copy/paste between the two. We're a 500K client org spread across the country so the cut to Azure is being handled in more of a staged approach, and with other work like CMG etc also happening we're sort of existing in an in-between state right now where on-prem work continues and Azure work follows.
Oct 02 2020 11:56 AM
Oct 05 2020 07:09 AM
Solution@Jamie Hosley If you're still editing objects (in this case: task sequences) in the source hierarchy, then your migration isn't finished yet. You can use Objects modified after migration jobs to migrate objects that were migrated previously, but that were updated in the source hierarchy after their initial migration. See Plan a migration job strategy in Configuration Manager: Plan for previously migrated object migratio... for details.
Oct 07 2020 05:03 AM
Oct 05 2020 07:09 AM
Solution@Jamie Hosley If you're still editing objects (in this case: task sequences) in the source hierarchy, then your migration isn't finished yet. You can use Objects modified after migration jobs to migrate objects that were migrated previously, but that were updated in the source hierarchy after their initial migration. See Plan a migration job strategy in Configuration Manager: Plan for previously migrated object migratio... for details.