locked
SMS 2003 to SCCM 2007: DPs Migration RRS feed

  • Question

  • Hello !!!

    In a Side by Side Migration..., Is there any way to migrate DP (with their packages) from SMS 2003 to SCCM 2007 without forward (resend) the packages ???
    Saturday, November 14, 2009 7:16 AM

Answers

  • Keeping the same package id is irrelevant to the original question at hand.
    You cannot prestage distribution points with content, whether you keep the same package id's or not does not matter to answer that question.
    Pre-staging is a branch distribution point feature only.

    You can request the feature on connect.microsoft.com, as plenty of people have done before you.
    The sad and simple truth is that this is not possible for standard distribution points.
    "Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
    Monday, November 16, 2009 6:59 PM

All replies

  • What you are trying todo is called prestaging a dp, and in sccm 2007 that is only supported for branch distribution points.
    So the answer is, it depends, are you willing to replace your sms 2003 dp's with sccm 2007 branch dp's?
    "Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
    Saturday, November 14, 2009 7:56 PM
  • No...
    I want to use "Standard DP"....

    Sunday, November 15, 2009 12:08 PM
  • New site => new sitecode => new IDs (= new package IDs) => can't use the old compressed files.
    Monday, November 16, 2009 7:50 AM
  • New site => new sitecode ....OK
    But..I've developed a tool to migrate packages & programs from one site to another site (keeping the package ID). By this way the client don't reinstall the SW..
     
    I would like to migrate DPs without sending the SW again...
    Monday, November 16, 2009 3:19 PM
  • Hi,

    I have seen migration scenarios where same package id + advertisement ID still causes a package reinstallation on the clients. This happens when the advertisement is configured to always rerun.

    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Monday, November 16, 2009 3:54 PM
  • Of course...
    But you can configure to re-run only if the previous advertisement failed......
    Monday, November 16, 2009 4:01 PM
  • that's true, but it's something I have seen causing problems in a few projects :-)
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Monday, November 16, 2009 4:59 PM
  • Why???

    Migrate PackageID fron one site to another site with difference site code is similar to:  have a central site and another child primary site, and break after the relation...
    The package of parent side are now in the child site but keep the parent site code.....


    Monday, November 16, 2009 6:12 PM
  • Keeping the same package id is irrelevant to the original question at hand.
    You cannot prestage distribution points with content, whether you keep the same package id's or not does not matter to answer that question.
    Pre-staging is a branch distribution point feature only.

    You can request the feature on connect.microsoft.com, as plenty of people have done before you.
    The sad and simple truth is that this is not possible for standard distribution points.
    "Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
    Monday, November 16, 2009 6:59 PM
  • A Little Tip to migrate a DP in a "side by side" migration (no secundary site, only one primary site with several DPs..)

    1) Delete DP (\\server1\smspkg) in old site (no packages...)
    2) Create DP in new site (\\server1\smspkg) and wait until the DP has been created...
    3) Configure the new site with these "software distribution settings": retries=1, retry=1
    4) Don't share \\server1\smspkg
    5) Copy packages (these packages has been migrated with the same Package ID and Source Path...) and wait to failed status
    6) Share \\server1\smspkg
    7) Update packages (SCCM will check that the package's content is the same in all DPS and don't copy anything...Only check..)

    Advantage: No necessary send packages again...
    Disadvantage: You must wait to sccm check all packages in all DPs...


    Note: SCCM SP2 doesn't support this. There is a bug because SCCM don't respect "software distribution settings". We've opened a case with microsoft and they are making a hotfix for SCCM SP2


    Regards

    Monday, November 16, 2009 7:48 PM
  • You cannot prestage distribution points with content [...]
    Of course you're right. I was thinking of sites and the question was actually DP (site system) related.
    Monday, November 16, 2009 10:41 PM