Deploying a System Center 2012 R2 Configuration Manager Hierarchy

Deploying a System Center 2012 R2 Configuration Manager Hierarchy

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. The descriptions of other companies products in this proposal, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers. This deliverable is provided, AS IS without warranty of any kind and MICROSOFT MAKES NO WARRANTIES, EXPRES OR IMPLIED, OR OTHERWISE. All trademarks are the property of their respective companies. Printed in the United States of America 2010 Microsoft Corporation. All rights reserved. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of the actual companies and products mentioned herein may be the trademarks of their respective owners.

Objectives Prerequisites Estimated Time to Complete This Lab Computers used in this Lab After completing this lab, you will be able to: Prepare Active Directory for Configuration Manager publishing Install a Configuration Manager 2012 R2 central administration site Install a Configuration Manager 2012 R2 primary site server Install a Configuration Manager 2012 R2 secondary site server View status message activity related to site server installation Configure appropriate boundaries for the environment This lab requires three computers with all the prerequisites to be installed as Configuration Manager 2012 R2 site servers. The images for this lab include Central, which will be installed as the central administration site, Primary1, which will be installed as the primary site, and Secondary, which will be installed as a secondary site below Primary1. These prerequisites include a supported version of Windows Server 2008 R2, SQL Server 2008,.Net Framework 4.0, IIS configured properly, a domain controller, and so on. 75 Minutes Central Primary1 Secondary The password for the administrator account on all computers in this lab is: password. Deploying a Configuration Manager 2012 R2 Hierarchy Page 1

1 EXTENDING THE ACTIVE DIRECTORY SCHEMA FOR CONFIGURATION MANAGER 2012 R2 INTEGRATION In this exercise, you will prepare Active Directory for use with Configuration Manager 2012 R2. You will use a utility that is provided with Configuration Manager to extend the Active Directory schema for publishing by Configuration Manager. You will also grant rights for each of the Configuration Manager site servers to publish data to Active Directory. The computer Primary1 is the domain controller for the domain, so you will start the process on this computer. The Active Directory schema is the same for Configuration Manager 2012 R2 as it was for Configuration Manager 2012 RTM and SP1 (as it was for Configuration Manager 2007). Tasks Detailed steps Complete the following task on: 1. Extend the Active Directory schema for Configuration Manager 2. Grant the Configuration Manager site servers rights to Active Directory Primary1 1. Start C:\ConfigMgr2012R2\SMSSetup\Bin\x64 \Extadsch.exe. Note: A Command Prompt window appears as you extend the Active Directory schema for use by Configuration Manager. When the schema extension process has completed, the command prompt window closes. 2. Open C:\ExtADSch.log. Note: Notepad displays the contents of the Extadsch.log file. This file is created by the Extadsch.exe utility and reports on the Active Directory schema extension process. Notice that the schema extension process was successful, and that 14 attributes and four classes were added to Active Directory. 3. Verify that there are no errors listed in the log, and then close Notepad. Note: The site server will publish site data to Active Directory after it has been deployed, provided it has been granted the required permissions to publish its data. You can then view the System\System Management container to see the objects that a site server publishes to Active Directory when configured to do so. 1. Click Start Administrative Tools, and then click Active Directory Users and Computers. Note: The Active Directory Users and Computers window appears. 2. On the View menu, click Advanced Features. Note: The Active Directory Users and Computers window displays additional Active Directory information, including displaying the System container. You will grant rights to the System container to allow each of the Configuration Manager site server computers to publish their own site data to Active Directory, and create the System\System Management container that the sites publish their site data to. Deploying a Configuration Manager 2012 R2 Hierarchy Page 2

3. In the console tree, expand ConfigMgrDom.local, and then click System. 4. On the Action menu, click Properties. Note: The System Properties dialog box appears. 5. Click the Security tab. Note: The System Properties dialog box displays the security permissions on the System container. Notice that none of the Configuration Manager site server computers have been granted the rights to the System container. You will need to add permissions to all three potential site servers to publish their site s data to AD. 6. Click Add. Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears. 7. Click Object Types. Note: The Object Types dialog box appears. 8. Under Object types, click Computers, and then click OK. Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears. 9. In the Enter the object names to select field, type Central and then click OK. Note: The System Properties dialog box appears. Notice that the Configuration Manager site server computer (Central) is now listed with Read rights. 10. Under Permissions for Central, click Full Control under Allow, and then click Advanced. Note: The Advanced Security Settings for System dialog box appears displaying the rights for various accounts. 11. Under Name, click Central, and then click Edit. Note: The Permission Entry for System dialog box appears displaying the rights for ConfigMgrDom\Central$. 12. In the Apply to field, click This object and all descendant objects, and then click OK. Note: The Advanced Security Settings for System dialog box appears. 13. Click OK. Note: The System Properties dialog box appears. 14. Repeat steps 6 through 13 to add Primary1 and Secondary as site servers to publish to AD. 15. Click OK. Note: The Active Directory Users and Computers window appears. You can leave this window open if you want to view information that Configuration Manager publishes to Active Directory after installation. Deploying a Configuration Manager 2012 R2 Hierarchy Page 3

