Microsoft Teams s’ouvre vers l’extérieur !

On l’attendais depuis que le produit a été presenté : La possibilité d’utiliser Teams avec des comptes utilisateurs externes comme des partenaires ou des personnes extérieures à l’organisation.

L’annonce officielle

« L’accès invité dans Microsoft Teams permet aux équipes de votre organisation de collaborer avec des personnes extérieures à votre organisation en leur donnant accès aux équipes et aux canaux. Un invité est une personne qui n’est pas un employé, un étudiant ou un membre de votre organisation. Ils n’ont pas de compte d’école ou de travail dans votre organisation. Par exemple, les invités peuvent inclure des partenaires, des vendeurs, des fournisseurs ou des consultants.

Les organisations qui utilisent Microsoft Teams peuvent fournir à leurs partenaires un accès externe aux équipes, aux documents dans les canaux, aux ressources, aux chats et aux applications, tout en gardant un contrôle complet sur leurs propres données d’entreprise. »

Un propriétaire d’équipe dans Microsoft Teams peut ajouter et gérer des invités dans son équipe via le web ou le bureau. Les invités peuvent avoir n’importe quelle adresse courriel, et le compte de courriel peut être un compte de travail, personnel ou scolaire.

Publicités

Office 365 deployment abroad: take the time!

While the desire to bring together all Office 365 collaborative services can truly assert itself within multinational companies, it will nevertheless come up against many obstacles that sometimes call into question a rapid deployment. Having participated in several generalizations of the Office 365 solution in recent years in relatively consistent international environments, I would like to review the main difficulties encountered, which, in retrospect, tend to appear systematically in these scenarios. The knowledge of the latter should enable you to identify the main areas of reflection and anticipate the work sites to be organised before any deployment.

2 What is Office 365 Deploy?

If we consider only the technical aspect, Office 365 deployment could go through the following three major phases:

• Service activation;
• Directory synchronization;
• Customer deployment.

But to consider only these three steps would be extremely simplistic, because Microsoft’s Cloud offering cannot be limited to the most well-known functions, namely:

• Exchange Online – Exchange Online
• Skype Online – Skype Online
• Office Suite – The Office Suite

Office 365 is a Cloud offering that is particularly rich in features, in constant motion and with multiple options. Also, reducing the deployment of the 0365 environment to a simple technical project is a mistake not to commit! In reality, the deployment of the 0365 environment is larger and will raise many questions within the project team.

The first question concerns the functions you want to activate, in relation to user populations. The planned result must therefore take into account the technical and environmental prerequisites that your company will be able to deploy within the time allotted to the project and that are necessary for the proper functioning of the above-mentioned applications.

3 Determining the Functionality

The study of the technical aspects is of no use if you have not previously determined the functions you want to make available to users. In most Office 365 projects, the functional options can be distributed as follows:

• Major functions: These are the ones that will be deployed for all users. You’ll naturally find the Office suite, messaging and collaborative aspects such as Sharepoint, Outlook and of course Skype (Presence & Instant Messaging).
• Minor Functions: These are those that will be deployed or activated on a case-by-case basis depending on technical capabilities (Skype Video, Stream) and specific functions such as BI or Powell for smaller populations.

The choice of tools being guided by the acquisition of licenses, these will naturally condition the technical prerequisites that you will have to determine. It is also fundamental to consider these choices in relation to the multiple local environments that each remote site represents.

In addition, if the company has chosen to acquire all the licenses from the beginning of the project, it is likely that its management will expect a rapid deployment of these same functionalities.

But beware, this haste can be incompatible with the time it takes to deploy the prerequisites!

The functions selected will also have a more or less significant impact on the transition phase. Indeed, the more functions there are, the more important the change is. This is because the transition (data transfer and transformation of services) and the support of users will thus prove to be consequent.

4 Estimate the prerequisites

The deployment of Office 365 services will require a number of technical adaptations, which will mainly concern:

• The network
• DNS resolution modes of remote sites
• Security and traceability of accesses.

