- Server Requirements
- Software Requirements
- Internet Requirements
- Port Forwarding
- DNS Configuration
- Mail Configuration
- Backup Mail Server
- Antivirus and Anti-Spyware
- 2003 Windows Server Configuration
- 2008 Windows Server Configuration
- Document Revision History
The purpose of this guide is to provide you with the requirements to successfully implement LabTech. This guide is intended for new installations or troubleshooting existing installations. Once you are sure you have met the prerequisites, you can begin the LabTech installation. Refer to the LabTech Installation instructions for step-by-step instructions.
|IMPORTANT: It is very important that you complete the following Installation Prerequisites prior to installing LabTech 2012; otherwise your installation may fail or some components of LabTech 2012 will not function correctly!|
The server requirements will vary based on your environment (e.g., probe use, number of probes, number of agents, etc.). Depending upon actual usage, the hardware and software required may be more or less than what is recommended.
The following is a recommendation based on the number of LabTech agents in the following sizes: 500, 1000, 2500, 5000, 10,000 and 20,000. Due to performance issues, a physical server is recommended, especially with over 1000 agents. You can also download a copy of the Scalability Guide from the LabTech website.
|NOTE: LabTech CANNOT be set up on Windows Small Business Servers (SBS), Windows Essential Business Servers (EBS), Windows 2008 Foundation Edition (FE) or Windows 2012 Server. Refer to the Microsoft Windows Server 2012 Timeline KB for additional information.|
Table 1: Scalability Guide
|IMPORTANT: It is recommended that the LabTech server be given a static IP address. When the LabTech server contacts the licensing server, your licenses are tied to your IP address. If you do not use a static IP, you will have to contact LabTech occasionally to provide us with your IP for the licensing. In addition, the Web Control Center relies on the IP address. If your IP address changes, you will not able to access the Web Control Center unless you modify your registry to recognize the new IP.|
The following software is required prior to installing LabTech. If you need additional information on how to configure the following, please refer to the 2003 Windows Server Configuration and 2008 Windows Server Configuration sections later in this document.
- IIS 6.0 or higher.
- .NET 3.5 is required on all systems running the Control Center, including the LabTech server; otherwise, many of the new features will not be functional and may crash.
- Microsoft Windows Server 2003 or 2008 (32-bit or 64-bit)
- If using 2003 Server, Service Pack 2 MUST be installed.
- If using 2008 Server, you must do the following:
- Install IIS 6.0 Compatibility (all features)
- Add ASP and ASP.net
- Unbind IPv6 from your NIC(s) before starting the LabTech installation.
- Disable UAC on the server, if enabled.
- LabTech is installed with MySQL 5.5.28a and only supports version 5.5.xx with a minimum build of 5.5.28a. Other versions are not supported.
|NOTE: Ensure that these applications have been installed and configured properly prior to beginning the installation of LabTech.|
LabTech cannot be setup on a server with any of the following software installed:
- Microsoft SharePoint Services (any version)
- Windows Update Services (any version)
- Apache Web Service (any version)
|IMPORTANT: It is recommended that the LabTech server is a dedicated server/virtual machine without any other software/websites loaded on it. The exception to this is Antivirus. This is due to the changes that may be made to the default behavior of IIS and other Windows settings. WARNING: This may affect our Support department's ability to diagnose an issue and support may be refused if other software/websites exist on the same server.|
You must have Internet access and be able to reach http://labtechsoftware.com for licensing validation.
LabTech only needs two TCP ports (70 and 80) forwarded to the LabTech server for basic operations. For more advanced options, you may want to use SSL and VNC Quick Connect; therefore these ports will also need to be forwarded. The following ports need to be forwarded from your WAN IP to your LabTech server:
- Port 70 TCP: Redirector communications
- Ports 70-75 UDP: Tunnels and Redirectors
- Port 80: HTTP Normal communications
- Port 443: HTTP SSL Normal communications (optional)
- Ports 40000-40050 TCP: Connecting via HTTP or to use VNC from the Web Control Center. Open ports beginning with 40000 and ending with four times the number of total technicians using LabTech (e.g., If there are 25 technicians, then there are 25x4 (100) simultaneous sessions). So, ports 40000-40100 should be open. These ports are also needed for mobile devices if you plan on using VNC.
- Ports 40000-41000 UDP: Tunnels and Redirectors, only when advanced routers are blocking and not at the LabTech server, at client and agent locations or where the router in front of the Control Center is blocking.
- Local Machine Access:
- 127.0.0.1 on any port from 127.0.0.1 using any protocol should be opened (local machine access)
- Port 42000 UDP from local LAN computers (255.255.255.0) (local machine access)
|NOTE: If you change the default TCP port 70 in the Dashboard > Config > System to another port, then you would forward that port + 5 (e.g., 90-95)|
The following are restricted ports for Control Center connections from outside your network. Make sure the users are accessing via SSL by enabling SSL on the MYSQL server and checking the Enable SSL checkbox on the Control Center login window. For maximum security, do not forward these ports. If for some reason you need to forward these ports, limit the access to a list of IP Addresses.
- 3306 - Control Center
- 8000-9024 – Redirector ports
Figure 1: Sample D-Link Router
- You will need to register a FQDN for the LabTech server with your registrar (e.g., server.labtech.com)
- The WAN IP Address, of the LabTech server, should be used for the FQDN.
- The agents will use this to connect to the LabTech Web Control Center.
- The FQDN will be used in the redirector config.
- It is also recommended that an SSL is obtained for this domain.
- A wildcard certificate may be used.
- You will need to setup a new zone (matching your external domain name) if your local domain name is different from your external domain name AND your router/firewall is not setup to route your LAN traffic back from the WAN interface to the LAN interface (e.g., sonic walls have to be manually setup to do this).
- If you need assistance with creating a new zone and adding the correct CNAME and A Records, please consult your DNS software guide.
- Add the www and other records you need and set them the same as they are on the external DNS server.
- Add a LabTech record and use the local IP address of the LabTech server.
|NOTE: This will let your internal hosts connect to the LabTech server directly and external hosts will connect to the router and be forwarded.|
You will need an email address to use for support tickets. Any mail sent to this address will be downloaded to the LabTech server and each email message will be added as a support ticket. After downloading, the email(s) will be deleted from the mailbox.
- Allow anonymous connections.
- Use the LAN IP of your LabTech server to restrict anonymous connections for the new SMTP Connector.
- For more information about SMTP Connectors see the Microsoft TechNet Guides:
A backup mail server is strongly recommended. This ensures reliability and keeps your business running smoothly.
- Install a SMTP server on the LabTech server.
- Ensure the secondary mail server is running on the same SMTP port as the primary mail server. If the primary mail server cannot be reached for any reason, the second attempt will go to the secondary mail server.
NOTE: The easiest way to configure a second SMTP server is to enable the built-in SMTP server in IIS.
- Set the secondary server to listen on the same port as the primary mail server.
- Allow Everyone to Relay.
- Allow Everyone to Connect.
- Configure Smart Host to be the primary mail server.
|IMPORTANT: Do NOT forward port from router to this SMTP server on LabTech server.|
All antivirus and anti-spyware applications on the server need to be disabled before installation.
There are multiple items that must be configured for Windows Server 2003. The next several sections of this document will walk you through each of the following items:
- IIS 6.0 installed
- ASP.NET installed and enabled
- Windows Server 2003 SP2 installed
- .NET Framework 2.0 or higher
|NOTE: The Configure Your Server Wizard enables ASP.NET by default, unlike the Add/Remove Windows components install method.|
- Select Start > Administrative Tools > Manage Your Server.
Figure 2: Manage Your Server
- Click Add or remove a role in the Adding Roles to Your Server section.
- Read and follow the preliminary steps in the Configure Your Server Wizard and click Next.
Figure 3: Configure Your Server Wizard—Server Role
- Under Server Role, click Application server (IIS, ASP.NET) and then click Next. By default IIS, COM+, ASP.NET and Microsoft.NET Framework are installed automatically for this role.
Figure 4: Application Server Options
- Select Enable ASP .NET and click Next.
- A summary of your selections will appear. Click Next to proceed. It will take a few moments to configure the components.
When complete, click Finish.
|NOTE: The Configure your Server wizard enables ASP.NET by default, unlike the Installing Using the Control Panel method (below).|
To install IIS and ASP.NET, add additional components, or remove components using the Control Panel, follow the steps listed below.
- From the Start menu, select Control Panel > Add or Remove Programs.
- Click Add/Remove Windows Components.
- In the Components list box, click Application Server.
Figure 5: Window Components
- Click Details.
Figure 6: Application Server - ASP.NET
- Click ASP.NET and Internet Information Services Manager.
- Click Details to view the list of IIS optional components. Select all optional components you wish to install and click OK. This will return you to the Application Server screen (as shown above).
- Click OK again and then Next to complete the installation.
- When the wizard has completed, click Finish and close the Add or Remove Programs window.
- Verify ASP.NET in the IIS Manager is set to 'allow'.
- Select Start > Administrative Tools > Internet Information Services (IIS) Manager.
- Expand the local computer and click on the Web Service Extension folder.
- In the details pane of this window, ASP.NET should have the status of 'Allowed'. If it does not, right-click and select Allow.
If you do not have the .NET 2.0 framework or higher on your Windows 2003 server, you will need to upgrade it. The .NET 3.5 Framework can be downloaded from the Microsoft website.
- Download and run the .NET Framework.
- You will be prompted to accept the terms of the license agreement. Click on the I have read and ACCEPT the terms of the License Agreement. If you agree, and click Install.
- Once installation is complete, a Setup Complete screen will display. Click Exit to close this window.
If your installation of Windows Server 2003 is not SP 2, you will need to download and install this service pack. This service pack has heightened security, reliability and performance.
- Download and run the Windows Server 2003 SP2.
- Follow the on-screen prompts. When the installation has completed, click the Finish button to restart the server.
The following screens may very slightly depending on whether you are using 2008 Server Standard edition or 2008 Server Enterprise edition.
- Click Start > Administrative Tools > Server Manager.
- In the Server Manager window, scroll down to Roles Summary, and then click Add Roles.
Figure 7: Add Roles Wizard
- The Add Roles Wizardwill ask for verification of the following:
- The administrator account has a strong password.
- The network settings, such as IP addresses, are configured.
- The latest security updates from Windows® Update are installed.
- Select Server Roles from the menu on the left.
Figure 8: Select Server Roles
- Select Web Server (IIS) and click Next. An informational screen will display. Click Next to continue.
- You will be prompted to select role services.
Figure 9: Select Role Services
NOTE: When you use the Add Roles Wizard to install IIS, you get the default installation, which has a minimum set of role services. If you need additional IIS role services, such as Application Development or Health and Diagnostics, make sure to select the check boxes associated with those features. Add only the modules necessary.
- Select ASP.NET. You will be prompted to add role services required for ASP.NET. Click Add Required Role Services.
- Select ASP.
- Scroll down to Management Tools and select IIS 6 Management Compatibility and click Next. You will be prompted to confirm installation selections.
- If the selections are correct, click Install.
- IIS is now installed with IIS 6 Management Compatibility and the default configuration for hosting ASP and ASP.NET on Windows Server. Click Close to complete the process.
.NET 3.5 is the minimum and is included in 3.5 SP1 for Windows Server 2008. .NET 4.0 is not currently supported. Follow the steps listed below to install .NET 3.5.1:
- Click Start > Administrative Tools > Server Manager.
- In the Server Manager window, scroll down to Features Summary, and then click Add Features.
Figure 10: Select Features
- Select .NET Framework 3.5.1 Features and click Next.
- You will be prompted to add required features. Click Add Required Features.
- Click Next.
- You will be prompted to confirm your installation selections. If correct, click Install.
- Click Close when the installation has completed to close the wizard. .NET is now installed.
|03/22/2011||Updated steps for Windows Server 2003.|
|04/25/2011||Instructions to disable UAC have been removed.|
|08/17/2011||Updated for 2011.2 release.|
|10/25/2011||Added note about changing the default TCP port 70.|
|11/01/2011||Added additional port forwarding options if router/firewall is causing issues with tunnels/redirectors.|
|11/29/2011||Updated TCP ports for HTTP connections.|
|04/15/2012||Updated for 2012 release. Added .NET 3.5 requirements.|
|05/21/2012||Added recommendation to use physical servers due to performance of virtual machines.|
|06/07/2012||Changed the 'Important' notice regarding software/websites being loaded on the LabTech server.|
|10/12/2012||Updated for LabTech 2012 SP1. Added server recommendations. Removed Unbind IPv6|
|02/04/2013||Added information that LabTech cannot be installed on Windows 2012 Server at this time. Added link to KB article Server 2012 timeline.|
|02/18/2013||Added MySQL requirements|