locked
SCCM 2012 migrated deployment status. RRS feed

  • Question

  • Hi All,

    we have migrated packages to SCCM 2007 to SCCM 2012 (No Advertisments migrated to SCCM 2012. In future if we create the new deployment in SCCM 2012 for the migrated packages.what is the behaviour on any of the machine which the package already installed?

    The package will re-run on the machine or it will ignore (due to Advertisment history)?

    Friday, May 20, 2016 8:52 AM

Answers

  • The execution history regkey will still exist on the Client ... I don't have access to my lab right, so double check yourself if the advertisementID is also stored (or only PkgID:ProgramName). I *guess* (so verify that first) that it won't re-run if (!) the advertisementID is not stored in the registry and if the re-run behavior is set accordingly.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 20, 2016 9:29 AM

All replies

  • The execution history regkey will still exist on the Client ... I don't have access to my lab right, so double check yourself if the advertisementID is also stored (or only PkgID:ProgramName). I *guess* (so verify that first) that it won't re-run if (!) the advertisementID is not stored in the registry and if the re-run behavior is set accordingly.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 20, 2016 9:29 AM
  • Thanks Torsten.

    I hope advertisementID will not maintain because if we migrate any of Advertisment from SCCM 2007 to SCCM 2012 the deployment ID will not same(ID will be new site code based). if its maintain the advertisementID , as soon as its migrated based on program rerun behaviour it should re-run.

    I will build test lab and test based on your suggestion


    Friday, May 20, 2016 4:45 PM
  • "as soon as its migrated based on program rerun behaviour it should re-run"

    This is only true if as Torsten pointed out the program is set to always rerun.


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

    Saturday, May 21, 2016 2:38 AM
  • Thanks Jason.

    My query regarding the migrated package and new deployment in SCCM 2012.

    we have migrated packages to SCCM 2007 to SCCM 2012 (No Advertisments migrated to SCCM 2012. In future if we create the new deployment in SCCM 2012 for the migrated packages.what is the behaviour on any of the machine which the package already installed?

    The package will re-run on the machine or it will ignore (due to Advertisment history)?

    Saturday, May 21, 2016 8:59 AM
  • It's the same thing that we've already answered multiple times in this thread: it depends upon the re-run settings of your program.

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

    Saturday, May 21, 2016 5:46 PM
  • Thanks Jason. 

    I have created the new deployment for migrated package and set the program rerun behaviour to "Rerun if failed in previous attempt". will the new deployment re-trigger on the machines which the package already installed?

    Monday, May 23, 2016 12:51 AM
  • Only if the previous deployment failed exactly as the retry behavior specifies.

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

    Monday, May 23, 2016 1:26 AM
  • Thanks Jason.

    As per your update whether its new deployment in SCCM 2012 or deployment migrated from SCCM 2007 based on the program rerun behaviour or previous deployment status it will trigger the installation?

    please correct me if above statement wrong.

    Wednesday, May 25, 2016 5:21 AM
  • Any one pls confirm the above query.

    Thanks in Advance.

    Friday, May 27, 2016 1:18 AM
  • I have no idea what you are asking. The options are quite clear and the status of the deployment is set in the client's registry.

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

    Friday, May 27, 2016 2:16 AM
  • In the registry we can see the respective package - program ID and status.

    Package installation success in SCCM 2007 but now i have created the new deployment for migrated package in SCCM 2012 and deployed to collection. Couple of collection member already installed the package (As part of SCCM 2007)- Here will re-run the package again on those installed machines(program rerun behaviour not as always rerun)?


    Friday, May 27, 2016 6:42 AM
  • See my assumption above. Plus: it seems as if you already got both (CM07 and CM12) up and running side by side. You can easily test that yourself with a single test machine.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 27, 2016 7:15 AM