Home > Articles > Home & Office Computing > Entertainment/Gaming/Gadgets

  • Print
  • + Share This
This chapter is from the book

Configuring Sites

Configuration Manager 2012 deploys certain Site System roles such as Management Points and Distribution Points, but does not deploy other roles nor completely configure those that it does deploy by default. Site configuration entails completing the configuration of the deployed roles and deploying of the required roles.

When deploying Site System roles to either the Site Server or a remote server, it is important to note the component installation wizard doesn’t actually do the installation—it simply queues the installation for the Site Component Manager service. Even through the wizard always completes with a successful message, it is important to review the corresponding log files and the System Status container to ensure the component was actually installed correctly.

The log files for component installation are typically located on the server the component is being installed on, in a folder called \Program Files\Microsoft Configuration Manager\Logs. Additional status messages can be viewed in the sitecomp.log file on the Primary Site Server.

Deploying the Fallback Status Point Role

The Fallback Status Point (FSP) is very important. It provides a safety net for clients. The Configuration Manager agent should always be able to communicate status messages to the FSP, even if other communication has failed or is being blocked due to certificate or other issues.

To install FSP, complete the following steps:

  1. From within the Administration space, expand Site Configuration and select Servers and Site Systems Roles.
  2. Right-click CM2 and select Add Site System Roles.
  3. On the General page, click Next.
  4. Enable the Fallback Status Point role and click Next.
  5. Accept the default configuration and click Next.
  6. Review the summary and click Next.
  7. Wait for the installation to complete, and then close the wizard.

Review the fspMSI.log and the SMSFSPSetup.log files for installation status. During normal operation, problems can be identified with the fspmgr.log file and using reports such as the Client Deployment Status Details or the Client Deployment Failure report.

Deploying the Reporting Service Point Role

The Reporting Service Point (RSP) provides reporting of Configuration Manager data through SQL Reporting Services (SRS). SRS is a significantly more powerful platform for developing and delivering reports.

The Reporting Service Point component is installed in three steps. Initially, the role is added to the correct server from the Site Management\Site Systems node. Then the Reporting Point needs to be configured with a data source; this is necessary to establish communication with the database holding the Configuration Manager data. Finally, reports need to be migrated from the legacy Reporting Point to the Reporting Service Point.

To install RSP on the Central Administration Site (CM1), complete the following steps:

  1. From within the Administration space, select Servers and the Site System Roles folder.
  2. Right-click CM1 and select Add Site System Roles.
  3. On the General page, click Next.
  4. Enable the Reporting Services Point role and click Next.
  5. The Site Database Connection Settings will be discovered automatically. Click the Verify button to verify the settings.
  6. In the Reporting Services Point Account, click the Set button and choose New Account.
  7. Enter the appropriate credentials, and then click OK.
  8. Click Next.
  9. Review the summary and click Next.
  10. Wait for the installation to complete, and then close the wizard.

This process should be completed not only for the Central Administration Site, but also for each primary site as well. This allows each of the sites to generate reports covering their specific information. For example, reports generated from the Central Administration Site in San Francisco will include information from the entire Company XYZ hierarchy. Reports generated from either the SFO or PAR primary sites will only include information from their portion of the hierarchy.

Review the SRSRPSetup.log and the srsrp.log files. These log files are located on the server hosting the Reporting Service Point in the Configuration Manager log folder (often c:\Program Files\Microsoft Configuration Manager\Logs). To check the status of the Reporting Services Point, go to the Monitoring space in the console, expand the Reporting folder, and select the Reports node. Reports will be listed there once the role is completed deploying.

Deploying Software Updates Point Role

For Site Servers that will be supporting the Software Updates role, there are two parts to the role setup. The first is to set up Windows Server Update Services (WSUS) and the second is to set up the Software Update Point role. In a Configuration Manager 2012 hierarchy that includes a Central Administration Site, the Software Update Point role will be installed on the Central Administration Site Server.

The Windows Server Update Services (WSUS) 3.0 SP2 components are required by Configuration Manager to support synchronization of patch data from Microsoft Update. WSUS is not used to deliver patches to managed systems; instead, the Configuration Manager hierarchy is used to effectively create an enterprise patch delivery and installation system.

To install WSUS 3.0 SP2, do the following on the Central Site Server (CM1 in the Company XYZ hierarchy):

  1. Launch Windows Server Manager.
  2. Right-click on the Roles folder and select Add Roles.
  3. Click Next to skip the Welcome page.
  4. Check the Windows Server Update Services role.
  5. Click the Add Required Role Services if it pops up.
  6. Click Next.
  7. Click Next and Next past the Web Server (IIS) options.
  8. At the WSUS welcome screen, click Next.
  9. At the Confirmation screen, click Install.
  10. Once the Windows Server Update Services 3.0 SP2 Setup Wizard launches, at the Welcome screen click Next.
  11. Accept the terms of the license agreement and click Next.
  12. Store the updates on c:\WSUS and click Next.
  13. Select Using an Existing Database Server on This Computer.
  14. Click Next.
  15. If the connection is successful, click Next.
  16. Leave the default website preference and then click Next.
  17. Review the installation configuration and click Next.
  18. Close the wizard when the installation is complete.
  19. In the Before You Begin page of the Windows Server Update Services Configuration Wizard, click Cancel.

