1. 70-334: Core Solutions of Microsoft Skype for Business 2015
12/4/2017 2:10 AM
BRK3229
70-334: Core Solutions of Microsoft Skype for Business 2015
Rob Edwards
MCT
Global Knowledge UK
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Review the 3 main categories on the test
Agenda
Review the 3 main categories on the test
Review test questions after every category
Basic test taking recommendations
Q&A

3. 70-334: Core Solutions of Microsoft Skype for Business 2015
1-Plan and design Skype for Business (30-35%)
2-Deploy and configure Skype for Business (30-35%)
3-Manage and troubleshoot Skype for Business (30-35%)

4. 70-334: Core Solutions of Microsoft Skype for Business 2015
What this session is NOT about:
Relaying exact test questions
Going 400 level on all of Skype for Business

5. 70-334: Core Solutions of Microsoft Skype for Business 2015
What this session IS about:
Preparing you to take the exam
Getting your mind attuned to the question format/s

6. 70-334: MCSE Communications

7. 01 | Plan and Design Skype for Business

8. Plan Skype for Business Servers
Microsoft Ignite 2016
12/4/2017 2:10 AM
Plan Skype for Business Servers
Evaluate user distribution
associate workloads to business requirements
plan architecture; design SIP domains including shared SIP namespaces (Split Domain)
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Plan Skype for Business Servers support infrastructure
Microsoft Ignite 2016
12/4/2017 2:10 AM
Plan Skype for Business Servers support infrastructure
Define certificate requirements; design load balancing, plan for DNS, SQL, AD DS, and file store
assess network requirements including ExpressRoute
plan conferencing traffic, capacity, and QoS
estimate network usage
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. Express Route and Skype for Business
12/4/2017 2:10 AM
Express Route and Skype for Business
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. Customer’s connection
Microsoft Ignite 2016
12/4/2017 2:10 AM
ExpressRoute
Unified connectivity to all Microsoft Cloud Services
Predictable performance
Enterprise-grade resiliency and with SLA for availability
Large ExpressRoute partner ecosystem
Customer’s network
Customer’s connection
Traffic to public IP addresses in Azure
Traffic to Virtual Networks
Traffic to Office 365 Services and CRM Online
Microsoft Edge
Partner Edge
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Quality of Service (QoS)
Microsoft Ignite 2016
12/4/2017 2:10 AM
Quality of Service (QoS)
Voice, video, data transfers need to be treated differently
Voice and video sensitive to latency and jitter
Classify traffic and tag with appropriate DSCP value
Separate queue each traffic class
Voice
Video and interactive
Best effort
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. Plan Skype for Business Servers
Microsoft Ignite 2016
12/4/2017 2:10 AM
Plan Skype for Business Servers
Define server roles; hardware requirements
storage requirements for archiving and monitoring
define virtualization requirements
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Microsoft Ignite 2016
12/4/2017 2:10 AM
Design a Skype for Business Server high availability/disaster recovery (HA/DR) solution
Design a strategy for central and branch office scenarios
Resiliency, SQL mirroring, SQL AlwaysOn Failover Clustering Instances, load balancing, and Geo DNS
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. Microsoft Ignite 2016
12/4/2017 2:10 AM
Design conferencing
Design dial-in conferencing including conference access numbers and regions, conferencing lifecycle, policies, video interoperability server (VIS), Office Web Apps Server (OOS), and Skype Meeting Broadcast
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Design Skype for Business remote and external access using Edge Services
Design federation including Skype consumer connectivity, Skype for Business Online, and XMPP; design for mobility
design for directors; design for remote user access
define certificate requirements for remote servers
analyze and design firewall requirements, load balancing, DNS, and reverse proxy

17. Plan for Skype for Business clients and user experiences
Microsoft Ignite 2016
12/4/2017 2:10 AM
Plan for Skype for Business clients and user experiences
Plan contact list management, client version control, privacy, Address Book web search/download, Skype for Business mobility, client authentication options, Skype for Business users for VDI
design for client UI experience
plan for Skype for Business room system
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. Plan migration and upgrade from previous versions
Plan the migration sequence; plan for in-place upgrade
decommission old servers
monitoring and archiving server roles
plan for co-existence with previous server versions; upgrade from mirroring to AlwaysOn

