If you want to use a DFs share as the file store in a Lync topology, you will need to install the Cumulative Update 5 after installing the Topology Builder but before you run it to configure your topology for the first time.
Further details and the fix can be found in this KB Article KB2666344
BrianC
This is some great news for advocates of Lync Enterprise Voice. Here is another study (albeit a US centric one) that suggests Lync EV is seeing huge success and is set for even more growth!
This concurs with what I am seeing when I’m talking to customers and people in the marketplace about voice platforms. There seems to be a real buzz about Lync and particularly Lync voice this year. I’ve christened it “year of the Lync”! 
Happy reading!
BrianC
When users upload documents etc to their meetings that are hosted by Lync, the files are uploaded to the Lync File store. One question that seems to come up a lot when designing Lync solutions for security sensitive customers is “Is the file store cleaned out regularly?”
The files remain on the file store until they are deleted by the meeting organiser or they are cleaned out by Lync after the meeting. The default time period for this automated clean out is 15 days after the meeting. However, this is configurable in the Conferencing Configuration using the ContentGracePeriod attribute.
Note: The following commands assume you only have the default “Global” collection of conferencing settings configured. If you have more than this, you should use the –Identity attribute to specify the collection you want to view/amend.
To view the current setting, open the Lync Management Shell and view the ContentGracePeriod attribute using this command:
Get-CsConferencingConfiguration
To change the value, use this command:
Set-CsConferencingConfiguration -ContentGracePeriod <value>
where <value> is the time period after the meeting that you want content to be deleted. This can be set to any value between 30 minutes (00:30:00) and 180 days (180.00:00:00). The default value is 15 days (15.00:00:00).
BrianC
This is a great blog entry from the Microsoft UC Group Team
who have summarised the past year with Lync. It includes links to some
excellent content and makes for interesting reading when comparing Lync to
other vendor’s offerings.
http://blogs.technet.com/b/uc/archive/2011/09/23/lync-gets-people-talking.aspx
Great post!
BrianC
I was asked how to check that Lync Schema upgrade was successful. Hopefully the following information is useful:
Use the following cmdlet to verify that schema preparation ran to completion:
• Get-CsAdServerSchema
This cmdlet returns a value of Schema_Version_State_Current if the schema prep was successful.
If you want to go a step further:
In ADSIedit, under the Schema Container, look for the ms-RTC-SIP-SchemaVersion attribute. Opening the properties, look for the rangeUpper attribute. Check the list below for the correct value for your environment:
• LCS 2005 – 1006
• OCS 2007 R1 – 1007
• OCS 2007 R2 – 1008
• Lync Server 2010 – 1100
For Lync, the rangeLower value should be 14.
Checking that the ms-RTC-SIP-SchemaVersion values on each DC is what is expected, confirms that the changes have replicated around your AD.
To confirm that AD replication has occured, you can use the following command:
• repadmin /replsummary
This shows the AD replication state and relative health of the forest.
BrianC