2 INSTALLING A CONFIGURATION MANAGER 2012 R2 CENTRAL ADMINISTRATION SITE In this exercise, you will install a Configuration Manager 2012 R2 central administration site on the computer Central. A supported version of SQL Server 2008 SP2 has already been installed on the computer, as well as all other required prerequisites. Tasks Detailed steps Complete the following task on: 1. Install a Configuration Manager 2012 R2 central administration site CAS (computer name is Central) 1. Start C:\ConfigMgr2012R2\Splash.hta. Setup window appears. Notice the options available in the window include installing Configuration Manager 2012, assessing server readiness, downloading the latest updates, installing the Configuration Manager console, and downloading System Center Updates Publisher. Also notice that you can access product documentation and help. 2. Click Install. Setup Wizard Before You Begin dialog box appears. 3. Click Next. Setup Wizard Available Setup Options dialog box displays options for installation. 4. Click Install a Configuration Manager central administration site, and then click Next. Setup Wizard Product Key dialog box appears prompting for a product key. In the lab environment, you will install an evaluation version of Configuration Manager 2012 as there is no product key available. The evaluation version is fully functional, other than it will stop working after 180 days. In your production environment, you'd supply your product key to install a nonevaluation implementation of Configuration Manager 2012. 5. If you do not have a valid product key, click Install the evaluation edition of this product, and then click Next. 6. If you do have a valid product key, in the Install the licensed edition of this product field, type your product key, and then click Next. Setup Wizard Microsoft Software License Terms dialog box appears displaying the license agreement. Read the licensing information. 7. Click to select I accept these license terms, and then click Next. Deploying a Configuration Manager 2012 R2 Hierarchy Page 4

Setup Wizard Prerequisite Licenses dialog box appears prompting for agreement to install the required prerequisite components. Notice that there are license agreements for Microsoft SQL Server 2012 Express, Microsoft SQL Server 2012 Native Client, and Microsoft Silverlight 5. SQL Server 2012 Express can be used for installation on a secondary site server. 8. Click to select the I accept these License Terms checkbox for each of the three components, and then click Next. Setup Wizard Prerequisite Downloads dialog box appears prompting for the location of the required prerequisite components. Notice that there are two options, one to download the required updates from the Internet, and the other to use a local source of the required files. As we re in a virtual environment, the required files have already been downloaded and staged for the lab. Be careful to select the correct option, or you may corrupt the already downloaded files and not be able to complete the installation without resetting the virtual image. 9. Click Use previously downloaded files, and then click Browse. Note: The Browse For Folder dialog box appears. 10. Point to C:\ConfigMgr2012R2\Redist, and then click OK. Setup Wizard Prerequisite Downloads dialog box appears displaying the location of the required prerequisite components. 11. Click Next. Note: The Configuration Manager Setup Downloader dialog box appears while verifying the prerequisite component files at the configured location. When complete, the dialog will close and then the System Center 2012 R2 Configuration Manager Setup Wizard Server Language Selection dialog box appears. 10. Open C:\ConfigMgrSetup.log. Note: Notepad displays the contents of the ConfigMgrSetup.log file. Setup writes progress of the setup process to this log, including the results of the prerequisite component verification. Notice that the verification process was successful, and that 13 files were validated in six different groups. 11. Verify that there are no errors listed in the log, and then close Notepad. Note: The Configuration Manager 2012 R2SP1 Beta Setup Wizard Server Language Selection dialog box appears prompting for the languages to be supported in the Configuration Manager console and reports. Configuration Manager can display the Configuration Manager console in the local language of the Deploying a Configuration Manager 2012 R2 Hierarchy Page 5

computer's language if enabled to do so, otherwise English is used. Enabling additional languages will cause Configuration Manager Setup to download the appropriate language packs. These language packs replace the localized versions of Configuration Manager from previous versions of the product. In the lab environment, there is no need to select any other server languages, however you may need additional languages in your production environment. 12. Click Next to install English. Setup Wizard Client Language Selection dialog box appears prompting for the languages to be supported for Configuration Manager clients (to replace the International Client Packs (ICP) from previous versions of Configuration Manager. Notice that English is selected by default. Any additional languages selected would cause the appropriate language packs to be downloaded by Setup. In the lab environment, there may not be any additional languages available for download. 13. Click Next to install English. Setup Wizard Site and Installation Settings dialog box appears prompting for information about the site to be installed. 14. In the Site code box, type CAS 15. In the Site name box, type Configuration Manager 2012 R2 Central Administration Site 16. Verify that the Installation folder box contains the default setting of C:\Program Files\ Microsoft Configuration Manager. 17. Verify that Install the Configuration Manager console is selected, and then click Next. Setup Wizard Central Administration Site Installation dialog box appears prompting if this installation is for the first site in a new hierarchy, or if you are installing the CAS to create a hierarchy from an existing stand-alone primary site (this is a new feature for Configuration Manager 2012 SP1 and Configuration Manager 2012 R2). 18. Verify that Install as the first site in a new hierarchy is selected, and then click Next. Setup Wizard Database Information dialog box appears prompting for the SQL Server computer (and instance if appropriate) to use, the name of the database for Configuration Manager, and the port for the SQL Server Service Broker. 19. Click Next to accept the default values of the Configuration Manager site server s installation of SQL Server, CM_CAS for the database name, and 4022 for the SQL Server Service Broker port. Setup Wizard Database Information dialog box appears Deploying a Configuration Manager 2012 R2 Hierarchy Page 6

