1. On a computer that has Internet access, open Windows Explorer, and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.

2. Double-click Setupdl.exe. The Setup Downloader opens.

3. Specify the path for the folder that will host the updated installation files, and then click Download. Setup Downloader verifies the files that are currently in the download folder and downloads only the files that are missing or are newer than the existing files. Setup Downloader creates subfolders for the downloaded languages. Setup Downloader will create the folder if it does not exist.

   Security Note
   To run the Setup Downloader application, you must have Full Control NTFS file system permissions to the download folder.

4. View the ConfigMgrSetup.log file in the root of the drive C to review the download results.

1. Open a Command Prompt window and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.

2. Type setupdl.exe to open Setup Downloader. Optionally, you can use the following command-line options:

   • /VERIFY: Use this option to verify the files in the download folder, which include language files. Review the ConfigMgrSetup.log file in the root of the drive C for a list of files that are outdated. No files are downloaded when you use this option.
     
     
   • /VERIFYLANG: Use this option to verify the language files in the download folder. Review the ConfigMgrSetup.log file in the root of the drive C for a list of language files that are outdated.
     
     
   • /LANG: Use this option to download only the language files to the download folder.
     
     
   • /NOUI: Use this option to start Setup Downloader without displaying the user interface. When you use this option, you must specify the download path as part of the command line.
     
     
   • <DownloadPath>: You can specify the path to the download folder to automatically start the verification or download process. You must specify the download path when you use the /NOUI option. When you do not specify a download path, you must specify the path when Setup Downloader opens. Setup Downloader will create the folder if it does not exist.
     
     

     Security Note
     To run the Setup Downloader application, you must have Full Control NTFS file system permissions to the download folder.

    

   Usage examples:

   • setupdl \\MyServer\MyShare\ConfigMgrUpdates
     
     Setup Downloader starts, verifies the files in the \\MyServer\MyShare\ConfigMgrUpdates folder, and downloads only the files that are missing or are newer than the existing files.
     
     
   • setupdl /VERIFY c:\ConfigMgrUpdates
     
     Setup Downloader starts and verifies the files in the C:\ConfigMgrUpdates folder.
     
     
   • setupdl /NOUI c:\ConfigMgrUpdates
     
     Setup Downloader starts, verifies the files in the \\MyServer\MyShare\ConfigMgrUpdates folder, and downloads only the files that are missing or are newer than the existing files.
     
     
   • setupdl /LANG c:\ConfigMgrUpdates
     
     Setup Downloader starts, verifies the language files in the C:\ConfigMgrUpdates folder, and downloads only the language files that are missing or are newer than the existing files.
     
     
   • setupdl /VERIFY
     
     Setup Downloader starts, you must specify the path to the download folder, and after you click Verify, Setup Downloader verifies the files in the download folder.
     
     

3. View the ConfigMgrSetup.log file in the root of the drive C to review the download results.

1. In Windows Explorer, browse to one of the following locations:

   • <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.
     
     
   • <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.
     
     

2. Copy the following files to the destination folder on the other computer:

   • Prereqchk.exe
     
     
   • Prereqcore.dll
     
     
   • Basesql.dll
     
     
   • Basesvr.dll
     
     
   • Baseutil.dll
     
     

1. In Windows Explorer, browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.

2. Open prereqchk.exe to start Prerequisite Checker.

   Prerequisite Checker detects existing sites, and if found, performs checks for upgrade readiness. If no sites are found, all checks are performed. The Site Type column provides information about the site server or site system with which the rule is associated.

1. Open a Command Prompt window and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.

2. Type prereqchk.exe /LOCAL to start Prerequisite Checker and run all prerequisite checks on the server.

1. Open a Command Prompt window and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.

2. Type prereqchk.exe and choose from the following command-line options to check requirements for a primary site installation.

   Command-line option	Required	Description
   /NOUI	No	Starts Prerequisite Checker without displaying the user interface. You must specify this option before any other option in the command line.
   /PRI	Yes	Verifies that the local computer meets the requirements for the primary site.
   /SQL <FQDN of SQL Server>	Yes	Verifies that the specified computer meets the requirements for SQL Server to host the Configuration Manager site database.
   /SDK <FQDN of SMS Provider>	Yes	Verifies that the specified computer meets the requirements for the SMS Provider.
   /JOIN <FQDN of central administration site>	No	Verifies that the local computer meets the requirements for connecting to the central administration site server.
   /MP <FQDN of management point>	No	Verifies that the specified computer meets the requirements for the management point site system role. This option is only supported when you use the /PRI option.
   /DP <FQDN of distribution point>	No	Verifies that the specified computer meets the requirements for the distribution point site system role. This option is only supported when you use the /PRI option.
   /Ssbport	No	Verifies that a firewall exception is in effect to allow communication for the SQL Server Service Broker (SSB) port. The default is port number 4022.
   InstallDir <ConfigMgrInstallationPath>	No	Verifies minimum disk space on requirements for site installation.

    

   Usage examples (optional options are displayed in brackets):

   • prereqchk.exe [/NOUI] /PRI /SQL <FQDN of SQL Server> /SDK <FQDN of SMS Provider> [/JOIN <FQDN of central administration site>] [/MP <FQDN of management point>] [/DP <FQDN of distribution point>]
     
     

   When you run the command, unless you use the NOUI option, Prerequisite Checker opens and starts scanning the specified servers by using prerequisite checks that are applicable to the specified command-line options. Prerequisite Checker creates a list in the Prerequisite result section for any detected problems.

3. Click an item in the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you install the site server, site system, or Configuration Manager console. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review Prerequisite Checker results. The log file can contain additional information that are not displayed in the user interface.

1. Open a Command Prompt window and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.

2. Type prereqchk.exe and choose from the following command-line options to check requirements for a central administration site installation.

   Command-line option	Required	Description
   /NOUI	No	Starts Prerequisite Checker without displaying the user interface. You must specify this option before any other option in the command line.
   /CAS	Yes	Verifies that the local computer meets the requirements for the central administration site.
   /SQL <FQDN of SQL Server>	Yes	Verifies that the specified computer meets the requirements for SQL Server to host the Configuration Manager site database.
   /SDK <FQDN of SMS Provider>	Yes	Verifies that the specified computer meets the requirements for the SMS Provider.
   /Ssbport	No	Verifies that a firewall exception is in effect to allow communication on the SSB port. The default is port number 4022.
   InstallDir <ConfigMgrInstallationPath>	No	Verifies minimum disk space on requirements for site installation.

    

   Usage examples (optional options are displayed in brackets):

   • prereqchk.exe /CAS /SQL <FQDN of SQL Server> /SDK <FQDN of SMS Provider> /Ssbport 4022
     
     
   • prereqchk.exe /NOUI /CAS /SQL <FQDN of SQL Server> /SDK <FQDN of SMS Provider>
     
     

   When you run the command, unless you use the NOUI option, Prerequisite Checker opens and starts scanning the specified servers by using prerequisite checks that are applicable to the specified command-line options. Prerequisite Checker creates a list in the Prerequisite result section for any problems that are found.

3. Click an item in the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you install the site server, site system, or Configuration Manager console. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the prerequisite checker results. The log file can contain additional information that are not displayed in the user interface.

1. On the primary site server from which you plan to install the secondary site, open a Command Prompt window and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.