Once the Windows WSUS role has been installed, the next step is to deploy the Software Update Point role. To do this, complete the following steps:

  1. On the Central Administration Site Server (CM1 in the Company XYZ hierarchy), launch the Configuration Manager console.
  2. In the Administration space, expand the Site Configuration folder and select the Servers and Site System Roles node.
  3. Right-click the Central Administration Site Server, in this case CM1, and choose Add Site System Roles.
  4. Click Next.
  5. Check the Software Update Point role and click Next.
  6. At the Software Update Point screen, leave the defaults and click Next.
  7. At the Active Settings screen, check the Use This Server as the Active Software Update Point check box and click Next.
  8. At the Synchronization Source screen, leave the defaults and click Next.
  9. At the Synchronization Schedule screen, check the Enable Synchronization on a Schedule check box.
  10. Change the schedule to run every 1 Days and click Next.
  11. At the Supersedence Rules screen, leave the default and click Next.
  12. At the Classifications screen, check All Classifications and click Next.
  13. At the Products screen, check the required products and click Next.
  14. At the Languages screen, check the appropriate languages and click Next.
  15. Review the summary screen and then click Next.
  16. Close the wizard when completed.

The Central Administration Site will now perform update synchronization for the entire Configuration Manager 2012 hierarchy.

Deploying Endpoint Protection Point Role

In Configuration Manager 2012, the System Center 2012 Endpoint Protection is integrated into the product rather than a separate install. There is now a Site Server role called Endpoint Protection Point, which provides endpoint protection services.

In a Configuration Manager 2012 hierarchy that includes a Central Administration Site, the Endpoint Protection Point role will be installed on the Central Administration Site Server.

To deploy the Endpoint Protection Point role, complete the following steps:

  1. On the Central Administration Site Server (CM1 in the Company XYZ hierarchy), launch the Configuration Manager console.
  2. In the Administration space, expand the Site Configuration folder and select the Servers and Site System Roles node.
  3. Right-click the Central Administration Site Server, in this case CM1, and choose Add Site System Roles.
  4. Click Next.
  5. Check the Endpoint Protection Point role.
  6. There will be a pop-up warning that software updates require special configuration or endpoint protection needs to use a different source. Click OK.
  7. Click Next.
  8. At the Endpoint Protection screen, accept the license terms and click Next.
  9. Choose the appropriate Microsoft Active Protections Service (MAPS) membership type and click Next.
  10. Review the summary screen and then click Next.
  11. Close the wizard when completed.

The Central Administration Site will now perform endpoint protection for the entire Configuration Manager 2012 hierarchy.

Deploying Asset Intelligence Synchronization Point Role

An additional component called the Asset Intelligence Synchronization Point is also available. This component provides integration between Configuration Manager and Microsoft System Center Online services provided by Microsoft.

In a Configuration Manager 2012 hierarchy that includes a Central Administration Site, the Asset Intelligence Synchronization Point role will be installed on the Central Administration Site Server.

To deploy the Asset Intelligence Synchronization Point role, follow these steps:

  1. On the Central Administration Site Server (CM1 in the Company XYZ hierarchy), launch the Configuration Manager console.
  2. In the Administration space, expand the Site Configuration folder and select the Servers and Site System Roles node.
  3. Right-click the Central Administration Site Server, in this case CM1, and choose Add Site System Roles.
  4. Click Next.
  5. Check the Asset Intelligence Synchronization Point role and click Next.
  6. At the Asset Intelligence Synchronization Point Settings screen, leave the defaults and click Next.
  7. At the Proxy Server Settings screen, leave the defaults and click Next.
  8. At the Synchronization Schedule screen, leave the Enable Synchronization on a Schedule check box checked.
  9. Change the schedule to run every one days and click Next.
  10. Review the summary screen and then click Next.
  11. Close the wizard when completed.

The Central Administration Site will now perform asset intelligence synchronization for the entire Configuration Manager 2012 hierarchy.

Preparing for OS Deployment

To support OS deployment user state migration and using network boot, the State Migration Point and PXE-enabled Distribution Point are required. To also support a complete operating system refresh with the ability to capture the users’ existing settings, store them securely on the network, then reapply them to the new operating system; the State Migration Point is required.

The PXE functionality requires the WDS transport feature. This is available by default on Windows Server 2008, and can be installed automatically during the PXE configuration.

To enable CM2 to support PXE for OS deployment, complete the following steps:

  1. Launch the Configuration Manager console.
  2. In the Administration space, expand the Site Configuration folder and select the Servers and Site System Roles node.
  3. Select the Primary Site Server, in this case CM2, and choose the Distribution Point role from the details window below.
  4. Right-click the Distribution Point role and select Properties.
  5. Select the PXE tab.
  6. Enable PXE support for clients.
  7. Click Yes after reviewing the ports information pop-up.
  8. Check the Allow This Distribution Point to Respond to Incoming PXE Requests check box.
  9. Check the Enable Unknown Computer Support check box and click OK to the warning pop-up.
  10. Uncheck the Require a Password when Computers Use PXE check box.
  11. Click OK to save changes to the Distribution Point.

The next step is to install the State Migration Point. This allows systems that are undergoing operating system deployment to upload the captured user state and then download the captured user state once the operating system is upgraded.

To deploy the State Migration Point role, follow these steps:

  1. Launch the Configuration Manager console.
  2. In the Administration space, expand the Site Configuration folder and select the Servers and Site System Roles node.
  3. Right-click the Primary Site Server, in this case CM2, and choose Add Site System Roles.
  4. Click Next.
  5. Select the State Migration Point and click Next.
  6. Click the orange “*” to specify a new folder to store state.
  7. Enter a folder to use, such as c:\StateMigration and click OK.
  8. Click Next.
  9. Leave the default boundary groups and click Next.
  10. Review the summary screen and then click Next.
  11. Close the wizard when completed.

The preceding steps to configure PXE functionality and state migration functionality need to be completed on each Distribution Point and Site Server where Operating System Deployment (OSD) functionality is needed. Typically, this is all Primary Site Servers and all secondary site servers in the Configuration Manager 2012 hierarchy, as well as locations with just Distribution Points.

  • + Share This
  • 🔖 Save To Your Account