prompting for the location to create the two required SQL Server files (data file and transaction log). Notice that the default configuration is to create these two files in the installed directory for SQL Server, which is in Program Files. It is not recommended to install SQL Server on the same drive as the operating system, however it is for the lab environment to reduce drives for the virtual machines. 20. Click Next to accept the default location for the data and log files. Setup Wizard SMS Provider Settings dialog box appears prompting for the computer on which to install the SMS Provider. The SMS Provider is a security layer between the administrator and the information in the Configuration Manager site database. Usually this is recommended to be installed on the SQL Server computer, unless using a clustered SQL Server environment. 21. Click Next to use the Configuration Manager site server for the SMS Provider. Setup Wizard Customer Experience Improvement Program dialog box appears prompting for participation in the customer experience improvement program. In the lab environment, there is no need to participate in this program, however in your production environment, it is recommended that you do participate. This response can be modified after site installation if you choose to change your response at a later time. 22. Click I don't want to join the program at this time, and then click Next. Setup Wizard Settings Summary dialog box appears displaying various configuration values to be used during the installation of Configuration Manager 2012. 23. Click Next. Note: The Configuration Manager Installation Prerequisite Check runs to validate that the computers targeted for Configuration Manager 2012 R2 installation meet the requirements for installation. When complete, the System Center 2012 R2 Configuration Manager Setup Wizard Prerequisite Check dialog box appears indicating the status of the validation process. Notice that there were no problems found with the configuration that will prevent installation. The first warning is for a lack of rights to publish to the System\System Management container in AD (which does not currently exist and will be created by the site server). The next two warnings are related to SQL Server memory - the fact that SQL Server is not configured to be limited in memory and that SQL Server does not have 8GB of memory allocated to it. None of these warnings prevent the site from installing and won t affect the lab environment. 24. Open the file %TEMP%\ConfigMgrAutoSave.ini. Deploying a Configuration Manager 2012 R2 Hierarchy Page 7

Note: The ConfigMgrAutoSave.ini file is created by Configuration Manager Setup automatically when starting the prerequisite check. This file is useful if you would like to perform an unattended installation of a site server using the /SCRIPT [script file] command line option of Setup. For example, you may want to configure a Windows scheduled task to silently install the site server after business hours. The settings within the script file can also be modified and used to install other site servers, as well. Another use for this file is if any prerequisites are missing and the installation of the prerequisite requires a reboot. You can use the script file to perform an unattended installation instead of having to run through the Configuration Manager Setup wizard and select all the same options again. 25. Close Notepad. Setup Wizard Prerequisite Check dialog box appears. 26. Click Begin Install. Setup Wizard Install dialog box appears displaying the status of the site installation, as well as listing individual tasks that are in progress and as they are completed as part of the Configuration Manager 2012 R2 installation. The time to install a Configuration Manager 2012 R2 central administration site will be dependent on the hardware available - it could take as little as 10 minutes, or more than 30 minutes to complete. When complete, the System Center 2012 R2 Configuration Manager Setup Wizard Install dialog box appears indicating that Setup completed each action successfully. 27. Click Close. Setup Wizard window appears. 28. Click Exit. Note: You have now installed a Configuration Manager 2012 R2 central administration site server. You will use the Configuration Manager console to verify the installation of the central administration site prior to installing a primary site in the hierarchy. In the following procedure, you will use Configuration Manager status messages generated by the site server installation to verify that the central administration site server installation was successful. You will begin by starting the Configuration Manager 2012 console. Tasks Detailed steps Complete the following task on: CAS (computer name is Central) 1. Start the Configuration 1. On the Start menu, click All Programs, expand Microsoft System Center 2012 R2, expand Deploying a Configuration Manager 2012 R2 Hierarchy Page 8

