In this post I’ll list to you 30 fact and info about Lync which is totally new and different than OCS:
Great list!! I'll borrow it to my Swedish blog (www.DiverseTips.se).
I also liked your posts about deploying an Lab environment off Lync server
Of interest will be the ability to fully virtualise all of the Lync workloads. Yeah!
Is it true that only Enterprise Edition will be supported if virtualized, or can you virtualize Standard Edition and be supported?
Microsoft Lync Server 2010 communications software supports virtualization topologies that support all major workloads—instant messaging (IM) and presence, conferencing, and Enterprise Voice. Windows Server 2008 R2 is required, and both Microsoft Hyper-V technology and VMware are supported.
The supported topologies are as follows:
• Lync Server 2010 Standard Edition server topology, supporting up to 2,000 users, for proof-of-concept, pilot projects, and small businesses that do not need remote connectivity. This topology includes a physical host server running one virtualized Lync Server 2010 Standard Edition server. You can also deploy an Edge Server (either physical or virtual). You may also deploy Monitoring Server and/or Archiving Server on a physical server. Other server roles are not supported in this topology.
The user capacity for a single virtualized Standard Edition server is 2,000 users. You can add more user capacity by adding more virtualized Standard Edition servers. If you do so, each virtualized server must run on a separate physical host server.
• Data center topology, supporting up to 40,000 users.
You can read the full details in the "Planning for Other Features in Microsoft Lync Server 2010 (Release Candidate)" document
Thanks for the info.
Is there any documentation on using the Merge-CsLegacyTopology command, or the Merge 2007 R2 Topology wizard in the Topology Builder? We are trying to move users from a 2007 R2 environment to a new Lync Environment,
Great article, I have a question regarding the SBA feature : Leaving voicemail :
I'm interested in exactly how this feature will behave. The SBA will re-route the call for voicemail via the PSTN to the ExUM OVA numbers I assume?
This will mean the caller will be presented with the default auto-attendant, as the calling coming into ExUM won't have a diverted number associated to it (PSTN doesn't support passing divert headers). So the caller would need to provide the name or number of the person they called again to the ExUM Autoattendant?
The Merge-CsLegacyTopology command enables you to migrate configuration settings from a previous version of Office Communications Server to Lync, Merge-CsLegacyTopology should be used in conjunction with the Import-CsLegacyConfiguration and Import-CsLegacyConferenceDirectory cmdlets... I'll try to see if there is more detailed document about it.
The below is from the Planning for EV Lync RC...
To enable voice mail survivability for branch site users, the following configurations are recommended:
- An Exchange administrator should configure Exchange UM Auto Attendant (AA) to Message Taking Mode. This is a special type of AA that disables all other generic functionality, such as transfer to a user or transfer to an operator, and limits the AA to only accept messages. Alternatively, the Exchange administrator may choose to use a generic AA, or an AA customized to route the call to an operator.
- The Lync Server administrator should set the AA phone number as the Exchange UM Auto Attendant phone number when configuring voice mail rerouting for either the Survivable Branch Appliance or branch server.
- The Lync Server administrator should set the Exchange UM subscriber access number that corresponds to the branch user’s Exchange UM dial plan as the Exchange UM subscriber access number when configuring voice mail rerouting on the Survivable Branch Appliance.
- The Exchange administrator should configure Exchange UM so that only one dial plan is associated with all branch users who need access to voicemail during a WAN outage.
Hi, Thanks for the info.
Is there any documentation about integration with Cisco CUCM and/or Avaya ACM ?
How do I setup basic IM functionality to MSN? I have completed the provisioning request with Microsoft but cannot IM either way