18 September 2010
Important the following information is based on the Release Candidate and could change on RTM. Please check the latest documentation
With the release of Lync Server 2010 (RC) the settings which were deployed using group policy for OCS 2007 R2 are now for the most part sent using in-band provisioning to the client. There are a few setting which are used for Client bootstrapping and therefore still need to be configured in Group Policy.
The majority of group policy settings have been moved to PowerShell commands:
||Create a new client policy either at site or per-user scope
||Modify an existing client policy
||Assign a client policy to a user or group of users
||Remove a client policy from a user of group of users
||Get information on existing client policies
New-CsClientPolicy -Identity SalesPolicy -DisableEmoticons $True
Here we are creating a policy called SalesPolicy with 2 settings to turn off Emoticons and to turn off checking that the Outlook and Lync are running under the same account.
Now to apply this to the Sales department we can use the following:
Get-CsUser -LDAPFilter "Department=Sales" | Grant-CsClientPolicy
Here we are getting all the enabled users in AD who have a department of Sales and applying the policy to them.
You can also apply the Client Policy in Lync Control Panel as well
There are a large number of settings for the client policy so I won’t reproduce them here either check the documentation of in the Lync Management Shell use the following command to see all the options:
get-help New-CsClientPolicy -full | more
15 September 2010
If you thought licensing for OCS 2007 R2 was complicated we now have the licensing for Lync. http://www.microsoft.com/en-us/lync/pricing-licensing.aspx
The cost of an Enterprise CAL has come down but no longer includes telephony functions. Telephony in Lync server requires the new Plus CAL in addition to the Standard and Enterprise CALs. At the bottom there is the matrix of what each CAL covered both on R2 and Lync
If you have the Microsoft Enterprise CAL suite the Lync Standard and Enterprise CALs are included but the Plus CAL is still an addition.
The Lync client software is available either standalone or is included in the Office Professional Plus 2010 product.
Depending on your current Software Assurance your current OCS 2007R2 licenses as a qualifying license for Lync.
Having read details it has generated a lot of questions in mind and once I have answers I will update everyone.
IM and Presence
Audio, Video and Web Conferencing
15 September 2010
When you setup the topology for your Lync deployment you need to setup 3 simple URL’s. These URLs are used for administration, dial-in and Meet
The administration URL you keep within your internal network but the Meet and dial-in are required internally and externally. By default these are set to dialin.domain.com and meet.domain.com.
This may not seem to be a problem however if you have multiple SIP domains the number of SAN’s you require can become quite costly. A simple solution to these simple URL’s is to change them to use the same sub-domain for example lync.domain.com/dialin and lync.domain.com/meet.
Using this format halves the number of SAN’s required at the expense of slightly lengthening the actual URL.
The other consideration is that these URL’s expect you to have split brain DNS as there is no external/internal option for defining these. However if you don’t have split brain DNS the request can route externally and the meeting GRUU that is returned enables you to connect either directly internally or externally.
13 September 2010
After months of talking about Wave 14 and CS2010 the product has finally been given its official name ready for release. We now have Microsoft Lync Server 2010. The full rebranding is as follows
If you want to try out the Release Candidate then you can download everything you need from here
Over the next few weeks I’ll be blogging about the new functionality.
29 July 2010
If you install all the current patches to your server before installing OCS it will install .NET Framework 4.0. When .NET 4.0 is installed OCS cannot detect .NET 3.5 and you receive the error message
Microsoft Office Communications Server 2007 R2, Microsoft Unified Communications Managed API 2.0 Core Redist 64-bit installation requires Microsoft .NET Framework version 3.5. Installation cannot continue.
Microsoft has put up a knowledge base article kb2224981 describing the issue and also the work around.
To resolve this problem, follow these steps:
- Remove .NET Framework 4.0 from the server.
- Install the OCS products that you want to have on the server
- Install .NET Framework 4.0 on the server
27 July 2010
By default OCS only installs the US English language pack for Response Groups. There are 11 other language packs you can install. The RGS uses the UCMA 2 Speech language packs which can either be found on the OCS install CD in the \Setup\amd64\Setup\Speech\ directory. You can also download the packs from here.
After running the msi to install the language pack you need to register the language pack. To install the language packs you need to run the rgslang.exe application from the OCS 2007 R2 Resource Kit. From a cmd prompt run RGSlang sync then restart the RGS service. Full details of the install process can be found on TechNet.
As well as the speech packs you can also manage OCS in different languages or display the OC Tab in a different language by downloading the Response Group Service Language Pack.