PENDING SCCM CB 1606 - Fresh Install

[avi_ei]

Hi,
About 8 years ago we had sccm 2007 installation that wasn't configured as needed and wasn't in use for many reasons.
3 years ago I've dismissed the old SCCM server and shut it down while old XP workstations remain with the SCCM client agent. (Of course new workstations including win7 didn't had the client anymore).
Since we have about 500 Workstations (260 of them still XP, 220 Win7, Remaining Win8/10) I had in mind last year to clean install SCCM 2012R2 version (leaded by your excellent Step by Step Installation and Configuration guide) to support our XP Workstations. (Installation that never made since then).
The last few days i'm working on a plan to finally install SCCM but in it's 1606 version taking in consideration that we will migrate this year all our Win XP workstations to win7/10.
According to this scenario I have several questions:

1. I understand that beginning version 1602 SQL AlwayOn is supported at last. we have SQL 2012 SP2 configured as AlwaysOn containing RDCB DB, SCVMM DB where I want to build the SCCM 1606 DB.
Is our current version of SQL is supported for SCCM 1606 ?
2. Can I use the old Site Code we had on the retired SCCM 2007 some years ago ?
3. is it necessary to do any schema extension in order to use SCCM 1606 ? or the current schema that was supported for SCCM 2012 R2 is enough ?
4. I didn't find any new Step by Step article of yours regarding a fresh installation and configuration of SCCM 1606, only the old Step by Step for version 2012 R2 - Can I stick this guide in order to install version 1606 ?
Any changes in this guide that I should take in consideration when installing version 1606 ?
5. In general is my plan OK to install version 1606 even before migrating all remaining XP workstations knowing that they wouldn't be managed anyway in this version of SCCM. (only version 7 and earlier).

Sorry for the long message, I'll appreciate any advice, suggestion and guide.

Regards,

 

[Prajwal Desai]

1. I understand that beginning version 1602 SQL AlwayOn is supported at last. we have SQL 2012 SP2 configured as AlwaysOn containing RDCB DB, SCVMM DB where I want to build the SCCM 1606 DB.
Is our current version of SQL is supported for SCCM 1606 ? - Yes the version of your SQL server is supported. https://prajwaldesai.com/supported-sql-server-versions-sccm-current-branch/

2. Can I use the old Site Code we had on the retired SCCM 2007 some years ago ? - Nope, i suggest use a new site code. This shouldn't be difficult as you can change the site code of clients using script - https://social.technet.microsoft.co...ite-code-of-configuration-manager-client.aspx

3. is it necessary to do any schema extension in order to use SCCM 1606 ? or the current schema that was supported for SCCM 2012 R2 is enough ? - If you had extended the schema during installation of sccm 2007 you need not extend it while you install or upgrade 2012.

4. I didn't find any new Step by Step article of yours regarding a fresh installation and configuration of SCCM 1606, only the old Step by Step for version 2012 R2 - Can I stick this guide in order to install version 1606 ?
Any changes in this guide that I should take in consideration when installing version 1606 ? - Using baseline media you can install SCCM 1606. There is an upgrade path from 2012 R2 to 1606, here is my step by step post - https://prajwaldesai.com/upgrade-sccm-2012-r2-to-sccm-1606/

5. In general is my plan OK to install version 1606 even before migrating all remaining XP workstations knowing that they wouldn't be managed anyway in this version of SCCM. (only version 7 and earlier). - You need to upgrade Windows XP to windows 7 for SCCM 1606 to manage those computers. So i suggest upgrade computers using XP to 7 and then go ahead with 1606 install.

 

[avi_ei]

Hi again,

I've made a fresh install of version 1702 CB and the installation was made on an existing SQL always-on remote server without any problems.

I have now 3 issues to consider:

1) As a preliminary step I've installed WSUS rule on the SCCM server (the WSUS repository files located on different disk on the server) and used remote SQL server for it.
since I understand that SQL always-on is not supported for WSUS DB I've installed it on one of the SQL servers that is member of the always-on HA, but at the end of the installation I cant see the WSUS DB on that server (the WSUS rule ended without any error).
How can I check and resolve that issue ?
(currently we have an existing WSUS server that is published to the clients via group policy and the new one on the SCCM server will replace it).

2) I've installed the SCCM 1702 CB despite we have still about 200 XP workstations that are in the process of replacing to Windows 7 until the end of the year knowing that they couldn't be managed by the SCCM.
as I understand I can configure the boundaries and the discoveries without any exceptions and the only way those Windows XP workstations wont get the SCCM client is by configuring appropriate collection to deploy the agent that will consist all the other supported OS workstations !? is may approach right ?

3) What is the recommended discovery method to use taking in consideration that we have only one site (no sub-domains) and no WAN connections ?
to be honest, I didn't understand way I need more than one discovery method and if I need to discover groups besides the users and the workstations.

Sorry for the long post and the newbie questions

Regards,

 

[Prajwal Desai]

1. After installing WSUS role, did you run the Post-Installation tasks ?.

