Set-up Server Features and Roles Once the users are created we will move on to setting up the Internet Information Services (IIS) role on the server.

Transcription

1 HOW TO: Install and Setup System Center Configuration Manager (SCCM) 2012 SP1 on a Windows Server 2012 Part 1 - Prerequisites In the following three part guide we will be going over how to install and set-up System Center Configuration Manager 2012 or SCCM 2012 for short on a Windows Server 2012 environment. In the first part we will be installing all the prerequisites that SCCM requires to function correctly and general setting up to make our lives easier in the long run. To start off it is a good idea to create a set of administrative users that both SCCM and the SQL database can use to perform their tasks. In total we recommend creating six users as can be seen below. These users will need to have full admin rights so it is a good idea to give them a separate password than any existing admin accounts on your system. List of Admin Users Set-up Server Features and Roles Once the users are created we will move on to setting up the Internet Information Services (IIS) role on the server. On the Server Manager click 'Add Roles and Features' then click 'Next' until you reach 'Features'. Make sure the following features are ticked. -.NET Framework 3.5 Features -.NET Framework 3.5 (This includes.net 2 and 3) -.NET Framework 4.5 Features -.NET Framework ASP.NET WCF Services - TCP Port Sharing - Background Intelligent Transfer Service (BITS) - IIS Server Extension - Remote Differential Compression

2 Specify Features 1 Specify Features 2 Then go to the 'Roles' section. Find 'Web Server' and tick it. Navigate to 'Role Services' and make sure the following services are ticked.

3 - Common HTTP Features - Default Document - Directory Browsing - HTTP Errors - Static Content - HTTP Redirection - Health and Diagnostics - HTTP Logging - Logging Tools - Request Monitor - Tracing - Performance - Static Content Compression - Dynamic Content Compression - Security -Request Filtering - Windows Authentication - Application Development -.NET Extensibility NET Extensibility ASP.NET ASP.NET ISAPI Extensions - ISAPI Filters - Management Tools - IIS Management Console - IIS 6 Management Compatibility - IIS 6 Metabase Compatibility - IIS 6 WMI Compatibility

4 IIS Service Settings 1 IIS Service Settings 2

5 Install Windows Assessment Deployment Kit Once all the settings are ticked click 'Next' until finished. The next step is to install Windows Assessment Deployment Kit (WADK). To download WADK click (Here), the page states it is for Windows 8 but this also works with Server Once WADK has been downloaded, run the install. Navigate through until you reach the screen below. Specifying Install Path Specify where you want WADK to be installed and click 'Next'. When asked make sure the following features are selected. - Deployment Tools - Windows Preinstallation Environment (Windows PE) - User State Migration Tool (USMT)

6 Selecting WADK Features Click 'Install' and let it do its thing. Forward Ports on Windows Firewall After that has finished we need to forward some ports on the Windows Firewall. On the server, open up the Metro interface and search for 'Windows Firewall' then select 'Windows Firewall with Advanced Security'. Click 'Inbound Rules' and then 'New Rule' on the right hand side. Once open select 'Port' and then create a rule for each of the following. Once one is done go through the same process until all are done. TCP Port SQL Server TCP Port SQL Admin Connection TCP Port SQL Service Broker TCP Port SQL Debugger/RPC TCP Port Analysis Service TCP Port SQL Browser TCP Port 80 - HTTP TCP Port SSL UDP Port SQL Browser UDP Port 67, 68, 69, PXE Boot TCP Port 8530, WSUS TCP Port WSUS SQL Server You will also need to forward ports for File and Printer Sharing. Click to create a new rule and select 'Predefined' and then select 'File and Printer Sharing'. This will forward all the ports required.

7 Firewall Settings Install SQL Server 2012 The next step is to install SQL Server Once loaded you will be greeted with a screen like this: SQL Server Initial Screen Click 'Installation' on the left. We want to create a new SQL install so select 'New SQL Server standalone installation...'. The installer will then check and setup some support roles. Let this finish and make sure they all say passed, do not worry if 'Windows Firewall' says 'Warning'. Click 'Next'.

