LYNC 2013 New Features

-

Let's start with the overview and the major changes introduced into LYNC 2013.


Operating System:
64bit and Windows Server 2008 or 2008 R2 is required, with the Std, Ent or DC version only.

Consolidated Server Roles:
Now the A/V Conferencing Server is always collocated with the Front-End Server.
Monitoring and Archiving can also be collocated with the Front-End Server (with its own dedicated SQL Database)

High Availability:
Lager Pools are possible, up to 20 Servers
Disaster Recovery Data Center option allows an Admin to failover the effected User to the second paired Pool.
Including an optional Witness Server (SQL), you can now deploy SQL Server Synchronous Mirroring.

Enterprise Voice:
Multi Trunk Support between Mediation Server and Gateway (Inter-Trunk)
Additional Call Authorization for Call Forwarding and Simultaneous Ringing
Manager and Delegate simultaneous ringing
Voice Mail Escape
Caller ID presentation
Conferencing dail-out for non Enterprise Voice enabled users

IM and Presence:
Unified Contact Store (with Exchange 2013), enables contact management via O2k13, OWA, Lync 2013. All Users Contact information are now optional stored in Exchange 2013
better XMPP integration, e.g. Skype

Conferencing:with the new Office Web App Server, the PPTX will be used via OWA in higher-resolution and better support for Mobile Devices
You can have a Gallery View in Conferencing, so you see multiple parties video
Archiving will now store shared conferencing document in E2k13 Data Storage (PPTX, Attachments, Whiteboards and Polls)

External User Access:
IPv6 on the Edge Server (if you are connected with IPv6)
Edge Server has the XMPP Proxy included

Monitoring/ Archiving:
Monitoring is a feature on the Front-End Server now and only
Archiving is integrated with E2k13
it can make use of the SQL mirroring feature and stores Whiteboards and Polls

Persistent Chat Server:
this is really cool !
you can now have chats, where you can join it again, after you left a chat (over time persistence)

IPv6:
you can now fully rely on an IPv6 integrated network.
(Ferrari Electronic Mediagateways are also since today supported with IPv6)


Comments

  1. ShahbazJuly 18, 2012 at 3:26 AM

    Excellent Thomas.

    A quick question: Will Lync 2013 support in-place upgrade from Lync 2010?

    Do you know if any Microsoft course on Lync 2010 coming soon?

    --
    Shahbaz
    (MCT)

    ReplyDelete
  2. Thomas PoettJuly 18, 2012 at 5:37 AM

    Hi Shahbaz,
    An in-place upgrade is not supported, you have to install a new pool and move the users as you did e.g. from OCS -> Lync 2010. This is regarding totally different bits and Database schema in Lync 2013.

    Courses are coming soon after the RTM is released, but there is right now no release date for RTM. Personally i guess for Q1'13

    Hope this helps

    ReplyDelete

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more