Manager console 2. View Configuration Manager status messages Configuration Manager, and then click Configuration Manager Console. console window appears displaying the Assets and Compliance Overview page. Notice that the window title includes the site code and site name of the site that the System Center 2012 R2 Configuration Manager console is connected to. You could also have started the Configuration Manager Console from the Start menu, as it is automatically pinned to the Start menu. 1. Click the Monitoring workspace. Note: The Monitoring workspace Overview page appears. 2. In the navigation pane, expand System Status, and then click Site Status. Note: The list of Configuration Manager site system roles and their status appears in the results pane. Notice that all four roles are installed with a status of "OK". 3. In the navigation pane, click Component Status. Note: The list of Configuration Manager components and their status appears in the results pane. 4. In the results pane, click SMS_SITE_COMPONENT_MANAGER, and then on the Ribbon, click Show Messages. Note: A new menu appears. 5. Click All. Note: The Status Messages: Set Viewing Period dialog box appears allowing you to configure the age of status messages to be displayed. Notice that the default value is to display status messages for the past 24 hours. 6. Click OK. Note: The Configuration Manager Status Message Viewer for <CAS> <Configuration Manager 2012 R2 Central Administration Site> window appears. Notice the message with the ID of 1027. It indicates that the site server was configured to receive Configuration Manager server components. 7. Click the message, and then on the View menu, click Detail. Note: The Status Message Details dialog box appears. Notice the header information for the message, as well as the text under Description. 8. Click OK. Note: The Configuration Manager Status Message Viewer for <CAS> <Configuration Manager 2012 R2 Central Administration Site> window appears. 9. On the File menu, click Exit. Note: The list of Configuration Manager components appears in the results pane. 10. Display all status messages for SMS_HIERARCHY_MANAGER. Deploying a Configuration Manager 2012 R2 Hierarchy Page 9

Note: The Configuration Manager Status Message Viewer for <CAS> <Configuration Manager 2012 R2 Central Administration Site> window appears. Notice the messages with message IDs of 3306. These messages indicate that Hierarchy Manager has successfully processed a site control file modification and updated the site database. 11. On the File menu, click Exit. Note: The list of Configuration Manager components appears in the results pane. 12. Display all status messages for SMS_WINNT_SERVER_DISCOVERY_AGENT. Note: The Configuration Manager Status Message Viewer for <CAS> <Configuration Manager 2012 R2 Central Administration Site> window appears. Notice the message with a message ID of 4202. This message indicates one server was discovered and discovery data was written for it. This occurred as a result of installing Configuration Manager site components on the site server computer. 13. On the File menu, click Exit. Note: The list of Configuration Manager components appears in the results pane. 14. Click the Administration workspace. Note: The Administration workspace Overview page appears. 15. In the navigation pane, expand Site Configuration, and then click Sites. Note: The list of sites appears in the results pane. Notice that we only have one site at this time, "CAS". Later in this lab you'll install primary and secondary sites, so additional sites will appear here. Also notice that the preview pane displaying summary information for the site. 16. In the navigation pane, click Servers and Site System Roles. Note: The list of Configuration Manager site systems appears in the results pane. Notice that the installed roles for the central administration site appear in the preview pane. Notice also that the Site server and Site database server roles have all been installed on the site server computer (as well as Site system and Component server ). A CAS does not include all the same site system roles that a primary site includes. Because no clients are managed by a central administration site, there is no need for a management point or a distribution point. After you install the primary and secondary sites, you will see additional site systems and roles. Deploying a Configuration Manager 2012 R2 Hierarchy Page 10

3 INSTALLING A CONFIGURATION MANAGER 2012 R2 PRIMARY SITE In this exercise, you will install a Configuration Manager 2012 R2 primary site on the computer Primary1. SQL Server 2008 SP2 has already been installed on the computer. This site will be connected to the central administration site that was just installed. Tasks Detailed steps Complete the following task on: 1. Install a child Configuration Manager 2012 R2 primary site Primary1 1. Start C:\ConfigMgr2012R2\Splash.hta. Setup window appears. Notice the options available in the window include installing Configuration Manager 2012, assessing server readiness, downloading the latest updates, installing the Configuration Manager console, and downloading System Center Updates Publisher. Also notice that you can access product documentation and help. 2. Click Install. Setup Wizard dialog box appears. 3. Click Next. Setup Wizard Available Setup Options dialog box displays options for installation. 4. Verify that Install a Configuration Manager primary site is selected, and then click Next. Setup Wizard Product Key dialog box appears prompting for a product key. In the lab environment, you will install an evaluation version of Configuration Manager 2012 R2 as there is no product key available. The evaluation version is fully functional, other than it will stop working after 180 days. In your production environment, you'd supply your product key to install a nonevaluation implementation of Configuration Manager 2012. 5. If you do not have a valid product key, click Install the evaluation edition of this product, and then click Next. 6. If you do have a valid product key, in the Install the licensed edition of this product field, type your product key, and then click Next. Setup Wizard Microsoft Software License Terms dialog box appears displaying the license agreement. Read the licensing information. 7. Click to select I accept these license terms, and then click Next. Deploying a Configuration Manager 2012 R2 Hierarchy Page 11

