Incompatible Security Setting’ error occurred in Office communicator while calling.

Incompatible Security Setting’ error occurred in Office communicator while calling.
 I came across ‘Incompatible Security Setting’ issue; there are many people which are affected regarding this issue.

Already verified configuration the VoIP security setting in the properties of the Unified Messaging Dial Plan to use ‘Secured’. It is set as Secured.

After checking all configuration, look over the Registry and found the "PC2PCAVEncryption" key is missing from users computer.

After adding above key rebooted computer and calling worked fine

Here are the steps to verify Registry and if any key missing then add the same:

1. Click on Start > RUN> type ‘regedit’ and say OK.

2. Expand and verify the following registry entries -


[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]

"MaxAudioVideoBitrate"=dword:0003e800

"PC2PCAVEncryption"=dword:00000000

"DisablePC2PCAudio"=dword:00000000

"DisablePC2PCVideo"=dword:00000000


Thank you!

What are the Software prerequisites for Lync Server 2010?

What are the Software prerequisites for Lync Server 2010?

I have tried installation of Lync Server on lab and faced numerous error messages.

Unfortunately, Lync Server 2010 generates the few generic error messages. The error itself states the problem, but it does not mention which modules are not installed. The simply states that all are needed.

Like: The cmdlet completed with errors.

 

There are number of software prerequisites must be met before begin the installation.

  

Active Directory Prerequisite- 

• Update Active Directory to support Lync Server.
• Active Directory topologies are supported are:
• Single forest with single domain
• Single forest with a single tree and multiple domains
• Single forest with multiple trees and disjoint namespaces
• Multiple forests in a central forest topology
• Multiple forests in a resource forest topology
• The Active Directory forest must be Windows Server 2003 Native Mode or higher, and all the domains in which Lync Server 2010 will be deployed must also be Windows Server 2003 Native Mode or higher.

The domain controllers must be Windows Server 2003 (32-bit or 64-bit) or higher,

 

The Schema, Forest, and Domain preparation must be performed from a 64-bit machine.

Lync Server 2010 is supported on the following Windows Server versions:

• Windows Server 2008 Standard (with SP2)
• Windows Server 2008 Enterprise (with SP2)
• Windows Server 2008 Datacenter (with SP2)
• Windows Server 2008 R2 Standard
• Windows Server 2008 R2 Enterprise
• Windows Server 2008 R2 Datacenter

The SQL Server version, of which the Following are supported (only 64-bit versions are supported):-

• SQL Server 2005 Standard (with SP3)
• SQL Server 2005 Enterprise (with SP3)
• SQL Server 2008 Standard (with SP1)
• SQL Server 2008 Enterprise (with SP1)
• SQL Server 2008 R2 Standard
• SQL Server 2008 R2 Enterprise
• SQL Server Express (for Lync Server 2010 Standard Edition and the local server databases).

 Required components-

There are number of additional components are required:

•  Windows PowerShell 2.0
• .NET Framework 3.5 with SP1
•  Windows Installer Version 4.5

Individual roles have different additional component requirements based on their configuration:

Front-End Servers and Directors require IIS modules installed:

• Static content
• Default document
• HTTP errors
• ASP.NET
• .NET extensibility
• Internet Server API (ISAPI) extensions
• ISAPI filters
• HTTP logging
• Logging tools
• Tracing
• Windows authentication
• Request filtering
• Static content compression
• IIS management console
• IIS management scripts and tools
• Anonymous authentication
• Client certificate mapping authentication

If you attempt an installation without any of these, we will see generic error messages.

Thank you!

Useful power shell command

Hello Friends,



While performing Administrative duty, We require to enable, disable, Lync user list, Specific OU user list etc task multiple time. GUI mode is not good option. Instead GUI you can use CMDLETS,


Here are the lists of cmdlet which are getting use daily basis.

The difference between Get-CsUser and Get-CsAdUser:


Both cmdlets return information about Lync users. Use Get-CsUser unless you require access to the generic AD attributes, or if the user has not been enabled for Lync Server
Show all the properties returned by Get-CsUser:

Get-CsUser
Get-Member

Show the number of Lync enabled users:

@(Get-CsUser).Count

Get all AD users who are not, and who have never been, enabled for Lync or OCS:

Get-CsAdUser -Filter {Enabled -eq $null}
Format-Table -Wrap

Get users who are disabled for Lync or OCS:

Get-CsAdUser -Filter {Enabled -eq $False}

Get all users who have been enabled for Lync or OCS but are not currently assigned to a registrar pool.

Get-CsUser -UnassignedUser

Get all Lync Users in the 'Sales' Department (You may change sales name with any other name):

Get-CsUser -LDAPFilter 'Department=Sales'



Thank you!