Limited Functionality Error After Cumulative update

After Installing cumulaive update on all Lync servers we need to update database.
Installation of update will be very smooth and very less issues.But when it comes to update database its very critical and your heart beat will increase!!!For me yes..i have very bad experience on update database command.Whenever i have updated my database(SQL Cluster) My lync shows limited Functionlity error.
I tried with bothe of the commands

1- Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <EEBE.Fqdn> -UseDefaultSqlPaths

2- Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <EEBE.Fqdn>

Initially i struggled alot and played in SQL,but no luck last i got the solution.
Whenever i am getting Limited Functionlaty error i went and checked in my SQL databases using SQL management Studio and Found my rtcdyn database changed to single user mode.If i try to alter the same to multiuser mode it will not allow.
But Dont worry rtcdyn doesn't have any critical datat and it is only a dynamic content based on users login and activities it will udate.So what i done here is

Stoped SQL services
Gone to the physical path of the rtcdyn data path and Log Path
Renamed those files to something Else
Started SQL services
Open SQL Management Studio
Now you can see empty rtcdyn Database
Just right Click and delete the same.
Now goto the Front end server and run Below command

Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn < EEBE.Fqdn > -DatabasePaths <RtcDyn log path>, <RtcDyn data path>

 This will recreate your rtcdyn database and if you signout your Lync and signin back you can see preence and contacts.
Enjoy!!!!!!

If you have any suggession or any other solution Feel free to write here in Comments.

 

Lync 2013 Guides

Microsoft come up with new product every now and there it is very difficult to support people to upto date on their technologies.Anyway we have to be upto dated else we will be out of market.
Ignite have wonder full document to learn more about Lync 2013 and Exchange 2013 ,here it goes

Lync 2013 Guides

Exchange 2013 Guides

Move CMS from Lync 2010 to Lync 2013

When we introduce Lync 2013 on Lync 2010 infra CMS will be on Lync 2010.So if we want to move the CMS to new 2013 pool here is the steps.
For safer part we can take config backup using export-csconfig and export-cslisconfig.
Next step is to install CMS store new Lync 2013 pool for that run the below command.

Install-Csdatabase -centralmanagementdatabase -usedefaultsqlpaths -sqlserverfqdn <backendsqlserverfqdn>

Next step is to move CMS server.

move-csmanagementserver

If the source cms server is offline you can use below command.

Move-CsManagementServer -ConfigurationFileName "C:\configfile.zip" -LisConfigurationFileName "C:\CsLisConfigfile.zip" -Force

Lync with Cisco VCS Integration/HD Integration

Most of the organisation wil be having High defnition conference feature available.So the users who are using Lync they can utilise that feature using Lync client easily with below steps.The document is svailable on Cisco sites but still below one will be an easy refernce for you.

First you need to add VCS domain as truted application in Lync topology then only Lync will accept request from VCS.

Here is command to make VCS as trusted application:
1- Add application pool
New-CsTrustedApplicationPool -Identity <vcsdomainfqdn> -Registrar LyncFEPool -site <Sitenumber you want to integrate> -RequiresReplication $false -ThrottleAsServer $true -TreatAsAuthenticated $true

2- Add application
New-CsTrustedApplication -ApplicationID VCSApplication1 -TrustedApplicationPoolFqdn <vcsdomainfqdn> -Port 5061
3- Set The encryption Level.
set-CsMediaConfiguration -EncryptionLevel supportencryption
4- Create static route to route the request towards VCS.
$Route1=New-CsStaticRoute -TLSRoute -Destination "vcsdomainfqdn" -MatchUri "domainname" –Port 5061 -UseDefaultCertificate $true
Set-CsStaticRoutingConfiguration -Identity global -Route @{Add=$Route1}

Above part is from Lync side.Same way need to configure Cisco VCS to accept lync request.
Once both side configured you can dial conference number from Lync and enjoy the conference from your Desk.
 

Port Requirements for Lync 2010 Application sharing with external user

For Small buisness network this topic may not be that much usefull,but for a Large enterprise with restricted network setup this will be very usefull.Below requirements i captured using lot of testing and network tracing.When i recieved this requirement there was no articles clearly mentioned about how we can achieve this,all was mentioned some specific ports for application wise.

Scenario:Users are sitting in a restricted network.User only have text IM access with othere users as well as federation/external users.Requirement here is to application sharing with external/federated users.After the study i concluded with below ports for application sharing with external users.

Public to edgeserver:

TCP/443

UDP/3478

TCP/8057

TCP/50,000-59,999 (Outbound only)

From the internal Client to the internal Edge:

TCP - 443
UDP – 3478

Above ports for only to conference and Media traffic from internal user to External user.

If you wanted to have internal conference between 2 restricted netwok users below is the port requirements.

Client to Front End Pool

UDP		49152 to 57500
TCP		8057
TCP		443
TCP		49152 to 65535
TCP		448

Client to AV Pool

UDP		49152 to 57500
UDP		57501 to 65535

 

Lync 2010 User provisioning using AD Attributes

When it comes to Large setup you may need to provision users using some thirdparty tools or any other scripts.Here i faced major challenge like tried with dfault attributes but it was not success.User was showing not enabled for Lync access.

Below is the attributes i enabled initially.

sRTCSIP-PrimaryUserAddress:
msRTCSIP-UserEnabled: TRUE
msRTCSIP-PrimaryHomeServer:
msRTCSIP-FederationEnabled: TRUE
msRTCSIP-InternetAccessEnabled: TRUE
msRTCSIP-OptionFlags: 257

But it failed to enable users in Lync.Finally after lot of try i got solution like i need to enable default user policy also.below is the attribute which we need to enable.

msRTCSIP-UserPolicies:

Hope this will help you to enable using AD attributes or using FIM or any other provisioning tools.

Set Media Port Ranges in Lync

Here i am explaining this mainly for Enabing QoS for Lync services.If your organization is with large network this is necessary to limit lync Media traffic into a defined port ranges.SO this QoS can be enabled inall network appliances and assign the bandwidth from the network level.
Below is the commands to set the mediaports in Lync 2010

Client Ranges

Set-CsConferencingConfiguration -ClientMediaPortRangeEnabled 1 Set-CsConferencingConfiguration -ClientAudioPort 20000 -ClientAudioPortRange 40 -ClientVideoPort 20040 -ClientVideoPortRange 40 -ClientAppSharingPort 20080 -ClientAppSharingPortRange 40 -ClientFileTransferPort 20120 -ClientFileTransferPortRange 40 -ClientMediaPort 20160 -ClientMediaPortRange 40

Lync Pools

Set-CsConferenceServer -Identity <PoolFQDN> -AppSharingPortStart 40803 -AppSharingPortCount 8348

Set-CsApplicationServer -Identity <PoolFQDN> -AppSharingPortStart 40803 -AppSharingPortCount 8348