Setup Wizard Prerequisite Licenses dialog box appears prompting for agreement to install the required prerequisite components. Notice that there are license agreements for Microsoft SQL Server 2012 Express, Microsoft SQL Server 2012 Native Client, and Microsoft Silverlight 5. SQL Server 2012 Express can be used for installation on a secondary site server. A primary site requires a Standard or Enterprise edition of SQL Server 2008 or SQL Server 2008 R2 or later. 8. Click to select the I accept these License Terms checkbox for each of the three components, and then click Next. Setup Wizard Prerequisite Downloads dialog box appears prompting for the location of the required prerequisite components. Notice that there are two options, one to download the required updates from the Internet, and the other to use a local source of the required files. As we re in a virtual environment, the required files have already been downloaded and staged for the lab. 9. Click Use previously downloaded files, and then click Browse. Note: The Browse For Folder dialog box appears. 10. Point to C:\ConfigMgr2012R2\Redist, and then click OK. Setup Wizard Prerequisite Downloads dialog box appears displaying the location of the required prerequisite components. Be careful to select the correct option, or you may corrupt the already downloaded files and not be able to complete the installation without resetting the virtual image. 11. Click Next. Note: The Configuration Manager Setup Downloader dialog box appears while verifying the prerequisite component files at the configured location. If successful, the dialog will close and then the System Center 2012 R2 Configuration Manager Setup Wizard Server Language Selection dialog box appears. 12. Open C:\ConfigMgrSetup.log. Note: Notepad displays the contents of the ConfigMgrSetup.log file. Setup writes progress of the setup process to this log, including the results of the prerequisite component verification. Notice that the verification process was successful, and that 13 files were validated in six different groups. 13. Verify that there are no errors listed in the log, and then close Notepad. Setup Wizard Server Language Selection dialog box appears prompting for additional server languages to be installed Deploying a Configuration Manager 2012 R2 Hierarchy Page 12

for the Configuration Manager console and reports. Configuration Manager can display the Configuration Manager console in the local language of the computer's language if enabled to do so, otherwise English is used. Enabling additional languages will cause Configuration Manager Setup to download the appropriate language packs. These language packs replace the localized versions of Configuration Manager from previous versions of the product. In the lab environment, there is no need to select any other server languages, however you may need additional languages in your production environment. 14. Click Next to install English. Setup Wizard Client Language Selection dialog box appears prompting for additional languages to be installed for Configuration Manager clients. Any additional language packs selected will be downloaded by Setup. In the lab environment, there is no requirement to download any additional languages, however you may need to do so in your production environment. 15. Click Next to install English. Setup Wizard Site and Installation Settings dialog box appears prompting for information about the site to be installed. 16. In the Site code box, type PR1 17. In the Site name box, type Configuration Manager 2012 R2 Primary Site 1 18. Verify that the Installation folder box contains the default setting of C:\Program Files\Microsoft Configuration Manager. 19. Verify that Install the Configuration Manager console is selected, and then click Next. Setup Wizard Primary Site Installation dialog box appears allowing you to configure whether this site will be joined with other servers in a hierarchy or if it will be a stand-alone site. 20. Verify that Join the primary site to an existing hierarchy is selected, and then in the Central administration site server (FQDN) box, type Central Note: If you type the name of the central administration site as a NetBIOS name, it will be automatically converted to FQDN as it is identified. 21. Click Next. Setup Wizard Database Information dialog box appears prompting for the SQL Server computer (and instance if required) to use, as well as the name of the database for Configuration Manager and the port to use for the SQL Server Service Broker. 22. Click Next to accept the default values of the Configuration Manager site server s installation of SQL Server, CM_PR1 for the database name, and 4022 for the Deploying a Configuration Manager 2012 R2 Hierarchy Page 13

SQL Server Service Broker port. Setup Wizard Database Information dialog box appears prompting for the location to create the two required SQL Server files (data file and transaction log). Notice that the default location is in Program Files, which is not recommended for a production environment. The recommendation is for a unique drive to install SQL Server. 23. Click Next to accept the default location. Setup Wizard SMS Provider Settings dialog box appears prompting for the computer on which to install the SMS Provider. 24. Click Next to use the Configuration Manager site server for the SMS Provider. Setup Wizard Client Computer Communication Settings dialog box appears prompting for the protocol that clients will use to communicate with the site, either HTTP or HTTPS. This is a new configuration option in Configuration Manager 2012 that replaces the mixed/native mode setting from Configuration Manager 2007. 25. Click Configure the communication method on each site system role, and then click Next. Setup Wizard Site System Roles dialog box appears prompting for which additional site system roles should be installed by Setup and the computer name(s) on which each role should be installed. Since Configuration Manager requires a management point and a distribution point, Setup will install them on the site server computer by default. Notice that both site system roles are configured for HTTP given the configuration on the previous wizard page. 26. Click Next. Setup Wizard Customer Experience Improvement Program dialog box appears prompting for participation in the customer experience improvement program. In the lab environment, there is no need to join the program. However for your production environment, we do recommend that you participate in the program. You can change this configuration from the Configuration Manager console after the site has been installed. 27. Click I don't want to join the program at this time, and then click Next. Setup Wizard Setting Summary dialog box appears displaying various configuration values to be used during the installation of Configuration Manager 2012 R2. 28. Click Next. Note: The Configuration Manager Installation Prerequisite Check Deploying a Configuration Manager 2012 R2 Hierarchy Page 14