8 SQL Setup Support Roles On the next screen make sure 'SQL Server Feature Installation' is selected and click 'Next'. SQL Server Feature Install On the 'Feature Selection' screen make sure the following features are selected: - Instance Features - Database Engine Services - SQL Server Replication - Full-Text and Semantic Extractions for Search - Reporting Services - Native - Shared Features - Management Tools - Basic - Management Tools - Complete -SQL Client Connectivity SDK

9 Click 'Next' when finished. SQL Feature Selection 1 SQL Feature Selection 2 Next we want to create a 'Named Instance'. We will need two in total, call the first one 'SCCM2012' or something similar and make sure the 'Instance ID' is the same.

10 SQL Instance Configuration Click Next. On the following screen you will need to input three of the accounts we created at the beginning of this guide into the top three fields. Do not touch the bottom two and make sure the 'Startup Type' is set to Automatic for the top three. Adding Service Accounts Once the accounts have been entered click on the 'Collation' tab at the top and then click 'Customize...'. On the screen that appears you will need to select the bottom of the two radio buttons and choose the collation, 'SQL_Latin1_General_CP1_CI_AS'. Make sure you have the correct collation as it could mess up the whole process. Click OK and you should then see a screen like below.

11 Setting Database Collation Click Next. On the next screen make sure 'Windows authentication mode' is selected. Below this click 'Add...' and add in the SQLAdmin account created at the beginning of the guide. Setting Authentication Mode Click Next. On the next screen make sure 'Install and Configure' is selected.

12 Setting Reporting Services Click Next. On the next screen wait for the program to finish Installing Configuration Rules. When it's finished they should all of passed. Installing Configuration Rules Click Next until prompted to install. Click to install and wait for the installation to finish. You may want to get a drink and something to eat at this point as it's going to take a while. Once everything has finished installing find and open 'SQL Server Configuration Manager'. In here you will need to expand both 'SQL Native Client 11.0 Configuration' and 'SQL Native Client 11.0 Configuration (32bit)'. In both of these click 'Client Protocols' and right click 'TCP/IP' on the right hand side and select 'Properties'. Make sure the properties are set as follows: Default Port: 1433 Enabled: Yes Keep Alive: Keep Alive Interval 1000

13 SQL TCP/IP Settings Next expand 'SQL Server Network Configuration', click on 'Protocols for SCCM2012' then right click TCP/IP on the right hand side and select 'Properties'. On the 'Protocol' tab change 'Listen All' to 'No'. TCP/IP Protocol Settings Next select the 'IP Addresses' tab at the top. There will be a few adapters in here. On each one make sure 'TCP Dynamic Ports' is left blank removing even those that just have 0 in the field. In the 'TCP Port' field on each one change it to '1433'. Lastly find the adapter that has the IP Address of the server you are working on and set its 'Enabled' value to 'Yes'.

14 TCP/IP IP Address Settings TCP/IP IP Address Settings 2 Click Next. After this find and open 'SQL Server Management Studio'. Once it has loaded up log in to the SCCM2012 Instance using 'Windows Authentication'. Once logged in right click the instance name on the left hand side and select 'Properties'. Click on 'Memory' and set both the 'Minimum server memory' and 'Maximum server memory' to the same value depending on how much RAM you have in

15 the server. In this scenario we have set the values to 8192 as we have 8GB RAM in the server. Setting Memory Settings Once that is all done the next thing is to install 'SQL Server 2012 Cumulative Update'. Version 2 or higher is required for this installation. You can find Version 5 (Here), click 'Hotfix Download Available' and select the update shown in the image below: SQL Cumulative Update Choice Once downloaded and installed the next step is to load up ADSI Edit on another machine that has Remote Server Admin Tools (RSAT) installed. You can get RSAT for Windows 7 (Here) and Windows 8 (Here). Once ADSI Edit is loaded, right click where it says 'ADSI Edit' on the left hand side then select 'Connect To'. Leave everything as it is then click 'OK'.

