Single-Host Server Deployment

This topology provides a simple pilot or very small deployment. This topology is primarily geared toward smaller deployments with no need for redundancy or proof-of-concept scenarios in which rapid deployment is a priority. There is no high-availability or backup pool. A single Lync Standard Edition Server and a single SharePoint Office Web Apps server are deployed on a single host as shown in Figure 29.4.

Figure 29.4. Single-host server deployment.

There is the potential here to specify the host with enough power (move to dual physical CPU and add RAM) to also run the Lync Edge and Reverse Proxy role, allowing a complete Lync deployment on one physical server, with the inside and outside networks running on different network interface cards. In reality it is rare for organizations to accept that it is secure practice to have a hypervisor as the only barrier between DMZ and internal servers.

If monitoring or archiving are required, a separate Microsoft SQL server would be required to store the data. To summarize, an example host could use the following hardware configuration:

Host Server Configuration

• Windows Server 2012 with Hyper-V

• 2.26GHz or higher CPU with 10 cores

• 48GB RAM

• 500GB SAS 10K disks with eight spindles

• Four 1Gb network adapters

Guest Configuration

Lync Server 2013 Standard Edition:

• Six CPU cores

• 32GB RAM

• Dedicated 1GB network adapter

Office Web Apps Server 2013:

• Four CPU cores

• 12GB RAM

• Dedicated 1GB network adapter