The next version of Office Communications Server and Communicator, Lync Server 2010 has been now been released to manufacturer. This should start to appear on the Volume Licensing website in the next few days. More info here –> http://blogs.technet.com/b/uc/archive/2010/10/27/microsoft-lync-released-to-manufacturing.aspx
There are some obscure and misleading terms used when describing an OCS or Lync environment. For those new to OCS or Lync, some of the more common terms are explained below:
Lync supports text-based instant messaging conferencing (also known as “Multi-party IM conferencing”) which allows users to initiate text messaging with more than one peer.
Audio / Video Calls
One core feature of Lync is to provider peer-to-peer (P2P) Audio and Video Calls. In this mode, session is established through the SIP protocol and Media Path negotiated between clients and does not route through any Lync server.
Audio / Video Conferencing
Audio / Video Conferencing differs from Audio / Video calls since the Media Path is established between clients and the Audio/Video MCU (Multi-Conferencing Unit) located the Lync front-end server. In A/V Conferencing mode, there is one active speaker (upstream) and at least two listeners (downstream).
An often misleading term, Web Conferencing does not provide conferencing features through a Web browser. Web Conferencing extends previous conferencing modalities and adds additional features such as Audio/Video/IM Conferencing, Collaboration tools (Poll page, Whiteboard, Q&A, Text, Web pages), Application and Desktop Sharing, Conversion of PowerPoint presentations to streamed content, Meeting Control, Scheduling, Recording and Playback.
The Web Conferencing feature can integrate with Outlook through a specific add-in to allow scheduled meetings to be held online.
Federation allows a company to communicate with another through various gateways and for designated services.
Desktop Sharing allows users to share their desktop (and optionally share control) with the RDP protocol embedded in the Media Stream, with one or multiple peers.
Group Chat enables users to engage in persistent, ongoing IM conversations. Group Chat differs from group IM in that the latter is not persistent. After a group IM session has ended, its state is lost. With Group Chat, the conversation persists, along with all files, Web links, and other associated data. This persistence makes it possible to maintain complete records of each session. It enables the instant exchange of information across an organization and with external partners in a way that makes it possible to maintain a continuing flow of information among project members.
Edge Servers allow connection of internal Lync infrastructure to the external world.
Communicator Web Access (CWA)
Communicator Web Access Servers provide Web Sites to allow users to logon to Lync services from a Web browser, which may be extended to support connecting from any endpoint on the Internet.
A SIP (Session Initiation Protocol) address consists of a user name and a domain name, similar to an email address. This is completely separate to an email address, but many organisations opt to keep the format of the SIP addresses in the same format as user’s primary email address in an attempt to keep the user logon process as simple as possible.
Public Instant Messaging Connectivity (PIC)
Enables organizations to interoperate with four proprietary instant messagne services – AOL Instant Messenger, .NET Messenger Service (Windows Live Messenger), Yahoo! Messenger, and Google Talk.
Lync Server 2010
Refers to the server component of Lync.
Refers to the client (workstation) component of Lync.
I’m usually a big fan of whatever rolls off the Microsoft production line. Not so with the first generation of Xbox 360s from a few years ago – these have to be one of the most flawed pieces of technology in history. After getting my early Xbox 360 fixed no less than 3 times I was frustratingly still getting the red ring of death.
I then implemented a permenant fix of my own – I took it outside and smashed it with a mattock – very satisfying after many years of frustrations.
PS. Yes I did buy a new one on sale for $198.
Sometimes you know a fair amount about the network environment into which you are to deploy SCCM. Other times you are fresh to the environment and need to gather as much technical and organisational information as possible to allow you to create an design that will meet requirements and exceptions. I’ve compiled a list of questions over the years that helps you to have the information you need to create at least a high level design document. I am sharing this because I haven’t seen a comprehensive collection of questions in any books or on the net.