16 ADSI Edit Connection Once it has connected navigate down to 'CN=System' as shown below: ADSI Edit Container

17 Right click on 'CN=System' and select 'New > Object'. When it asks to select a class scroll down and select 'container'. ADSI Edit Select Container Click Next. On the next screen enter the value as 'System Management'. ADSI Edit Add Value Click Next until the container is created. Now right click on the container that was just created and select 'Properties'.

18 ADSI Edit Container Properties Go to the 'Security' tab and click 'Add...'. Refine the search to just include 'Computers' and then search for the SCCM Server and add it in. Once it is added give the server 'Full Control'. Security Settings

19 Refine Object Search Giving Server Full Control Once that is all done we can move on to the last step of setting up the Prerequisites, Extending the Active Directory Schema. Put the SCCM Disk into your soon to be SCCM Server. Open up the disk so you can see the files stored on the disk. Navigate to: SMSSETUP - > BIN - > I386

20 Copy this file path and then open Command Prompt, Run As Admin. Begin by typing 'D:' followed by right clicking the Command Prompt window and selecting 'Paste'. After the pasted text type 'extadsch.exe' and press enter. If it fails make sure the account you are using has been added to the 'Schema Admins' group in Active Directory. Extend Active Directory Schema Once that is done all the prerequisites are done and we are now ready to begin installing SCCM You will find how to do this in This is Part 2 of a 3 part guide explaining how to set up and install System Center Configuration Manager (SCCM) 2012 on Windows Server Before you continue to read this you may want to check out: Part 1 - Prerequisites as this part will be useless to you otherwise. So at the end of Part 1 we had just put the SCCM 2012 disk into the server that will become the SCCM 2012 Server. The next step is to run the installation of SCCM. To do this explore the disk to find the files on it and double click 'Splash.hta' then if prompted to open with a program just select the top option. You will then be presented with the start screen. SCCM 2012 Start Screen Click 'Install' to begin. On the 'Getting Started' screen select 'Install a Configuration Manager primary site' and click 'Next'.

21 Install Site Settings Next you will need to select 'Install the Licensed edition of this product' and input your license key for SCCM Entering License Key On the next two screens accept all the licensing check boxes and continue.

22 Accept License Terms 1 Accept License Terms 2 Once done, open up the C: Drive and create a folder called 'Prerequisites'. Create Prerequisites Folder

23 With that done, go back to the installer and on the next screen enter the path to the folder you just created into the 'Download required files' field. Saving Prerequisites Click 'Next'. You may have to wait for a little while for the Prerequisites to download. On the next screens select what languages you wish SCCM to use. Choose Language Packs After this you will be asked to specify a Site Code and Site Name. Name these relevant to your scenario and click 'Next' to continue.

24 Adding Site Code and Site Name On the next screen select 'Install the primary site as a stand-alone site' and then click 'Next'. Primary Site Options Then add in the name of the SQL Instance we created earlier for SCCM in the 'Instance name' field. The other fields should already be filled in.

25 Adding SQL Instance Click 'Next'. On the next screen leave the SMS Provider Settings as they are and click 'Next'. SMS Provider Settings On the next screen select 'Configure the communication method on each site system role'.

26 Client Computer Communication Settings Click 'Next'. On the screen after that leave the settings as they are and click 'Next'. Site System Roles All that's left is to check the summary and then begin the installation of SCCM. This process will take a while so go and grab some biscuits and while you wait you can read the third part of this guide This is Part 3 of a 3 part guide explaining how to set up and install System Center Configuration Manager (SCCM) 2012 on Windows Server Before you continue to read this you may want to check out: Part 2 - Installation otherwise there won't be anything to configure. At the end of Part 2 we left SCCM to install and now it should be done but we're not finished yet. The first thing to do is to find and open up 'Configuration Management Console'. It will look like this: Configuration Manager Icon

