The PDF file is a 162 pages document that contains all informations to install and configure SCCM Current Branch. Use our products page or use the button below to download it . |
 | This blog post has been updated. Please refer to the new SCCM Current Branch Installation Guide. |
In the first post of this SCCM 1511 Installation Guide blog series, we planned our hierarchy, prepared our server and Active Directory.
In part 2, we installed and configured SQL in order to perform SCCM 1511 installation.
In part 3, we will run the prerequisite checker and proceed to the complete SCCM 1511 installation. We will install a stand-alone Primary site.
If you’re already running SCCM 2012 and want an upgrade to SCCM 1511, do not follow this guide. This guide is for a new SCCM 1511 installation only. See our upgrade guide instead.
Prerequisite Check
Before launching the SCCM 1511 installation, we recommend to launch the Prereqchk tool in order to verify if all components are configured correctly. The SCCM 1511 installation wizard will also run this check but if you’re missing a requirement, you’ll have to go through the whole installation wizard again after fixing it. We prefer to use the standalone tool before running the setup.
To start the prerequisite check tool :
- Open an Administrator command prompt
- Browse to .\SMSSETUP\BIN\X64
- Run the following command : Prereqchk.exe /AdminUI
If you follow the prerequisite guide correctly you’ll have this result :
Refer to this Technet article to see the list of all checks done by the tool.
If you have any warning or error refer to this Technet article in order to resolve it, or go thought part 1 and part 2 of this guide.
SCCM 1511 Installation
We are finally ready to launch the setup. First, reboot the server. This will make sure that the machine is not in a Reboot pending state.
- Mount and open the SCCM 1511 ISO that was previously downloaded from the Microsoft Volume Licensing Site
- Run Splash.hta
- Select Install
- On the first screen, Click Next
- On the Getting Started screen, Select Install a Configuration Manager Primary Site and click Next
- On the Product Key screen, enter it and click Next
- On the Microsoft Software License Terms screen, accept the terms and click Next
- On the Prerequisite Licences screen, accept the License Terms and click Next
- On the Prerequisite Downloads screen, specify a location to download the prerequisite file. This folder can be deleted after setup
- On the Server Language Selection screen, select the language you want to display in the SCCM Console and Reports. You can modify language later by running setup again and select the Site Maintenance option
- On the Client Language Selection screen, select the Client language to support. You can modify languages later by running setup again and select the Site Maintenance option
- On the Site and Installation Settings screen, enter your Site Code. Use the same Site Code as you specified when creating your Database
- Note : Site codes cannot be used more than one time in a Configuration Manager hierarchy for a central administration site or primary sites. If you reuse a site code, you run the risk of having object ID conflicts in your Configuration Manager hierarchy. This applies also if you’re doing a migration from an earlier version.
- Enter your Site Name. This name will appear in the console so choose accordingly
- On the Primary Site Installation screen, select Install the primary site as a stand-alone site. If you have a Central Administration site, this is where you would join the Primary Site to the existing hierarchy
- On the warning, click Yes
- On the Database Information screen
- Enter your SQL Server Name. In our case the SQL server is the same box as SCCM
- Leave the Instance Blank
- Enter your Database name. Once again, this must match the previously created Database in part 2
- Leave the Service Broker Port to 4022
- On the Database Information screen :
- Enter the path to the SQL Server data file. Locate this on the SQL Volume
- Enter the path to the SQL Server log file. Locate this on the SQL Logs Volume.
- I like to use the same directory where I created my database and logs (E:\SCCMDB, G:\SCCMLogs)
- On the SMS Provider Settings screen, leave the SMS Provider to the default value which is the local server. Refer to the following Technet article to read about the SMS Provider.
- On the Client Computer Communication Settings screen, select Configure the communication method on each site system role. This is where you select to have HTTPS or not on your initial Management Point and Distribution Point. This settings can be change later
- On the Site System Roles screen :
- Check Install a Management Point
- Check Install a Distribution Point
- We will install both MP and DP on the same box so leave the FQDN as is
- The Client connection drop-down is unavailable due to our previous selection
- On the Usage Data screen, click Next. This new screen basically tells that you accept that you will send some telemetry data to Microsoft
- On the Service Connection Point screen, click Next. This new role enables your deployment to download updates and new features
- On the Settings Summary Screen, review your options and click Next
- On the Prerequisite Check screen, you should have no error since you’ve run it before setup, click Next
- The installation is in progress. You can count between 15 and 30 minutes depending of your server specifications
- You can follow the progress by clicking the View Log button or open the ConfigMgrSetup.log file on the C: drive
- Wait for Core setup has completed and close the wizard
We’re still not done yet ! Before opening the SCCM console, we suggest to install the following tools :
CMTrace
CMTrace will become your best friend when reading log files.
- Open the SCCM ISO
- Browse to .SMSSETUPTOOLS
- Click on CMTrace.exe
- Click on YES to set is as your default log viewer
Additionally you can read our blog post :
System Center 2012 R2 Configuration Manager Toolkit
The SCCM 2012 R2 toolkit is compatible with SCCM 1511 and contains fifteen downloadable tools to help you manage and troubleshoot SCCM.
Download and install it here
Extra
You can also refer to our blog post about Useful Resources to help you begin with SCCM.
23 Comments on “Complete SCCM 1511 Installation Guide”
Useful info. Lucky me I found your web site accidentally, and I’m stunned why this accident did not took
place earlier! I bookmarked it.
My company is going to install SCCM but the problem is that there are multiple domains (every office has it is own Domain), I wanted to know If I am able to add multiple domains in SCCM ?
Hi
I have got SCCM all up and running and everything is looking go, However; after doing an OS deployment to a new device, the client doesn’t check in unless I manually run the Health Check scheduled task.
I’ve tried leaving a device for a few days but it never checks in and so doesn’t update AV definitions etc.
If I manually run the Scheduled Task then it checks in that one time but still doesn’t do it automatically.
Any help would be greatly appreciated.
Ian
Has anyone seen an issue where it states the “Core setup has completed,” but some of the items in the list have the blue circular arrows next to them, instead of the green check box? I have a number of items with the blue arrows. Similar to the third to the last photo on this site, https://social.technet.microsoft.com/wiki/contents/articles/36614.sccm-2016-step-by-step-walk-through-setup.aspx.
I was installing 1702 from scratch on a newer server using the ISO.
Thank you!
Pingback: How to apply SCCM 1610 Update Rollup 3 (KB4010155) |
Pingback: Step-by-Step SCCM 1702 Installation Guide |
When I come to the stage where I am asked to specify the Paths to the SQL Server data file and SQL Server log file I receive the error “Path does not exist, please select valid path”
I have tried all of the drives on the server, pre-existing folders and created folders as part of the specification, none of which have worked.
Any suggestions?
Not to worry about this. It turns out that if you have SQL on the local server and that server has a hostname longer than 16 characters, which you truncated earlier in the setup process to ensure that it satisfies NetBIOS restrictions, the installation thinks that you are trying to put the database and log files on a remote server, so a path such as c:\data will not work.
I have ended up renaming my server to not need a name change to satisfy NetBIOS restrictions to overcome this.
We’re having a SQL Connection issue when attempting to do the installation of 1511: Cannot detect SMS Type because either SiteServer, SqlServer or SiteServerName is empty
At times it appears to make a connection, but then stops: Connection null? FALSE
12/7/2016 3:53:20 PM: ConfigMgrSetupWizard Information: 1 : Connection state Closed
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Detected instance name: SCCM
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Detected default data path: D:\Program Files\Microsoft SQL Server\MSSQL13.SCCM\MSSQL\DATA\
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Detected default log path: D:\Program Files\Microsoft SQL Server\MSSQL13.SCCM\MSSQL\DATA\
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Is SQL clustered?: False
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Is SQL availability group?: False
12/7/2016 3:53:32 PM: ConfigMgrSetupWizard Information: 1 : Does database CM_DC1 already exist?: False
Any Help would be great. Tried creating the DB before setup as well. Same issue.
Hello
Hope some one can help. We recently deployed current batch 1511 in our environment. We are able ot push clinet and deploy EPP. However we are not able to push software update.
I have followed your documents on setting up the software update component and also able to form download the updates for example in my case (Windows 7). I am also able to create the package and I see a package ID created. However when I deploy the package to a collection, I am not able ot see the package ID, the package ID column remain blank while an entry for this deployment shows up in the deployment tab of the collection.
WSUS is communicating OK. Is there another deployment logs that I can view other CCM
In WCM log I do get a PublishApplication :failed with error system.componentModelwin32Exception
Error:failed to publish client with error = 0x80004005
HandleSMSClientPublication failed
I am able to push any Apllication deployment ok, for example I published 7zip application and that was receved OK at the client side, and I am able to see the package ID in the device collection
My environmnent
Windows 2008 local SQL 2014, the WSUS is using windows DB,
Hope some one can help in solving this
Thanks
Buck
My upgrade was sucessful!! Thank you guys so much for putting this together for us! One question I do have, Only my x86 boot image upraded to the new version. I have two x64 boot images that are still on version 6.2.9200.16384. Is this a problem? How do I update them manually? Thanks for your help!!
Only default boot image gets updated. You can update your custom one manually.
Amazing Website gang! I do have a question, I had purchased one of your guides but I have yet to receive it? Is there anyway that this can be checked for me.
Thank you
Michael Dickson
Send us an email, the download link will be resent to you.
Pingback: Dave’s SCCM Current Branch Packing List | Skatterbrainz Blog
Hi Benoit
Can you tell me if there is a difference between CM 1602 and System Center 2016 Preview?
Hi Michael,
Configuration Manager is not part of System Center 2016. Configuration manager goes by Currant branch naming now. Version 1602 is the latest release to production users.
You can follow this technet article to see Technical Preview for Configuration manager.
https://technet.microsoft.com/en-us/library/mt595861.aspx
As you will see, they release one preview per month since the beginning of 2016!
Enjoy
Jonathan
Great tutorial. Thanks!!!
The beginning prerequisite check passed. But the 2nd one right before pushing “Begin Install” states Warning on WSUS on site server, and Failed on USMT, Windows Deployment Tools, and Windows Preinstallation Environment.
I started from the beginning of your how-to guides and I didn’t see anywhere you had listed these 4 items. You may want to mention them in the beginning.
Thanks again for the great guides.
Thanks for the comment. I’ll be reviewing that part.
Le BEC se transmet il par le sang? La salive?La Condensation NGC est elle autorisée par la Convention de Genève? Peut on s’en protèger par une combinaison spéciale?
Pingback: SCCM Deploy – Post 1. Setting up VMware AD and SCCM 1511
Hi Benoit,
I have at the time sccm 2012 R2 SP1 runing and I want to install on a new hardware the sccm1511 with the same domain and migrade from sccm2912 R2 to sccm1511. But during the new installation of sccm1511 I get the error message by the prerequisite check the following error as faild
#######
A site server or site system role is already installed on the computer selected for site server installation. Remove the site or site system role from the computer, or select another computer for site server installation
#######
Any Idea why?
best regards
Nick