2. SCCM 1702 CB doesn't support Windows XP i.e. you cannot deploy the client agent to Windows XP systems.

3. Every discovery method is unique. There is no harm in discovering all the information about your computers and devices in domain. So I would suggest you to run the discovery methods
Active Directory Forest Discovery, Active Directory Group Discovery, Active Directory System Discovery, Active Directory User Discovery (you could schedule it to run every week / month). Network discovery is optional and Heartbeat discovery method is enabled by default.

 

[avi_ei]

hello,
1. No, I didn't run the post installation tasks of WSUS, is it the cause for the DB not created ?
I understand from the past that not all the steps should be run cause it will break the SCCM integration with WSUS.

2. I'm aware of that, so I don't have to separate the XP workstation and exclude them from the collection that the client install will be deployed to ?
that means that trying to deploy the client install on XP will just fail and wont harm in any way those OS ?

3. Thanks, will use all the methods but is there any schedule suggestions for the various method cause I believe some of them are network and system intensive and can impact the network / systems ?

Many thanks for all the support.

 

[Prajwal Desai]

Let me know if you need any help before I mark this thread as Solved.

 

[avi_ei]

Hi,

Yes, I need your advice on my followed questions in my post from Thursday 12:03.

Thanks,

 

[Prajwal Desai]

1. you have to run the post install tasks so the SUSDB is created.
2. That's correct. With the auto client upgrade, you could exclude the windows XP collections from client install/upgrade.
3. You could schedule it to run during non-peak hours or run it per week once. You can also run the methods manually when it's required.

 

[avi_ei]

Hi again,

1. I ran now the WSUS post installation and the SUSDB was created on the SQL Server.
2. From that I understand that I need to create a XP collection in order to exclude from them the client install !?
3. Will be done as suggested.

thanks,

 

[Prajwal Desai]

If you already have a device collection with XP computers, it's more likely that you will exclude it from client agent upgrade. https://prajwaldesai.com/community/threads/exclude-computers-from-sccm-client-agent-upgrade.1111/

 

[avi_ei]

Two last things (I Hope)

1. Configured all discoveries the boundaries were created from the Active Directory Forest Discovery but I see something that can't find in any reference:

A boundary group was auto created named "Default-Site-Boundary-Group<XXX>" I can add to it the Site System Server but I can't add any boundary as members (I have 2 subnets) and I cant delete that group.
Is it enough to use this group even there are no boundary members in it and I can even add them ? Is it like this because it was created from the Forest Discovery ? (for now I added a new group but i'm afraid about overlapping).​

2. When I chose a Site system server I see not only my SCCM server but also my 2 SQL servers and the Always-On SQL name - is it OK ? I of course didn't choose any of them beside the SCCM server as a Site System.

Thanks,

 

[avi_ei]

Hi,

awaiting for response for my last issue

regards,

 

[avi_ei]

Hi,

Still waiting

Regards,

 

[vuonmatong]

Two last things (I Hope)

1. Configured all discoveries the boundaries were created from the Active Directory Forest Discovery but I see something that can't find in any reference:

A boundary group was auto created named "Default-Site-Boundary-Group<XXX>" I can add to it the Site System Server but I can't add any boundary as members (I have 2 subnets) and I cant delete that group.
Is it enough to use this group even there are no boundary members in it and I can even add them ? Is it like this because it was created from the Forest Discovery ? (for now I added a new group but i'm afraid about overlapping).​

2. When I chose a Site system server I see not only my SCCM server but also my 2 SQL servers and the Always-On SQL name - is it OK ? I of course didn't choose any of them beside the SCCM server as a Site System.

Thanks,View attachment 786

I've also had this problem

 

[avi_ei]

I've also had this problem

Hi,

And did you continue to implement SCCM and it's working OK ?

We'll appreciate Desai answer and/or suggestions.

Regards,

 

[Prajwal Desai]

Two last things (I Hope)

1. Configured all discoveries the boundaries were created from the Active Directory Forest Discovery but I see something that can't find in any reference:

A boundary group was auto created named "Default-Site-Boundary-Group<XXX>" I can add to it the Site System Server but I can't add any boundary as members (I have 2 subnets) and I cant delete that group.
Is it enough to use this group even there are no boundary members in it and I can even add them ? Is it like this because it was created from the Forest Discovery ? (for now I added a new group but i'm afraid about overlapping).​

2. When I chose a Site system server I see not only my SCCM server but also my 2 SQL servers and the Always-On SQL name - is it OK ? I of course didn't choose any of them beside the SCCM server as a Site System.

Thanks,View attachment 786

Apologies I am replying late. The default site boundary group is automatically created for each site by SCCM. This is to service clients that are not served by any other boundary group. I would stick with creating a new boundary group, adding your boundaries and configure that for site assignment. You can ignore / not use the default site boundary group.

 

[Prajwal Desai]

Hi,

And did you continue to implement SCCM and it's working OK ?

We'll appreciate Desai answer and/or suggestions.

Regards,

Go ahead by creating new boundary and boundary groups. You can ignore the default site BG.