19. Example Questions

20. Question 1:
You need to move all users to the new Skype for Business Server 2015 infrastructure. How should you configure the relevant Skype for Business Management Shell cmdlet?
Get-CsUser
-Identify all Set-CsUser -ProxyPool fepool01.contoso.com
-OnlyLyncUsers Move-CsUser -RegistrarPool lyncpool1.contoso.com
-UnassignedUser Enable-CsUser -Target sql.contoso.com
Get-CsUser
-Identify all Set-CsUser -ProxyPool fepool01.contoso.com
-OnlyLyncUsers Move-CsUser -RegistrarPool pool1.contoso.com
-UnassignedUser Enable-CsUser -Target SFB13 01 contoso.com

21. Question 2:
A company plans to deploy Skype for Business Mobile app. Skype for Business mobile users must be able to access conversation history and meetings. You need to enable mobility access for external networks. On the Reverse Proxy which two services should you publish?
Each correct answer presents part of the solution.
A. Exchange Web Services
B. Skype for Business Internal Web Services
C. Autodiscover
D. Skype for Business Phone Access URL

22. 02 | Deploy and configure Skype for Business

23. Configure and publish topology
Create Skype for Business roles
create gateways and trunks; add/remove server features
deploy Edge Server
deploy SQL HA options, create Office Web Apps Server

24. Configure conferencing
Microsoft Ignite 2016
12/4/2017 2:10 AM
Configure conferencing
Create PIN policy, regions and conference dial-in access numbers, meeting configuration, conference policies, mediation server co-location, and trunks and gateways
configure Skype Meeting Broadcast
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25. Configure Skype for Business remote and external access
Configure federation, including Skype consumer connectivity, Skype for Business Online, and XMPP
configure mobility policies and remote user access policies
configure load balancing, DNS, and reverse proxy

26. Deploy and configure clients
Configure Skype for Business client features, client policies, and client security options; deploy Skype for Business users for VDI
deploy Skype for Business room system

27. Migrate and upgrade from previous versions and/or Skype for Business Online
Consolidate servers to a supported single version;
move users
migrate Response Groups or LIS
move CMS or File Share Data
transition to SQL AlwaysOn
perform in-place upgrade; configure clients for Skype for Business Online
enable or move users to Skype for Business Online; migrate user settings
migrate to Skype for Business Online

28. Configure HA/DR
Configure pool pairing, configure Geo DNS for site failover, configure SQL HA

29. Deploy and configure monitoring and archiving services
Deploy monitoring reports; configure CDR and Quality of Experience
configure archiving storage
configure archiving and eDiscovery with Exchange including Exchange Online, archiving policies, Media Quality Dashboard (MQD), and server-side conversation history

30. Deploy and configure Persistent Chat servers
Implement chat history, room management URLs, HA and DR, user policies, room design, and ethical boundaries

31. Example Question

32. Question 3:
You have a Skype for Business Server 2015 infrastructure that contains an Enterprise Edition pool. You plan to add the following servers and roles to the existing infrastructure.
Edge Server, Archiving, Persistent Chat, Monitoring
You need to add SQL Server servers to the existing infrastructure. The solution must not use the current SQL Server Back End Server.
What is the minimum number of SQL servers that you should add?
A. 1
B. 2
C. 3
D. 4

33. Question 4: You need to implement the Unified Contact Store.
Which three actions should you perform? Each correct answer presents part of the solution.
Choose three.
A. From a server that has Skype for Business Server 2015 deployed, run the New-
CsPartnerApplication Skype for Business Management Shell cmdlet.
B. From a server that has Exchange Server 2013 deployed, run the ExchUCUtil.ps1 script.
C. From a server that has Skype for Business Server 2015 deployed, run the Set-CsUserServicesPolicy
Skype for Business Management Shell cmdlet.
D. From a server that has Exchange Server 2013 deployed, run the Configure-
EnterprisePartnerApplication.psI script.
E. From a server that has Skype for Business Server 2015 deployed, run the Set-CsClientPolicy Skype
for Business Management Shell cmdlet.