For having to explain them several times, depending on the functionalities you decide to activate, these will have different impacts on your networks.

4.1 DNS resolution modes of remote sites

The most common consequence of deploying office 365 services is the DNS resolution of remote branches and sites. Each user of these sites must be able to be geolocated via local DNS services in order to allow the connection of customers as close as possible to an Azure Office 365 point. Otherwise, your remote clients may have relatively long access times, which will inevitably affect application responsiveness.

4.2 Networks and their evaluation

The company networks, when they concern international companies, are varied because the offer and possibilities of connection, according to countries or continental plates, are also varied. From the MPLS complex to the simple VPN connection, the usage, capacities and characteristics of the connections will have to be closely examined with regard to the application requirements (Bandwidth, latency etc.).

The aim here is to ensure that the services envisaged will function properly through these links and for which population groups. Network evaluation is therefore one of the most important tasks that your technical teams will have to perform.

4.3 Access security and traceability

One of the most neglected issues in Office 365 projects is security and access traceability. With regard to safety, it is not uncommon for these projects to be abruptly slowed down by safety requirements that would not have been taken into account at the beginning of the project. The most common points raised were as follows:

• Authentication: How does client authentication (workstations and mobiles) on the Microsoft environment work?
• Securing connections: What are the protocols used and the data sent to the various authentication services, whether basic or modern, based on a delegation of services (Federation) or not?
• Encryption: What types of data will require additional protection, such as additional encryption?
• Conditional access: Is the username/password pair sufficient to guarantee access to sensitive data in a mobile environment?
• Proxy Service: How to track client accesses through proxy services without compromising infrastructure support and guaranteeing geolocation?

So many questions that you will have to answer sooner rather than later and that you should discuss with the security teams right from the start of your migration project!

5 Propose a governance model

Migrating all the workstations of a large company will lead to the standardization of tools but also the arrival of a centralized administration. Previously distributed over the various sites, maintenance responsibilities in operational conditions and service levels of the various software solutions were thus the preserve of local teams, close to their users and specific constraints often related to the business lines.

The advent of a single platform, however efficient it may be, will therefore upset these organizations and bring new organizational needs to the forefront

It is then essential to ask yourself some questions:

• Which teams will be in charge of the platform’s administration?
• What will be the privileges of the local teams on the organization’s leader?
• Who will be responsible for the financial part of the solution (license management, service consumption etc.)
• What will be the account creation processes (provisioning) and reporting?
• How to organize the re-invoicing of services within the various subsidiaries?
• How is technical support organised in case of problems accessing the platform?

These aspects of governance must be taken into account at the earliest in your migration project. Indeed, you understand that these subjects raise sensitive issues because they touch on the question of responsibilities, which, by their very nature, can take longer and be more difficult to resolve.

6 Involving safety

Security teams must obviously be an integral part of the project from the start, because implementing an Office 365 solution means mobility, connecting to the host and storing data in the cloud, with partial replication on workstations.

Ignoring safety means taking the risk of stopping the project from the very first phases of the pilot. It is therefore crucial to discuss their requirements and recommendations with them, so that you can propose possible solutions or additional functions such as Multifactor authentication or the possibility of using a company-specific encryption key (Bring Your Own Key).

Some adjustments are likely to be necessary in particular to strengthen the protection of mobile devices, such as conditional access to the 0365 platform, which would require prior enrolment of the Mobile Device Management (MDM) type.

In general, you will therefore need to demonstrate that the transition to Office 365 services is not detrimental to the security and confidentiality of information.

7 The legal aspect

Deploying Office 365 means above all entrusting your data to an American company. Most of these data will be stored on two data centers on the same continental plate. These centers can be located in Europe or in Microsoft infrastructures around the world.

Microsoft takes data storage issues outside Europe (GDPR) very seriously or vice versa (the problem of data storage outside the USA for US subsidiaries in particular), but its offer still has some limitations that you must take into account. And some business constraints may lead you to accept that certain services remain locally on remote sites. In experience, getting the legal department of a large company to give the green light to centralize data outside the country of origin takes time because the process is usually complex and sometimes new. You should address these points as soon as possible.