2. Type prereqchk.exe and choose from the following command-line options to check requirements for a secondary site installation on a remote server.

   Command-line option	Required	Description
   /NOUI	No	Starts Prerequisite Checker without displaying the user interface. You must specify this option before any other option in the command line.
   /SEC <FQDN of secondary site server>	Yes	Verifies that the specified computer meets the requirements for the secondary site.
   /INSTALLSQLEXPRESS	No	Verifies that SQL Server Express can be installed on the specified computer.
   /Ssbport	No	Verifies that a firewall exception is in effect to allow communication for the SQL Server Service Broker (SSB) port. The default is port number 4022.
   /Sqlport	No	Verifies that a firewall exception is in effect to allow communication for the SQL Server service port and that the port is not in use by another named instance of SQL Server. The default port is 1433.
   InstallDir <ConfigMgrInstallationPath>	No	Verifies minimum disk space on requirements for site installation.
   SourceDir	No	Verifies that the computer account of the secondary site can access the folder that hosts the source files for Setup.

    

   Usage examples (optional options are displayed in brackets):

   • prereqchk.exe /SEC /Ssbport 4022 /SourceDir <Source Folder Path>
     
     
   • prereqchk.exe [/NOUI] /SEC <FQDN of secondary site> [/INSTALLSQLEXPRESS]
     
     

   When you run the command, unless you use the NOUI option, Prerequisite Checker opens and starts scanning the specified servers by using prerequisite checks that are applicable to the specified command-line options. Prerequisite Checker creates a list in the Prerequisite result section for any problems that are found.

3. Click an item in the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you install the site server, site system, or Configuration Manager console. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the prerequisite checker results. The log file can contain additional information that is not displayed in the user interface.

1. On the primary site server from which you install the secondary site, open a Command Prompt window and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64 or <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.

2. Type prereqchk.exe /Adminui to check requirements for Configuration Manager console installation on the local computer.

    

   When you run the command, Prerequisite Checker opens and starts scanning the specified servers by using prerequisite checks that are applicable to the specified command-line options. Prerequisite Checker creates a list in the Prerequisite result section for any detected problems.

3. Click an item in the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you install the site server, site system, or Configuration Manager console. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the prerequisite checker results. The log file can contain additional information that is not displayed in the user interface.

1. In Windows Explorer, browse to <ConfigMgrInstallationPath>\Tools\ConsoleSetup\LanguagePack.

2. Rename the .msp and .mst files. For example, you could change <file name>.MSP to <file name>.MSP.disabled.

3. Install the Configuration Manager console on the computer.

   Important
   When new server languages are configured for the site server, the .msp and .mst files are recopied to the LanguagePack folder, and you must repeat this procedure to install new Configuration Manager consoles in only English.

1. On the computer that is running the Configuration Manager console, close the Configuration Manager console.

2. In Windows Explorer, browse to <ConsoleInstallationPath>\Bin\ on the Configuration Manager console computer.

3. Rename the appropriate language folder for the language that is configured on the computer. For example, if the language settings for the computer were set for German, you could rename the de folder to de.disabled.

4. To open the Configuration Manager console in the language that is configured for the computer, rename the folder to the original name. For example, rename de.disabled to de.

1. Verify that the administrative user who runs Setup has the following security rights:

   • Local Administrator rights on the central administration site server computer.
     
     
   • Local Administrator rights on each computer that hosts one of the following:
     
     
     • The site database
       
       
     • An instance of the SMS Provider for the site
       
       
     • A management point for the site
       
       
     • A distribution point for the site
       
       
   • Sysadmin (SA) rights on the instance of SQL Server that hosts the site database.
     
     

2. On the central administration site computer, open Windows Explorer and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.

3. Double-click Setup.exe. The Configuration Manager Setup Wizard opens.

4. On the Before You Begin page, click Next.

5. On the Getting Started page, select Install a Configuration Manager central administration site, and then click Next.

6. On the Product Key page, choose whether to install Configuration Manager as an evaluation or a full installation. Enter your product key for the full installation of Configuration Manager. Click Next.

   If you install Configuration Manager as an evaluation, after 180 days the Configuration Manager console becomes read-only until you activate the product with a product key from the Site Maintenance page in Setup.

7. On the Microsoft Software License Terms page, read and accept the license terms, and then click Next.

8. On the Prerequisite Licenses page, read and accept the license terms for the prerequisite software, and then click Next. Setup downloads and automatically installs the software on site systems or clients when it is required. You must select all check boxes before you can continue to the next page.

9. On the Prerequisite Downloads page, specify whether Setup must download the latest prerequisite redistributable files, language packs, and the latest product updates from the Internet or use previously downloaded files, and then click Next. If you previously downloaded the files by using Setup Downloader, select Use previously downloaded files and specify the download folder. For information about Setup Downloader, see the Setup Downloader section in this topic.

   Note
   When you use previously downloaded files, verify that the path to the download folder contains the most recent version of the files.

10. On the Server Language Selection page, select the languages that are available for the Configuration Manager console and for reports, and then click Next. English is selected by default and cannot be removed.

11. On the Client Language Selection page, select the languages that are available to client computers, specify whether to enable all client languages for mobile device clients, and then click Next. English is selected by default and cannot be removed.

    Important
    If you are installing a central administration site to expand a stand-alone primary site, select the same client languages that are installed at the stand-alone primary site.

12. On the Site and Installation Settings page, specify the site code and site name for the site. For more information about site code naming, including best practices and limitations, see the Configuration Manager Site Naming section in this topic.

13. Specify the installation folder and whether Setup will install the Configuration Manager console on the local computer, and then click Next. The folder path must not contain trailing spaces or Unicode characters.

    Warning
    You cannot change the installation folder after Setup is finished. Verify that the disk drive has enough disk space before you continue.

14. If you are using Configuration Manager with no service pack, skip to step 15.

    On the Central Administration Site Installation page, select the option that is appropriate to your scenario:

    • To install a central administration site as the first site of a new hierarchy, select Install as the first site in a new hierarchy, and then click Next to continue.
      
      
    • To install a central administration site to expand an existing stand-alone primary site into a hierarchy, select Expand an existing stand-alone primary into a hierarchy, specify the FQDN of the stand-alone primary site server, and then click Next to continue.
      
      

      Note
      The stand-alone primary site must run the same version of Configuration Manager as the version that you use to install the central administration site.

15. On the Database Information page, specify the information for the site database server and the SQL Server Service Broker (SSB) port that the SQL Server is to use, and then click Next. You must specify a valid port that no other site or service is using, and that no firewall restrictions block.

    Important
    With Configuration Manager with no service pack, when you configure the site database to use the default instance of SQL Server, you must configure the SQL Server service port to use TCP port 1433, the default port. With Configuration Manager SP1, you can use a nondefault TCP port for the default instance.

    Note
    Typically, the Service Broker is configured to use TCP port 4022, but other ports are supported.

16. On the SMS Provider Settings page, specify the FQDN for the server that hosts the SMS Provider, and then click Next. You can configure additional SMS providers for the site after the initial installation.

17. On the Customer Experience Improvement Program Configuration page, choose whether to participate, and then click Next.

18. On the Settings Summary page, review the setting and verify that they are accurate. Click Next to start Prerequisite Checker to verify server readiness for the central administration site server.

19. On the Prerequisite Installation Check page, if no problems are listed, click Next to install the central administration site. When Prerequisite Checker finds a problem, click an item in the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you continue setup. After you resolve the issue, click Run Check to restart prerequisite checking. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the Prerequisite Checker results. The log file can contain additional information that is not displayed in the user interface. For a complete list of installation prerequisite rules and descriptions, see Technical Reference for the Prerequisite Checker in Configuration Manager.

20. On the Installation page, Setup displays the overall installation status. When Setup completes the core site server installation, you can close the wizard. Site configuration continues in the background.

    Note
    You can connect a Configuration Manager console to the central administration site before the site installation finishes, but the console connects to the site by using a read-only console. The read-only console lets you view objects and configuration settings but prevents you from introducing any change that could be lost when the site installation finishes.

