How can I install System Center Configuration Manager version 1606 (Current Branch) on Windows Server 2016 with SQL 2016

[ogeccut]

Thanks for another great post.

Just a qq, what are the rights do i need to assign for the created users?

* CM_BA, used for building ConfigMgr created images

* CM_JD, used for joining computers to the domain
* CM_SR used for reporting services

And CM_NAA, a domain user and CM_CP, a domain user just regular user accounts?

 

And do i need to open the ports 1433, 4022 for SQL with this install?

I see ports are open in PS script......Big Thank you.

 

Thank you,

[anyweb]

all the users are regular user accounts and yes do open the sql ports

[ogeccut]

Thank you for reply. After SQL installation SQL browser and SQL Server Integration services are not running, is that normal?

Also should i change the log and backup path to a different drive "other then c:\"

Thank you,

[anyweb]

you can adjust the SQL services as you require them, but this script should be enough to get you up and running with SCCM in a SQL Server 2016 environment, I have it running just fine in 3 labs

 

as regards where you store the logs that only really matters if the drives are on different spinning disks

[Mino]

Thank you for this comprehensive guide! Very easy to follow.

A question about 'Step 11. Install the WSUS role'. After this step, I see a 'Windows Internal Database' service running, but aren't we suppose to avoid that since we already installed a SQL Server?

 

 

[anyweb]

good point, i see a reference to it in the wsus xml file but it still uses the SQL DB, and in my lab the wid services are not even running are they running on yours ?

i'll see what i can find out in my lab...

[anyweb]

mystery solved, when generating the XML i add WSUS via the server manager, and as part of that process it automatically adds required features including WID, see here

[Mino]

I expected that also. And yes, WID was running in my Lab. May I assume you are going to update your script repository and make it available to us?

[anyweb]

WID is required, see the screenshot. You can try manually removing it and scripting that yourself but why worry you are not using it, wsus is using SQL for the DB

[anyweb]

this might be enough, please test

 

Uninstall-WindowsFeature -Name Windows-Internal-Database -Restart