Jump to content


Recommended Posts

Dear Experts,

Currently Managing the infra with 5600 End Points (1 Primary, 22 DP's) with Windows 7 Management. We are looking to upgrade to Current Branch 1702 and So on.

Prior to the Deployment, Preferred to Create 1 Test Environment.

1227509

We have already 1 PROD Environment. SYS Management Container is given with Permission (Full Control) for Primary Site server (Host name) of the Machine.

If we grant the access for System Management Container with Full Control (For TEST Environment) server. It will be creating automatically with New Container (Right below to SMS-MP) right?

Also, Preferred to get advice from you, about there will not be any impact with existing Containers.

For added safer side, Shall I create another folder right below to System Management (Container) as TEST to progress further.

Please share your advice

Share this post


Link to post
Share on other sites

you should separate your test environment from production entirely, i.e. use a separate test vm environment with separate AD, SCCM, etc virtual machines that you test with, I wouldn't mix or recommend using a test lab in production

 

here's a guide to setup your test environment

 

 

Share this post


Link to post
Share on other sites

Dear Admin,

I feel so happy to receive your response. You are the real helping person for many people like me. No one forget your post/materials..:)

Regarding my environment:

I do not get chance to create new AD, DNS in my Environment. So Preferred to use the PROD Domain Controller.

However, the following plan is in my check list. Happy to adopt your idea if you feel the following is not good..Please advice.

1. Creating Separate TEST service account for all Installation activities

2. Creating Sepereate Test AD Security Group's

3. Assigning the System Management Container - Delegate Permission for the TEST AD Security Group Only. In PROD We are having the Site Code as OLY, and plan to use the Site code as PPT or DEV for Test Environment

4. During the Boundary group creation, will not use the option use this boundary group for Site assignment

If this Precautions made, Is this Okay.

I Would like to follow your advice..:)

 

Share this post


Link to post
Share on other sites

once again, don't create a test environment in production, you'll regret it later.

Get a laptop or desktop with 16GB or ram and 500GB ssd and install AD and SCCM  virtual machines on that, can you not do that instead ?

 

if you use the production environment to do your test environment then all i can say is read what i said above

 

cheers

niall

Share this post


Link to post
Share on other sites

Dear Admin,

I Would like to hear some additional feedback from you on this.

Currently my infrastructure is having the following

Windows Server 2008 R2 - AD + DNS

Windows Server 2008 R2  - DHCP

Windows Server 2008 R2 - SCCM 2012 SP2 (5.00.8239.1000) with SQL 2008 R2 Standard, with 21 DP's *All DP's are Windows Server 2008 R2 Standard*

My Windows Team is not aware of the status of Schema Level or OS Patch Level. So they are not looking or allowing me to install the SCCM on Test Environment to Upgrade from (SCCM 2012 SP2 to SCCM CB V1702)

Hence the possible approach arrived for Testing as follows:

1. With help of Network - Creating an isolated Subnet, VLAN in the Data Center Level 

2. AD + DNS, DHCP, SCCM Primary Site (Clone, and getting moved with in the Isolated subnet VLAN Range)

3. The Test Environment will be also having few Clients (Which is with in the isolated subnet)

4.Upgrade activity starts with Windows SERVER 2008 to 2012, SQL 2008 to SQL 2012, Upgrade the SCCM 2012 SP2 to SCCM CB V1702, TEST DP Upgrade on one of the Remote Site (With in the Same IP Subnet Range)

5. Install Client *Client Upgrade from SCCM 2012 SP2 to SCCM 2012 CB V1702*

Based on the Testing and Validation, We will perform the activity on PROD

Any feedback/inputs from you Please...

Share this post


Link to post
Share on other sites

you should not upgrade the server os until SCCM can support it, and that means SCCM needs to be at version 1602 or later
 

