Prepare for installation:
<![if !supportLists]>1. <![endif]>Join the server(w-sr-2) to Domain
<![if !supportLists]>2. <![endif]>AD accounts:
Sccm_smsadmin - Domain user, member of ‘Administrators’ on SCCM machine(W-SR-2), I will use this account to install SQL,WSUS and
Sccm_clientInstall - Domain user, admin of all the client computers.
<![if !supportLists]>3. <![endif]>Create ‘System Management’ Container in AD
<![if !supportLists]>· <![endif]>Open ‘ADSI Edit’, ‘Default naming context’ -> ‘CN=System’ –> right click ‘New’ ‘Object…’->’Container’ -> ‘Next’ -> type in ‘System Management’ as value.
<![if !supportLists]>· <![endif]>Open ‘Active Directory Users and computers’ -> Click ‘view’ on the top manu, ‘advanced Features’ -> ‘ System Management’ -> ‘All Tasks’ -> ‘Delegate Control’
When the ‘Welcome to Delegation of Control’ Wizard appears click next, -> ‘Add’ -> ‘Object Types’ -> ‘Computers’. Type in your SCCM server name (w-sr-2 in my case) -> ‘Check Names’, it should resolve. -> ‘next’ -> ‘Create a Custom Task to Delegate’ -> ‘Next’ -> ‘This folder, existing objects in this folder and creation of new objects in this folder’.
click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific child objects are selected then place a check mark in FULL CONTROL, and click next then Finish.
Failure to do the above will mean that the System Management Container in AD will NOT POPULATE with ConfigMgr site info needed by the Clients and you will see many errors in your site status warning you of same.Note: Repeat the above for Each site server that you install in a Hierarchy.
Failure to do the above will mean that the System Management Container in AD will NOT POPULATE with ConfigMgr site info needed by the Clients and you will see many errors in your site status warning you of same.Note: Repeat the above for Each site server that you install in a Hierarchy.
Step C needs ‘Domain Admin’ or ‘Enterprise Admin’ privilege rights.
<![if !supportLists]>4. <![endif]>Extend AD Schema
Find \SMSSetup\Bin\x64\Extadsch.exe, right click and choose Run As another user, run it under ‘Schema Admin’ privilege.
Install SQL2012
Beta supports SQL 2012 RTM with a minimum of CU 2. ConfigMgr has very strict SQL collation requirement, pretty much across the entire System Center range, essentially only SQL_Latin1_General_CP1_CI_AS collation is supported. This has to be selected during installation if you are running a non-USA regional\system OS
Something handy to know ahead of the installs is that you can use CMTrace to view the resulting log files for the SQL 2012 RTM and CU 2 installations. Each execution creates a new folder on the following path called detail.txt:
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log
FW:
To open a port in the Windows firewall for TCP access, open 1433 and 4022 on the SQL server.
netsh advfirewall firewall add rule name=”SQLServer” dir=in action=allow protocol=TCP localport=1433
netsh advfirewall firewall add rule name=”SQL Service Broker” dir=in action=allow protocol=TCP localport=4022
<![if !supportLists]>1. <![endif]>Server stand-alone installation or add features to an existing installation
<![if !supportLists]>2. <![endif]>SQL Server Feature Installation
<![if !supportLists]>3. <![endif]>Select the following
<![if !supportLists]>· <![endif]>Database Engine Services
<![if !supportLists]>· <![endif]>Reporting Services – Native
<![if !supportLists]>· <![endif]>Management Tools – Basic
<![if !supportLists]>· <![endif]>Management Tools – Complete
<![if !supportLists]>4. <![endif]>By default each of the services will be configured using a service-specific user account, we need to revert back to using NT AUTHORITY\SYSTEM
Do this for the SQL Server Agent, the SQL Server Database Engine and the SQL Server Reporting Services services
Click Account Name
Browse
Browse locally for SYSTEM and accept
Set the services Start-up Type to automatic
<![if !supportLists]>5. <![endif]>When done, Select the Collation tab
If SQL_Latin1_General_CP1_CI_AS is not shown, click Customize otherwise skip this part
Select SQL collation, used for backwards compatibility Scroll down the list and choose SQL_Latin1_General_CP1_CI_AS
<![if !supportLists]>6. <![endif]>Choose ‘Windows authentication mode’
Preinstall the SCCM machine:
<![if !supportLists]>a. <![endif]>Make sure windows server is updated
<![if !supportLists]>b. <![endif]>Install AIK
Nothing special, the following features installed:
Un-tick everything short of
Deployment Tools
Windows Preinstallation Environment (Windows PE)
User State Migration Tool (USMT)
<![if !supportLists]>c. <![endif]>OS Features
Open a PowerShell prompt and type
Import-Module servermanager
Add-WindowsFeature BITS,RDC,Web-WMI,WDS
I’ve really cut this down, magic happens during the installs that results in what we need being switched on or installed
Note: .NET Framework 4.0 is built in to Server 2012 now, so no need to install it anymore!
<![if !supportLists]>d. <![endif]>WSUS
Previously the WSUS installer wizard would be launched after we’d elected to install the role, that would then allow us to configure the Database and Website settings. We now have this integrated pretty much into the role creation
Tick WSUS Services
Tick Database
<![if !supportLists]>e. <![endif]>Configure SQL 2012 Maximum server memory usage
SQL will consume all your memory, as I installed it to same SCCM server box. It needs to be throttled back:
Open SQL Server Management Studio and get the properties for the database up
Select Memory and change the maximum server memory setting
Features installed on the SCCM box
As I am using one VM to host both SQL and SCCM, I have
experienced some issues, when I tried to installed so SCCM roles, and did quite
a bit troubleshooting, but at the end, here is all the features installed.
[X] File And Storage Services
[X] File and
iSCSI Services
[X] File
Server
[X] Storage
Services
[X] Web Server (IIS)
[X] Web Server
[X] Common
HTTP Features
[X]
Default Document
[X] Directory Browsing
[X] HTTP
Errors
[X]
Static Content
[X] HTTP
Redirection
[X] Health
and Diagnostics
[X] HTTP
Logging
[X]
Logging Tools
[X]
Request Monitor
[X]
Tracing
[X]
Performance
[X]
Static Content Compression
[X]
Dynamic Content Compression
[X] Security
[X]
Request Filtering
[X] Basic
Authentication
[X]
Centralized SSL Certificate Support
[X]
Client Certificate Mapping Authentic...
[X]
Digest Authentication
[X] IP
and Domain Restrictions
[X]
Windows Authentication
[X]
Application Development
[X] .NET
Extensibility 3.5
[X] .NET
Extensibility 4.5
[X] ASP
[X]
ASP.NET 3.5
[X]
ASP.NET 4.5
[X] ISAPI
Extensions
[X] ISAPI
Filters
[X] Management
Tools
[X] IIS Management Console
[X] IIS 6
Management Compatibility
[X] IIS 6
Metabase Compatibility
[X] IIS 6
Management Console
[X] IIS 6
Scripting Tools
[X] IIS 6
WMI Compatibility
[X] IIS Management
Scripts and Tools
[X]
Management Service
[X] Windows Deployment Services
[X] Deployment
Server
[X] Transport
Server
[X] Windows Server Update Services
[X] WSUS Services
[X] Database
[X] .NET Framework 3.5 Features
[X] .NET
Framework 3.5 (includes .NET 2.0 and 3.0)
[X] HTTP
Activation
[X] Non-HTTP
Activation
[X] .NET Framework 4.5 Features
[X] .NET
Framework 4.5
[X] ASP.NET 4.5
[X] WCF Services
[X] TCP Port
Sharing
[X] Background Intelligent Transfer Service (BITS)
[X] IIS Server
Extension
[X] Remote Differential Compression
[X] Remote Server Administration Tools
[X] Feature
Administration Tools
[X] BITS
Server Extensions Tools
[X] Role
Administration Tools
[X] Windows Server Update Services Tools
[X] API
and PowerShell cmdlets
[X] User
Interface Management Console
[X] User Interfaces and Infrastructure
[X] Graphical
Management Tools and Infrastructure
[X] Server
Graphical Shell
[X] Windows Internal Database
[X] Windows PowerShell
[X] Windows
PowerShell 3.0
[X] Windows
PowerShell 2.0 Engine
[X] Windows
PowerShell ISE
[X] Windows Process Activation Service
[X] Process Model
[X] .NET
Environment 3.5
[X] Configuration
APIs
[X] WoW64 Support
|
SCCM installation
<![if !supportLists]>1. <![endif]>
<![if !supportLists]>2. <![endif]>
<![if !supportLists]>3. <![endif]>Database Info.
<![if !supportLists]>4. <![endif]>Client Comuter Communication settings:
