Jump to content


anyweb

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

Recommended Posts



sure it is, it's the Powershell script called install sql server 2016.ps1. or did you mean something else ?

Share this post


Link to post
Share on other sites

Step 9. SQL Memory Configuration  

The script referenced in this step.  I've installed SQL now I want to configure the memory.

 

Oops, my apologies,  Looks like I had an older version of the Scripts.zip file.   I noticed it when I went to install the SCCM and the script was named for 1607.

WD

Edited by Witchdoctor
New information

Share this post


Link to post
Share on other sites

no problem and thank you for using the scripts :)

Share this post


Link to post
Share on other sites

1702 is installed on a new server, new hierarchy. What is the best practice to upgrade the clients? The new sccm is discovering everything, I created a pre-production test collection and set the client to upgrade that collection but it is not working.

Share this post


Link to post
Share on other sites

Dear Niall,

Great admirer of yours, All my SCCM knowledge credit goes to you.

I want to understand, If I am going through the manual installation approach for my LAB(SCCM 1702, domain controller server 2016 and sql server 2016 sp1) do I need to Enable Named Pipes and TCP/IP in SQL server protocols the same way you taught us in the sql 2008 for configuration manager 2012, Also Do I need to change the Status from Disabled (default) to Enabled for both the Servers local ip and localhost values in SQl server.

 

Edited by Maninder
more detail
  • Haha 1

Share this post


Link to post
Share on other sites

hi, thanks for the kind words,

" To support Kerberos authentication, the TCP/IP network communication protocol must be enabled for the network connection of each SQL Server cluster node. Named pipes is not required, but can be used to troubleshoot Kerberos authentication issues. The network protocol settings are configured in SQL Server Configuration Manager, under SQL Server Network Configuration. "

via

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/use-a-sql-server-cluster-for-the-site-database

hope that helps, from

cheers

niall

Share this post


Link to post
Share on other sites
On 6/1/2017 at 9:08 PM, SCCM N00B said:

Great article so far. I'm just going through the steps to become familiar with the process and to build a lab environment once I have the process down.

I'm using the script to install SQL Server 2016 and it seemed to ignore my desired location that I configured in your script. It installed to C:\Program Files instead of D:\Program Files. Once the SQL installation was executed in the PowerShell ISE, the install time using the script was about 15 minutes.

 

Same problem here. Any ideas? There is a "install sql 2016.txt" file in the scripts directory that has "/INSTANCEDIR="C:\Program Files\Microsoft SQL Server" in it. So I assume this is where its getting C: from, but I cannot see any reference to it in the .ps1 file...... wierd. Going to do a manual install for now as it seems SQL didnt install correctly anyway. I only have SQL Client Connectivity SDK install when i try to uninstall. And it wont let me uninstall it which is rather annoying.

Edited by Ewan Monro

Share this post


Link to post
Share on other sites

no the txt file is only there for reference it is not used.

if you share your edits to the SQL powershell script, then I can see what is going on...

Share this post


Link to post
Share on other sites

Dear Nial,

I am encountering two issues.

1. Software center doesn't shows up in my DC server 2016. Apart from DC it was installed on CM1 and two VM's  win7, Win10 without any issue.

2. WSUS is unable to sync with Microsoft updates. Want to confirm shall I be using port 80 and 443 or 8530 and 8531. What could be the possible reason causing this.

Attaching few logs.

 

MS

ccmsetup.log

ccmsetup-ccmeval.log

client.msi.log

WCM.log

WSUSCtrl.log

wsyncmgr.log

Share this post


Link to post
Share on other sites

hi Maninde,

are these 2 problems occuring after completing my guide or something else ?

Share this post


Link to post
Share on other sites

did you configure WSUS in any way ? I do not cover configuring WSUS in this guide, and I do not cover Client deployment in this guide. You can find those topics and more here.

Share this post


Link to post
Share on other sites

Hi awesome posts as each and everyone one of yours are. :)