When you use Configuration Manager version 1602 or later, it is also supported to upgrade Windows Server 2008 R2 to Windows Server 2012 R2 (See additional details.

more details below https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure#bkmk_from2008r2

 

Upgrade Windows Server 2008 R2 to Windows Server 2012 R2

This operating system upgrade scenario has the following conditions:

Before upgrade:

  • Uninstall WSUS 3.2.
    Before you upgrade a server operating system to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server. For information about this critical step, see the New and changed functionality section in Windows Server Update Services Overview in the Windows Server documentation.

After upgrade:

  • Ensure the Windows Deployment Service is started and running for the following site system roles (this service is stopped during upgrade):

    • Site server
    • Management point
    • Application Catalog web service point
    • Application Catalog website point
  • Ensure the Windows Process Activation and WWW/W3svc services are enabled, set for automatic start, and running for the following site system roles (these services are disabled during upgrade):

    • Site server
    • Management point
    • Application Catalog web service point
    • Application Catalog website point
  • Ensure each server that hosts a site system role continues to meet all of perquisites for site system roles that run on that server. For example, you might need to reinstall BITS, WSUS, or configure specific settings for IIS.

    After restoring any missing prerequisites, restart the server one more time to ensure services are started and operational.

Unsupported upgrade scenarios

The following Windows Server upgrade scenarios are commonly asked about, but not supported by Configuration Manager:

  • Windows Server 2008 to Windows Server 2012 or later
  • Windows Server 2008 R2 to Windows Server 2012

 

Share this post


Link to post
Share on other sites

5 minutes ago, anyweb said:

you should not upgrade the server os until SCCM can support it, and that means SCCM needs to be at version 1602 or later
 


When you use Configuration Manager version 1602 or later, it is also supported to upgrade Windows Server 2008 R2 to Windows Server 2012 R2 (See additional details.

more details below https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure#bkmk_from2008r2

 

Upgrade Windows Server 2008 R2 to Windows Server 2012 R2

This operating system upgrade scenario has the following conditions:

Before upgrade:

  • Uninstall WSUS 3.2.
    Before you upgrade a server operating system to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server. For information about this critical step, see the New and changed functionality section in Windows Server Update Services Overview in the Windows Server documentation.

After upgrade:

  • Ensure the Windows Deployment Service is started and running for the following site system roles (this service is stopped during upgrade):

    • Site server
    • Management point
    • Application Catalog web service point
    • Application Catalog website point
  • Ensure the Windows Process Activation and WWW/W3svc services are enabled, set for automatic start, and running for the following site system roles (these services are disabled during upgrade):

    • Site server
    • Management point
    • Application Catalog web service point
    • Application Catalog website point
  • Ensure each server that hosts a site system role continues to meet all of perquisites for site system roles that run on that server. For example, you might need to reinstall BITS, WSUS, or configure specific settings for IIS.

    After restoring any missing prerequisites, restart the server one more time to ensure services are started and operational.

Unsupported upgrade scenarios

The following Windows Server upgrade scenarios are commonly asked about, but not supported by Configuration Manager:

  • Windows Server 2008 to Windows Server 2012 or later
  • Windows Server 2008 R2 to Windows Server 2012

 

Dear Admin,

 

Thank You again for your teachings.

 

Please, let me know - Am I giving the correct plan and Please correct me If I Wrong.

1. At Present the Infrastructure is with Windows Server 2008 R2 Standard (Included with SQL 2008 R2 Standard) with 22 DP's (Windows Server 2008 R2 Standard) with SCCM 2012 SP2 for Supporting 5000 + Clients

 

2. At Present, We are looking forward to upgrade the SCCM Environment to Current Branch. The reason for upgrading to Current Branch is to support the Windows 10 Operating System upgrade and deployment.

 

3. If it is Windows 10 Operating System, the Possible upgrade is needed with SCCM CB V1702 for Supporting Windows 10 Clients with Version 1709

 

Hence, We have Plan to upgrade the Operating System, SQL Upgrade.

However, As per your article - It is Referred by you...

 

1. I need to upgrade the Configuration Manager upgrade from SCCM 2012 SP2 to SCCM 2012 Version 1602

2. Then, I need to upgrade the Operating System from Windows Server 2008 R2 to Windows Server 2012 R2 *Along with SQL upgrade from SQL 2008 R2 to SQL 2012* 

3. Once the upgrade is completed, Need to upgrade the Configuration Manager from Version 1602 to V1702 and So on..

 

Am I correct?

 

Earlier, I have Posted the Query on MS Article, got confused.

 

I Would request you to guide me the upgrade approach based on my Infrastructure. So that, I will progress in TEST Environment and move to PROD.

 

Please forgive if any silly questions

 

Regards,

Veera

 

Share this post


Link to post
Share on other sites

Dear Admin,

 

I Understand now, that as per my Infra

 

It is required to upgrade my SCCM Environment to SCCM CB V1602 as Intial Level

Then

I must upgrade the Operating System from Windows Server 2008 to Windows Server 2012, SQL upgrade using 

https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure#bkmk_from2008r2

Then, I must Upgrade the Configuration Manager CB V1602 to V1702 and So on.

My Question now:

If the Current Branch is upgraded to CB V1602 from SCCM 2012 SP2? If I Install the Role called SERVICE CONNECTION POINT

With that help of Service Connection Point? DO I get chance to upgrade from SCCM CB V1602 to V1702 Or Do I need to download the Copy of SCCM CB V1702 ISO File and Install it (For Upgrade). Please Suggest?

Share this post


Link to post
Share on other sites

By Referring the following. Is that upgrade is Possible from 

SCCM 2012 SP2 to SCCM CB V1606 (With Windows Server 2008 R2 + SQL 2008 R2 STD)

Windows SERVER 2008 Upgrade to Windows Server 2012

SQL 2008 STD upgrade to SQL 2012

SCCM CB V1606, Upgrade to SCCM CB V1702

After that using Service Connection Point further upgrade's. Is this Okay?

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

 

 

3.png

Share this post


Link to post
Share on other sites

Dear Admin,

This is the final Approach, Which is planned based on the recommendations/suggestions from MS Tech-net Forums.

However, feel to get advice from you, before progressing.

As I am having WS 2008 R2 STD with SQL 2008 R2 STD, Will upgrade to SCCM CB V1606 as per the recommendations. (SCCM 2012 SP2 to SCCM CB V1606 Using Baseline0

After Completing, the SCCM CB V1606 Upgrade,  Will upgrade 

Operating System, SQL, CB V1606 to Possible Version, DP Upgrade and Client upgrade.

All this is to Satisfy my environment to equip to Windows 10 OS Deployment, Upgrade, Windows 10 Life Cycle Management (Windows 10 V1709)

Please Suggest...

 

Share this post


Link to post
Share on other sites

you can upgrade from SCCM 2012 SP2 directly to the 1702 CB baseline.

 

In-place upgrade paths

Upgrade to version 1702
When you have version 1702 baseline media, you can upgrade the following to a fully licensed version of System Center Configuration Manager version 1702:

  • An evaluation install of System Center Configuration Manager version 1702
  • System Center 2012 Configuration Manager with Service Pack 1
  • System Center 2012 Configuration Manager with Service Pack 2
  • System Center 2012 R2 Configuration Manager
  • System Center 2012 R2 Configuration Manager with Service Pack 1

Once done with the upgrade to 1702, you can upgrade the Operating System of the server.

Share this post


Link to post
Share on other sites

Thank You Admin,

But my Current Infra is running with Windows Server 2008 R2 along with SQL 2008 R2 as Single Standalone Primary Site with 20+ DP.

All Distribution Points are running with Windows Server 2008 R2 STD.

So, I believe the Upgrade Windows Server and SQL Server is needed to reach SCCM CBV1710 from SCCM 2012 SP2. However, We Preferred to retain the Version of Windows Server 2008 R2 STD for all Distribution Points

https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

image.png.b736d8ede933fb8b0d3a726d73285f35.png

Please suggest..

Share this post


Link to post
Share on other sites

Yes Admin,

Thank You again, for your great efforts and educating me.

Do you think, any other area that I need to focus.

With Regards to HW Sizing., On VM

AS-IS Infra

SCCM 2012 SP2 (5.00.8239.1000)

Pre Requisite's:

Processor  4, Core 8, RAM 32 GB

Windows Server 2008 R2 STD (Version 6.1/Winver 7600 SP1)

SQL 2008 R2 SP1 (10.50.2811)

MDT (6.3.8330.1000)

ADK (10.0.26624)

SCUP 2011 (5.00.1727.0000)

TO-BE Infra with Phase I from SCCM 2012 SP2 to SCCM CB V1606

Processor  4, Core 8, RAM 32 GB

Windows Server 2008 R2 STD (Version 6.1/Winver 7600 SP1)

SQL 2008 R2 SP1 (10.50.2811)

Retaining the DP (With Same Server Level as Windows Server 2008 R2 SP1)

ADK  - Do we need to upgrade << Please suggest >>

SCUP - Do we need to upgrade << Please suggest >>

Running the System Center Upgrade Configuration Manger V1606 using Baseline Version, and Upgrade via System Center Console using  Service Connection Point Role.

1. Upgrading the Primary Site

2. Upgrading the DP's

3. Upgrading the Client

TO-BE Infra with Phase II from SCCM CB V1606 to SCCM CB V1710

Pre Requisite's:

Processor  4, Core 8, RAM 32 GB  to Processor  8, Core 16, RAM 64 GB

Windows Server 2008 R2 STD (Version 6.1/Winver 7600 SP1) to Windows Server 2012 SP1 (Standard Edition)

SQL 2008 R2 SP1 (10.50.2811) to SQL 2012 Standard Edition

ADK  - Do we need to upgrade << Please suggest >>

SCUP - Do we need to upgrade << Please suggest >>

Using Service Connection Point Role, Upgrade from SCCM CB V1606 to SCCM CB V1702 and So On.

1. Upgrading the Primary Site

2. Upgrading the DP's

3. Upgrading the Client

With this, I can still manage my existing Windows 7 Clients, and also can upgrade to Windows 10 Client and Windows 10 Management (Complete Life Cycle Environment)

 

Edited by Veera
Phase I and II Differences

Share this post


Link to post
Share on other sites

On 2/13/2018 at 1:49 PM, anyweb said:

you should separate your test environment from production entirely, i.e. use a separate test vm environment with separate AD, SCCM, etc virtual machines that you test with, I wouldn't mix or recommend using a test lab in production

 

here's a guide to setup your test environment

 

 

Dear Admin,

However,  Will be performing the Green Field Implementation of SCCM CB on Existing PROD Domain Controller.  

If I am using Different Site code, Different Host Name for SCCM CB  - Is that makes any impact on Existing System Management Container Please.

Share this post


Link to post
Share on other sites

Green Field implentation ? what on earth is that ? and please tell me you are not installing SCCM on a production domain controller, have you had any training with SCCM ?

  • Like 1

Share this post


Link to post
Share on other sites

Dear Admin,

Sorry if any questions are wrong. I have been managing SCCM  - But this Migration is 1st time, that we are doing which the existing version installed by 3rd Party PPL.

Hence, it is require to get some advice from experts like you.

At Present, Upgrade seems to be more complicated with lengthy process. Hence, it is Planned to Install Complete New Environment with Existing Production DC (With Different Site Code)

I hope, We can have Multiple Environment of SCCM with in the same container (System Management), However the Site Code/Server Name should not be the same.

Is that Correct?

So the Plan as follows:

1. Performing the SCCM CB Environment

2. Slowly moving all Clients from One Domain to Other Domain.

 

Current Infrastructure:

SCCM 2012 SP2 with Windows 7 Clients (Managing – Application, Patch, Operating System Deployment)

This is running on Windows Server 2008 with SQL 2008

Required Infrastructure:

It is required to Manage Windows 10 Clients, Windows 7 Operating System (Application, Patch, OS Deployment)

After being and hearing more responses from our Engineer’s/Experts. It is planned to progress the Green Field Implementation

1.       Windows Server 2016

2.       SQL Server 2014 or SQL Server 2016

3.       Windows 10 ADK with Version ADK 1709 - 10.1.16299

4.       System Center Configuration Manager V1710 New Implementation along with Distribution Point

5.       Making the Environment with Complete Readiness for all Application Source, OSD Task Sequences, Software Updates., etc.,

This New Infra will be completely ready with supporting all contents.

IP Assignment:

We are already having the Boundary Groups, which is based on the IP Range with Region wise in the OLD Environment.

New Environment – Client Movement from Old Infrastructure:

Let us consider we have the IP Range called 192.168.1.1 to 192.168.1.254 is active and supplying the service with Windows 7 Client OS on Old Infrastructure (SCCM 2012 SP2)

Now, the New Infrastructure is ready with all sources (SCCM CB V1710) – If the Client IP Range, Boundary Settings for Site assignment is getting moved from Old Infra to New Infra

By Using Automatic Site Client Push Installation

1.       SCCM Agent Will get install/upgrade with Version CBV1710

2.       Since the IP Range, Boundary Group is allocated with New Environment

All the Deployments will get started to run on new Environment.

By performing this activity

1.       All Windows 7 Clients will be running with SCCM CBV1710 Agent Version

2.       All Windows 7 Clients will be reporting to SCCM CBV1710 Infrastructure

3.       Slowly, I can prepare myself for Windows 10 Upgrade Projects.

Hence, it is require to have 2 Environments in the Same System Management Container (SCCM 2012 SP2, and SCCM CB V1710). If I hold the 2 Environment with Different Site code and host name, Will that be Okay..

Please Advice!!

My Sincere apologize to send the details, Personally.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...