As you will have understood, apart from the organizational aspects, the generalization of O365 services within international distributed companies and therefore subject to local constraints is not so simple!

The resulting problems are sometimes far removed from the world of technology but nevertheless remain structuring for this type of projects.

Precise knowledge of the 0365 offer, adapted support and a consistent methodology should thus constitute an additional weapon to face these questions and guarantee the success of your O365 deployment projects!

Laurent TERUIN

Fin de partie Pour RPC over HTTPS Office 365

Microsoft vient d’annoncer que le 31 octobre 2017, le protocole RPC over HTTPS utilisé par Windows Outlook 2010 SP2 pour se connecter sur Office 365 ne sera plus actif. Ce qui signifie que ce client d’Exchange Online ne pourra plus se connecter sur Exchange Online sauf s’il il dispose du services pack 2 et du correctif du 8 Décembre 2015. Mise à jour qu’il vous faudra déployer également pour les clients Outlook 2013 et 2016.

Il est également fortement conseillé de vérifier que ces anciens clients sont dans la capacité d’activer le protocole remplaçant à savoir Mapi Over http. Pour cela, il vous faudra vérifier l’Absence de la clef de registre ci-dessous évitant l’activation du protocole Mapi Over http.

Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange
DWORD: MapiHttpDisabled
Value: 1

Fonctionnant mais non supporté, Windows Outlook 2010 SP2 se connecte et fonctionne plutôt correctement avec Office 365 même s’il ne supporte pas intégralement les fonctions avancées proposées par Exchange Online comme l’authentification Modern notamment.

Passé la date du 31 octobre 2017, voici les clients Windows Outlook qui demeureront capable d’interagir avec Exchange Online:

Version d’Office	Mise à jour	Numéro de version
Office 2016	Mise à jour du 8 décembre 2015	Abonnement : 16.0.6568.20xx MSI : 16.0.4312.1001
Office 2013	Office 2013 Service Pack 1 (SP1) et mise à jour du 8 décembre 2015	15.0.4779.1002
Office 2010	Office 2010 Service Pack 2 (SP2) et mise à jour du 8 décembre 2015	14.0.7164.5002

 

Pour connaitre les versions utilisées par vos clients de messagerie utilisez les 2 commandes Powershell suivantes pour extraire les versions.

• Get-Mailbox | Set-Mailbox -AuditOwner MailboxLogin -AuditEnabled $true
• Get-Mailbox | Search-MailboxAuditLog -LogonTypes owner -ShowDetails | ? { $_.ClientInfoString -like « *Outlook* » } | select MailboxOwnerUPN,Operation,LogonType,LastAccessed,ClientInfoString | export-csv .\OutlookConnections.csv

 

Cordialement

Laurent TERUIN

Mais où est donc passé Office Web App Server ?

Si vous devez déployer Skype for Business 2015 vous devrez installer un composant nommé office Web App server pour l’affichage des Présentations powerpoint dans les conférences. Il fut un temps Office Web app était proposé gratuitement en download. Nous l’avons cherché

Ici : https://www.microsoft.com/en-us/download/details.aspx?id=38833

La : https://technet.microsoft.com/fr-fr/library/jj219455.aspx

Visiblement le produit n’est plus disponible si facilement et selon le lien ci-dessous celui ne serait accessible uniquement que via un programme de licence en volume. Au passage la nouvelle version est nommée Office Online Server.

https://blogs.office.com/2016/05/04/office-online-server-now-available/

Nous nous sommes donc connecté sur le programme qui est censé fournir ce produit à savoir et là toujours pas de Office One line server ? 

 

Laurent TERUIN

Google sommé de livrer au FBI des données stockées en dehors des USA

