It is Friday (half day) again and I can go back my playground. I have been waiting for Lync Mobile Client quietly for some time and today my patience ran out. I know that deploying CWA (Communicator Web Access) will not give me reach experience but, it least, some IM connectivity when away from the commuter.
Since this is greenfield Lync installation (OCS or R2 have never been present), the AD Schema was not prepped for OCS. I will do it now. My OS of choice is Windows Server 2008 R1 SP1 standard edition. Dues to the fact that “Microsoft Office Communications Server R2, Core components” and “Microsoft Office Communications Server R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit” will be installed, I cannot use any server where Lync bits are already installed.
Since we will ONLY have one virtual web server, I think any web server that exist in the environment could do. However, a careful evaluation of IP addresses and used ports must be done beforehand.
As first step I will download Communications Server 2007 R2 Core Components Runtime package from this link: http://www.microsoft.com/download/en/details.aspx?id=4070 and install it in my Domain Controller (which is also a Schema Master).
The components are now installed in “C:\Core Components Runtime Runtime Package”.
I will use “ldifde” tool to prep the schema for OCS. The command in this case will be:
ldifde -i -v -k -s DC1 -f schema.ldf -c DC=X “DC=lynclog,DC=com”.
***Note that if you are logged as different user, you must use the “-b” parameter in format:
ldifde –i –v –k –s DC1 –f schema.ldf –c DC=X “DC=contoso,DC=com” –b Administrator contoso password
More information can be found here: http://technet.microsoft.com/en-us/library/dd441329(office.13).aspx
In Command Prompt I will navigate to C:\Core Components Runtime Runtime Package and run the above command.
Strangely, I received an error and since couldn’t find any reference on Internet, decided to modify “schema.ldf” file where I replaced every instance of “DC=X” with “DC=lynclog,DC=com” and now my command looked like this: “ldifde -i -v -k -s DC1 -f schema.ldf”. The command ran sucessfuly this time. Go figure…
Because I must use LcsCmd.exe to proceed further, I will install sqlncli_x64.msi, vcredist_x64.exe, and ocscore.msi (in this order), located in C:\Core Components Runtime Runtime Package.
I need also .NET and so, I will run servermanagercmd -install Net-Framework Net-Framework-Core Net-Win-CFAC Net-HTTP-Activation NET-HTTP-Activation WAS WAS-Process-Model WAS-Net-Environment WAS-Config-ApIs
LcsCmd.exe is now located in C:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2.
Time to run LcsCmd.exe /forest /action:forestprep and LcsCmd.exe /domain /action:domainprep
***Because I am done with the Domain Controller, it is safe to remove the core components.
It is now imperative to run Lync Server Deployment Wizard and run the Schema Prep again.
Even thou I don’t have (yet) any OCS servers in this environment, I will “Merge” the topology at this point.
Darn, I forgot to install the Backward Component Module located in the installation media.
Now “Merge” complete successfully.
Moving now to our CWA server – first the prereqs. I will run “Import-Module ServerManager” from Powershell and then “Add-WindowsFeature web-windows-auth,web-digest-auth,web-basic-auth,web-mgmt-compat,web-mgmt-console,web-common-http,web-ISAPI-ext,web-ISAPI-filter,web-request-monitor,web-http-redirect,web-http-logging” and of course – “servermanagercmd -install Net-Framework Net-Framework-Core Net-Win-CFAC Net-HTTP-Activation NET-HTTP-Activation WAS WAS-Process-Model WAS-Net-Environment WAS-Config-ApIs”
The CWA role Deployment guide can be found here: http://technet.microsoft.com/en-us/library/dd441267(office.13).aspx
***I already requested and imported Public Certificate from StartCom – steps which will not be described here.
I must create an account at this point…
…and of course – set it in AD to “password never expire”.
Next step – Create virtual server.
***I must be careful to select a port number that is not in use from any other application that could be already installed on this box.
Lastly – Publish the URL’s
***Install the required updates:http://go.microsoft.com/fwlink/?LinkID=202639
Now I will Merge the topology again and check if my CWA server is present.
Indeed, my server is now shown In the Legacy Trusted Application Servers list and I will publish the Topology at this point.
Next I will restart the Lync server services from Lync Management Shell:
Time to test my CWA deployment: