Hi,
I just started a new job. Now I have an outdated SCCM 2303 environment with a single primary site server on Server 2012R2 and SQL 2012 I have to deal with.Management wants me to create a new site with a remote SQL server. Updating the old systems is not allowed. Don't ask.
The plan is to use site-by-site migration to get apps, TSs, collections... to the new site and updating it to 2409 later.
I did set up a test environment for that: a source site SCCM 2303 on 2012 and a target site 2303 on 2019 (2022 is not allowed) and a remote SQL server 2019.All works fine.
But starting the migration caused some trouble.
The gathering works. But when I create a migration job, I only see collections, boundaries and boundary groups. No apps, or anything else.
The migmctrl.log (attached) shows e.g.:
Start syncing #MIG_Entity.
Query against Legacy Site...
Query completed, 5 record(s) merged to target table...
Query completed, 0 record(s) merged to target table...
Query completed, 5 record(s) merged to target table...
5/5 records copied for #MIG_Entity
Synced one batch.
5 records in #MIG_Entity Synced.
The target site's DB table "MIG_Entity" contains all objects from the source site.
All objects that are NOT available in the migration job have a 1 in the column "IsDeleted". So, something makes the decision which data is relevant and which isn't.
The view "v_MIG_Entities" only contains data that was NOT marked as "IsDeleted".
Does anyone have an idea what's happening here?
Thanks, Alex
I just started a new job. Now I have an outdated SCCM 2303 environment with a single primary site server on Server 2012R2 and SQL 2012 I have to deal with.Management wants me to create a new site with a remote SQL server. Updating the old systems is not allowed. Don't ask.
The plan is to use site-by-site migration to get apps, TSs, collections... to the new site and updating it to 2409 later.
I did set up a test environment for that: a source site SCCM 2303 on 2012 and a target site 2303 on 2019 (2022 is not allowed) and a remote SQL server 2019.All works fine.
But starting the migration caused some trouble.
The gathering works. But when I create a migration job, I only see collections, boundaries and boundary groups. No apps, or anything else.
The migmctrl.log (attached) shows e.g.:
Start syncing #MIG_Entity.
Query against Legacy Site...
Query completed, 5 record(s) merged to target table...
Query completed, 0 record(s) merged to target table...
Query completed, 5 record(s) merged to target table...
5/5 records copied for #MIG_Entity
Synced one batch.
5 records in #MIG_Entity Synced.
The target site's DB table "MIG_Entity" contains all objects from the source site.
All objects that are NOT available in the migration job have a 1 in the column "IsDeleted". So, something makes the decision which data is relevant and which isn't.
The view "v_MIG_Entities" only contains data that was NOT marked as "IsDeleted".
Does anyone have an idea what's happening here?
Thanks, Alex