1. Verify that the administrative user that runs Setup has the following security rights:

   • Local Administrator rights on the central administration site server computer
     
     
   • Sysadmin rights on the site database of the central administration site
     
     
   • Local Administrator rights on the primary site server computer
     
     
   • Local Administrator rights on each computer that hosts one of the following at the primary site:
     
     
     • The site database
       
       
     • An instance of the SMS Provider for the site
       
       
     • A management point for the site
       
       
     • A distribution point for the site
       
       
   • Sysadmin rights on the instance of SQL Server that hosts the site database
     
     
   • Role-based administration rights that are equivalent to the security role of Infrastructure Administrator or Full Administrator
     
     

   Note

   Setup automatically configures the-sender address to use the computer account for the primary site server. This account must have Read, Write, Execute, and Delete NTFS file system permissions on the SMS\Inboxes\Despoolr.box\Receive folder on the central administration site server. Also, your security policy must allow the account Access this computer from the network rights on the central administration site. After Setup is finished, you can change the account to a Windows user account if it is required. For example, you must change the account to a Windows user account if your central administration site is in a different forest. For more information about communication requirements across forest trusts, see Planning for Communications Across Forests in Configuration Manager.

2. On the new primary site computer, open Windows Explorer and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.

3. Double-click Setup.exe. The Configuration Manager Setup Wizard opens.

4. On the Before You Begin page, click Next.

5. On the Getting Started page, select Install a Configuration Manager primary site, verify that Use typical installation options for a stand-alone primary site is cleared, and then click Next.

6. On the Product Key page, choose whether to install Configuration Manager as an evaluation or a full installation. Enter your product key for the full installation of Configuration Manager. Click Next.

   If you install Configuration Manager as an evaluation, after 180 days the Configuration Manager console becomes read-only until you activate the product from the Site Maintenance page in the Setup Wizard.

7. On the Microsoft Software License Terms page, read and accept the license terms, and then click Next.

8. On the Prerequisite Licenses page, read and accept the license terms for the prerequisite software, and then click Next. Setup downloads and automatically installs the software on site systems or clients when it is required. You must select all check boxes before you can continue to the next page.

9. On the Prerequisite Downloads page, specify whether Setup will download the latest prerequisite redistributable files, language packs, and the latest product updates from the Internet or use previously downloaded files, and then click Next. If you previously downloaded the files by using Setup Downloader, select Use previously downloaded files and specify the download folder. For information about Setup Downloader, see the Setup Downloader section in this topic.

   Note
   When you use previously downloaded files, verify that the path to the download folder contains the most recent version of the files.

10. On the Server Language Selection page, select the languages that are available for the Configuration Manager console and for reports, and then click Next. English is selected by default and cannot be removed.

11. On the Client Language Selection page, select the languages that are available to client computers, specify whether to enable all client languages for mobile device clients, and then click Next. English is selected by default and cannot be removed.

12. On the Site and Installation Settings page, specify the site code and site name for the site. For more information about site code naming, including best practices and limitations, see the Configuration Manager Site Naming section in this topic.

13. Specify the installation folder and whether Setup will install the Configuration Manager console on the local computer, and then click Next. The folder path must not contain trailing spaces or Unicode characters.

    Warning
    You cannot change the installation folder after Setup is finished. Verify that the disk drive has enough disk space before you proceed.

14. On the Primary Site Installation page, select Join the primary site to an existing hierarchy, specify the FQDN for the central administration site, and then click Next. Setup verifies that the primary site server has access to the central administration site server, and that the site code for the central administration site can be retrieved by using the security credentials of the administrative user that is running Setup.

15. On the Database Information page, specify the information for the site database server and the SQL Server Service Broker (SSB) port that SQL Server is to use, and then click Next. You must specify a valid port that no other site or service is using, and that no firewall restrictions block. Typically, the Service Broker is configured to use TCP port 4022, but other ports are supported.

    Important
    With Configuration Manager without a service pack, when you configure the site database to use the default instance of SQL Server, you must configure the SQL Server service port to use TCP port 1433, the default port. With Configuration Manager SP1, you can use a nondefault TCP port for the default instance.

16. On the SMS Provider Settings page, specify the FQDN for the server that will host the SMS Provider, and then click Next. You can configure additional SMS providers for the site after the initial installation.

17. On the Client Computer Communication Settings page, choose whether to configure all site systems to accept only HTTPS communication from clients or for the communication method to be configured for each site system role, and then click Next. When you select All site system roles accept only HTTPS communication from clients, the client computer must have a valid PKI certificate for client authentication. When you select Configure the communication method on each site system role, you can choose Clients will use HTTPS when they have a valid PKI certificate and HTTPS-enabled site roles are available. This ensures that the client selects a site system that is configured for HTTPS if is available. For more information about PKI certificate requirements, see PKI Certificate Requirements for Configuration Manager.

18. On the Site System Roles page, choose whether to install a management point or distribution point. When selected for installation, enter the FQDN for site system and select the client connection method. Click Next. If you selected All site system roles accept only HTTPS communication from clients on the previous page, the client connection settings are automatically configured for HTTPS and cannot be changed unless you go back and change the setting.

    Note
    The site system installation account is automatically configured to use the primary site’s computer account to install the site system role. If you have to use an alternate installation account for remote site systems, you should not select the roles in the Setup Wizard and install them later from the Configuration Manager console.

19. On the Customer Experience Improvement Program Configuration page, choose whether to participate, and then click Next.

20. On the Settings Summary page, review the setting and verify that they are accurate. Click Next to start Prerequisite Checker to verify server readiness for the primary site server and for specified site system roles.

21. On the Prerequisite Installation Check page, if no problems are listed, click Next to install the primary site and site system roles that you selected. When Prerequisite Checker finds a problem, click an item on the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you continue setup. After you resolve the issue, click Run Check to restart prerequisite checking. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the Prerequisite Checker results. The log file can contain additional information that is not displayed in the user interface. For a complete list of installation prerequisite rules and descriptions, see Technical Reference for the Prerequisite Checker in Configuration Manager.

22. On the Installation page, Setup displays the overall installation status. When Setup completes the core site server and site system installation, you can close the wizard. Site configuration continues in the background.

    Note
    You can connect a Configuration Manager console to a primary site before the site installation finishes, but the console will connect to the site by using a read-only console. The read-only console lets you view objects and configuration settings but prevents you from introducing any change that could be lost when the site installation finishes.

1. Verify that the administrative user who runs Setup has the following security rights:

   • Local Administrator rights on the primary site server computer
     
     
   • Local Administrator rights on each computer that hosts one of the following:
     
     
     • The site database
       
       
     • An instance of the SMS Provider for the site
       
       
     • A management point for the site
       
       
     • A distribution point for the site
       
       
   • Sysadmin rights on the instance of SQL Server that hosts the site database.
     
     

2. On the new primary site computer, open Windows Explorer and browse to <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.

3. Double-click Setup.exe. The Configuration Manager Setup Wizard opens.

4. On the Before You Begin page, click Next.

5. On the Getting Started page, select Install a Configuration Manager primary site, verify that Use typical installation options for a stand-alone primary site is not selected, and then click Next.

6. On the Product Key page, choose whether to install Configuration Manager as an evaluation or a full installation. Enter your product key for the full installation of Configuration Manager. Click Next.

   If you install Configuration Manager as an evaluation, after 180 days the Configuration Manager console becomes read-only until you activate the product with a product key from the Site Maintenance page in Setup.