27 Once loaded up navigate to 'Administration' on the left hand side of the window. Expand 'Hierarchy Configuration' and right click 'Boundary Groups' then select 'Create Boundary Group'. Create Boundary Group Under the 'General' tab, name the Boundary Group '[Site Code] Boundary' where Site Code is whatever you set the Site Code to be. Create Boundary Group 2

28 Next go to the 'References' tab. Tick the box that says 'Use this boundary group for site assignment'. At the bottom of the window click 'Add...' and add the SCCM server. Once done click 'OK'. Create Boundary Group 3 Next right click 'Boundaries' on the left hand side of the window and select 'Create Boundary'. On the 'General' tab in 'Description' put 'AD Site' and then change the 'Type' selection box to 'Active Directory Site'. Call the 'Active Directory Site Name', 'Default-First-Site-Name'. Next move over to the 'Boundary Groups' tab and click 'Add...' then select the Boundary Group we previously created. Now we need to create another boundary. The second one will be called 'IP Scope' and change the 'Type' selection box to 'IP Address Range'. You will then need to enter the starting and ending IP addresses in your DHCP scope. Next go over to the 'Boundary Groups' tab and add the boundary group we created earlier.

29 Create Boundary Create Boundary 2 Once the two boundaries are created we need to go back to 'Administration' on the left hand side and click on 'Discovery Methods' then right click on 'Active Directory System Discovery' and then click 'Properties'.

30 Active Directory System Discovery On the 'General' tab tick 'Enable Active Directory System Discovery'. Below that click the yellow star to add an Active Directory Container. Put in the LDAP path to where your computers are located and Specify an account to be used to search the specified location. This will be the SCCM Admin account that was created earlier. Active Directory System Discovery Properties Next move to the 'Polling Schedule' tab and click 'Schedule...'. Here you can change how often SCCM will poll Active Directory, set this to how often you want it to run. In this scenario it is set to every 1 hour.

31 Active Directory System Discovery Polling Schedule Next move over to the 'Options' tab. Make sure 'Only discover computers that have logged on to a domain in a given period of time' is ticked. You can change the amount of time in days this setting uses but in this scenario we will be leaving it as the default 90 days. Active Directory System Discovery Options

32 Once this is done click 'OK' and make your way back to the main SCCM Console Window. The next thing to do is to set up User Discovery. In the same place as the System Discovery, right click 'Active Directory User Discovery' and select 'Properties'. Active Directory User Discovery Just like the System Discovery make sure it is 'Enabled' and set the path to the Active Directory Container for your users and set the SCCM Admin account as account that can search the container. Then again go to 'Polling Schedule' and change this to suit the needs of your scenario. Next go back to the main SCCM window and underneath the 'Active Directory User Discovery', right click 'Heartbeat Discovery' and select 'Properties'. Heartbeat Discovery On the next screen make sure 'Enable Heartbeat Discovery' is ticked and set the 'Send every:' to 1 hour.

33 Heartbeat Discovery Options Next thing to do is go back to the main SCCM Window and right click 'Distribution Point Groups' and select 'Create Group'. Create Distribution Point Group Once there give the group a name of [Site Code] DistGroup where [Site Code] is your Site Code. Then below click 'Add...' and add in the server SCCM is located on.

