Migration Job Has Failed On SCCM 2012 r2 RRS feed

  • Question

  • Dears,

    I try to migrate my old endpoint update package from SCCM 2012 on server 2008 r2 to SCCM 2012 r2 on Windows 2012 r2. I have connect the source hierarchy and made created migration job between both old and new SCCM.  but when I create new migration job the migration failed due to this error " the destination site has not yet synchronized software update with unique id 277".

    My task is I want to migrate Endpoint package with all configuration to the new server SCCM 2012 r2. Kindly any help.

    Best Regards.

    Wednesday, March 23, 2016 7:17 PM

All replies

  • Why would you migrate this in the first place? It's a package with all of what, 8-10 updates in it. Just create a new one.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, March 23, 2016 8:04 PM
  • Dear Sir,

    To explain the error, please take a look below link, you'll get the answer:


    Strongly agree with Jason's. Create a new one will not have many work to do. Or is there any reason that need to use migration scenario?

    Best regards


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, March 24, 2016 6:33 AM
  • Dear Jason, in old SCCM we already configured Endpoint package and deployed to user machines, so in new SCCM 2012 r2 I have to migrate old endpoint and windows updates package to keep continue send daily or weekly new updates to machines. But if I create new Endpoint package and windows package maybe it will affect old windows updates and endpoint update package to user machines. What do you think? If I configure new endpoint and windows update package is those new packages will continue sending new updates to machines?
    Thursday, March 24, 2016 8:22 AM
  • Dear Frank thanks, I already explained the reason for Jason why I need migrate Endpoint and windows update packages. What it is your idea?
    Thursday, March 24, 2016 8:23 AM
  • Update packages don't send anything. Clients simply download content from any available update package. Thus, creating a new package in the new site with the same content will work fine.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Frank Dong Tuesday, April 5, 2016 8:35 AM
    Thursday, March 24, 2016 1:04 PM
  • Thanks Jason. But what about old machines which they already have CCM packages for old SCCM? Are they taken new CCM packages from new SCCM 2012 r2 again? or is the updates compatible with old CCM package in C:\Windows?
    • Edited by Dana.Kadi Monday, March 28, 2016 5:59 AM New info
    Thursday, March 24, 2016 8:39 PM