Expand .NET Framework 3.5 Features and select HTTP Activation and Non-HTTP Activation. When selecting HTTP Activation, click on Add Features in the window that will pop up to add all required features for HTTP Activation.
Expand .NET Framework 4.5 Features and select HTTP Activation and TCP Activation. When selecting HTTP Activation, click on Add Features in the window that will pop up to add all required features for HTTP Activation.
Select Background Intelligent Transfer Service (BITS). Click on Add Features in the windows that will pop up to add all required features for BITS.
Select Remote Differential Compression. Click on Next. Click on Next again.
Now in the Roles Services for the Web Server Role (IIS) select Windows Authentication, select ASP.NET 3.5, expand IIS 6 Management Compatibility and select IIS 6 WMI Compatibility. Click on Next.
Tick the box to Restart the destination server automatically if required and click on Install.
Now let's install WSUS. Select the WSUS role and click on Next. Select WSUS Services and Database and click on Next.
Specify where to store the updates. Click on Next.
Specify the SQL server which will host the database. Click on Next.
Click on Install.
Now click HERE to download the Windows Assessment and Deployment Kit (ADK). This must be installed in the site server and in all servers where the SMS Provider role is installed.
Once downloaded, run the file, click on Next.
Select whether or not you want to participate in the CEIP. Click on Next.
Accept the license.
Select Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tool (USMT). Click on Install.
While the ADK is being downloaded and installed let's extend the AD schema with SCCM 2012 SP1 schema extensions.
In order to extend it open an elevated commmand prompt (using a schema admin account) and browse to the SCCM 2012 SP1 source files\SMSSETUP\BIN\X64. Run extadsch.exe
You can check the file ExtADSch.log which will be created in the root folder of the drive where your OS is installed. In my case is C:\ExtADSch.log
The log should look like the following:
Now using ADSI let's create the System Management container and grant the site server computer account full control permissions.
Run ADSI.msc, expand the Default naming context, expand your domain container, right click the System container and select New -> Object.
Select container and click on Next.
Type System Management and click on Next. Click on Finish.
Now right click the newly created System Management container and click on Properties.
Select the Security tab and click on Add. Click on Object types and make sure computer objects are also included in the query. Type the name of your site server and click on OK.
Give it full control and click on Advanced.
Select the Site Server name and click on Edit. Change the Apply to
field to This object and all descendant (child) objects and click on OK three times.
Now open AD Users and Computers so we can create the users required. We are going to create one user for the SQL Server and one user for the SCCM site system roles. Right click in the OU where the user will be created, select New -> User.
Type the name of the user for the SCCM site system role. In my case it's sccmadmin. Click on Next.
Type the password, untick User must change password at next logon and tick Password never expires and click on Next. Click on Finish.
Repeat the steps to create the sqlservice account for the SQL Server role. Add the
sccmadmin account to the Domain Admins group.
Now that the ADK installation has finished let's install the SQL Server. In my case I will install SQL Server 2012 Enterprise in a different server. You can install it in the same server but bare in mind that if you install them in the same server it will be restricted to a maximum of 50000 clients that SCCM can manage. The same is true if you are using the Standard edition of SQL Server.
From the SQL Server source run Setup.exe. Select Installation and click on New SQL Server stand-alone installation or add feature to an existing installation. It will run the rule check. Click on OK.
Now it will search for updates. Click on Next. Then it will install the setup files and run another check. Click on Next. Choose Perform a new installation of SQL Server 2012 and click
on Next.
Specify the product key and click on Next. Accept the license. Click on Next.
Leave the default and click on Next.
In the features selection, select Full-Text, Reporting Services and Management Tools. Click on Next. Click on Next again.
Now choose a new instance name or use the Default Instance and click on Next. Click on Next again.
Replace the username for SQL Server Database Engine with the one we created before. Type the password. In the Collation tab, click on Customize, select SQL Collation used for backwards compatibility and choose SQL_Latin1_General_CP1_CI_AS. Click on Next.
Click on Add Current User and click on Next.
Click on Next 3 times and click on Install. Once it's finished, click on Close.
If you are using a new instance then make sure you do the following:
Launch the SQL Server Configuration Manager. Expand SQL Server Network Configuration and click on Protocols for InstanceName. Make sure TCP/IP is enabled.
Double click the TCP/IP and change the Listen All to No. Click on OK.
Now click on the IP Addresses tab, remove everything that is in the TCP Dynamic Ports field of all the IPs and replace with the number 0 or leave it blank and in TCP Port for IPAll specify a port to be used. Click on OK.
In the SQL Native Client 11.0 Configuration, click on Client Protocols and double click TCP/IP. Change the default port to the same port you used before. Click on OK.
Restart the SQL Server service.
Now install the SQL Server 2012 CU 4. Download it from HERE.
OK. Now we can to the actual SCCM installation. From the source run the splash. Click on Install.
Click on Next. In this scenario we are going to install a stand-alone primary site. So go ahead and leave the default and click on Next.
Type the product key. Click on Next. Accept the License. Click on Next. Accept the prerequisite licenses. Click on Next.
Create a new folder or specify a existent one to download required prerequisites and click on Next.
Select the required server and client languages. Click on Next.
Specify a site code, site name and click on Next.
Specify the site as a stand-alone site.
Click Yes when prompted with the warning.
Specify the SQL FQDN, instance name (leave it blank for default) and click on next.
Specify the FQDN of the server where the SMS Provider will be installed. Click on Next.
Choose whether the communication will be restricted to only HTTPS or will also allow HTTP communication. PKI certificates are required if you select the first option. Click on Next.
Specify where the management point and distribution point will be installed. Click on Next.
Select whether to join the Customer Experience Improvement Program or not and click on next.
Review your settings and click on next.
Now you should get something like below with no errors. If you get any errors or warnings go ahead and fix them before you can continue.
If you forgot to change the SQL Collation you can do it after the installation using the following command:
setup.exe /quiet /action=rebuilddatabase /INSTANCENAME=SCCM2K12 /sqlsysadminaccounts=itself\admin
/sqlcollation=SQL_Latin1_General_CP1_CI_ASOnce everything is OK click on Begin Install.
And if everything goes as planned you should see the screen below.
Come back later for the next post on Configuring SCCM 2012 SP1.
Configuring SCCM 2012 SP1 - Part 1
Configuring SCCM 2012 SP1 - Part 2
Configuring SCCM 2012 SP1 - Part 3
No comments:
Post a Comment