Lync Server 2010 Pricing and Licensing Details

http://www.microsoft.com/en-us/lync/pricing-licensing.aspx

It is totally more than microsoft office communications server 2007

1. You can virtualize all topologies and we support all workloads, including Enterprise Voice to be virtualized
2. When you virtualize, Scalability is roughly 50% of the scalability offered by a Lync Server 2010 topology running only on physical servers
3. In Microsoft Lync Server 2010, A/V Conferencing service functionality, which normally runs on the Front End Server, can also run in a standalone server role called A/V Conferencing Server
4. If your site has more than 10,000 users, we recommend that you deploy a separate A/V Conferencing pool
5. Lync introduced ‘Survivable Branch Appliance’, which is a new device introduced in Lync Server 2010 that combines a PSTN gateway with a Lync Server Registrar and Mediation Server. This appliance is targeting branch offices who require telephony services in case of WAN failures with the central site
6. In the event a branch office’s WAN connection to a data center fails, the Survivable Branch Appliance provides the following voice features to users in that branch office:
   1. PSTN inbound and outbound calls
   2. Intra-site and inter-site calls
   3. Call hold, retrieve, and transfer
   4. User authentication and authorization
   5. Leaving and retrieving voicemail
   6. Call forwarding, simultaneous ringing, boss-administrator, and team calling
   7. Call Detail Recording (CDR).
   8. All two-party functionality, including instant messaging and audio-video conferencing
   9. PSTN dial-in conferencing with Conferencing Auto-Attendant
7. In Lync Server 2010, the Director is now a unique server role which you cannot home users on it
8. A Director is not designated as either a Standard Edition server or an Enterprise Edition server; it does not require any type of Microsoft Lync Server 2010 license (interesting huh)
9. Collocation of mediation with FE is recommended if you are not using SIP trunking or Direct SIP
10. New to Lync is the ‘Topology Builder’ which is a wizard-driven user interface that you use to create and edit your Microsoft Lync Server 2010 topology
11. With Microsoft Lync Server 2010, configuration data about servers and services is moved to the Central Management store. Read-only copies of the data are replicated to all servers in the topology, including Edge Servers and survivable branch appliances
12. Although most of the Lync configuration is stored in the central management store, the Active Directory Domain Services (AD DS) are still used to store basic Lync Server user information, such as the user’s SIP URI and phone number
13. The Lync Server 2010 Management Shell is a new method of administration and management
14. Lync introduces role-based access control (RBAC). Lync Server 2010 includes 11 predefined roles that cover many common administrative tasks
15. Administration console is no longer using MMC, Lync Server Control Panel replaces the MMC administrative interfaces of previous releases
16. Microsoft Lync Server 2010 introduces DNS load balancing for load balancing for SIP and media traffic (you will still need hardware LB for other traffic such as HTTP however this is the easiest part in configuring a HW load balancer)
17. DNS load balancing is supported for Front End pools, Edge Server pools, Mediation Server pools, and Director pools
18. Microsoft Lync 2010 Attendee is a new downloadable client that enables users without Microsoft Lync 2010 to attend meetings
19. You manage Edge Servers from the internal network. All configuration data for servers and services resides in the Central Management database, which you can manage by using internal administrative tools
20. Lync Server 2010 introduces support for integration with hosted Exchange UM
21. Lync supports Enhanced 9-1-1 (E9-1-1) as part of your Enterprise Voice deployment
22. New for the Mediation Server in Microsoft Lync Server 2010 is the ability for a single Mediation Server to route outbound calls through multiple gateways
23. Also new for Lync Server 2010 is the ability for a Mediation Server to be deployed as a pool; this pool can be collocated with the Front End pool, or can be a standalone pool
24. Malicious call tracing enables users to flag incoming calls which are harassing, threatening, or obscene. Immediately after hanging up, the user can select an option to report the call as malicious. If they do so, a trace request is sent to mark the record of the call, and an event is logged
25. Lync introduced the concept of ‘Anonymous call’ in the Response Group feature, when a response group is so configured, agents can accept incoming and make outgoing calls on behalf of the response group without revealing their identity (Anonymous call). Anonymous calls do not support conferencing, application sharing and desktop sharing, file transfer, whiteboarding and data collaboration, or call recording
26. Archiving policy settings for both IM and meetings are unified. The core archiving store contains both IM content and Web conferencing attendee entries and exits consolidated together
27. You can do searchable transcript of archived information without the need for scripts
28. In Microsoft Lync Server 2010, the Group Policy settings used in previous Office Communications Server releases are now controlled by in-band provisioning client policies that are server-based.
29. Lync 2010 clients can now receive updated software from Windows Server Update Service (WSUS) or Microsoft Update instead of from a location hosted on Lync Server 2010
30. Lync Server 2010 provides support for analog devices. Specifically, the supported analog devices are analog audio phone and analog fax machines. Now you can configure the analog gateways and devices in your organization to use Lync Server 2010. After you do this, analog devices use Lync Server to make and receive calls, and Lync Server makes routing decisions and log calls in call detail records (CDRs) for analog devices, just as it does for any device