34. 03 | Manage and troubleshoot Skype for Business

35. Manage and troubleshoot conferencing and application sharing
troubleshoot Conferencing Auto Attendant (CAA), Conference Announcement Service (CAS), contact objects, and conference directories
troubleshoot web scheduler, multipoint control unit (MCU) health, simple URLs (join launcher), UC add-in for Microsoft Outlook
troubleshoot multi-party video, server resources, media relay, and third-party interop
troubleshoot Microsoft PowerPoint presentation connections, Office Web App/Online server configurations
troubleshoot Skype Meeting Broadcast.

36. Manage and troubleshoot sign-in, presence, and client configuration
troubleshoot DNS, certificates, registration, network connectivity including ExpressRoute, authentication, and auto-discover
troubleshoot aggregation (OOF, calendar, machine, and user), enhanced privacy, subscriptions, contact list
troubleshoot file transfer, policy assignment, URL filtering, client version filtering, GPO

37. Manage and troubleshoot federation and remote access
troubleshoot federation, XMPP, and federation types (open, direct, and enhanced), federation policy, and legacy interop
troubleshoot mobile auto-discover issues, mobile device usage issues, mobile callback feature, push notification, call establishment, and mobile conference data

38. Manage and troubleshoot Address Book
Configure Address Book
troubleshoot normalization, local versus web lookup, internal file download, external file download, Address Book generation

39. Manage and troubleshoot high availability and resiliency
troubleshoot the backup service, server storage replication, and file share replication
manage single server failure (Skype for Business, SQL)
manage data center failure; backup and restore application service data
manage filestore data and contacts
maintain and recover Skype for Business topology
recover CMS (Invoke-CSManagementServerFailover)

40. Always On Some Known Issues

41. SQL AlwaysOn SQL Server AlwaysOn HA Solutions AlwaysOn Advantages
Next generation of Database Mirroring technologies
Provides High Availability and Disaster Recovery in SQL
Introduced in SQL Server 2012 and present in SQL Server 2014
Runs on top of WSFC (Windows Server Failover Clustering)
AlwaysOn Advantages
Latest and Greatest SQL HA solution
Although database mirroring is still available in its original feature set, it is now considered a deprecated feature and will be removed in a future release of SQL Server.
More Reliable
AlwaysOn (One Primary, can have up to three corresponding Secondary Replicas)
Mirroring (One Primary, One Mirror)
Multi-Database Failovers
Useful in applications with several databases
Databases can be added to an Availability Group that can be failed over between replicas
All databases in Availability Group are failed over at the same time

42. Microsoft Lync
12/4/2017
Issue 1
Clients go into resiliency mode after failing over Availability Group to secondary replica
Reason:
The Availability Group wizard does not replicate the SQL logins from the primary node to each of the defined secondary replicas.
RTC Universal Groups are missing
Workaround Steps:
1. Launch Topology Builder and download topology
2. Verify the SQL machine FQDN value is set to the AG Listener FQDN
2a. If not, change and then publish the topology and wait for CMS replication to occur
3. Use SQL Management Studio to failover the AG Listener cluster resource to one of the replica servers
4. Run Install-CsDatabase –ConfiguredDatabases –SqlServerFqdn {AG Listener fqdn} –ForInstance {instance} –Update  (which creates the missing SQL logins on the replica server)
5. Repeat steps 3 – 4 for each additional replica server
Note :
If you want to create a new database you will need to repoint the SQL Machine FQDN to the Primary Node in the Availability Group
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

