locked
Setting SCCM Dev Environment RRS feed

  • Question

  • We currently have a very outdated SCCM 2012 SP1 in prod. I will create a Dev environment so that I can implement 1610 or 1702. I will create a Primary point, secondary point, a distribution point and install Windows 10 . I was thinking that as long as I don't have any overlapping boundaries and AD system discovery OUs, it should be non-impactful. Is there any concern having 2 primary points writing to the same System Management AD container? Once familiar with the 1610/1702, I will upgrade prod, I was thinking that due to the big gap in the version, I would simply build out a new SCCM 1702 Prod environment and update the client agents. Also, are there any other gotchas and pitfalls I should be watching for?

    Much thanks.

    Sunday, April 9, 2017 10:58 PM

Answers

  • > "Is there any concern having 2 primary points writing to the same System Management AD container? "

    No, this is perfectly fine.

    Also, they are called primary "sites" and secondary "sites". The word "point" is usually used for the individual site roles.

    > "I was thinking that due to the big gap in the version, I would simply build out a new SCCM 1702 Prod environment and update the client agents."

    Why? This would cause you to lose all of your configuration. There's no need to do this. You can upgrade directly from SP1 to 1606 using the baseline media.


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

    • Proposed as answer by Frank Dong Monday, April 10, 2017 6:26 AM
    • Marked as answer by Goku777 Monday, April 10, 2017 3:10 PM
    Monday, April 10, 2017 2:31 AM

All replies

  • > "Is there any concern having 2 primary points writing to the same System Management AD container? "

    No, this is perfectly fine.

    Also, they are called primary "sites" and secondary "sites". The word "point" is usually used for the individual site roles.

    > "I was thinking that due to the big gap in the version, I would simply build out a new SCCM 1702 Prod environment and update the client agents."

    Why? This would cause you to lose all of your configuration. There's no need to do this. You can upgrade directly from SP1 to 1606 using the baseline media.


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

    • Proposed as answer by Frank Dong Monday, April 10, 2017 6:26 AM
    • Marked as answer by Goku777 Monday, April 10, 2017 3:10 PM
    Monday, April 10, 2017 2:31 AM
  • It's supported to upgrade from SCCM 2012 sp1 to Current branch 1606 using baseline media.

    https://docs.microsoft.com/en-us/sccm/core/servers/manage/updates#bkmk_Baselines

    Which is a better option as you'll save a lot of work.

    Baseline download:

    From MSDN:

    https://msdn.microsoft.com/en-us/subscriptions/hh442898.aspx

    From EvalCenter:

    https://www.microsoft.com/en-us/evalcenter/

    Download from VLSC:

    https://www.microsoft.com/Licensing/servicecenter/default.aspx


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

    Monday, April 10, 2017 6:32 AM
  • > "Is there any concern having 2 primary points writing to the same System Management AD container? "

    No, this is perfectly fine.

    Also, they are called primary "sites" and secondary "sites". The word "point" is usually used for the individual site roles.

    > "I was thinking that due to the big gap in the version, I would simply build out a new SCCM 1702 Prod environment and update the client agents."

    Why? This would cause you to lose all of your configuration. There's no need to do this. You can upgrade directly from SP1 to 1606 using the baseline media.


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

    Thanks for the advice. The other reason I wanted to build a separate production environment instead of upgrading is because we're still running 2008 R2 with a 40 GB hard drive on our current prod environment. I understand that SCCM does not respond well to having the hard expanded.
    Monday, April 10, 2017 10:12 AM
  • I understand that SCCM does not respond well to having the hard expanded.
    I expand the VHD all the time, so..... I'm, not sure where you heard that.

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Monday, April 10, 2017 12:16 PM
  • Concur with Garth -- expanding a VHD is not a problem.

    Alternatively, if you don't want to perform an in-place OS upgrade, use a ConfigMgr site backup and restore to move the site to a new VM without having to migrate anything.


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

    Monday, April 10, 2017 4:06 PM