The C-spot

Lync 2010 Client Unsupported with OCS.

Logon with Lync 2010 client to an OCS 2007 server.

This scenario is not supported, the Lync Client only functions correctly when used with the intended Lync Server back-end. Now this approach is no different then what was supported between the last major releases of LCS and OCS as Office Communicator clients could not sign-in to LCS servers.

Although that was due to mainly the introduction of the Enhanced Presence states which LCS was not aware of. For this release it’s the basic fact that much of the new client capabilities stem from changes to the back-end server components, thus using the Lync client against and OCS 2007 R2 server will offer a pretty limited experience.

So, it is possible but with a lot of limited features, i don’t think is’t good idea to offer this solution to your users. They will have a lot of frustrations about the product.

/Tim

These are the new released Lync 2010 cumulative updates and fixes:

• Cumulative update package for Lync 2010 (64bit) & (32 bit): January 2011 http://support.microsoft.com/?kbid=2467763
• Cumulative update for Microsoft Lync 2010 Phone Edition for Polycom CX700 and LG-Nortel IP Phone 8540: January 2011 http://support.microsoft.com/?kbid=2493722
• Cumulative update for Lync 2010 Phone Edition for Aastra 6721ip and Aastra 6725ip: January 2011http://support.microsoft.com/?kbid=2493724
• Cumulative update for Lync 2010 Phone Edition for Polycom CX500, Polycom CX600, and Polycom CX3000: January 2011 http://support.microsoft.com/?kbid=2493723
• Cumulative update for Lync 2010 Attendee – Administrator level installation: January 2011 http://support.microsoft.com/?kbid=2467762
• Cumulative update for Lync 2010 Attendee – User level installation: January 2011 http://support.microsoft.com/?kbid=2467761
• Cumulative update for Lync 2010 Attendant: January 2011 http://support.microsoft.com/?kbid=2467760
• Update for Lync 2010 Group Chat Client: January 2011 http://support.microsoft.com/?kbid=2467765
• Update for Lync Server 2010, Group Chat Administration Tool: January 2011http://support.microsoft.com/?kbid=2467764

/Tim

If you can’t add domain or enterprise admins, there is a workaround for this!

Turn on advanced features in AD and go to the users security tab.

Normally you should create another (second) user for using LYNC for all admins, but if you really need this, do it this way.

Mark include inheritablepermissions from the object’s parent.

Click OK.

/Tim

If you allready have a CMS installed in your domain you can remove the old CMS by entering the following command in the lync powershell: remove-csconfigurationstore.

This command will actually remove the service control point in Active Directory that points to your Central Management Store.

When you perform Remove-CSconfigurationStoreLocation the reference is deleted from active directory.

To completely remove references to old topology objects, you will also need to remove some additional entries using ADSI Edit.

/Tim

Configure Lync communicator client policy error by importing the adm file.

This is a bug in the adm file. Open the adm file with notepad and change the next values:
PolicyGalUseCompactDeltaFile=”Use Compact Delta File for GAL”
ExplainText_GalUseCompactDeltaFile= “This policy allows Microsoft Lync to use compact delta file for GAL.”
GalUseCompactDeltaFileVal0=”Do not use compact delta file”
GalUseCompactDeltaFileVal1=”Use compact delta file (default)”
GalUseCompactDeltaFileVal2=”Use compact data file, but do not issue an LDAP query to retrieve the ‘Title’ and ‘Office’ attribute from AD.”

After these changes the adm file works fine.

/Tim