Powerpoint Whiteboard and New Poll are not activated ????

I faced to a serious and unidentified error while i am doing my first lync installation. I Saw my Powerpoint Whiteboard and new poll buttons are not enabled. Due to Lync is new to me I thought it was an error with certificate configurations and I went through every certificate and analyzed. But every things are correct. Then I asked about it from one of my friend who works with Microsoft. Aftr That I understood while I am not in the meeting I cannot see thease options.

Microsoft Lync 2010 Attendee (RC) - User Level Install

As I told you earlier, Microsoft Lync is new name for Office Communications Server. It is most powerful and reliable tool for solve communication troubles that occurs within an organization.

Microsoft Live meeting released with OCS 2007 R2 has now changed to Microsoft Lync Attendee. But in Microsoft Lync 2010 Attendee is a conferencing client that allows users without Microsoft Lync 2010 installed.to participate in online meetings. If you are not an administrator on the computer but an administrator has allowed you to perform installations, you can install this application.

Overview

Join Meetings

With Lync 2010 Attendee, a user can join a meeting in one of two ways:

1. As an unauthenticated user, by providing a guest display name.
2. As an authenticated user by providing corporate credentials.

Depending on how the organizer has set up the meeting, the user will either join the meeting immediately or wait in the lobby until a meeting presenter admits the user.

Latest Videos found From Microsoft

http://www.msteched.com/2010/NorthAmerica

Upgrade Communicator 2007 to Lync 2010

Just like previous versions, you can perform an in-place upgrade directly to Lync 2010 client (release candidate) from Communicator 2007 R2. You will be prompted to close any affected applications that are opened at the time of running setup for the Lync 2010 client. At the end of installation, you can choose to start and run the Lync client to get online immediately.

Microsoft Lync Release Candidate Launched..- System Requirements ?

Operating System Requirements for Servers Running Lync Server 2010

Servers running any of the following Lync Server 2010 server roles must run a 64-bit edition operating system: Standard Edition Server Front End Server Edge Server A/V Conferencing Server Mediation Server Monitoring Server Archiving Server

Each server must run a 64-bit edition of the following operating systems: The Windows Server 2008 R2 Standard operating system The Windows Server 2008 R2 Enterprise operating system The Windows Server 2008 Standard operating system with Service Pack 2 (SP2) The Windows Server 2008 Enterprise operating system with SP2

Hardware Support for Servers Running Lync Server 2010

The following table describes the recommended minimum hardware for all servers where you plan to install Lync Server 2010.

