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!

How to search user in Lync server 2010 control panel?

How to search user in Lync server 2010 control panel?

You can search for users by using the Lync Server Control Panel or the Active Directory Users and Computers snap-in.

To search for one or more users via Lync server control panel-

1.   From a user account that is assigned to the CsUserAdministrator role or the CsAdministrator role, log on to any computer in your internal deployment.

2.   Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel.

3.   In the left navigation bar, click Users.

4.   In the Search users box, type all or the first portion of the display name, first name, last name, SAM account name, SIP address, or line URI of the user account that you want to search for, and then click Find.

5.   (Optional) Specify additional search criteria to narrow the results:

     a. Click the expand arrow button in the upper-right corner of the screen above Search  results, and then click Add Filter.

    b. Enter the user property by typing it or clicking the arrow in the drop-down list to select a user property.

   c. In the Equal to list, click Equal to or Not equal to.

   d. In the text box, type the search criteria you want to use to filter search results, and then click Find.

Microsoft Lync Server 2010 Software and Hardware requirement.

Microsoft Lync Server 2010 Software and Hardware requirement.

Hardware Requirement:-

•  Lync Server 2010 is available only in 64-bit., which requires 64-bit hardware and 64-bit editions of Windows Server.
•  Lync Server 2010 is not available in a 32-bit version.
•  Lync Server 2010 required multiple processor groups (dynamic hardware partitioning)

Software Requirement:-Operating Systems for Server Roles

Microsoft Lync Server 2010 supports the 64-bit editions of the following operating systems:
•  The Windows Server 2008 R2 Standard operating system (required) or latest service pack (recommended)
•  The Windows Server 2008 R2 Enterprise operating system (required) or latest service pack (recommended)
•  The Windows Server 2008 R2 Datacenter operating system (required) or latest service pack (recommended)
•  The Windows Server 2008 Standard operating system with Service Pack 2 (SP2) (required) or latest service pack (recommended)
•  The Windows Server 2008 Enterprise operating system with SP2 (required) or latest service pack (recommended)
•  The Windows Server 2008 Datacenter operating system with SP2 (required) or latest service pack (recommended).
•  To deploy Lync Server 2010 on a computer that is running either the Windows Server 2008 R2 Datacenter operating system or the Windows Server 2008 Datacenter   operating system with Service Pack 2 (SP2)

Lync Server 2010 is not supported on the following operating systems:

•  The Server Core installation option of Windows Server 2008 R2 or Windows Server 2008
•  The Windows Web Server 2008 R2 operating system or the Windows Web Server 2008 operating system
•  Windows Server 2008 R2 HPC Edition or Windows Server 2008 HPC Edition

Backend server (SQL) requirement:-•  Microsoft SQL Server 2008 Express database software, which is installed by default when you install Lync Server 2010, to Microsoft SQL Server 2008 R2 Express.
•  The SQL instance name is RTC for a Standard Edition server back-end database and RTCLocal for the local configuration store (on each server role).
•  A server running Lync Server 2010 Standard Edition has both SQL instances, and each needs to be upgraded separately.

Event id: 7034

An event is any significant occurrence in the system or in a program that requires users to be notified, or an entry added to a log. The Event Log Service records application, security, and system events in Event Viewer. With the event logs in Event Viewer, you can obtain information about your hardware, software, and system components, and monitor security events on a local or remote computer. Event logs can help you identify and diagnose the source of current system problems, or help you predict potential system problems.

Today I am trying to collect the information based on Event id: 7034 so that it would be useful for the people to get the information at one place.

1.       Alert Name: User Code Host service fails to start

Source: Service Control Manager

Event ID: 7034

Level: Error

Article: Microsoft KB:

http://support.microsoft.com/kb/2509267

http://xblogs.kompas-xnet.si/post/SharePoint-User-Code-Service-not-starting.aspx

Resolution Mentioned:

Set the data value of ProcessNameFormat in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance to 1

2.      Alert Name: Service instance provisioning failed

Summary: An attempt to start or stop a service instance failed on a server in your farm because the service instance provisioning failed.

Resolution: Start the service (Please refer the following for detailed documentation)

Article: http://technet.microsoft.com/en-us/library/ff519517.aspx

3.      Alert Name: Service Stop Operations

Applies To: Windows Server 2008

Description: Service Control Manager (SCM) stops services and driver services. It also reports when services terminate unexpectedly or fail to restart after it takes corrective action.

Message: The %1 service terminated unexpectedly. It has done this %2 time(s).

Article: http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-event-id-7034-service-stop-operations.aspx

Reference: http://technet.microsoft.com/en-us/library/cc756361(WS.10).aspx  

4.      Alert Name: The Windows Firewall has detected an application listening for incoming traffic.

Event Type: Failure Audit

Event Source: Security

Event Category: Detailed Tracking

Article: http://www.eventid.net/display.asp?eventid=861&eventno=4615&source=Security&phase=1

5.      Log name: Application

Source: SharePoint Foundation

Task Category: Web controls

user: domain name\usernaccount name

Description: Load control template file file/_controltemplate/taxonomypicket.ascx failed

Article: http://todd-carter.com/post/2010/05/03/Help-Wanted-Taxonomy-Picker.aspx