7. On the Microsoft Software License Terms page, read and accept the license terms, and then click Next.

8. On the Prerequisite Licenses page, read and accept the license terms for the prerequisite software, and then click Next. Setup downloads and automatically installs the software on site systems or clients when it is required. You must select all check boxes before you can continue to the next page.

9. On the Prerequisite Downloads page, specify whether Setup will download the latest prerequisite redistributable files, language packs, and the latest product updates from the Internet or use previously downloaded files, and then click Next. If you previously downloaded the files by using Setup Downloader, select Use previously downloaded files and specify the download folder. For information about Setup Downloader, see the Setup Downloader section in this topic.

   Note
   When you use previously downloaded files, verify that the path to the download folder contains the most recent version of the files.

10. On the Server Language Selection page, select the languages that will be available for the Configuration Manager console and for reports, and then click Next. English is selected by default and cannot be removed.

11. On the Client Language Selection page, select the languages that will be available to client computers, specify whether to enable all client languages for mobile device clients, and then click Next. By default, English is selected and cannot be removed.

12. On the Site and Installation Settings page, specify the site code and site name for the site. For more information about site code naming, including best practices and limitations, see the Configuration Manager Site Naming section in this topic.

13. Specify the installation folder and whether Setup will install the Configuration Manager console on the local computer, and then click Next. The folder path must not contain trailing spaces or Unicode characters.

    Warning
    You cannot change the installation folder after Setup finishes. Verify that the disk drive has enough disk space before you proceed.

    Important
    If you selected Use typical installation options for a stand-alone primary site, skip to step 17 - the Customer Experience Improvement Program Configuration page.

14. On the Primary Site Installation page, select Install the primary site as a stand-alone site, and then click Next. Click Yes to confirm that you want to install the site as a stand-alone site.

    Important
    You cannot join the stand-alone primary site to a central administration site after Setup finishes.

15. On the Database Information page, specify the information for the site database server and the SQL Server Service Broker (SSB) port that SQL Server is to use, and then click Next. You must specify a valid port that no other site or service is using, and that no firewall restrictions block. Typically, the Service Broker is configured to use TCP port 4022, but other ports are supported.

    Important
    With Configuration Manager with no service pack, when you configure the site database to use the default instance of SQL Server, you must configure the SQL Server service port to use TCP port 1433, the default port. With Configuration Manager SP1, you can use a nondefault TCP port for the default instance.

16. On the SMS Provider Settings page, specify the FQDN for the server that will host the SMS Provider, and then click Next. You can configure additional SMS providers for the site after the initial installation.

17. On Client Communication Settings page, choose whether to configure all site systems to accept only HTTPS communication from clients or for the communication method to be configured for each site system role, and then click Next. When you select to All site system roles accept only HTTPS communication from clients, client computer must have a valid PKI certificate for client authentication. For more information about PKI certificate requirements, see PKI Certificate Requirements for Configuration Manager.

18. On the Site System Roles page, choose whether to install a management point or distribution point. When selected for installation, enter the FQDN for site system and choose the client connection method. Click Next. When you selected All site system roles accept only HTTPS communication from clients on the previous page, the client connection settings are automatically configured for HTTPS and cannot be changed unless you go back and change the setting.

    Note
    The site system installation account is automatically configured to use the primary site’s computer account to install the site system role. If you have to use an alternate installation account for remote site systems, you should not select the roles in the Setup Wizard and install them later from the Configuration Manager console.

19. On the Customer Experience Improvement Program Configuration page, choose whether to participate, and then click Next.

20. On the Settings Summary page, review the setting and verify that they are accurate. Click Next to start Prerequisite Checker to verify server readiness for the primary site server and site system roles.

21. On the Prerequisite Installation Check page, if no problems are listed, click Next to install the primary site and site system roles. When Prerequisite Checker finds a problem, click an item on the list for details about how to resolve the problem. You must resolve all items in the list that have an Error status before you continue Setup. After you resolve the issue, click Run Check to restart prerequisite checking. You can also open the ConfigMgrPrereq.log file in the root of the system drive to review the Prerequisite Checker results. The log file can contain additional information that is not displayed in the user interface. For a complete list of installation prerequisite rules and descriptions, see Technical Reference for the Prerequisite Checker in Configuration Manager.

22. On the Installation page, Setup displays the overall installation status. When Setup completes the core site server and site system installation, you can close the wizard. Site configuration continues in the background.

    Note
    You can connect a Configuration Manager console to the primary site before the site installation finishes, but the console will connect to the site by using a read-only console. The read-only console lets you view objects and configuration settings but prevents you from introducing any change that could be lost when the site installation finishes.

1. Verify that the following security rights exist:

   • The administrative user who configures the installation of the secondary site in the Configuration Manager console must have role-based administration rights that are equivalent to the security role of Infrastructure Administrator or Full Administrator.
     
     
   • The computer account of the parent primary site must be a Local Administrator on the secondary site server computer.
     
     
   • When the secondary site uses a previously installed instance of SQL Server to host the secondary site database:
     
     
     • The computer account of the parent primary site must have sysadmin rights on the instance of SQL Server on the secondary site server computer.
       
       
     • The Local System account of the secondary site server computer must have sysadmin rights on the instance of SQL Server on the secondary site server computer.
       
       

2. In the Configuration Manager console, click Administration.

3. In the Administration workspace, expand Site Configuration, and then click Sites.

4. On the Home tab, in the Site group, click Create Secondary Site. The Create Secondary Site Wizard opens.

5. On the Before You Begin page, confirm that the primary site that is listed is the site in which you want this secondary site to be a child, and then click Next.

6. On the General page, specify the following settings:

   • Site code: Specify a site code for the secondary site. For more information about site code naming, including best practices and limitations, see the Configuration Manager Site Naming section in this topic.
     
     
   • Site server name: Specify the FQDN for the secondary site server. Verify that the server meets the requirements for secondary site installation. For more information about supported configurations, see Supported Configurations for Configuration Manager.
     
     
   • Site name: Specify a name for the secondary site.
     
     
   • Installation folder: Specify the installation folder to create on the secondary site server.
     
     

   Click Next.

   Important

   You can click Summary to use the default settings in the wizard and go directly to the Summary page. Use this option only when you are familiar with the settings in this wizard. Boundary groups are not associated with the distribution point when you use the default settings. As a result, clients do not use the distribution point that is installed on this secondary site as a content source location. For more information about boundary groups, see the Create and Configure Boundary Groups for Configuration Manager section in the Configuring Boundaries and Boundary Groups in Configuration Manager topic.

7. On the Installation Source Files page, specify the location for the installation files for the secondary site, and then click Next. You can copy the files from the parent site to the secondary site, use the source files from a network location, or use source files that are already available locally on the secondary site server.

   When you choose the Use the source files at the following network location or Use the source files at the following location on the secondary site computer options, the location must contain the Redist subfolder with the prerequisite redistributable files, language packs, and the latest product updates for Setup. Use Setup Downloader to download the required files to the Redist folder before you install the secondary site. The secondary site installation will fail if the files are not available in the Redist subfolder. For more information about Setup Downloader, see Setup Downloader in this topic.

   Note
   The folder or share name that you choose for the Setup installation source files must use only ASCII characters.

   Security Note
   The computer account for the secondary site must have Read NTFS file system permissions and share permissions to the Setup source folder and share. Avoid using administrative network shares (for example, C$ and D$) because they require the secondary site computer account to be an administrative user on the remote computer.

