skype for business end user experience management

More and more enterprises are implementing their voice and video infrastructure as a hybrid architecture that leverages both on-premise and cloud-based elements. Unaffected users see updates made by affected users.Īll modalities of conference are terminated.Ĭonference continues, and affected user can stay in the conference and all modalities work.LiveNX: Cloud-based Network Architecture with Skype for Business Shows the last presence state set by the affected user. User Experience for a User Homed in an Unaffected Pool During Failback of Another Pool User task Shows the last presence state set by the user, and presence changes will now be reflected.Ĭontacts list and Address Book Service availability Presence unknown while user is signed into backup pool during Resiliency mode. Presence as seen by other users in the same pool Not possible while user is in Resiliency mode. Scheduling or modifying scheduled meetings, creating ad-hoc conferences Affected user is restricted to what he/she can do in Resiliency mode.Ĭonference continues, and affected user can stay in the conference and all modalities work after user exits Resiliency mode. Ongoing conferences organized by unaffected userĬonference continues and affected user can stay in the conference. Every participant needs to click to rejoin the conference. Rejoin button will appear, but no users can rejoin while the affected user is in Resiliency mode.Īll modalities now work. Ongoing conferences organized by affected userĪll modalities of conference are terminated. User can sign in to the original home pool in regular mode. User can sign in to the home pool in Resiliency mode. User remains signed in and goes into regular mode. At some point user will be signed out and sign back in to the original home pool, in Resiliency mode. User stays signed in and connected to backup pool.

User Experience for an Affected User in a Pool in Failback User state or task A user originally homed on the backup pool is not an affected user. The term affected user refers to any user who was failed over from the home pool and is being serviced by the backup pool. The following tables show more details about how a user is affected during and after failback, and also how users in other pools see and interact with a user in a pool who is being failed back. For reference, it is expected to take up to 60 minutes for a pool of 20,000 users. Note that the failback process takes several minutes to complete. Pool failback can happen while an affected user is logged on to the backup pool, and the user remains logged on and working during the failback. Only then can a user establish new sessions or re-establish previous sessions. If they log in before the failover has completed, they will be in Resiliency mode until failover is complete. When the user logs back in, they will log in to the backup pool. The user cannot log back in until either the registrar resiliency timer expires or the administrator initiates failover procedures, whichever comes first. Any peer-to-peer session the user was participating in is ended, as are conferences organized by that user. When a user is in a pool that fails, the user is logged out. For best practice, the administrator should regularly back up the LIS database and use the latest backup copy to restore the LIS database in the backup pool after the failover. Note that the Location Information Server database is not replicated to the backup pool. When the home pool is restored, the administrator can fail back these users to be serviced by their original pool, where they are still homed. Users who are homed on a pool that fails will be temporarily serviced by the backup pool. Users are not rehomed during failover or failback. After the failover is complete, all users can get all services from the backup pool.Īny calls, meetings, or conversations a user has when the pool fails are disrupted, and the user must re-establish those sessions after failover to continue. In Resiliency mode, users are unable to perform tasks that would cause a persistent change on Skype for Business Server, such as adding a contact. For a brief period users who sign into the backup pool may be in resiliency mode. If a pool is failed over, all users in the affected pool are forced to sign out and then sign into the backup pool. Learn about what users experience when a Front End pool fails over or fails back during disaster recovery in Skype for Business Server.

Skype for business end user experience management