I am looking at upgrading mu current Server 2012 R2, SQL 2012, CM 2012 1702 environment to Server and SQL 2016. I am looking at installing a complete new server with and setting everything up from scratch.

I know with my Applications/Packages/Drivers/TS's, etc, they will need to be redistributed. Will my clients need to be re-discovered and agents re-installed. I will use the same site code, but different server name and IP. 

  • Thanks 1

Share this post


Link to post
Share on other sites

Hi great post. I'm actually setting up a new production environment in the next few weeks. I'm setting up the environment initially to run along side so we can slowly migrate the users and setting etc. Im hoping i wont need to extend the AD schema as we are already using SCCM 2012 R2 is there a way to check to ensure no issues?

Share this post


Link to post
Share on other sites

if you've already extended the schema for ConfigMgr then you are good to go. to verify you can delete everything in the system mangement container using adsiedit and restart the sms_executive component, it should repopulate the system management container, if not it's not working or delegated correctly

Share this post


Link to post
Share on other sites

use what Microsoft supports and you should be fine, if in doubt, try it in a lab first

Share this post


Link to post
Share on other sites

Hello,

Excellent document..

I am using the wizard

Where do I specified the SQL instance?

I don't use MSSQLSERVER but Severname\ConfigMgr ... I cannot figure out where to enter this and it fails by not finding the instance...

Thanks,

DOm

Share this post


Link to post
Share on other sites

Great guide, thanks so much for making this available to everyone this resource is the best by far on the web. Slowly working my way through this, a couple of quick questions though,

Do I need to amend the computer name and server name that's mentioned in the DeploymentConfigTemplate at all?

I don't plan on using Config Manager for WSUS at the moment so should i still install the role? We currently already have a WSUS server which is looking after updates.

Is it best practice to use the default local SQL accounts for the SQL services or should I apply domain accounts for those services?

I mentioned in a previous post about having to re-install Config Manager from scratch as the whole thing was a mess when I took it on, I have managed to uninstall most of the clients on the domain but as I will be using the same site names going forward as before am I likely to run into trouble after following this setup guide?

Thanks very much

Share this post


Link to post
Share on other sites
Great guide, thanks so much for making this available to everyone this resource is the best by far on the web.  

hi and thanks for your comments :)

Do I need to amend the computer name and server name that's mentioned in the DeploymentConfigTemplate at all? 

not in my testing, but please verify first in a LAB

I don't plan on using Config Manager for WSUS at the moment so should i still install the role? We currently already have a WSUS server which is looking after updates.

if you don't intend to use SCCM for software updates, then you don't need to install WSUS.

Is it best practice to use the default local SQL accounts for the SQL services or should I apply domain accounts for those services?

I mentioned in a previous post about having to re-install Config Manager from scratch as the whole thing was a mess when I took it on, I have managed to uninstall most of the clients on the domain but as I will be using the same site names going forward as before am I likely to run into trouble after following this setup guide?

Use SQL accounts that work with your enterprise, here are some tips, and as regards your current setup and installing configmgr again, i'd suggest you verify everything in a lab first, it's easy to do so.

Share this post


Link to post
Share on other sites

HI - Excellent notes.  Thanks for sharing the scripts.

My question is - I would like to make use of your XML file for deploying roles and features.  Do, I need to specify servername while running install roles and features.ps1?  As you know the computername in the XML file is CM01.

Thanks

 

RL

Share this post


Link to post
Share on other sites
HI - Excellent notes.  Thanks for sharing the scripts. 

thanks!

i've tested the xml file on a server with a different name and it worked fine, please do a quick test on a VM with a different computername than CM01 and post your result here

Share this post


Link to post
Share on other sites

Tested your xml file to install roles and features on a VM.  It worked out fine. 

No need to include server name.  Just run the install roles and features script and all the roles/features will get installed in less than 4 minutes.  Will save the script for future use.

Here is the screen shot for information.

 

3.JPG

  • Haha 1

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...