We've reached a junction on the Path to Lync Server. From this point on we're not speculating or planning or brainstorming. Now we're working with Lync Server 2010 itself. First stop? The install.
Now, I'm not going into heavy detail here about the actual installation process. The Lync Server documentation will guide you better there.
Deployment of Lync Server 2010 – TechNet
There's also an excellent step-by-step Lync Server Install post at OCSPedia.com.
What I'll talk about today are some things you should keep in mind during the install.
If You're Migrating, Read Up.
Two ways to approach a Lync Server install – you're either installing fresh, or you're migrating from a previous solution. For sake of argument let's say it's OCS 2007.
Microsoft has a whole reference library on TechNet to help guide you through an OCS migration.
Migration from Office Communications Server 2007 R2 to Lync Server 2010 – TechNet
Prepare Active Directory.
Active Directory Domain Services needs a few updates to fully support Lync Server 2010. New classes and attributes must be installed on your Windows Server (2008, 64-bit), to prepare it for storing URI information and user object extensions.
The Lync Server Deployment Wizard will help you – it installs the necessary core components and system updates for Lync installs (.NET Framework 3.5, Visual C++ 2008, RSAT) .
Don't install Lync on a DC.
Lync Server won't like you if you try installing it on a domain controller. This is by design, and it will frustrate you if you try. Deploy a fresh Windows 2008 Server, either physical or virtualized with Hyper-V.
Do You Have a Topology Ready?
If you read my post on the Lync 2010 Planning Tool, then you know it can create & export a topology for you. Having a pre-configured topology on hand will save you time during the Topology Builder phase of the Lync install…
Define the Director First.
Once the initial deployment is up & running, you can define additional server roles. A/V Conferencing,Edge Servers,etc. If you plan to allow access for external users, it's a good idea to deploy a Director before the Edge Servers go up. The Director role authenticates internal/external user requests, and helps protect against traffic overloading.
Deploy Enterprise Voice Last.
Wait until last to deploy the Enterprise Voice role. It requires a basically-complete Lync Server setup to run, as you'll see by its prerequisites. There's more documentation on Deploying Enterprise Voice here.
I'd even suggest doing the Lync installation, taking a break, and coming back for Enterprise Voice.
I'll go into more configuration details next week, on Step 7: Configure Lync to Your Office.
What do you think of Lync so far? How'd the install treat you? Comment and let's talk about it.