Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Lync Server 2010 Edge : Reverse Proxy

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
9/19/2011 6:10:38 PM
To support all the remote features available in Lync Server, a reverse proxy must be used to publish internal web services in addition to an Edge Server pool. The type of reverse proxy used is flexible because almost any kind of reverse proxy should be capable of handling the requirements. Microsoft recommends using either the Forefront Unified Access Gateway or Threat Management Gateway products for publishing Lync Server. Threat Management Gateway, or TMG, is the next generation of the Internet Security & Acceleration (ISA) Server product and Unified Access Gateway (UAG) builds on TMG with additional security and filtering capabilities. This section focuses on publishing the Lync Server Front End or Director pools using Forefront Threat Management Gateway 2010.

Reverse Proxy Installation

If a reverse proxy already exists in the organization, it can be used to also publish Lync Server web services. There is no requirement for a reverse proxy to be dedicated only to Lync Server, but if no reverse proxy exists, one should be deployed when an Edge Server is provisioned. The following section details how to use the Microsoft Forefront Threat Management Gateway 2010 as a reverse proxy for Lync Server.

Forefront Threat Management Gateway 2010 Prerequisites

This section discusses the hardware, operating system, and software requirements necessary for installing Forefront Threat Management Gateway.

Hardware Requirements

The Forefront Threat Management Gateway server processor requirement is as follows:

  • 1.86 GHz dual processor or dual-core processor

Caution

Threat Management Gateway 2010 is only a 64-bit application and requires a 64-bit capable processor. This is generally not an issue with any modern hardware. However, verify that legacy hardware supports a 64-bit operating system before attempting to use it as a reverse proxy.


The Forefront Threat Management Gateway server memory requirement is as follows:

  • 2 GB RAM (4 GB recommended)

The Forefront Threat Management Gateway disk requirement is as follows:

  • Local storage with at least 2.5 GB free space

The Forefront Threat Management Gateway server network requirements are as follows:

  • One network adapter for communication with the internal network

  • An additional network adapter for each network connected to the Forefront TMG server

Note

Designing a high-availability solution for Threat Management Gateway is not discussed in detail here. However, this can be done with Windows Network Load Balancing or a hardware load balancer. Follow the documentation on TechNet to design a solution that matches and meets availability requirements for the Lync Server infrastructure.


Operating System Requirements

Forefront Threat Management Gateway supports the following operating systems:

  • Windows Server 2008, x64 Standard Edition with Service Pack 2

  • Windows Server 2008, x64 Enterprise Edition with Service Pack 2

  • Windows Server 2008, x64 Datacenter Edition with Service Pack 2

  • Windows Server 2008 R2, Standard Edition

  • Windows Server 2008 R2, Enterprise Edition

  • Windows Server 2008 R2, Datacenter Edition

The Windows Server Core, Web, and High Performance Computing editions for any operating system version are not supported for deployment.

Software Requirements

The Forefront Threat Management Gateway server requires installation of the following components:

  • .NET Framework 3.5, Service Pack 1

  • Windows Web Services API

  • Windows Update

  • Windows Installer 4.0

Server Roles and Features

In addition to the operating system and software requirements listed previously, the Forefront Threat Management Gateway requires several Windows server roles, role services, and features to be installed. The following roles and features can either be preinstalled or installed automatically by the Forefront Threat Management Gateway preparation tool.

  • Network Policy Server

  • Routing and Remote Access Services

  • Active Directory Lightweight Directory Services Tools

  • Network Load Balancing Tools

  • Windows PowerShell

Forefront Threat Management Gateway 2010 Installation

This section discusses installing a standalone Forefront Threat Management Gateway 2010 server to support the reverse proxy functionality required for external access. For detailed instructions on configuring an array of Threat Management Gateway servers or centralized management options, refer to TechNet.

1.
Launch the Forefront Threat Management Gateway 2010 installation media.

2.
If the required server roles and features have not applied, click Run Preparation Tool.

3.
Click Next to begin the Preparation Wizard.

4.
Select I accept the terms of license agreements and then click Next.

5.
Select Forefront TMG services and Management and then click Next.

6.
Select Launch Forefront TMG Installation Wizard and then click Finish.

7.
Click Next to begin the installation.

8.
Select I accept the terms in the license agreement and then click Next.

9.
Enter a username, organization, and product serial number. Then click Next.

10.
Enter an installation path and then click Next.

11.
Click the Add button to begin entering internal network ranges.

12.
Click Add Adapter, select the network adapter, and then click OK.

13.
Verify the start and end addresses account for the internal network ranges of the Lync Server servers. Include additional ranges, and then click OK and Next.

14.
Click Next and then Install to begin the installation.

15.
Click Finish when the installation completes.
Other -----------------
- Microsoft Lync Server 2010 Edge : Edge Configuration
- Managing Exchange Server 2010 Clients : Checking Private and Public Folders with IMAP4 and UNIX Mail Servers
- Managing Exchange Server 2010 Clients : Leaving Mail on the Server with POP3
- Securing Windows Server 2008 R2 : Encrypting File System
- Securing Windows Server 2008 R2 : Auditing
- Microsoft Dynamics NAV : Business Intelligence - Reporting capabilities in NAV
- Microsoft Dynamics NAV and Business Intelligence
- SharePoint 2010 Search : Troubleshooting Crawl Errors & Server Name Mappings
- SharePoint 2010 Search : Setting Up the Crawler - Using Crawl Rules
- Windows Small Business Server 2011 : Set Up Your Internet Address (part 2) - Add a Trusted Certificate
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server