Hardware component	Minimum requirement
CPU	One of the following: • 64-bit dual processor, quad-core, 2.0 gigahertz (GHz) or higher • 64-bit 4-way processor, dual-core, 2.0 GHz or higher
Memory	16 gigabytes (GB) recommended
Disk	Local storage with at least 72 GB free disk space on a 10,000 RPM disk drive
Network	2 network adapters, each 1 gigabits per second (Gbps)

Database Server Requirements

In addition to these server roles, a Lync Server deployment also includes database servers. These include a back-end database, an archiving database, and a monitoring database. For these databases, the following software is supported:

• The 64-bit edition of Microsoft SQL Server 2008 with SP1 Enterprise database software
• The 64-bit edition of Microsoft SQL Server 2008 Express (for Standard Edition server only; it is automatically installed by Lync Server 2010 on each Standard Edition server)
• Microsoft SQL Server 2005 Enterprise Edition with Service Pack 3 (SP3) or the 64-bit edition of SQL Server 2005 Standard Edition with SP3

Hardware Support for Database Servers: Recommendations for Back End Servers and Other Database Servers

The following table describes the recommended minimum hardware for database servers in a Lync Server Enterprise Edition deployment. Although they host their own Lync Server database, Standard Edition servers use the hardware recommendations in the “Hardware Recommendations for Servers Running Lync Server 2010” Table.

These recommendations apply to servers hosting back-end databases, Monitoring Server databases, and Archiving Server databases.

Hardware component	Minimum requirement
CPU	One of the following: • 64-bit dual processor, quad-core, 2.0 gigahertz (GHz) or higher • 64-bit 4-way processor, dual-core, 2.0 GHz or higher
Memory	32 GB recommended for back-end server (with or without collocated Archiving and Monitoring databases), 16 GB recommended for Archiving and Monitoring database (not collocated with the Back End Server)
Disk	Local storage with at least 72 GB free disk space on a 10,000 RPM disk drive
Network	2 network adapters, 1 Gbps each

Client Software Requirements

This section summarizes the software support for the following Lync Server 2010 clients:

• Microsoft Lync 2010
• Online Meeting Add-in for Microsoft Lync 2010
• Microsoft Lync 2010 Attendee
• Microsoft Lync 2010 Attendant

Operating Systems Requirements

Supported operating systems for these clients include the following:

• Windows 7
• Windows Vista
• Windows XP Professional with Service Pack 3 (SP3)

Other Software Requirements

Browser and Operating System Combinations for Microsoft Lync 2010, Online Meeting Add-in for Microsoft Lync 2010, and Microsoft Lync 2010 Attendee. Lync Web App supports specific combinations of operating systems and browsers. The following table lists the various combinations.

Operating System	Internet Explorer 8	Internet Explorer 7	Internet Explorer 6	Firefox 3.X	Safari 5.X	Safari 4.X
Windows 7 (32-bit and 64-bit)	Yes	Yes	—	Yes	—
Windows Vista SP2 (32-bit and 64-bit)	Yes	Yes	—	Yes	—	—
Windows XP SP3 (32-bit)	Yes	Yes	Yes	Yes	—	—
Windows XP SP2 (64-bit)	Yes	Yes	Yes	Yes	—	—
Windows Server 2008 R2	Yes	Yes	—	—	—	—
Windows Server 2003 (except IA-64)	Yes	Yes	Yes	—	—	—
Windows Server 2000 SP4	—	—	Yes	Yes	—	—
Mac OS 10.4.8+ (Intel-based)	—	—	—	Yes	Yes	Yes

• Microsoft Silverlight Microsoft Silverlight browser plug-in version 4.0 is required for Lync 2010, the Online Meeting Add-in for Lync 2010, and Lync Web App.
• Microsoft .NET Framework 3.5 To install Lync 2010 Attendant, the Microsoft .NET Framework 3.5 must already be installed. Install Microsoft .NET Framework 3.5
• Microsoft Office Lync Server 2010 clients support integration with various versions of Microsoft Office:
  • The Microsoft Outlook 2010 messaging and collaboration client and Microsoft Exchange Server 2010 are required for the full set of new Outlook integration features in Lync 2010.
  • Certain Lync 2010 integration features are supported on Microsoft Office 2007 and Microsoft Office 2003 Service Pack 3 (SP3). For integration with Office 2007 to work correctly, you may have to install an update to Outlook 2007. For details about the Outlook update, "Description of the 2007 Office hotfix package" (KB article 936864).
  • The Online Meeting Add-in for Lync 2010 is supported with Microsoft Office 2003, Microsoft Office 2007, and Microsoft Office 2010.