34 Distribution Point Settings Next on the main SCCM Window on the 'Administration' tab expand 'Site Configuration' and click on 'Sites'. On the right hand side right click on your site and select 'Add Site System Roles'. Add Site System Roles Once loaded click 'Next' on the 'General' and 'Proxy' sections but stop on the 'System Role Selection' window. Tick the following boxes: - Endpoint Protection Point (The following screenshot doesn't have it as it is already set up in this case but it will be there)

35 Site System Roles Click 'Next'. When asked accept the license terms and make sure you select 'Basic Membership' when asked and click 'Next' until finished. Configure Site Components Next go back to the main SCCM window. Then under 'Sites' right click on your site name on the right hand side, click on 'Configure Site Components' then click 'Software Distribution'. Go to the 'Network Access Account' tab and specify the account as the SCCM Admin we created earlier.

36 Set Network Access Account Click 'OK'. Next go back to the main SCCM window and again under 'Sites' right click on your site name on the right hand side, click on 'Client Installation Settings' and then 'Client Push Installation'. On the 'General' tab tick the following to Enable: Client Installation Settings - Enable automatic site-wide client push installation - Always install the Configuration Manager client on domain controllers

37 Client Push Settings Once done move to the 'Accounts' tab. Here add in the SCCM_Admin account created earlier. Client Push Add Account Next move to the last tab, 'Installation Properties'. This window should already have something in it like:

38 SMSSITECODE=[Your Site Code] If the above is not there then add it in then after it leave a space then type: SMSCACHESIZE=15360 Click 'OK' when done. Setting Client Push Cache Size Back on the main SCCM window and still in Administration expand 'Site Configuration' and click on 'Servers and Site System Roles'. At the bottom of the window find 'Distribution point', right click it and select 'Properties'.

39 Distribution Point Next go to the 'PXE' tab. On this screen tick the boxes to enable the following: - Enable PXE Support for Clients - Allow this distribution point to respond to incoming PXE requests - Enable unknown computer support Underneath these you will need to set a password. This is used when booting clients through PXE to log in and get advertised content. The password can be anything you want as long as you can remember it as you may need to use it quite often. Once finished go to the 'Content Validation' tab. On this screen enable 'Validate content on a schedule' then go in and set a custom schedule. In this scenario we have set the schedule to 1 Day. Distribution Point Schedule

40 Once done click 'OK' and go back to the main SCCM window. Now right click on 'Client Settings' and select 'Create Custom Client Device Settings'. Client Settings On the next screen enter a name in the 'Name' field. In this scenario it is called [Your Site Code] Device Client Settings. Below this tick the following boxes: - Endpoint Protection - Remote Tools - Software Deployment - Software Inventory - Software Metering Device Client Settings Choices You will notice as you click these boxes that they appear on the left hand side under 'General'. The next thing to do is go through these and change the following settings: Endpoint Protection: Change 'Manage Endpoint Protection Client on Client Computers' to 'Yes'. Remote Tool:

41 Change 'Enable Remote Control on Clients' to 'Enabled' and tick only 'Domain'. Change 'Prompt User for Remote Control Permission' to 'No' Software Deployment / Inventory / Metering: Change the 'Schedule' on each of these to a 'Simple Schedule' and set the time to '30 Minutes'. For the Custom Client Settings to work in your environment it will need to be deployed to the relevant collections. These will not be created yet however and we will be going over collections in a future post so for now just remember where the Client Settings are. Now for the last step of the configuration you will need to load up DHCP and change an option on your scope. To do this once in DHCP expand the scope(s) that have computers you wish to image through SCCM. Right click 'Scope Options' and select 'Configure Options'. On the 'General' tab you will need to scroll down and find Option '66 Boot Server Host Name'. When you click on this there is a text box below. In here put the name of the server that has SCCM followed by the Fully Qualified Domain Name (FQDN). e.g. servername.domain.place And that should be it. SCCM should be all set up and ready for you to use and help administrate your site. The first thing to do is to go into SCCM and just familiarise yourself with where stuff is located. Tune in for future guides on how to set up your collections, build and capture images and deploy software to machines. Hopefully this guide has been pretty self explanatory but if you have any issues during any part of the guide just drop us a comment and we will try our best to help you out, just be warned that we're not certified experts on SCCM we've just installed it this way about 5 or 6 times and it works for us.