runs to validate that the computers targeted for Configuration Manager 2012 installation meet the requirements for installation. When complete, the System Center 2012 R2 Configuration Manager Setup Wizard Prerequisite Check dialog box appears indicating the status of the validation process. Notice that there were no problems found with the configuration that will prevent installation. There are two warnings regarding SQL Server configuration which do not prevent installation of the primary site server. 29. Open the file %TEMP%\ConfigMgrAutoSave.ini. Note: The ConfigMgrAutoSave.ini file is created by Configuration Manager Setup automatically when starting the prerequisite check. This file is useful if you would like to perform an unattended installation of a site server using the /SCRIPT [script file] command line option of Setup. For example, you may want to configure a Windows scheduled task to silently install the site server after business hours. The settings within the script file can also be modified and used to install other site servers, as well. Another use for this file is if any prerequisites are missing and the installation of the prerequisite requires a reboot. You can use the script file to perform an unattended installation instead of having to run through the Configuration Manager Setup wizard and select all the same options again. 30. Close Notepad. Setup Wizard Prerequisite Check dialog box appears. 31. Click Begin Install. Setup Wizard Install dialog box appears displaying the status of the site installation, as well as the individual tasks that are in progress or have been completed as part of the Configuration Manager 2012 R2 installation. The time to install a Configuration Manager 2012 R2 site will be dependent on the hardware available - it could take as little as 10 minutes, or more than 30 minutes, to complete a primary site installation. When complete, the System Center 2012 R2 Configuration Manager Setup Wizard Install dialog box appears indicating that Setup completed each action successfully. Setup may actually complete and allow you to close the Setup wizard before all components have completed installation. If you leave the Setup wizard open, eventually all components should install, and indicate that they were installed. It is recommended to leave Setup running until all options are listed as completed. If you close before all options have completed installation, the System Center 2012 R2 Configuration Manager console may start in read-only mode until database replication has completed. 32. Click Close. Setup Wizard window appears. Deploying a Configuration Manager 2012 R2 Hierarchy Page 15

33. Click Exit. Note: You have now installed a Configuration Manager 2012 R2 primary site in a hierarchy as a child of a central administration site. You will now start the Configuration Manager 2012 R2 console to verify the site installation, and perform some configuration of the primary site. Once you have completed those steps, you will then install a secondary site under the primary site to create a three-tier hierarchy. Deploying a Configuration Manager 2012 R2 Hierarchy Page 16

In the following procedure, you will use Configuration Manager status messages generated by the site server installation to verify that the primary site server installation was successful. You will begin by starting the Configuration Manager console. Tasks Detailed steps Complete the following task on: 1. Start the Configuration Manager console 2. View Configuration Manager status messages, replication status, and site status Primary1 1. On the Start menu, click All Programs, expand Microsoft System Center 2012 R2, expand Configuration Manager, and then click Configuration Manager Console. console window appears displaying the Assets and Compliance Overview page. Notice that the window title includes the site code and site name of the site that the System Center 2012 R2 Configuration Manager console is connected to. You could also start the Configuration Manager Console from the Start menu, as it is automatically pinned to the Start menu. 1. Click the Monitoring workspace. Note: The Monitoring Overview page appears. 2. In the navigation pane, expand System Status, and then click Site Status. Note: The list of Configuration Manager site system roles and their status appears in the results pane. Notice that the status of all six installed site system roles is listed as "OK". This is a quick check that status appears "OK" for the installed site. 3. In the navigation pane, click Component Status. Note: The list of Configuration Manager components and their status appears in the results pane. You saw this from the central administration site earlier. You can view any messages from any components that you need here. As you already saw this process earlier in this lab, you do not need to view them again unless you see an error or warning state. It is common for a few components to display a warning state after an initial site installation. You can generally ignore those unless you see error conditions or many components with status other than OK. Note: You may observe a critical value for the SMS_DISCOVER_DATA_MANAGER component, this is due to the environment and would age off after a period of 24 hours. This will have no impact on the outcome of the lab 4. In the navigation pane, click Database Replication. Note: The status of the SQL replication processing between the central administration site and the primary site appears in the results pane. Notice that the preview pane displays details on global and site data replication for the selected link. Until the status of the "Link State" displays "Link Active", you should not do any administration of the environment from the primary site, only the central administration site. Deploying a Configuration Manager 2012 R2 Hierarchy Page 17

