# Step-by-Step Guide: Installing and Setting Up the Summary and Probe Servers You can set up the Summary Server in your network using the installation file provided via email. If you don't have the file, you can request it by filling out this [form](https://www.manageengine.com/products/desktop-central/summary-server.html). **Note:** - It is crucial to start the installation with the Summary Server, followed by the Probe Server on a separate machine. - Deviating from this order may disrupt the installation process. ## Table of Contents 1. [How the Setup Works](#how-the-setup-works) 2. [Summary and Probe Server Port Details](#summary-and-probe-server-port-details) 3. [Prerequisites for Summary Server and Probe Server Installation](#prerequisites-for-summary-server-and-probe-server-installation) 4. [Installation Demo Video](#installation-demo-video) 5. [Steps for Summary Server Installation](#steps-for-summary-server-installation) 6. [Steps for Probe Server Installation](#steps-for-probe-server-installation) 7. [Frequently Asked Questions (FAQ)](#frequently-asked-questions-faq) ## How the Setup Works - **Summary Server:** Typically installed at the headquarters, where the IT admin, CISO, or IT decision-maker oversees the Central IT team. The Summary Server functions as the main dashboard for managing the organization's endpoints. - **Probe Server:** Installed in regional offices and managed by the regional IT team. The Probe Server ensures scalability by managing numerous endpoints across various departments or divisions. Multiple Probe Servers send endpoint data to the Summary Server, which consolidates it for a comprehensive view of the network. ## Summary and Probe Server Port Details ### Ports Used by Summary Server The Summary Server will communicate with the Probe Server through port 8383 by default. | Port | Purpose | Type | Connection | |---|---|---|---| | 8383 | For accessing Web console | HTTPS | In bound to server | | 8443 | For Sharing Remote Desktops, System Manager, Chat and File Transfer. | HTTPS/UDP | In bound to server | ### Ports Used by Probe Server The Probe Server will communicate with the Summary Server through port 8383 by default. To know more about the ports used by Probe Server, please visit this [page](https://www.manageengine.com/products/desktop-central/desktop-central-lan-architecture.html). ## Prerequisites for Summary Server and Probe Server Installation Please ensure that communication is allowed between the Summary Server and Probe Server host machines before proceeding with the installation. **Steps to ensure bidirectional communication between the two servers:** 1. Get hostnames of Summary Server and Probe Server hosted machines by entering the `hostname` command from command prompt. 2. Ensure that Summary Server's port (default: 8383) is reachable from the machine where Probe Server is to be hosted, with the following command in PowerShell: ```plaintext tnc -port ``` 3. Ensure that the Probe Server is reachable from the machine where Summary Server is hosted, with the following command in PowerShell: ```plaintext tnc ``` ## Installation Demo Video Watch this video for a step-by-step guide on installing and setting up the Summary and Probe servers. https://www.youtube-nocookie.com/embed/F01lEUEKQA4 ## Steps for Summary Server Installation 1. Launch the installation file via the InstallShield Wizard. 2. Accept the Endpoint Central license agreement. 3. Select **Summary Server** as the server type. ![Summary Server installation image](https://www.manageengine.com/products/desktop-central/help/images/ssinst-1.png) 4. Choose the destination folder and set the port for the Summary Server (default port: 8383, can be changed). 5. Click **Finish** to complete the installation. ## Steps for Probe Server Installation **Important:** Log in to the Summary Server web console on the machine where you plan to install the Probe Server, then follow these steps: ### Step 1: Generate the Probe Installation Key 1. Click on **Generate Key** in Step 1 of the web console. ![Generate Key image](https://www.manageengine.com/products/desktop-central/help/images/ssinst-2.png) 2. Enter the Probe Name and description, then click **Save**. The key will be generated. ![Save Probe Key image](https://www.manageengine.com/products/desktop-central/help/images/ssinst3.png) ### Step 2: Download the Probe Installer 1. Download the Probe installer file in Step 2 and begin the installation. 2. Accept the Endpoint Central license agreement. 3. Select **Probe Server** as the server type (since the Summary Server is already installed). ![Probe Server installation image](https://www.manageengine.com/products/desktop-central/help/images/ssinst-4.png) 4. Choose the destination folder and set the port for the Probe Server (default port: 8383, can be changed). ### Step 3: Enter the Summary Server Details 1. During installation, enter the Summary Server details available in Step 3 of the Summary Server web console. ![Summary Server details image](https://www.manageengine.com/products/desktop-central/help/images/ssinst-5.png) 2. Click **Finish** to complete the installation. Once the Probe Server is successfully installed, access the Summary Server web console and refresh the page to see the updated Probe details. To know more about upgrading the summary server, click [here](https://www.manageengine.com/products/desktop-central/summary-server/upgrade-summaryserver.html). ## Frequently Asked Questions (FAQ) ### What should be done if the hostname is not reachable? If the hostname is not reachable, please check the connectivity using the IP address with the following command in PowerShell: ```plaintext tnc -port ``` If the port is accessible using the IP address but not the hostname, please add a DNS entry for the hostname in the hosts file located at **C:\Windows\System32\drivers\etc\hosts**. ### Can the FQDN be used instead of hostname during the Probe Server installation? Yes. If the Summary Server machine is reachable from the Probe Server using its FQDN, please use the FQDN in the Probe Server installation wizard. ### What should be done if the port is not accessible using any of the above - hostname, IP address, or FQDN? If the port is inaccessible with any of these options, try pinging the hostname without specifying a port number using the following command: ```plaintext ping ``` If the hostname is not pingable, try pinging using the IP address. If it is reachable using the IP address, add a DNS entry for the hostname. If the hostname/IP address is pinging successfully but the port is not accessible, check for any firewall inbound or outbound rules that might be blocking the port and remove them if necessary.