8. On the SQL Server Settings page, specify whether the secondary site will use SQL Server Express or an existing instance of SQL Server for the site database, and then configure the associated settings.

   Important
   With Configuration Manager with no service pack, when you configure the site database to use the default instance of SQL Server, you must configure the SQL Server service port to use TCP port 1433, the default port. With Configuration Manager SP1, you can use a nondefault TCP port for the default instance.

   Install and configure a local copy of SQL Express on the secondary site computer

   • SQL Server Service port: Specify the SQL Server service port for SQL Server Express to use. The service port is typically configured to use TCP port 1433, but you can configure another port.
     
     
   • SQL Server Broker port: Specify the SQL Server Service Broker (SSB) port for SQL Server Express to use. The Service Broker is typically configured to use TCP port 4022, but you can configure a different port. You must specify a valid port that no other site or service is using, and that no firewall restrictions block.
     
     

   Use an existing SQL Server instance

   • SQL Server FQDN: Review the FQDN for the SQL Server computer. You must use a local SQL Server to host the secondary site database and cannot modify this setting.
     
     
   • SQL Server instance: Specify the instance of SQL Server to use as the secondary site database. Leave this option blank to use the default instance.
     
     
   • ConfigMgr site database name: Specify the name to use for the secondary site database.
     
     
   • SQL Server Broker port: Specify the SQL Server Service Broker (SSB) port for SQL Server to use. You must specify a valid port that no other site or service is using, and that no firewall restrictions block.
     
     

     Note
     Setup does not validate the information that you enter on this page until it starts the installation. Before you continue, verify these settings.

   Click Next.

