This document guide you through installation of Microsoft System Center Configuration Manger (SCCM) 2012 SP1 with Windows Server 2012 AD and MS SQL Server Standard 2012 SP1.
Configure Active Director (AD) on Windows server 2012:
Creating Active directory rather simple in Windows 2012.
Add the roles and feature from Server Manager Dashboard (AD DS);
Back in Server Manager, you will notice that AD DS has been added to the left navigation tree. Click on it and then click on More on the right navigation pane where it states that Configuration is required for Active Directory Domain Services.
No dcpromo command needs to enter from command prompt or Windows Run.
You will now be presented with the All Servers Task Details, in which you will click on Promote this server to a domain controller under Action. The Deployment Configuration screen appears and we will select “Add a new forest” as this is the first domain controller.
Enter your Root domain name and then click Next.
The following screen will then appear in which you will enter and select your Domain Controller Options.
You will then get the below warning in which you can ignore for now.
The NetBIOS domain name will then be inputted automatically. In the event of a conflict, it will suggest an alternative by appending the original name with a 0.
Note: click on following link next for the screen that is not show on above.
Microsoft SQL server 2012 SP1 Setup:
Configuration Manager 2012 SP1 requires the following SQL versions
SQL Server 2008 SP2 with Cumulative Update 9 or higher
SQL Server 2008 SP3 with Cumulative Update 4 or higher
SQL Server 2008 R2 SP1 with Cumulative Update 6 or higher
SQL Server 2012 with Cumulative Update 2 or higher
You can install additional feature as you required but I just go with minimum required for SCCM installation.
Ensure you have select following SQL Collation for SCCM:
Click Add Current user or Other Amin users:
Download SP1 this is now supported SQLServer2012SP1 (KB2674319-x64-ENU.exe)
Now open SQL Manger and connect using your current user (user that you have entered during installation as admin)
Note: Ignore the server name;
Microsoft recommend 50 to 80% of available physical memory.
Note: more memory certainly improve performance. It is ideal to use a different server for SQL for real operational server.
Install Windows ADK:
The Windows® Assessment and Deployment Kit (Windows ADK) is a collection of tools that you can use to customize, assess, and deploy Windows operating systems to new computers.
Prepare Active Directory (schema update for AD) for SCCM.
Run following file from DC server if SCCM server is not your DC server. Note: do not use SCCM server as DC server in real production server. AD has to be separated but for lab environment it is OK.
On the CD or mounted/extracted iso it should be here: SMSSETUP\BIN\X64\extadsch.exe
\SMSSetup\Bin\x64\Extadsch.exe, right click and choose Run As Administrator.
A command prompt window will appear briefly as the schema is extended, check in c:\ for a log file called ExtADSch.log it should look similar to this
If you see error message following log file; run this for domain controller login with Administrator.
Configure Windows Host firewall to required ports for SCCM:
Right click on Incoming rules and create new rule
Crate System Object Container:
Right click CN=system management then properties
Create firewall rules using Group policy:
Open Group Policy Management tools to open WMI and File and printer sharing for SCCM clients.
Repeat again for WMI
Adding required Windows Roles and Feature>
If require PXE boot; the Windows Deployment Service is required. Note: Enabling PXE boot from SCCM consoled also automatically install “Windows Deployment Service” so you can install now or later.
———– Note: installation of Default WSUS server with Windows Server 2012 ————–
It is better choice to use Database rather WID database. Recreate SUP (Software Update Point) in SCCM Site server roles if sync is failed between WSUS and SCCM SP1
WSUS is bit cranky for now but here is what I did to fix it:
1) Uninstall SUP role
2. Uninstall WSUS
4. Delete SUSDB from SQL Server if any
5. Restart Server
6. Install WSUS (Chose to install DB not WID)
7. Configured Updates to be stored locally
8. Run Post Deployment Configuration from Server manager
9. Started WSUS Admin Console and ran Wizard (also chose to connect for the catalog sync) up to the Point where you select the products. Here I canceled the wizard without choosing any products
10. Install SUP role in SCCM and configure the right Settings (WSUS on Server 2012 Defaults to its own admin Website and ports 8530 and 8531) and select the products you required.
11. Check following log file if WSUS does not sync with SCCM.
Path: C:\Program Files\Microsoft Configuration Manager\Logs
12.) Starts synchronization in the sccm console
Install with Windows Server 2008 R2 SP1 [very stable]
Alternatively; download and install stable version of WSUS 3.0 SP2 or better still if you go with Windows 2008 R2 and WSUS 3.0 SP2 [stable]. Windows server 2008 R2 SP1, SCCM 2012 SP1, MS SQL 2008 R2 with required updates/ MS SQL 2012 SP1 with cumulative updates.
WSUS 3.0 SP2 installation steps:
Apply following KB for WSUS 3.0 Service Pack 2 (SP2) to work on Windows 2008 R2 Server.
Installation steps are here:
Install SCCM 2012 (auto boot DVD or Run splash.hta file as an administrative privilege):
Click on the begun installation if no error found. Note: SCCM 2012 SP1 needs 8GB RAM for Primary site.
Required Hotfix release on Feb-2013 for SCCM SP1
Restart the server and ensure required services are running. Done.