5. Click the Administration workspace. Note: The Administration Overview page appears. 6. In the navigation pane, expand Site Configuration, and then click Sites. Note: The list of Configuration Manager sites appears in the results pane. Notice that the local site is the only one displayed as the Configuration Manager console is connected to the local site s database, and there are no other sites below this site. Notice the preview pane displays summary information for the site selected in the results pane. Notice also that the Parent Site Code value is displayed as CAS, which is the parent site for the local primary site. If you were at the central administration site and accessed this same node, you would see both sites displayed in the results pane. 7. In the navigation pane, click Servers and Site System Roles. Note: The list of Configuration Manager site systems appears in the results pane. Notice that the installed roles appear in the preview pane for the one site system in the site. Notice also that the Site server, Site database server, Management point, and Distribution point roles have all been installed on the site server computer (as well as Site system and Component server ). If you were accessing this node from the central administration site, you would be able to see site systems and installed roles for both sites displayed in the results pane. In the following procedure, you will add an IP address range as a Configuration Manager 2012 boundary for the primary site. You then will create a boundary group, which will include this new boundary. This will designate which clients are to be managed by this specific Configuration Manager site clients that have IP addresses within the configured range of IP addresses. Tasks Detailed steps Complete the following task on: 1. Configure Configuration Manager to an IP address range as a boundary Primary1 1. Click the Administration workspace. Note: The Administration workspace appears displaying the available site systems in the local site "PR1". 2. In the navigation pane, expand Hierarchy Configuration, and then click Boundaries. Note: The list of boundaries for the hierarchy appears in the results pane. Notice that there are no default boundaries added to the hierarchy. All primary sites in a hierarchy, as well as the central administration site, will display boundaries for all sites, as boundary information is considered global data. You could also create the boundary from the central administration site, and it Deploying a Configuration Manager 2012 R2 Hierarchy Page 18

would replicate down to the primary site for use. 3. On the Ribbon, click Create Boundary. Note: The Create Boundary dialog box appears allowing the creation of a new boundary. 4. In the Description box, type IP address range for Primary Site 1 5. In the Type box, click IP address range. 6. In the Starting IP address box, type 192.168.3.10 7. In the Ending IP address box, type 192.168.3.19 8. Click OK. Note: The list of boundaries for all sites appears in the results pane. Notice that the new IP address range now appears as a boundary for the hierarchy in the results pane. As the central administration site does not manage clients, boundaries are not required to be configured for a central administration site. 9. In the navigation pane click Boundary Groups. Note: The list of boundary groups for the hierarchy appears in the results pane. Notice that there are no default boundary groups added to the hierarchy. However in order to assign clients to a site through discovery, and for clients to access content from distribution points, you must create a boundary group with appropriate boundaries. Boundary groups are also global data, so will replicate to all primary sites, as well as the central administration site, in the hierarchy. 10. On the Ribbon, click Create Boundary Group. Note: The Create Boundary Group dialog box appears allowing the creation of a new boundary group. 11. In the Name box, type Primary Site 1 Clients and then click Add. Note: The Add Boundaries dialog box appears allowing the addition of new boundaries to this group. 12. Under Boundaries, click to select 192.168.3.10-192.168.3.19, and then click OK. Note: The Create Boundary Group dialog box appears displaying the configuration of this boundary group. 13. Click the References tab. Note: The Create Boundary Group dialog box appears allowing the use of this boundary group for site assignment, as well as the addition of appropriate site systems to this boundary group. You would add appropriate distribution points and state migration points for each boundary group. 14. Click to select Use this boundary group for site assignment. Note: The Create Boundary Group dialog box appears indicating that this boundary group will now be used to assign resources to "PR1". 15. Under Site system servers, click Add. Note: The Add Site Systems dialog box appears allowing you Deploying a Configuration Manager 2012 R2 Hierarchy Page 19

to select the appropriate site systems (distribution points and state migration points) to add to this boundary group. 16. Under Site systems, click to select \\Primary1, and then click OK. Note: The Create Boundary Group dialog box appears displaying the site systems added to this boundary group. 17. Click OK. Note: The new boundary group appears in the results pane. Notice that it indicates that there is one member (boundary) in the boundary group, as well as one site system. You are now ready to install manage clients in this site. You will not install clients in this lab, however you will now install a secondary site as a child of this primary site. You can experience client deployment in the Deploying Configuration Manager 2012 R2 lab, which installs a stand-alone primary site, as well as a client. Deploying a Configuration Manager 2012 R2 Hierarchy Page 20

