Search the Community

I will give background about the scenario, we are in the process of Side-by-Side Migration from SCCM 2012 R2 to SCCM 1906 CB. As per the guideline, I have configured the products classification in the new site identical like the old site and synchronized. Now I am at the phase of the migrating Applications, Collections, ADR, Software Update Package and its deployment. For E.g.: I am trying to migrate Office 2010 Software Update Package and its deployment and it’s all associated collection and rules from SCCM 2012 R2 site to SCCM 1906 Site. Migration is failing and the error was that the destination site doesn’t have software updates with unique id: b2f2052b-d652-4895-bc2e-c5105acadb00, 10756e43-6c49-45c1-a897-12b4e89fdc11 Screenshot for your reference below as i couldnt paste it here I have given below a details screenshot of the error from the Migration manager log: The migration manager is complaining that file lib id b2f2052b-d652-4895-bc2e-c5105acadb00 doesn’t exist in the destination hierarchy so it couldn’t move the Office 2010 package from SCCM 2012 to SCCM 1906. I was looking for this update in the all software update group list. I was even unable to find that software update even in the SCCM 2012 R2 Hierarchy, which means that content_id is invalid and stale. It needs to be removed from the package id so the migration manager won’t look into it during migration Below is the screenshot for location the where all the software update deployment package are: When I open this package id, I was able to find all the references of all software update in it: screenshot given below for your reference: If you look at the screenshot above, the Office software deployment package has the reference of a software member (b2f2052b-d652-4895-bc2e-c5105acadb00) in it, so the migration manager is looking for it the new site. However i have checked Microsoft Catalog to see if the above unique_id is what software update, but even it is not in Microsoft Catalog. I think it is a stale unique Id which needs to be removed from the package. Due to the reference still exist in the Package, the migration manager is not able to migrate the package from SCCM 2012 R2 to SCCM 1906 CB. PS: I have used content library clean-up tool but it freed up only the orphaned contents in the DP. But it didn't remove the stale references from the Package. Also I have validated the package and even redistributed the content again to the DP to see if it fixes the issue. I used t-sql query to find the article Id and title information from in the SQL db, but there is no information. can you guys help me to fix the issue. The main agenda is to migrate all contents from current hierarchy to the new hierarchy.

Hi. I am the sole SCCM administrator for a small company. The current site is running Config Manager 2012 R2, on a Windows Server 2008 R2 VM. It's a simple hierarchy, consisting of one primary site, all managed from a single server, and 3 distribution points. SQL is hosted on a separate cluster. This was all set up long before I joined the company. Now that I'm wishing to upgrade to current branch, I've also decided to put it on a new Windows Server 2016 VM. I could do a side-by-side migration, but am quite tempted to start again from scratch, with a clean slate. My plan is to leave the current site up and running, while I set up the new one, giving me ample time to configure it all, create the deployments, distribute content, etc. Once it's ready, I can push-deploy the new client, and eventually take down the old site. I've already chosen a new site code and name, and new names for all the servers, so there should be no conflicts there. The only thing I'm a little uncertain about at present, is what's going to happen in the System Management container, when I set up the new site. Will its site code and name be added alongside the current one, or will it over-write? In either casem will the clients get confused (if not current ones, then new builds)? Should I maybe not give the new site server permissions on the container, and instead get it to publish to ADDS when everything's ready? As a bonus question, I thought I might as well set up the new SQL Server 2016 database for it, on the same cluster as the current one (since we have a cluster already in place, I prefer to use it). I thought I could just install SQL 2016 on the cluster, set up a new instance, and point the new site at that, but are there any potential pitfalls I'm overlooking / anything else I need to consider? Any guidance would be much appreciated. Thank you.

I have been playing with the side by side migration tool in sccm 2012 and have a few questions. I built a test lab (lab.local 1X DC - win2008r2 running dhcp and dns 1X sccm 2007 sp2 r3 server 1X sccm 2012 r2 server I then went and configured sccm 2007 to do the following, which all work fine OSD , build, capture, patch at build Application delivery (single flash player application) Then built an sccm 2012r2 server (local sql etc) Ran the migration tool and specified the source hierarchy. This all worked well, found items to migrate etc. I then migrated various test bits, boundary, collection, and package. I noticed my package had migrated by the package source was still located on the sccm 2007 server. If I were to decommission the sccm 2007 server, this would then break. Do I need to manually recreate a package source, manually populate (copy) the source files / applications / packages across. - Then migrate and manually adjust the package source on the sccm 2012 server to point to the new package source and redistribute ? Any experience or pointers would be nice, as the tool itself looks to be really useful. Just wondering if I have missed something ?? Any pointers appreciated ! Regards WAZZIE

Hello, First I would like to say how wonderful these forums are. This community has already helped me so much that I had to finally sign up. I look forward to participating in discussions moving forward. Today I have a question of my own. I have worked with SCCM for a few years now doing OSD and package deployment and just began building my first SCCM 2007 server at a new company. I took a class dedicated to SCCM 2007 and thought I asked all the right questions but want to verify my migration from SMS 2003 to SCCM 2007 is sound. All Windows XP machines are deployed and managed by SMS2003 at a single AD site. My plan has been to deploy Windows 7 and thus SCCM 2007 configmgr through SCCM2007. As we migrate to Win7 so will the client agents. So I will NOT be upgrading the SMS2003 clients, and the SMS server is NOT a child of the SCCM server (I don’t need any data from it). Both servers have a different site code so as far as I am concerned they are two completely separate environments (which is what I prefer). The only issue I could see is both servers share the same site boundary. The schema in AD has been extended for both SMS and SCCM. I only push the client out during the OSD deployment so they do get the correct site code automatically. The clients get approved automatically (I have had an issue with one or two in testing so far). Will SMS or SCCM clients have unstable communication? It will be difficult to create separate sites as we need to deploy Win7 to test users in different subnets that will overlap with SMS clients. I would prefer not to migrate the winXP machines to the SMS 2007 server. The entire migration should be complete in 6 months. Thank you for your time, Rick