Hardware Support for Lync Server 2010 Clients

This section describes the recommended hardware for Lync Server 2010 clients.

Hardware component	Minimum requirement
CPU	Intel Pentium 4, AMD Athlon 64, or equivalent Data and voice: 1.6 gigahertz (GHz) or higher processor, 2 GHz 32-bit or 64-bit processor (recommended) For video: Dual Core 1.9 GHz processor or higher for VGA, Quad Core 2.0 GHz or higher for high definition For the Microsoft RoundTable conferencing device: 2 GHz processor or higher
Memory	On Windows XP: 1 gigabyte (GB) of RAM On Windows Vista or Windows 7: 2 GB of RAM
Display resolution	1024x768 required
Graphics hardware	• Support for Microsoft DirectX 9.0 application programming interface (API) • 128 MB of graphics memory (minimum) • Windows Display Driver Model driver • Pixel Shader 2.0 in hardware • 32 bits per pixel
Telephony	Microphone and speakers, headset with microphone, or equivalent device Recommended: Microsoft unified communications (UC) device, or a phone running Microsoft Lync 2010 Phone Edition
Video source	USB 2.0 video camera or RoundTable device
Network	Voice: • Peer-to-peer: 40 kbps (minimum); 60 kbps (typical); 90 kbps (maximum) • Conferencing: 40 kbps (minimum); 95 kbps (typical); 160 kbps (maximum) • Media bypass: 80 kbps (minimum); 95 kbps (typical); 160 kbps (maximum) Video: • CIF: 50 kbps (minimum); 210 kbps (typical); 250 kbps (maximum) • VGA: 350 kbps (minimum); 500 kbps (typical); 600 kbps (maximum) • High definition: 800 kbps (minimum); 1.2 Mbps (typical); 1.5 Mbps (maximum) • RoundTable device: 50 kbps (minimum); 280 kbps (typical); 350 kbps (maximum) Data: • Web conferencing (PSOM): 20 kbps (minimum); 200 kbps (typical); 500 kbps (maximum) • File Transfer: 20 kbps (minimum); 200 kbps (typical); 200 kbps (maximum) • Application Sharing: 256 kbps (minimum); 1 Mbps (typical); 3.5 Mbps (maximum) Typical bandwidth values are measurements of typical activity levels under good network conditions (for example, with no forward error correction, or FEC). This value can be used for capacity planning to assess if a network is provisioned appropriately. The values are cumulative. For example, for a conference call with audio, Common Intermediate Format (CIF) video, and panoramic video, an appropriately provisioned network would provide a bandwidth speed of 585 Kbps (95+210+280=585 Kbps).

Recommended Hardware for Microsoft Lync 2010 Attendant:

Hardware component	Minimum requirement
CPU	Intel Pentium 4, AMD Athlon 64, or equivalent Data and voice: 1 GHz or larger processor. Support for 32-bit and 64-bit For the Microsoft RoundTable conferencing device: 2 GHz processor or higher
Memory	On Windows XP: 1 GB of RAM On Windows Vista or Windows 7: 2 GB of RAM
Display resolution	Required: Super VGA 1024 x 768 Recommended: Super VGA 1280 x 1024 or higher
Hard drive	At least 100 MB free
Telephony	Microphone and speakers, headset with microphone, or equivalent device Recommended: Microsoft UC device, or a phone running Microsoft Lync 2010 Phone Edition
Bandwidth requirements	Voice: 50 kbps (minimum); 80 kbps (high-quality) RoundTable device (for audio): 50 kbps (minimum); 350 kbps (high-quality)