43. Issue 2
Unable to move from SQL mirroring to AlwaysOn Availability Groups due to location of CMS database
Reason:
If the CMS database is homed on or paired with the pool where you are attempting to move to AlwaysOn Availability Groups, you will be unable to change the HA model for the backend database.
Workaround Steps:
If the pool is not paired, use the Move-CsManagementServer cmdlet to move the CMS database to another pool.
If the pool is paired and the CMS is not homed locally on the pool where you are attempting to change the backend HA model:
Disable pool pairing and uninstall the CMS database
Change the HA model from SQL mirroring to Availability Groups
Reinstall the CMS database and re-enable pool pairing
Add the CMS databases to the Availability Group
If the pool is paired and the CMS is homed on locally on the pool where you are attempting to change the backend HA model:
Use Invoke-CsManagementServerFailover cmdlet to failover the CMS database

44. Pool quorum Pool quorum
Pool will go offline if less than 50% of Front End servers are available
Pool will also go offline if exact 50% are online but SQL database is not
Total Number of Front End Server in the pool (defined in Topology)
Number of Servers that must be running for pool to be functional 2 1
3-4
Any 2
5-6
Any 3 7
Any 4
8-9
Any 4 of the first 7 servers
10-12
Any 5 of the first 9 servers

45. SQL back end database Same location as FE servers High Availability
SQL mirroring
One mirror server
Use SQL witness
“Feature Not Supported in a Future Version of SQL Server”
SQL AlwaysOn
Runs on top of Windows Server Failover Clustering
Up to three Secondary Replicas
SQL Enterprise required for more than one replica
Disaster Recovery
Via pool failover

46. File Share Used for Same location as FE servers High Availability
meeting content, address book files
Same location as FE servers
High Availability
Distributed File Share (DFS)
Disaster Recovery
Via pool failover

47. Office Web App Server Used for Same location as Front End pool
Presenting PowerPoint
Same location as Front End pool
High Availability
Pool of OWAS
Hardware Load Balancer recommended
Disaster Recovery
Via pool failover

48. Monitoring Server Database
Used for
Collection Quality of Experience and CDR data
Runs SQL Server Reporting Services and the Server Monitoring Reports
Globally one Monitoring database
Complete view on your data
For performance you might want to copy data to a second database and run reports against the second
High Availability
Via SQL

49. Edge Server Used for Same location as Front End pool High Availability
In Hybrid, on premises environment required for sign-in! High Availability is crucial
Used for
Remote Access, Federation, O365 Integration
Same location as Front End pool
High Availability
Pool of Edge Servers
DNS Load Balancing recommended
Disaster Recovery
Via pool failover
Hardware Load Blancing recommended if
Federation with OCS 2007, OCS 2007 R2
Exchange UM 2007 or Exchange UM 2010
Legacy clients

50. Reverse Proxy Used for Same location as Edge Server High Availability
Meeting join, mobile clients, file download
Same location as Edge Server
Qualified Reverse Proxies to be published on TechNet
High Availability
Depends on Reverse Proxy solution
Disaster Recovery
Via pool failover

51. Reverse Proxy Used for Same location as Edge Server High Availability
Meeting join, mobile clients, file download
Same location as Edge Server
Qualified Reverse Proxies to be published on TechNet
High Availability
Depends on Reverse Proxy solution
Disaster Recovery
Via pool failover

52. InPlace Upgrade
More convenient upgrade path from Lync Server 2013 to Skype for Business by:
Preserving existing hardware/server investments
Smoother upgrade process without extensive planning
Reducing the overall cost for deployment
The goal of heading towards Smart Setup
Upgrade Path
Original Topology
New Topology
In-Place Upgrade Supported ?
Lync 2013
SfB
Yes. In-Place upgrade support from > SfB
Lync 2010
SfB
No. Upgrade from > SfB , Same as > 2013
Lync Coexistence
( )
Mandatory migration from > 2013 before deploying SfB. Then In-Place upgrade from 2013 to SfB

53. Identify issues by using troubleshooting tools
Skype for Business monitoring reports
configure synthetic transactions
Understand RBAC (especially RTCUniversalServerAdmins)
test connectivity with PowerShell Test cmdlets
configure core reliability and media quality monitoring; verify service health and CMS replication
recover from failed server build
DNS
CLSlogging
Snooper
identify issues using NetMon, Event Viewer, and Performance Monitor
analyze signaling and media call flow for Skype for Business
use Microsoft Online Services Diagnostics and Logging Support Toolkit