9. On the Distribution Point page, configure the general distribution point settings.

   • Install and configure IIS if required by Configuration Manager: Select this setting to let Configuration Manager install and configure Internet Information Services (IIS) on the server if it is not already installed. IIS must be installed on all distribution points. If IIS is not installed on the server and you do not select this setting, you must install IIS before the distribution point can be installed successfully.
     
     
   • Configure how client devices communicate with the distribution point. There are advantages and disadvantages for using HTTP and HTTPS. For more information, see Security Best Practices for Content Management section in the Security and Privacy for Content Management in Configuration Manager topic.
     
     

     Important
     You must select HTTPS when the parent primary site is configured to communicate only by using HTTPS.

     For more information about client communication to the distribution point and other site systems, see the Planning for Client Communications in Configuration Manager section in the Planning for Communications in Configuration Manager topic.
     
     
   • Allow clients to connect anonymously: This setting specifies whether the distribution point will allow anonymous connections from Configuration Manager clients to the content library.
     
     

     Warning

     When you deploy a Windows Installer application on a Configuration Manager client, Configuration Manager downloads the file to the local cache on the client and the files are eventually removed after the installation finishes. The Configuration Manager client updates the Windows Installer source list for the installed Windows Installer applications with the content path for the content library on associated distribution points. Later, if you start the Repair action from Add/Remove Programs on a Configuration Manager client that is running Windows XP, MSIExec attempts to access the content path by using an anonymous user. You must select the Allow clients to connect anonymously setting, or the repair fails for clients that are running Windows XP. For all other operating systems, the client connects to the distribution point by using the logged-on user account.

   • Create a self-signed certificate or import a public key infrastructure (PKI) client certificate for the distribution point. The certificate has the following purposes:
     
     
     • It authenticates the distribution point to a management point before the distribution point sends status messages.
       
       
     • When you select the Enable PXE support for clients check box on the PXE Settings page, the certificate is sent to computers that perform a PXE boot so that they can connect to a management point during the deployment of the operating system.
       
       
     When all your management points in the site are configured for HTTP, create a self-signed certificate. When your management points are configured for HTTPS, import a PKI client certificate.
     
     To import the certificate, browse to a Public Key Cryptography Standard (PKCS #12) file that contains a PKI certificate with the following requirements for Configuration Manager:
     
     
     • Intended use must include client authentication.
       
       
     • The private key must be enabled to be exported.
       
       

     Note
     There are no specific requirements for the certificate subject or subject alternative name (SAN), and you can use the same certificate for multiple distribution points.

     For more information about the certificate requirements, see PKI Certificate Requirements for Configuration Manager.
     
     For an example deployment of this certificate, see the Deploying the Client Certificate for Distribution Points section in the Step-by-Step Example Deployment of the PKI Certificates for Configuration Manager: Windows Server 2008 Certification Authority topic.
     
     
   • Enable this distribution point for prestaged content: Select this setting to enable the distribution point for prestaged content. When this setting is selected, you can configure distribution behavior when you distribute content. You can choose whether you always want to prestage the content on the distribution point, prestage the initial content for the package, but use the normal content distribution process when there are updates to the content, or always use the normal content distribution process for the content in the package.
     
     

10. On the Drive Settings page, specify the drive settings for the distribution point. You can configure up to two disk drives for the content library and two disk drives for the package share, although Configuration Manager can use additional drives when the first two reach the configured drive space reserve. The Drive Settings page configures the priority for the disk drives and the amount of free disk space to remain on each disk drive.

    • Drive space reserve (MB): The value that you configure for this setting determines the amount of free space on a drive before Configuration Manager chooses a different drive and continues the copy process to that drive. Content files can span multiple drives.
      
      
    • Content Locations: Specify the content locations for the content library and package share. Configuration Manager copies content to the primary content location until the amount of free space reaches the value that is specified for Drive space reserve (MB). By default, the content locations are set to Automatic, and the primary content location will be set to the disk drive that has the most disk space at installation and the secondary location that is assigned the disk drive that has the second most free disk space. When the primary and secondary drives reach the drive space reserve, Configuration Manager selects another available drive with the most free disk space and continues the copy process.
      
      

11. On the Content Validation page, specify whether to validate the integrity of content files on the distribution point. When you enable content validation on a schedule, Configuration Manager initiates the process at the scheduled time, and all content on the distribution point is verified. You can also configure the content validation priority. To view the results of the content validation process, click the Monitoring workspace, expand Distribution Status, and click the Content Status node. The content for each package type (for example, Application, Software Update Package, and Boot Image) is displayed.

12. On the Boundary Groups page, manage the boundary groups for which this distribution point is assigned. During content deployment, clients must be in a boundary group that is associated with the distribution point to use it as a source location for content. You can select the Allow fallback source location for content option to allow clients outside these boundary groups to fall back and use the distribution point as a source location for content when no preferred distribution points are available. For more information about preferred distribution points, see the Planning for Preferred Distribution Points and Fallback section in the Planning for Content Management in Configuration Manager topic.

13. On the Summary page, verify the settings, and then click Next to install the secondary site.

14. On the Completion page, click Close to exit the wizard.

Tip
The Windows PowerShell cmdlet, New-CMSecondarySite, performs the same function as this procedure. For more information, see New-CMSecondarySite in the System Center 2012 Configuration Manager SP1 Cmdlet Reference documentation.

1. In the Configuration Manager console, click Administration.

2. In the Administration workspace, expand Site Configuration, and then click Sites.

3. Select the secondary site server to check installation status, and then on the Home tab, in the Site group, click Show Install Status.

4. Verify that the secondary site successfully finished.

   Note
   When you install more than one secondary site at a time, the prerequisite check runs against a single site at a time, and must complete for a site before it starts to check the next site.

Use the following section to install a central administration site by using an unattended Setup script file.

Section	Key name	Required	Values	Details
Identification	Action	Yes	InstallCAS	Installs a central administration site
Options	ProductID	Yes	xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or Eval	Specifies the Configuration Manager installation product key, including the dashes. Enter Eval to install the evaluation version of Configuration Manager.
	SiteCode	Yes	<SiteCode>	Specifies three alphanumeric characters that uniquely identify the site in your hierarchy. For more information about site code restrictions, see Configuration Manager Site Naming.
	SiteName	Yes	<SiteName>	Specifies the name for this site.
	SMSInstallDir	Yes	<ConfigMgrInstallationPath>	Specifies the installation folder for the Configuration Manager program files.
	SDKServer	Yes	<FQDN of SMS Provider>	Specifies the FQDN for the server that will host the SMS Provider. You can configure additional SMS Providers for the site after the initial installation. For more information about the SMS Provider, see the Site System Roles in Configuration Manager section in the Planning for Site Systems in Configuration Manager topic.
	PrerequisiteComp	Yes	0 or 1 0 = download 1 = already downloaded	Specifies whether Setup prerequisite files have already been downloaded. For example, if you use a value of 0, Setup will download the files.
	PrerequisitePath	Yes	<PathToSetupPrerequisiteFiles>	Specifies the path to the Setup prerequisite files. Depending on the PrerequisiteComp value, Setup uses this path to store downloaded files or to locate previously downloaded files.
	AdminConsole	Yes	0 or 1 0 = do not install 1 = install	Specifies whether to install the Configuration Manager console.
	JoinCEIP	Yes	0 or 1 0 = do not join 1 = join	Specifies whether to join the Customer Experience Improvement Program.
	AddServerLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, or JPN For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Specifies the server languages that will be available for the Configuration Manager console, reports, and Configuration Manager objects. English is available by default.
	AddClientLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, or TRK For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Specifies the languages that will be available to client computers. English is available by default.
	DeleteServerLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, or JPN For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Modifies a site after it is installed. Specifies the languages to remove that will no longer be available for the Configuration Manager console, reports, and Configuration Manager objects. English is available by default and cannot be removed.
	DeleteClientLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, or TRK For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Modifies a site after it is installed. Specifies the languages to remove that will no longer be available to client computers. English is available by default and cannot be removed.
	MobileDeviceLanguage	Yes	0 or 1 0 = do not install 1 = install	Specifies whether the mobile device client languages are installed.
SQLConfigOptions	SQLServerName	Yes	<SQLServerName>	Specifies the name of the server, or name of the clustered instance, that is running SQL Server. It will host the site database.
	DatabaseName	Yes	<SiteDatabaseName> or <InstanceName>\<SiteDatabaseName>	Specifies the name of the SQL Server database to create or use to install the central administration site database. Important You must specify the instance name and site database name if you do not use the default instance.With Configuration Manager with no service pack, when you configure the site database to use the default instance of SQL Server, you must configure the SQL Server service port to use TCP port 1433, the default port. With Configuration Manager SP1, you can use a nondefault TCP port for the default instance.
	SQLSSBPort	No	<SSBPortNumber>	Specifies the SQL Server Service Broker (SSB) port that SQL Server uses. Typically, SSB is configured to use TCP port 4022, but other ports are supported.

Use the following section to install a primary site by using an unattended Setup script file.

Section	Key name	Required	Values	Details
Identification	Action	Yes	InstallPrimarySite	Installs a primary site.
Options	ProductID	Yes	xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or Eval	Specifies the Configuration Manager installation product key, including the dashes. Enter Eval to install the evaluation version of Configuration Manager.
	SiteCode	Yes	<SiteCode>	Specifies the three alphanumericcharacters that uniquely identify the site in your hierarchy. For more information about site code restrictions, see Configuration Manager Site Naming.
	SiteName	Yes	<SiteName>	Specifies the name for this site.
	SMSInstallDir	Yes	<ConfigMgrInstallationPath>	Specifies the installation folder for the Configuration Manager program files.
	SDKServer	Yes	<FQDN of SMS Provider>	Specifies the FQDN for the server that will host the SMS Provider. You can configure additional SMS Providers for the site after the initial installation. For more information about the SMS Provider, see the Site System Roles in Configuration Manager section in the Planning for Site Systems in Configuration Manager topic.
	PrerequisiteComp	Yes	0 or 1 0 = download 1 = already downloaded	Specifies whether Setup prerequisite files have already been downloaded. For example, if you use a value of 0, Setup downloads the files.
	PrerequisitePath	Yes	<PathToSetupPrerequisiteFiles>	Specifies the path to the Setup prerequisite files. Depending on the PrerequisiteComp value, Setup uses this path to store downloaded files or to locate previously downloaded files.
	AdminConsole	Yes	0 or 1 0 = do not install 1 = install	Specifies whether to install the Configuration Manager console.
	JoinCEIP	Yes	0 or 1 0 = do not join 1 = join	Specifies whether to join the Customer Experience Improvement Program.
	ManagementPoint	No	<Management point site server FQDN>	Specifies the FQDN of the server that will host the management point site system role.
	ManagementPointProtocol	No	HTTPS or HTTP	Specifies the protocol to use for the management point.
	DistributionPoint	No	<Distribution Point site server FQDN>	Specifies the protocol to use for the management point.
	DistributionPointProtocol	No	HTTPS or HTTP	Specifies the protocol to use for the distribution point.
	RoleCommunicationProtocol	Yes	EnforceHTTPS or HTTPorHTTPS	Specifies whether to configure all site systems to accept only HTTPS communication from clients or for the communication method to be configured for each site system role. When you select to EnforceHTTPS, client computer must have a valid PKI certificate for client authentication. For more information about PKI certificate requirements, see PKI Certificate Requirements for Configuration Manager.
	ClientsUsePKICertificate	Yes	0 or 1 0 = do not use 1 = use	Specifies whether clients will use a client PKI certificate to communicate with site system roles. For more information about PKI certificate requirements, see PKI Certificate Requirements for Configuration Manager.
	AddServerLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, or JPN For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Specifies the server languages that will be available for the Configuration Manager console, reports, and Configuration Manager objects. English is available by default.
	AddClientLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, or TRK For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Specifies the languages that will be available to client computers. English is available by default.
	DeleteServerLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, or JPN For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Use when modifying a site after it is installed. Specifies the languages to remove that will no longer be available for the Configuration Manager console, reports, and Configuration Manager objects. English is available by default and cannot be removed.
	DeleteClientLanguages	No	For Configuration Manager with no service pack: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, or TRK For Configuration Manager with SP1: DEU, FRA, RUS, CHS, JPN, CHT, CSY, ESN, HUN, ITA, KOR, NLD, PLK, PTB, PTG, SVE, TRK, or ZHH	Use when modifying a site after it is installed. Specifies the languages to remove and that will no longer be available to client computers. English is available by default and cannot be removed.
	MobileDeviceLanguage	Yes	0 or 1 0 = do not install 1 = install	Specifies whether the mobile device client languages are installed.
SQLConfigOptions	SQLServerName	Yes	<SQLServerName>	Specifies the name of the server or name of the clustered instance that runs SQL Server that will host the site database.
	DatabaseName	Yes	<SiteDatabaseName> or <InstanceName>\<SiteDatabaseName>	Specifies the name of the SQL Server database to create or use to install the primary site database. Important You must specify the instance name and site database name if you do not use the default instance.With Configuration Manager with no service pack, when you configure the site database to use the default instance of SQL Server, you must configure the SQL Server service port to use TCP port 1433, the default port. With Configuration Manager SP1, you can use a nondefault TCP port for the default instance.
	SQLSSBPort	No	<SSBPortNumber>	Specifies the SQL Server Service Broker (SSB) port that SQL Server uses. Typically, SSB is configured to use TCP port 4022, but other ports are supported.
HierarchyExpansionOption	CCARSiteServer	No	<FQDN of central administration site>	Specifies the central administration site that a primary site will attach to when it joins the Configuration Manager hierarchy. You must specify the central administration site during Setup. After Setup finishes, you cannot join a stand-alone primary site to a central administration site.
	CASRetryInterval	No	<Interval>	Specifies the retry interval (in minutes) to attempt a connection to the central administration site after the connection fails. For example, if the connection to the central administration site fails, the primary site waits the number of minutes that you specify for CASRetryInterval, and then re-attempts the connection.
	WaitForCASTimeout	No	<Timeout>	Specifies the maximum time-out value (in minutes) for a primary site to connect to the central administration site. For example, if a primary site fails to connect to a central administration site, the primary site retries the connection to the central administration site, based on the CASRetryInterval until the WaitForCASTimeout period is reached. You can specify a value of 0 to 100.

Use the following section to recover a central administration site by using an unattended Setup script file.

Section	Key name	Required	Values	Details
Identification	Action	Yes	RecoverCCAR	Recovers a central administration site
RecoveryOptions	ServerRecoveryOptions	Yes	1, 2, or 4 1 = Recovery site server and SQL Server. 2 = Recover site server only. 4 = Recover SQL Server only.	Specifies whether Setup will recover the site server, SQL Server, or both. The associated keys are required when you set the following value for the ServerRecoveryOptions setting: Value = 1: You have the option to specify a value for the SiteServerBackupLocation key to recover the site by using a site backup. If you do not specify a value, the site is reinstalled without restoring it from a backup set. Value = 2: You have the option to specify a value for the SiteServerBackupLocation key to recover the site by using a site backup. If you do not specify a value, the site is reinstalled without restoring it from a backup set. Value = 4: The BackupLocation key is required when you configure a value of 10 for the DatabaseRecoveryOptions key, which is to restore the site database from backup.
	DatabaseRecoveryOptions	See Details	10, 20, 40, 80 10 = Restore the site database from backup. 20 = Use a site database that has been manually recovered by using another method. 40 = Create a new database for the site. Use this option when there is no site database backup available. Global and site data is recovered through replication from other sites. 80 = skip database recovery.	Specifies how Setup recovers the site database in SQL Server. This key is required when the ServerRecoveryOptions setting has a value of 1 or 4.
	ReferenceSite	See Details	<ReferenceSiteFQDN>	Specifies the reference primary site that the central administration site uses to recover global data if the database backup is older than the change tracking retention period or when you recover the site without a backup. When you do not specify a reference site and the backup is older than the change tracking retention period, all primary sites are reinitialized with the restored data from the central administration site. When you do not specify a reference site and the backup is within the change tracking retention period, only changes after the backup are replicated from primary sites. When there are conflicting changes from different primary sites, the central administration site uses the first one that it receives. This key is required when the DatabaseRecoveryOptions setting has a value of 40.
	SiteServerBackupLocation	No	<PathToSiteServerBackupSet>	Specifies the path to the site server backup set. This key is optional when the ServerRecoveryOptions setting has a value of 1 or 2. Specify a value for the SiteServerBackupLocation key to recover the site by using a site backup. If you do not specify a value, the site is reinstalled without restoring it from a backup set.
	BackupLocation	See Details	<PathToSiteDatabaseBackupSet>	Specifies the path to the site database backup set. The BackupLocation key is required when you configure a value of 1 or 4 for the ServerRecoveryOptions key, and configure a value of 10 for the DatabaseRecoveryOptions key.
Options	ProductID	Yes	xxxxx-xxxxx-xxxxx-xxxxx-xxxxx Eval	Specifies the Configuration Manager installation product key, including the dashes. Enter Eval to install the evaluation version of Configuration Manager.
	SiteCode	Yes	<SiteCode>	Specifies three alphanumeric characters that uniquely identify the site in your hierarchy. You must specify the site code that the site used before the failure. For more information about site code restrictions, see the Configuration Manager Site Naming section in the Install Sites and Create a Hierarchy for Configuration Manager topic.
	SiteName	No	<SiteName>	Specifies the name for this site.
	SMSInstallDir	See Details	< ConfigMgrInstallationPath>	Specifies the installation folder for the Configuration Manager program files.
	SDKServer	See Details	<FQDN of SMS Provider>	Specifies the FQDN for the server that will host the SMS Provider. You must specify the server that hosted the SMS Provider before the failure. You can configure additional SMS Providers for the site after the initial installation. For more information about the SMS Provider, see the Site System Roles in Configuration Manager section in the Planning for Site Systems in Configuration Manager topic.
	PrerequisiteComp	Yes	0 or 1 0 = download 1 = already downloaded	Specifies whether Setup prerequisite files have already been downloaded. For example, if you use a value of 0, Setup downloads the files.
	PrerequisitePath	Yes	<PathToSetupPrerequisiteFiles>	Specifies the path to the Setup prerequisite files. Depending on the PrerequisiteComp value, Setup uses this path to store downloaded files or to locate previously downloaded files.
	AdminConsole	See Details	0 or 1 0 = do not install 1 = install	Specifies whether to install the Configuration Manager console. This key is required except when the ServerRecoveryOptions setting has a value of 4.
	JoinCEIP	Yes	0 or 1 0 = do not join 1 = join	Specifies whether to join the Customer Experience Improvement Program.
SQLConfigOptions	SQLServerName	See Details	<SQLServerName>	Specifies the name of the server, or name of the clustered instance that is running SQL Server that will host the site database. You must specify the same server that hosted the site database before the failure.
	DatabaseName	See Details	<SiteDatabaseName> or <InstanceName>\<SiteDatabaseName>	Specifies the name of the SQL Server database to create or use to install the central administration site database. You must specify the same database name that was used before the failure. Important You must specify the instance name and site database name if you do not use the default instance.
	SQLSSBPort	See Details	<SSBPortNumber>	Specifies the SQL Server Service Broker (SSB) port that SQL Server uses. Typically, SSB is configured to use TCP port 4022. You must specify the same SSB port that was used before the failure.

Use the following section to recover a primary site by using an unattended Setup script file.

Section	Key name	Required	Values	Details
Identification	Action	Yes	RecoverPrimarySite	Recovers a primary site
RecoveryOptions	ServerRecoveryOptions	Yes	1, 2, or 4 1 = Recovery site server and SQL Server. 2 = Recover site server only. 4 = Recover SQL Server only.	Specifies whether Setup will recover the site server, SQL Server, or both. The associated keys are required when you set the following value for the ServerRecoveryOptions setting: Value = 1: You have the option to specify a value for the SiteServerBackupLocation key to recover the site by using a site backup. If you do not specify a value, the site is reinstalled without restoring it from a backup set. Value = 2: You have the option to specify a value for the SiteServerBackupLocation key to recover the site by using a site backup. If you do not specify a value, the site is reinstalled without restoring it from a backup set. Value = 4: The BackupLocation key is required when you configure a value of 10 for the DatabaseRecoveryOptions key, which is to restore the site database from backup.
	DatabaseRecoveryOptions	See Details	10, 20, 40, 80 10 = Restore the site database from backup. 20 = Use a site database that has been manually recovered by using another method. 40 = Create a new database for the site. Use this option when there is no site database backup available. 80 = skip database recovery.	Specifies options for Setup to recover the site database in SQL Server. This key is required when the ServerRecoveryOptions setting has a value of 1 or 4.
	SiteServerBackupLocation	No	<PathToSiteServerBackupSet>	Specifies the path to the site server backup set. This key is optional when the ServerRecoveryOptions setting has a value of 1 or 2. Specify a value for the SiteServerBackupLocation key to recover the site by using a site backup. If you do not specify a value, the site is reinstalled without restoring it from a backup set.
	BackupLocation	See Details	<PathToSiteDatabaseBackupSet>	Specifies the path to the site database backup set. The BackupLocation key is required when you configure a value of 1 or 4 for the ServerRecoveryOptions key, and configure a value of 10 for the DatabaseRecoveryOptions key.
Options	ProductID	Yes	xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or Eval	Specifies the Configuration Manager installation product key, including the dashes. Enter Eval to install the evaluation version of Configuration Manager.
	SiteCode	Yes	<SiteCode>	Specifies three alphanumeric characters that uniquely identify the site in your hierarchy. You must specify the site code that the site used before the failure. For more information about site code restrictions, see the Configuration Manager Site Naming section in the Install Sites and Create a Hierarchy for Configuration Manager topic.
	SiteName	No	<SiteName>	Specifies the name for this site.
	SMSInstallDir	See Details	<ConfigMgrInstallationPath>	Specifies the installation folder for the Configuration Manager program files.
	SDKServer	See Details	<FQDN of SMS Provider>	Specifies the FQDN for the server that will host the SMS Provider. You must specify the server that hosted the SMS Provider before the failure. You can configure additional SMS Providers for the site after the initial installation. For more information about the SMS Provider, see the Site System Roles in Configuration Manager section in the Planning for Site Systems in Configuration Manager topic.
	PrerequisiteComp	Yes	0 or 1 0 = download 1 = already downloaded	Specifies whether Setup prerequisite files have already been downloaded. For example, if you use a value of 0, Setup downloads the files.
	PrerequisitePath	Yes	<PathToSetupPrerequisiteFiles>	Specifies the path to the Setup prerequisite files. Depending on the PrerequisiteComp value, Setup uses this path to store downloaded files or to locate previously downloaded files.
	AdminConsole	See Details	0 or 1 0 = do not install 1 = install	Specifies whether to install the Configuration Manager console. This key is required except when the ServerRecoveryOptions setting has a value of 4.
	JoinCEIP	Yes	0 or 1 0 = do not join 1 = join	Specifies whether to join the Customer Experience Improvement Program.
SQLConfigOptions	SQLServerName	See Details	<SQLServerName>	Specifies the name of the server, or the name of the clustered instance that is running SQL Server that will host the site database. You must specify the same server that hosted the site database before the failure.
	DatabaseName	See Details	<SiteDatabaseName> or <InstanceName>\<SiteDatabaseName>	The name of the SQL Server database to create or use to install the central administration site database. You must specify the same database name that was used before the failure. Important You must specify the instance name and site database name if you do not use the default instance.
	SQLSSBPort	See Details	<SSBPortNumber>	Specify the SQL Server Service Broker (SSB) port that SQL Server uses. Typically, SSB is configured to use TCP port 4022. You must specify the same SSB port that was used before the failure.
HierarchyExpansionOption	CCARSiteServer	See Details	<SiteCodeForCentralAdministrationSite>	Specifies the central administration site to which a primary site attaches when it joins the Configuration Manager hierarchy. This setting is required if the primary site was attached to a central administration site before the failure. You must specify the site code that was used for the central administration site before the failure.
	CASRetryInterval	No	<Interval>	Specifies the retry interval (in minutes) to attempt a connection to the central administration site after the connection fails. For example, if the connection to the central administration site fails, the primary site waits the number of minutes that you specify for CASRetryInterval, and then attempts the connection again.
	WaitForCASTimeout	No	<Timeout>	Specifies the maximum time-out value (in minutes) for a primary site to connect to the central administration site. For example, if a primary site fails to connect to a central administration site, the primary site retries the connection to the central administration site, based on the CASRetryInterval until the WaitForCASTimeout period is reached. You can specify a value of 0 to 100.

1. Verify the administrative user that runs Setup has the following security rights:

   • Administrative rights on the secondary site computer.
     
     
   • Local Administrator rights on the remote site database server for the primary site, if it is remote.
     
     
   • Infrastructure Administrator or Full Administrator security role on the parent primary site.
     
     
   • Sysadmin rights on the site database of the secondary site.
     
     

2. In the Configuration Manager console, click Administration.

3. In the Administration workspace, expand Site Configuration, and then click Sites.

4. Select the secondary site server to remove.

5. On the Home tab, in the Site group, click Delete.

6. On the General page, select whether to uninstall or delete the secondary site, and then click Next.

7. On the Summary page, verify the settings, and then click Next.

8. On the Completion page, click Close to exit the wizard.

1. Verify the administrative user that runs Setup has the following security rights:

   • Local Administrator rights on the central administration site server.
     
     
   • Local Administrator rights on the remote site database server for the central administration site, if it is remote.
     
     
   • Sysadmin rights on the site database of the central administration site.
     
     
   • Local Administrator rights on the primary site computer.
     
     
   • Local Administrator rights on the remote site database server for the primary site, if it is remote.
     
     
   • User name associated with the Infrastructure Administrator or Full Administrator security role on the central administration site.
     
     

2. Start Configuration Manager Setup on the primary site server by using one of the following methods:

   • On Start, click Configuration Manager Setup.
     
     
   • Open Setup.exe from <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.
     
     
   • Open Setup.exe from <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.
     
     

3. On the Before You Begin page, click Next.

4. On the Getting Started page, select Uninstall a Configuration Manager site, and then click Next.

5. On the Uninstall the Configuration Manager Site, specify whether to remove the site database from the primary site server and whether to remove the Configuration Manager console. By default, Setup removes both items.

   Important
   When a secondary site is attached to the primary site, you must remove the secondary site before you can uninstall the primary site.

6. Click Yes to confirm to uninstall the Configuration Manager primary site.

1. Before you uninstall any primary site, you must disable distributed views on each link in the hierarchy between the central administration site and a primary site.

2. After you disable distributed views on each link, confirm that the data from the primary site completes reinitialization at the central administration site. You can monitor the initialization of data when you view the link in the Database Replication node of the Monitoring workspace of the Configuration Manager console.

3. After the data successfully reinitializes with the central administration site, you can uninstall the primary site. To uninstall a primary site, see the Uninstall a Primary Site section in this topic.

4. After the primary site is completely uninstalled, you can reconfigure distributed views on links to primary sites.

   Important

   If you uninstall the primary site before you disable distributed views at each site, or before the data from the primary site successfully reinitializes at the central administration site, replication of data between primary sites and the central administration site can fail. In this scenario, you must disable distributed views for each link in your hierarchy, and then, after the data successfully reinitializes with the central administration site, you can reconfigure distributed views.

1. Verify that the administrative user who runs Setup has the following security rights:

   • Local Administrator rights on the central administration site server.
     
     
   • Local Administrator rights on the site database server for the central administration site, when the site database server is not installed on the site server.
     
     

2. Start Configuration Manager Setup on the central administration site server by using one of the following methods:

   • On Start, click Configuration Manager Setup.
     
     
   • Open Setup.exe from <ConfigMgrInstallationMedia>\SMSSETUP\BIN\X64.
     
     
   • Open Setup.exe from <ConfigMgrInstallationPath>\SMSSETUP\BIN\X64.
     
     

3. On the Before You Begin page, click Next.

4. On the Getting Started page, select Uninstall a Configuration Manager site, and then click Next.

5. On the Uninstall the Configuration Manager Site, specify whether to remove the site database from the central administration site server and whether to remove the Configuration Manager console. By default, Setup removes both items.

   Important
   When there is a primary site attached to the central administration site, you must uninstall the primary site before you can uninstall the central administration site.

6. Click Yes to confirm to uninstall the Configuration Manager central administration site.