4 INSTALLING A CONFIGURATION MANAGER 2012 R2 SECONDARY SITE In this exercise, you will install a Configuration Manager 2012 R2 secondary site on the computer Secondary as a child of the primary site you just installed. SQL Server is not installed on the computer, so it will be installed as part of the remote installation of the secondary site. You will begin by adding the primary site server as an administrator on the secondary site computer, which is required to install a secondary site via a push install. Tasks Detailed steps Complete the following task on: 1. Grant administrative rights for the primary site server computer at the secondary site computer Secondary 1. On the Start menu, point to Administrative Tools, and then click Computer Management. Note: The Computer Management window appears. 2. In the tree pane, expand Local Users and Groups, and then click Groups. Note: The list of local group accounts appears in the results pane. The primary site server computer account is required to be a local Administrator on the secondary site server computer in order to successfully install a secondary site. This is because the primary site will push the installation of the secondary site with a package that is copied to the root of drive C on the target secondary site server as well as install a service on the secondary site server to perform the site installation. 3. In the results pane, click Administrators, and then on the Action menu, click Properties. Note: The Administrators Properties dialog box appears displaying the members of the local Administrators group. Notice that the primary site server computer account is not listed. 4. Click Add. Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears. 5. Click Object Types. Note: The Object Types dialog box appears. Notice that the Computers object is not selected by default. 6. Under Object types, click to select Computers, and then click OK. Note: The Select Users, Computers, Service Accounts, or Groups dialog box appears. 7. In the Enter the object names to select box, type Primary1 and then click OK. Note: The Administrators Properties dialog box appears displaying the members of the local Administrators group. Notice that the primary site server computer account is now listed as a member of the group. Formatted: Outline numbered + Level: 3 + Numbering Style: 1, 2, 3, + Aligned at: 0.15" + Tab after: 0.4" + Indent at: 0.4" Formatted: Font: Bold Formatted: Font: Bold Formatted: Font: Bold Deploying a Configuration Manager 2012 R2 Hierarchy Page 21

8. Click OK, and then close the Computer Management window. Note: Now that the primary site server computer account has been granted administrator rights on the secondary site computer, you can initiate the secondary site installation from the System Center 2012 R2 Configuration Manager console at the primary site. In the following procedure, you will initiate the secondary site installation from the parent primary site. In order to complete a secondary site installation, the parent primary site requires admin rights, which you just provided in the previous procedure. Tasks Detailed steps Complete the following task on: Primary1 1. Install a secondary site 1. In the navigation pane of the Administration workspace, expand Site Configuration, and then click Sites. Note: The list of Configuration Manager sites appear in the results pane. Notice that the local site, PR1, is the only site listed. 2. In the results pane, click PR1, and then on the Ribbon, click Create Secondary Site. Note: The Create Secondary Site Wizard Before You Begin dialog box appears. Notice that the secondary site will automatically be deployed with a management point and a distribution point. 3. Click Next. Note: The Create Secondary Site Wizard General dialog box appears allowing you to configure the site code, site server FQDN, site name, and installation directory. 4. In the Site code box, type SEC 5. In the Site server name box, type secondarysecondary Note: If you only supply the computer name, the wizard resolves it into the FQDN automatically, which is Secondary.ConfigMgrDom.local in the lab environment. 6. In the Site name box, type Configuration Manager 2012 R2 Secondary Site and then click Next to accept the default installation folder of C:\Program Files\Microsoft Configuration Manager. Note: The Create Secondary Site Wizard Installation Source Files dialog box appears allowing you to configure where the installation source files to install the secondary site reside. 7. Verify that Copy installation source files over the network from the parent site server is selected, and then click Next. Deploying a Configuration Manager 2012 R2 Hierarchy Page 22

Note: The Create Secondary Site Wizard SQL Server Settings dialog box appears allowing you to configure the location of the SQL Server that will be used by the secondary site. Configuration Manager 2012 secondary sites require SQL Server, which can be a full installation of SQL Server or a SQL Server Express installation. As no SQL Server installation exists on the secondary site server, you will have the secondary site installation process install SQL Server Express automatically. Notice that you can designate the SQL Server and SQL Server Service Broker ports for use between the two site servers. 8. Verify that Install and configure a local copy of SQL Server Express on the secondary site computer is selected, verify that the default ports of 1433 and 4022 are listed, and then click Next. Note: The Create Secondary Site Wizard Distribution point dialog box appears allowing you to configure the distribution point that will be installed on the secondary site server automatically. 9. Click to select Install and configure IIS if required by Configuration Manager, and then click Next to use the default options for all other distribution point options. Note: The Create Secondary Site Wizard Drive Settings dialog box appears allowing you to configure the drive(s) that the distribution point that will be installed on the secondary site server automatically will use. Notice that by default, Configuration Manager will automatically select the drive to use. 10. Click Next to use the default drive configuration. Note: The Create Secondary Site Wizard Content Validation dialog box appears allowing you to enable content validation for the distribution point. There is no need to enable this in the lab environment. 10. Click Next to not enable scheduled content validation. Note: The Create Secondary Site Wizard Boundary Groups dialog box appears allowing you to configure the boundary group that clients in this secondary site can use to communicate with the local management point and distribution point. 11. Click Create to create a new boundary group for the secondary site. Note: The Create Boundary Group dialog box appears allowing the creation of a new boundary group. 12. In the Name box, type Secondary Site Clients 13. Click to select Use this boundary group for site assignment, and then in the Assigned site box, verify that PR1-Configuration Manager 2012 R2 Primary Site 1 is listed. 14. Click OK. Note: The Create Secondary Site Wizard Boundary Groups dialog box appears displaying the new boundary group for the secondary site. At this point in time, the actual boundary for the secondary site has not been created. So you only created the Deploying a Configuration Manager 2012 R2 Hierarchy Page 23