54. Manage and troubleshoot topology and dependent infrastructure
Enable or move users
manage and troubleshoot DNS
troubleshoot database synchronization issues, including SQL HA and LYSS replication, topology replication, IIS
troubleshoot certificates

55. Manage and troubleshoot Persistent Chat servers
Manage categories, scope, chat rooms, room access, compliance, and add-ins

56. Example Questions

57. Question 5:
Fabrikam, Inc, changed their Access Edge fully qualified domain name (FQDN). This resulted in a
broken Federation relationship. You need to correct the issue and reduce further administrative
overhead as quickly as possible. What should you do?
A. Modify the SRV record_sipfederationtls._tcp.fabrikam.com to point to the new Fabrikam Access
Edge FQDN on port TCP/5061.
B. Modify the federation configuration to enable Open Federation.
C. Allow outbound connection on port TCP/5061 from Edge Server to any IP address on the Internet.
D. Modify the SRV record_sipfederationtls._tcp.fabrikam.com to point to the new
Fabrikam Access Edge FQDN on port TCP/443.

58. Question 6:
You are evaluating a disaster recovery solution for the Front End pools. You need to recommend the solution for restoring access to the Central Management store if a Front End pool fails.
Which Skype for Business Server 2015 cmdlet should you run?
A. Invoke-CsPoolFailover
B. Invoke-CsManagementServerFailover
C. Import-CsConfiguration
D. Move-CsManagementServer

59. Session objectives and takeaways
Tech Ready 15
12/4/2017
Session objectives and takeaways
Review all three tested categories
Review test question structure
Review test questions
Test taking tips
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

60. Resources Microsoft Learning Site: microsoft.com/learning
Your one-stop location for info on all available Microsoft certifications, training, and exam prep resources
Microsoft Virtual Academy: microsoftvirtualacademy.com
Your source for on-demand, online technical training
Microsoft Exam:

61. Please evaluate this session
12/4/2017 2:10 AM
Please evaluate this session
Your feedback is important to us!
From your PC or Tablet visit MyIgnite at
From your phone download and use the Ignite Mobile App by scanning the QR code above or visiting
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

63. Issue 3 Creating an Availability Group with only a single replica
Reason:
For test environments, you may want to create an Availability Group with only a single replica.  If you attempt to use SQL Management Studio to do this, you will be blocked as it requires a minimum of two replicas.  However, you can use PowerShell to work around this limitation.
Workaround Steps:
Use the powershell cmdlets to set this up
# Create an in-memory representation of the primary replica
$primaryReplica = New-SqlAvailabilityReplica -Name "lab2-sql5\Instance1" -EndpointURL "TCP://lab2-sql5.contoso.com:5022" -AvailabilityMode "SynchronousCommit" -FailoverMode "Automatic" -Version 12 -AsTemplate
# Create the availability group
New-SqlAvailabilityGroup -Name "MyAG" -Path "SQLSERVER:\SQL\lab2-sql5\Instance1" -Database "cpsdyn"
# Add additional database to the availability group
Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rgsconfig"
Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rgsdyn"
Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rtcab"
Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rtcshared"
Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rtcxds"
# Add availability group listener (note port number - you will get an error if default SQL port 1433 is already in use)
New-SqlAvailabilityGroupListener -Name lab2-sqlclu1 -StaticIp ' / ' -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Port 1431

64. Issue 4
Unable to create AlwaysOn Availability Group Listener due to connection failure
Reason:
For named instances, SQL Server listens for connections on a dynamic TCP port.  Some admins may wish to configure SQL to listen on either the default port (TCP/1433) or use a SQL alias to configure SQL to listen on a non-default static port (e.g. 1499).  If you configure your SQL servers to listen on the default port, you will encounter an error when attempting to create the Availability Group listener for SQL Always On due to a port conflict.
Workaround Steps:
Use a SQL alias to configure SQL to listen on a non-default static port (e.g. 1499) if default SQL port 1433 is already in use (
Verify that exceptions have been added in Windows Firewall for the port used by the Availability Group Listener.