A ce jour, l’obligation de recourir à un cloud souverain faites aux collectivités territoriales via la note d’information du 5 Avril 2016 relative à l’informatique en nuage émanant du Ministère de l’intérieur et de la Culture et de la communication ne semble pas avoir été suivi d’un grand ‘effet . De plus, elle considère que la confidentialité des données repose uniquement sur la localisation de celles-ci et non sur les organisations qui la gère. C’est par ailleurs une erreur stratégique qui semble témoigner d’un manque de réflexion globale.

La justice américaine a confirmé hier l’extraterritorialité du droit américain et impose à Google de livrer des messages stockés en dehors du territoire national (https://www.nytimes.com/reuters/2017/02/04/business/04reuters-google-usa-warrant.html). Sont concernés principalement des emails échangés sur la plateforme. Cette décision aussi regrettable soit elle aurait tendance à confirmer, même si cela tombe sous le sens, que la gouvernance de l’informatique en nuage prévaudrait sur sa localisation

Microsoft s’était par ailleurs battu contre cette obligation voir (https://www.nytimes.com/2016/07/19/business/dealbook/microsoft-case-shows-the-limits-of-a-data-privacy-law.html?_r=0) et avait obtenu gain de cause. La cour d’appel de Manhattan avait conclu à l’époque que la législation « n’autorise par les tribunaux à émettre et faire exécuter par des fournisseurs de services basés aux États-Unis des mandats destinés à faire saisir le contenu de courriels de consommateurs qui sont stockés exclusivement sur des serveurs à l’étranger.

Google a semble-t-il décider de faire appel. A suivre

L’interface Skype for Business au secours de la complexité

Je ne sais pas s’il vous est déjà arrivé de vous trouver dans une salle de Visio conférence avec un panel de télécommandes aux menus et sous menus sans aucune signification pour vous, et devoir démarrer ladite conférence. C’est parfois un « léger » moment de solitude. Un peu comme une personne d’un certain âge qui doit utiliser une souris pour la première fois. La différence c’est que dans ce cas précis, il s’agit de vous et de vos collaborateurs qui comptent précisément sur vous pour que tout démarre correctement en temps et en heure. Vous visualisez ?

En tous les cas, il se pourrait bien que cela soit de l’histoire ancienne. En effet Polycom vient de mettre à disposition des interfaces considérablement simplifiées et qui reprennent l’interface Skype for Business ainsi que la planification des rendez-vous Exchange. Basées sur des tablettes tactiles ces interfaces utilisateurs ayant un look and Feel Skype for Business permettront sans aucun doute un usage plus intuitif et plus rapide. Ces modalités d’usages sont visibles sur le lien suivant : https://www.youtube.com/watch?v=7MLS95HHVw4 dans cette vidéo qui explique plutôt bien les différentes fonctions lors des phases d’établissement de la conférence et de son utilisation. J’avoue que j’aurai tendance à applaudir des deux mains cette initiative qui va dans le sens de l’harmonisation des interfaces et qui devrait limiter la nécessité de recourir aux services de conciergerie.

Skype Everywhere ? plutôt une bonne idée !

Laurent TERUIN

 

Skype For Business: Evenement Microsoft à Paris 22 Novembre

Bonjour Actis propose un rendez-vous autour de Skype pour Business le Mardi 22 Novembre à 14H chez Microsoft. Ça sera l’occasion de rencontrer des professionnels Skype for Business et des personnes ayant une grande connaissance des techniques d’interconnexion.

L’adresse : 92130 Issy les Moulineaux 39 Quai du Président Roosevelt

Le contact pour vous inscrire : Bertrand Goldfarb/ bgoldfarb@actisdistribution.fr / +33 6 08 42 15 97

En voici le programme

• 14H00 : Accueil Autour d’un café
  
• 14H30 : Introduction
  

L’impact des Communications Unifiées sur le marché des Télécoms –

Bertrand Goldfarb – Directeur Actis France

• 14H40 : Microsoft
  

Office 365 E5, 3 propositions de Valeur additionnelles :  Voix, Sécurité et Analytics – Matthieu Silbermann – Chef de Produit Communications Unifiées & Office 365 E5

• 15H00 : AudioCodes
  

One Voice pour Skype for Business : une solution unifiée de produits et de services – Christophe Pichon – Directeur AudioCodes France

• 15H40 : Pause
  

Pause Café

• 16H00 : CC4Skype
  

Une solution complète de centre de contacts et de console opérateur native pour Skype for Business
–

Rob de Boer– International Partner Director

• 16H40 Plantronics
  

La collaboration mobile, un nouvel enjeu –

Stéphane Bilhaut
– Distributor & Telecom Reseller manager France

• 17H15 Actis
  

Conclusion et Q&R –

Bertrand Goldfarb – Directeur Actis France

• 17H30 Coktail
  

Venez discuter de vos projets autour de SFB et d’une coupe de Champagne

Skype for Business : Nouveau Mac client

Microsoft vient de sortir il y a quelques semaines une nouvelle version du client Mac les nouveautés sont détaillées ci-dessous (Extrait documentation Microsoft)

Vous pouvez également regarder la vidéo de présentation du client ici : https://www.youtube.com/watch?v=a70ZoOlq2NY ou une présentation plus technique ici : https://www.youtube.com/watch?v=PZOZYzibRB8

Ici quelques slides annonçant les nouvelles fonctionnalités ainsi que la Roadmap

 

Nouvelle apparence
Si vous êtes un utilisateur régulier de la version commerciale de Skype, vous apprécierez Skype Entreprise pour Mac : les photos, les indicateurs de présence, les boutons et les icônes faciles à utiliser vous sembleront très familiers.

Intégration de Skype for Business dans SalesForce

Microsoft vient de présenter une intégration des fonctionnalités Skype pour Business avec l’environnement Saleforce ce qui permet depuis l’interface d’interagir directement avec la personne concernée via Skype For Business

Skype pour Sales Forces est à ce jour en Beta version et pour activer ces fonctionnalités dans l’environnement SaleForce il faut que l’administrateur suive cette procédure : http://docs.releasenotes.salesforce.com/en-us/winter17/release-notes/skype_for_salesforce_enable.htm

C’est du grand classique me direz-vous mais ça existait pour Skype Grand public mais pas pour la version Skype pour entreprise

 

Skype for Business Unleashed: Must Have

Bonjour je voulais signaler la sortie de ce que l’on peut appeler un ouvrage de référence (plus de 1000 pages) sur Skype pour Business écrit par Alex Lewis, Par Richard, Phil Sharp et Rui Young Maximo.

Pour l’avoir lu (j’avoue en partie) c’est ouvrage est extrêmement complet c’en est assez impressionnant et rare pour le préciser.

Un MUST HAVE comme disent les anglais !!

Pour votre information et pour vous rendre compte du travail effectué ci-après la table des matières. Si vous trouvez plus complet, vous me faite signe 😉

About This E-Book

Title Page

Copyright Page

Contents at a Glance

Table of Contents

Foreword

About the Authors

Dedications

Acknowledgments

We Want to Hear from You!

Reader Services

Part I Overview

Chapter 1 What Is Skype for Business?

Skype for Business Server Overview

Skype for Business Server Terms and Acronyms

Versions and Licensing

Integration with Other Microsoft Applications

Summary

Chapter 2 What’s New in Skype for Business?

Animated Emoticons … and Consumer Integration

New Topologies and Supported Architectures

Hybrid and Online Features

Enhanced Mobile Experience

In-place Upgrades

Summary

Chapter 3 Business Case for Skype for Business?

Why Unified Communications

Unified Communications Return on Investment (ROI)

Why Skype for Business Server 2015 for Unified Communications

Summary

Part II Skype for Business Server 2015 Server Roles

Chapter 4 Skype for Business Server 2015 Front End Server

Front End Server Installation

Installation

Configuration and Administration Overview

Troubleshooting

Best Practices

Summary

Chapter 5 Skype for Business Server 2015 Edge Server

Edge Server Overview

Edge Server Installation

Edge Server Configuration

Edge Server Administration

Edge Server Troubleshooting

Best Practices

Summary

Chapter 6 Skype for Business Server 2015 Monitoring and Archiving Best Practices

Installing Monitoring Components

Monitoring Configuration

Monitoring Administration

Monitoring Troubleshooting

Installation of Call Quality Dashboard Components

Enabling CQD in Skype for Business Online

Call Quality Dashboard Configuration

Call Quality Dashboard Administration

Archiving Components Troubleshooting

Archiving Components Installation

Archiving Configuration

Archiving Administration

Archiving Troubleshooting

Best Practices

Summary

Chapter 7 Skype for Business Server 2015 Mediation Server

Mediation Server Overview

Mediation Server Design Considerations

Mediation Server Installation and Configuration

Mediation Server Administration

Mediation Server Troubleshooting

Best Practices

Summary

Chapter 8 Persistent Chat

Persistent Chat Overview

Persistent Chat Deployment

Configuring Persistent Chat

Persistent Chat Administration

Skype Online and Hybrid Environments

Persistent Chat Troubleshooting

Best Practices

Summary

Part III External Dependencies

Chapter 9 Network Requirements and Best Practices

Managed and Unmanaged Networks

IPv6 Support

Network Discovery

Edge: Interactive Connectivity Establishment and External Communications

Calculating Bandwidth Requirements

Wireless Networks

Call Admission Control

Quality of Service

Software Defined Networking

Summary

Chapter 10 Dependent Services

Active Directory Dependencies

Domain Name System Dependencies

Server Certificates Dependencies

Network Dependencies

Office Web Apps Server Dependencies

SQL Server Dependencies

Summary

Chapter 11 Firewall, Reverse Proxy, and Security Requirements

Firewall Requirements

Ports Required for Internal and External Access

Using Network Address Translation (NAT) with Skype for Business Server 2015

Reverse Proxy Requirements

Reverse Proxy Configuration

File Share Permissions

Securing Service Accounts

Security Threats

Summary

Part IV Administration and Management

Chapter 12 Monitoring Skype for Business Server 2015

Understanding Key Areas to Monitor in Your Deployment

Monitoring the Health and Performance of Skype for Business Server 2015

Summary

Chapter 13 Administration of Skype for Business Server 2015

Administration Overview

Leverage Get-Help

Using the Skype for Business Topology Model

Managing Servers and Users

Configuring Quality of Service

Troubleshooting

Third-party Tools

Best Practices

Summary

Chapter 14 High Availability and Disaster Recovery

Defining Business Requirements for High Availability and Disaster Recovery

Designing for High Availability

Designing for Disaster Recovery

Configuring Skype for Business Server 2015 for High Availability

Executing Disaster Recovery Procedures

Summary

Part V Migrating from Older Versions

Chapter 15 Migrating from Lync Server 2010/2013

Migration Steps: Side-by-Side Method

Completing the Migration to Skype for Business Server 2015

Migration Steps: In-place Upgrade Method

Troubleshooting

Best Practices

Summary

Part VI Skype for Business Server 2015 Voice, Video, and Integration

Chapter 16 Skype for Business Server 2015 Telephony and Voice Integration

Understanding Telephony Fundamentals

Integration Methods

End-User Scenarios

Analog Devices

Skype for Business Voice Routing

Best Practices

Summary

Chapter 17 Advanced Skype for Business Server 2015 Voice Configuration

Building the Skype for Business Topology

Voice Routing

Voice Features

Advanced Enterprise Voice Features

Dial-in Conferencing

Response Groups

Best Practices

Summary

Chapter 18 Skype for Business Native Video and Data Conferencing

Skype for Business Peer-to-Peer Video

Skype for Business Server 2015 Video Conferencing

Skype for Business Server 2015 Data Conferencing

Summary

Chapter 19 Skype for Business Video Integration with Third-Party Products and Services

Microsoft Video Interoperability Server (VIS)

Third-Party Video Integration Basics

Gateways

Back-to-Back User Agents

Edge Traversal

Native Registration

Multipoint Control Units

Software Plugins

Solution Comparisons

Summary

Part VII Integration with Other Applications

Chapter 20 Unified Contact Store, Exchange, and SharePoint Integration

Server-to-Server Authentication

Exchange Integration Features

SharePoint Integration Features

Summary

Chapter 21 Developing Skype for Business Solutions

Overview of Skype for Business Applications

Choosing a Skype for Business SDK

Skype for Business Application Scenarios

Debugging Skype for Business Applications

Summary

Part VIII Office 365 and Skype for Business Server 2015 Online

Chapter 22 Skype for Business Online and Hybrid Deployments

Overview of Skype for Business Online and Office 365

System Requirements

Experiencing Skype for Business Online

Deploying Skype for Business Online

AD FS Deployment for SSO

Configuring Directory Synchronization

Skype for Business Hybrid Deployment

Summary

Chapter 23 Skype Integration

Skype Connectivity Features

Configuring Skype Connectivity for Skype for Business Server 2015

Configuring Skype Connectivity for Office 365

Troubleshooting Skype Connectivity

Summary

Part IX Clients

Chapter 24 Microsoft Lync for Mac Client

Installing the Client

Feature Comparison

Navigation and Layout

Managing Contacts

Managing Groups

IM Features

Audio/Video Calls and Conferencing

Making a Video Call

Web Conferencing

Client Integration with Other Applications

Troubleshooting

Best Practices

Summary

Chapter 25 Mobile Clients

Introducing New Mobile Features

Understanding Skype for Business Mobility

Deploying Skype for Business Mobility

Summary

Chapter 26 Windows and Browser Clients

Installing the Client

Signing In

Navigating in the Client

Peer-to-Peer Conversations

Conferencing

Understanding Persistent Chat

Integration with Other Applications

Skype for Business Server Browser Capabilities

Skype for Business Server 2015 Web App Technical Review

Requirements to Deploy Skype for Business Browser Functionality

Summary

Chapter 27 VDI

VDI Basics

The Lync VDI Plugin

Protocol Partner Solutions for the Lync VDI Plugin

Thin Client Hardware Optimized for Skype for Business

Summary

Chapter 28 UC Endpoints

Standalone IP Phones

USB Headsets, Speakerphones, and Handsets

Webcams

Conferencing Devices

Best Practices

Summary

Part X Planning for Deployment

Chapter 29 Planning for Skype for Business Online and Hybrid Deployments

Comparing Topology Options

Skype for Business Online and Office 365 Subscription Plans

Planning for Single Sign-On with AD FS

Planning for Directory Synchronization

Planning for Skype for Business Online

Planning for a Hybrid Deployment

Summary

Chapter 30 Virtualization Support

Virtualization Configuration

Skype for Business Server Virtualization Support Guidelines

Skype for Business Server 2015 Virtual Machine Recommendations

Host Server Hardware Recommendations

Skype for Business Server 2015 Sample Virtual Topologies

Best Practices

Summary

Chapter 31 Planning for Basic Skype for Business Server 2015 Services

Determining the Scope of the Deployment

Determining Your Infrastructure Needs

Planning for Capacity

Planning for Instant Messaging

Planning for Conferencing

Planning for Clients and Devices

Planning for Archiving

Defining Your Archiving Requirements

Planning for Management

Documenting the Plan

Best Practices

Summary

Chapter 32 Planning to Deploy External Services

Determining Feature Requirements

Planning Edge Server Architecture

Planning for High Availability

Reverse Proxy Planning

Planning for Certificates

Network Planning

Preparing for Edge Servers

Summary

Chapter 33 Planning for Voice Deployment

Enterprise Voice Overview

Integration Scenarios

Active Directory Phone Number Configuration

Gateways and Trunks

Dial Plans

Voice Policies and Voice Routing

Emergency Services

Response Groups

Summary

Index