It's not a lot new which you would see on the spotting view. But it's more than you believe.
I will guide you through an entire setup of a Lync Enterprise Pool now:
Start with a new Topology and save it as usual.
Chose the primary SIP Domain, I have chosen lyncuc.blogspot.com
From here,if you have multiple other SIP domains, e.g. internal domains or other party domains, simply add them and have in mind you need to work out for certificates later.
Than we start defining our first Lync Site, usually this is the internal site or the internal site with Internet facing access.
Just provide the necessary information where the Site is located.
Than we have to proceed with the Front-End Pool coniguration, you can do this via the wizard or you do this individually later.
Remember the settings and information required.
Than I have chose the Pool Name, I mainly chose a name with the word "POOL" inside so it is more easy to identify this DNS Names in the DNS Server and you can easly remember it.
I have now setup up two Front-End Server, (remember for DR it will look differen) - just wait a while until i have the Blog Lab System ready so i will provide you with more information regarding the new DR features.
I make use of some new features here, I collocat the Archiving and the Monitoring Server on the FE's, therefore they become HA now.
I will not collocate the Mediation Server (but is just a click away if you want to do this later)
But Edge Server is required in my enrironment and it will guide me to the next Wizard later.
This is the most interesting feature setup here. This is for our old know SQL Server, BUT...
Not is time for HA, I will need to setup this feature in the Topology Builder first.
I define the PRIMARY SQL Server here.
Than it's part of the NEW FEATURE, the SQL MIRROR.
And because I like spending Microsoft more Money, I will make use of a WITNESS SQL Server.
The good FileShare should not be forgotten. Since we have no SQL Cluster (which would make use of Windows Failover Clustering), you now need having in your mind a individual FileServer Cluster !
The internal and external Web Service URL are well known and here we do not have some changes compared to Lync 2010. Just remember, if you have and internal and external DNS domain, here you need to adjust the settings!
As in the new feature already described, the NEW OFFICE WEB APPS Server will be defined here.
I will for sure describe the OWA Server more in detail and in a seperate Blog.
You remember with the nice advatage of collocated Archiving and Monitoring, you still need a dedcated DATABASE, even this can NOW BE HIGH AVAILABLE. So i will do so.
i do the same for Monitoring, but i can still use the same SQL Server Setup again.
Now it's time for EDGE server.
Now the new XMPP proxy feature can be enabled in the Topology.
If you are ready for IPv6 and your internet Provider offer this service, you can enable it also for the public site. If you fully run on IPv6 internally, EDGE Server support the IP Version Split, so internally IPv4&6 and IPv4 externally. for example.
Do it like you did for Lync 2010, the external access URL's
Edge Server still have only a singel internal IP Address, so define it (and remember about the DNS Suffix you need to set manually for the NON-Domain joined Edge Server.
Now the external IP addresses, if you would have chosen IPv6 too, you could prived the new address rage here.
the same for the second Edge Server.
And the external IPs.
Ready and you can now start defining the HOP Server.
Next hop for the Edge Server.
Next Hop Server for the Front-End Pool.
We did it, the Topology is READY.
Finally and now the hard work starts.
Configuring AD, installing SQL Server's, publish the Database and finally deploy LYNC 2013.
Author: Thomas Pött Managing Consultant Microsoft UC