01 |

• Evaluate user distribution

• associate workloads to business requirements
• plan architecture; design SIP domains including shared SIP
namespaces (Split Domain)
• 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








• Define server roles; hardware requirements
• storage requirements for archiving and
monitoring
• define virtualization requirements
• Design a strategy for central and branch office
scenarios
• Resiliency, SQL mirroring, SQL AlwaysOn Failover
Clustering Instances, load balancing, and Geo DNS
• 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
• 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
• 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
• 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
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
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
02 |
• 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
• 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
• 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
• 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
• 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
• Configure pool pairing, configure Geo DNS for site failover,
configure SQL HA
• 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
• Implement chat history, room management URLs, HA and
DR, user policies, room design, and ethical boundaries
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
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.
03 |
• 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.
• 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
• 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
• Configure Address Book
• troubleshoot normalization, local versus web lookup, internal
file download, external file download, Address Book
generation
• 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)
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
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:
1. If the pool is not paired, use the Move-CsManagementServer cmdlet to move
the CMS database to another pool.
2. 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:
a) Disable pool pairing and uninstall the CMS database
b) Change the HA model from SQL mirroring to Availability Groups
c) Reinstall the CMS database and re-enable pool pairing
d) Add the CMS databases to the Availability Group
3. 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:
a) Use Invoke-CsManagementServerFailover cmdlet to failover the CMS database
b) Disable pool pairing and uninstall the CMS database
c) Change the HA model from SQL mirroring to Availability Groups
d) Reinstall the CMS database and re-enable pool pairing
e) Add the CMS databases to the Availability Group
Total Number of Front End Server in Number of Servers that must be
the pool (defined in Topology) 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
•
•

•
•

•
•

•
•

•
•

•
•

•
 In Hybrid, on premises environment required for
sign-in! High Availability is crucial
•

•
•

Hardware Load Blancing recommended if

Federation with OCS 2007, OCS 2007 R2
Exchange UM 2007 or Exchange UM 2010
Legacy clients
•

•
•

•
 Smoother

Original Topology New Topology In-Place Upgrade Supported ?

Lync 2013 SfB + 2013 Yes. In-Place upgrade support from 2013 -> SfB

Lync 2010 SfB + 2010 No. Upgrade from 2010 -> SfB , Same as 2010 -> 2013

Lync Coexistence SfB + 2013 Mandatory migration from 2010 -> 2013 before deploying SfB.
(2013 + 2010) Then In-Place upgrade from 2013 to SfB
• 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
• Enable or move users
• manage and troubleshoot DNS
• troubleshoot database synchronization issues, including SQL
HA and LYSS replication, topology replication, IIS
• troubleshoot certificates
• Manage categories, scope, chat rooms, room access, compliance, and
add-ins
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.
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
Session objectives and takeaways
• Review all three tested categories
• Review test question structure
• Review test questions
• Test taking tips
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 70-334 Exam:

https://www.microsoft.com/en-us/learning/exam-
70-334.aspx
http://myignite.microsoft.com

https://aka.ms/ignite.mobileapp
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:
1. 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" -AvailabilityReplica @($primaryReplica) -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 '192.168.0.209/255.255.252.0' -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Port 1431
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:
1. 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
(http://technet.microsoft.com/en-us/library/dn776290.aspx).
2. Verify that exceptions have been added in Windows Firewall for the
port used by the Availability Group Listener.