Required Lync Server 2010 Components for Devices

Before you deploy UC phones, ensure that the following required Lync Server 2010 components are in place.

Web Services

The Device Update service, which is an automated way to update your IP phones, is installed with Web Services, on the Front End Server

Enterprise Voice

Enterprise Voice is the voice over IP (VoIP) solution in Lync Server 2010 that allows users to make calls and use rich communication and collaboration features, such as viewing enhanced presence information or location information for contacts in your organization’s address book.

Contact Objects

(Applies to Common area phones and analog devices only) Phones that are not associated with a specific user must be associated with an Active Directory contact object. Like user accounts, contact objects can be assigned policies and voice plans, thereby giving you a way to manage the device.

Dial Plans, Voice Polices, and Outbound Call Routes

Dial plans, voice polices, and call routes must be set up for users. Dial plans are named sets of normalization rules that translate phone numbers for a named location, individual user, or contact object into a single standard (E.164) format, allowing UC device users to make calls to the public switched telephone network (PSTN). Voice policies are records that define call permissions for users, sites, or an entire organization and include various calling features that may be enabled or disabled as appropriate. Voice policies must be set up for device users. Call routes are rules that specify how Lync Server 2010 handles outbound calls from UC devices.

PIN Authentication and Policy

If you’re deploying phones from the new line of IP phones, you must enable personal identification number (PIN) authentication on Lync Server, and an appropriate PIN policy need to be in place. This allows authentication to be automatic when a user signs in on an Aastra 6721ip, Polycom CX600, Polycom CX500, or Polycom CX3000 phone.

Hardware Support for Lync Server 2010 Devices

IP phones running Microsoft Lync 2010 Phone Edition support Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) and Power over Ethernet (PoE). To take advantage of LLDP-MED, the switch must support IEEE802.1AB and ANSI/TIA-1057. To take advantage of PoE, the switch must support PoE802.3AF or 802.3at.

To enable LLDP-MED, the administrator must enable LLDP by using the switch console window and set the LLDP-MED network policy with the correct voice VLAN ID.

In addition, if your deployment includes analog devices, you must configure the analog gateway to use Microsoft Lync Server 2010, and the gateway must be one of the following:

• An analog telephone adapter (ATA)
• A SIP-PSTN analog gateway
• A Survivable Branch Appliance that includes a SIP-PSTN analog gateway
• A Survivable Branch Appliance that includes a SIP-PSTN gateway that communicates with an ATA

Port Requirements

IP phones use port 443 for the Device Update service.

DNS Requirements

The following table lists the required DNS records for IP Phones and external devices.

Type	Value	Note
A	Fully qualified domain names (FQDNs) for the pool(s) hosting the Enhanced Registrars	The new Lync Server 2010 DNS load balancing feature requires you to specify the server FQDN and the pool FQDN, using the same IP address, for each server in the pool and to create A records for all pools that contain an Enhanced Registrar. For example: RegistrarServerOneInPool.: 1.2.3.4, RegistrarPool.: 1.2.3.4, RegistrarServerTwoInPool.: 1.2.3.5, and RegistrarPool.: 1.2. 3.5. If you are using hardware load balancing, just specify A records for each pool that contains an Enhanced Registrar. Allows external devices to connect by using SIP over TLS to the Enhanced Registrar internally.
SRV	_sipinternal._tcp. _sipinternaltls._tcp.	Specifies the two SIP FQDNs for internal routing, one for communications over TCP, and one for TCP communications secured by TLS.
A	ucupdates-r2.	Specifies the Web Services portion of the Device Update services URL. The device appends “:443/RequestHandler/ucdevice.upx”. Make sure the HLB translates external requests to use “:443/RequestHandler/ucdevice.upx.” (The external port is 443.)