Posts Tagged ‘Prerequisite’

Pre-requisites For Installing Lync 2010 Std Edition On Windows 2008 R2

October 25, 2011 1 comment

As more and more companies are deploying the unified communications product suite from Microsoft, 2011 will be a good time to master Lync 2010.

With that in view, following are the AD requirements for installing Lync.

  • All domain controllers should be running Windows 2003 (32 or 64bit) or higher.
  • Forest & domain functional level should be Windows 2003 native mode or higher.
  • 2003 mixed mode is not supported.
  • Atleast one GC should be available in each domain where you deploy Lync server.

AD schema has to be updated before Lync server can be installed. The pre-requisites are Lync Server Core components (which includes Lync Shell), .NET Framework 3.5.1 with SP1 & Remote server administration tools. IIS 7 features are required at a later stage and hence it is better to install all of these together in one go (with a single server restart).

Hence, run the following from an elevated PowerShell window to prepare your server to install Lync & update AD schema.

Import-Module ServerManager

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Static-Content,Web-Default-Doc,Web-Http-Errors,Web-Http-Redirect,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,Web-Windows-Auth,Web-Client-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools –Restart

If you are installing Lync on a 2008 SP2 Server, Powershell 2.0 has to be installed as well.

Preparing the schema, forest & domain are part of the Lync 2010 Deployment Wizard, which makes the process easier.

link related :

Categories: Lync Tags:

Exchange 2010 Pre-Requisites

October 17, 2011 2 comments

I’ve been working on Exchange 2010 Beta & RTM a lot lately and have found configuration of pre-requisites for the various single/combination of Exchange 2010 roles a breeze when running on Windows 2008 R2.

Instead of using the ‘ServerManagerCMD’’ routine in Windows 2008 (non-R2), the default Powershell ‘cmdlet’ ‘add-windowsfeature’ makes it very simple by adding all pre-req’s in a single line. Here’s what you need to run for the various roles: –


CAS = Client Access Server, HT = Hub Transport, MBX = Mailbox, UM = Unified Messaging, ET – Edge Transport


1. Import-Module ServerManager

2. Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy

Restart when 2. is complete

3. Set-Service NetTcpPortSharing -StartupType Automatic


1. Import-Module ServerManager

2. Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy,Desktop-Experience

Restart when 2. is complete

3. Set-Service NetTcpPortSharing -StartupType Automatic
Read more…

Categories: Exchange Tags: ,