From d2bd3554b7acb2c9ae793d42b5f4845217bce92c Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 19 Sep 2024 10:27:15 -0700 Subject: [PATCH 01/87] Update toc.yml --- Teams/toc.yml | 504 ++++++++++++++++++++++++++++---------------------- 1 file changed, 285 insertions(+), 219 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index cd125f6954..d0665c4bb0 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1297,8 +1297,10 @@ items: - name: Contact Center integrations href: teams-contact-center.md -- name: Devices and rooms management +- name: Teams Rooms and devices items: + - name: What's new in Teams devices + href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2 - name: Teams device store href: devices/device-store.md - name: Teams device certification @@ -1323,30 +1325,83 @@ items: href: devices/usb-devices.md - name: Teams certified Android devices href: devices/teams-ip-phones.md - - name: Microsoft Teams Rooms + - name: Android version support + href: devices/android-version-support.md + - name: Supported Teams apps for Android devices (in process) + href: devices/certified-device-apps.md + + - name: Teams Rooms & panels items: - - name: Overview - href: rooms/index.md - - name: Plan - items: - - name: Teams Rooms planning - href: rooms/rooms-plan.md - - name: Security - href: rooms/security.md + - name: Overview & planning + items: + - name: Teams Rooms + items: + - name: Copilot for Teams Rooms + href: copilot-admin.md + - name: Overview + href: rooms/index.md + - name: Teams Rooms planning + href: rooms/rooms-plan.md + - name: Features + items: + - name: Teams Room Home Screen and admin controls + href: rooms/mtr-home-refresh.md + - name: Teams In Meeting experiences (to be written) + href: rooms/meeting experiences.md + - name: Meetings with SIP and H.323 devices + href: rooms/meetings-with-SIP-H323-devices.md + - name: Join third-party meetings + href: rooms/third-party-join.md + - name: Join meetings with QR codes + href: rooms/teams-rooms-qr-codes.md + - name: Digital signage + href: rooms/digital-signage.md + - name: Manage custom backgrounds on Android + href: rooms/custom-backgrounds-android.md + - name: Manage custom backgrounds on Windows + href: rooms/custom-backgrounds.md + - name: Content cameras + href: rooms/content-camera.md + - name: Set up coordinated meetings + href: rooms/coordinated-meetings.md + - name: Join a meeting using Proximity Join + href: rooms/proximity-join.md + - name: Intelligent speaker + items: + - name: Voice and face recognition + href: rooms/voice-and-face-recognition.md + - name: Voice recognition controls for Intelligent speakers + href: rooms/voice-recognition.md + - name: IntelliFrame + items: + - name: IntelliFrame overview (to be written) + href: devices/overview.md + - name: Multi-Stream IntelliFrame + href: devices/smartvision-admin.md + - name: Cloud IntelliFrame + href: devices/cloud-intelliframe.md + - name: Teams panels + items: + - name: Teams panels overview + href: devices/overview-teams-panels.md + - name: Plan + href: devices/teams-panels.md + - name: Features + items: + - name: Use Teams panels + href: devices/use-teams-panels.md + - name: App support on Teams panels + href: app-support-on-Teams-panels.md + - name: Check-in and auto release + href: devices/check-in-and-room-release.md + - name: Reserve rooms with a QR code + href: devices/reserving-rooms-with-a-qr-code.md + - name: Set custom backgrounds on Teams panels + href: devices/custom-background-panels.md + - name: Teams Rooms and devices feature comparison + href: rooms/teams-devices-feature-comparison.md - name: Meeting room guidance for Teams href: rooms/room-planning-guidance.md - - name: Hardware and operating systems - items: - - name: Certified Teams Rooms hardware - href: rooms/certified-hardware.md - - name: Windows version support - href: rooms/rooms-lifecycle-support.md - - name: Android app and firmware versions - href: rooms/android-app-firmware.md - - name: Android version support - href: devices/android-version-support.md - - name: Teams Rooms and devices feature comparison - href: rooms/teams-devices-feature-comparison.md - name: Licensing items: - name: Overview of Teams Rooms licensing @@ -1355,228 +1410,239 @@ items: href: rooms/admin-center-license-overview.md - name: Teams Rooms legacy licensing href: rooms/rooms-legacy-licensing.md - - name: Release notes - href: rooms/rooms-release-note.md - - name: Deploy - items: - - name: Deployment overview - href: rooms/rooms-deploy.md - - name: Prepare your environment - href: rooms/rooms-prep.md - - name: Create resource accounts - href: rooms/create-resource-account.md - - name: Authentication + - name: Security + href: rooms/security.md + - name: Conditional Access and Intune compliance items: - - name: Deploy LAPs - href: rooms/laps-authentication.md - - name: Configure authentication - href: rooms/rooms-authentication.md - name: Best practices for Conditional Access and Intune compliance href: rooms/conditional-access-and-compliance-for-devices.md - name: Supported Conditional Access and Intune compliance policies href: rooms/supported-ca-and-compliance-policies.md - - name: Surface Hub - items: - - name: Set up Coordinated Meetings - href: rooms/coordinated-meetings.md - - name: Manage Microsoft Teams settings - href: rooms/surface-hub-manage-config.md - - name: Teams Rooms for Windows deployment tools + - name: Authentication best practices for Android devices + href: devices/authentication-best-practices-for-android-devices.md + - name: Release notes items: - - name: Create a Teams Room for Windows image - href: rooms/console.md - - name: Update a Teams Room for Windows - href: rooms/manual-update.md - - name: Peripherals + - name: Teams Rooms release notes + href: rooms/rooms-release-note.md + - name: Teams Panels release notes (to be written) + href: devices/teams-panels-release-notes.md + - name: Known issues items: - - name: Content cameras - href: rooms/content-camera.md - - name: Manage + - name: Teams Rooms on Windows + href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-windows + - name: Teams Rooms on Android + href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-android + - name: Teams Panels (to be written) + href: devices/teams-panels-known-issues.md + - name: Deploy items: + - name: Deployment overview + href: rooms/rooms-deploy.md + - name: Step 1 - Select your devices (to be written) + href: rooms/select-devices.md + - name: Step 2 - Prepare your environment + items: + - name: Preparing your network + href: rooms/rooms-prep.md + - name: QoS on Teams devices + href: devices/qos-on-teams-devices.md + - name: Configure authentication + href: rooms/rooms-authentication.md + - name: Intune Enrollment for Windows + items: + - name: AutoPilot and Autologin + href: rooms/autopilot-autologin.md + - name: Deploy LAPs + href: rooms/laps-authentication.md + - name: Intune Enrollment for Android + items: + - name: Device administrator + href: devices/phones-displays-deploy.md + - name: AOSP device management + href: rooms/android-migration-guide.md + - name: Step 3 - Create room accounts + href: rooms/create-resource-account.md + - name: Step 4 - Device setup + items: + - name: Teams Rooms on Windows + items: + - name: Use AutoPilot + AutoLogin for Teams Rooms on Windows + href: rooms/autopilot-autologin.md + - name: Create a one-time password + href: rooms/create-otp.md + - name: Set up using one-time passwords + href: rooms/first-time-setup.md + - name: Manual Join to Entra ID and Intune + href: /entra/identity/devices/device-join-plan.md + - name: Teams Rooms on Android and Teams Panels + items: + - name: Remote provisioning and sign-in + href: devices/remote-provision-remote-login.md + - name: Manage + items: - name: Management overview href: rooms/rooms-manage.md - - name: Maintenance and operations - href: rooms/rooms-operations.md - - name: Remotely configure layout, scale, and resolution - href: rooms/manage-front-room-scale-res.md - - name: Manage settings with an XML file - href: rooms/xml-config-file.md - - name: Feature management + - name: Keep up to date items: - - name: Teams Rooms Home screen - href: rooms/mtr-home-refresh.md - - name: Remotely configure front row layout - href: rooms/manage-front-row.md - - name: Join third-party meetings - href: rooms/third-party-join.md - - name: SIP and H.323 Calling with Teams Rooms - href: rooms/meetings-with-SIP-H323-devices.md - - name: Manage custom backgrounds on Android - href: rooms/custom-backgrounds-android.md - - name: Manage custom backgrounds on Windows - href: rooms/custom-backgrounds.md - - name: Digital signage - href: rooms/digital-signage.md - - name: Join meetings with QR codes - href: rooms/teams-rooms-qr-codes.md - - name: Multi-Stream IntelliFrame - href: devices/smartvision-admin.md - - name: Cloud IntelliFrame - href: devices/cloud-intelliframe.md - - name: Identification and enrollment + - name: Teams Rooms on Windows + href: rooms/rooms-lifecycle-support.md + - name: Teams Rooms on Android + href: rooms/android-app-firmware.md + - name: Teams panels + href: rooms/android-app-firmware.md + - name: Operations items: - - name: Voice and face recognition - href: rooms/voice-and-face-recognition.md - - name: Voice recognition controls for Intelligent speakers - href: rooms/voice-recognition.md - - name: Use the recovery tool - href: rooms/recovery-tool.md - - name: Known issues - href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues - - name: Microsoft Teams Rooms Pro Management - items: - - name: Getting started - items: - - name: Overview - href: rooms/rooms-pro-management.md - - name: Accessing the Pro Management portal - href: rooms/enrolling-mtrp-managed-service.md - - name: Enroll a device into Pro management - href: rooms/enroll-a-device.md - - name: Role-based access control - href: rooms/rooms-pro-rbac.md - - name: Resource accounts - href: rooms/resource-accounts.md - - name: Bring your own device (BYOD) spaces - items: - - name: Bring Your Own Device (BYOD) - href: rooms/bring-your-own-device.md - - name: Bookable Desks - href: rooms/bookable-desks.md - - name: Add peripherals to inventory - href: rooms/get-peripheral-information.md - - name: Planning and deployment - items: - - name: Standards and Rooms Planner - href: rooms/standards-and-room-planner.md - - name: Create a one-time password - href: rooms/create-otp.md - - name: Set up using one-time passwords - href: rooms/first-time-setup.md - - name: AutoPilot and Autologin - href: rooms/autopilot-autologin.md - - name: Monitoring and maintenance - items: - - name: Managing your inventory - href: rooms/inventory.md - - name: Monitoring and maintaining Teams Rooms - href: rooms/managed-meeting-rooms-portal.md - - name: Signal settings - href: rooms/signal-settings.md - - name: Remotely access a Teams Room console - href: rooms/remotely-access-teams-rooms.md - - name: Managed updates - href: rooms/update-management.md - - name: Configure ServiceNow - href: rooms/microsoft-teams-rooms-configure-servicenow.md - - name: Audit logs for activities - href: rooms/multi-tenant-auditing.md - - name: Viewing events - href: rooms/view-events.md - - name: Record an issue - href: rooms/customer-reported-incidents.md - - name: Multi-tenant management for partners - href: rooms/multi-tenant-management-partner.md - - name: Multi-tenant management for customers - href: rooms/multi-tenant-management-customer.md - - name: Analytics, reports, and insights - items: - - name: Health and usage reports - href: rooms/health-and-usage-reports.md - - name: Data and privacy information - href: rooms/data-and-privacy-info.md - - name: Devices - items: - - name: Phones for Teams - href: devices/phones-for-teams.md - - name: Teams panels - items: - - name: Overview - href: devices/overview-teams-panels.md - - name: Plan - href: devices/teams-panels.md - - name: Manage + - name: Teams Rooms operations + href: rooms/rooms-operations.md + - name: Teams Rooms for Window - Recovery + href: rooms/recovery-tool.md + - name: Media creation for Teams Rooms on Windows + href: rooms/console.md + - name: Update a Teams Room for Windows + href: rooms/manual-update.md + - name: Teams Admin Center items: - - name: Feature management - items: - - name: Use Teams panels - href: devices/use-teams-panels.md - - name: App support on Teams panels - href: app-support-on-Teams-panels.md - - name: Check-in and auto release - href: devices/check-in-and-room-release.md - - name: Reserve rooms with a QR code - href: devices/reserving-rooms-with-a-qr-code.md - - name: Manage custom backgrounds - href: devices/custom-background-panels.md - - name: SIP gateways + - name: Overview + href: rooms/rooms-manage.md + - name: Manage your devices in Teams + href: devices/device-management.md + - name: Manage Teams device tags + href: devices/manage-device-tags.md + - name: Update your devices remotely + href: devices/remote-update.md + - name: Use administrative units to manage devices + href: administrative-unit.md + - name: Analytics, reports, & insights + items: + - name: Teams device health + href: teams-device-health.md + - name: Teams device health monitoring + href: alerts/device-health-status.md + - name: Health and usage reports + href: rooms/health-and-usage-reports.md + - name: Microsoft Teams Rooms Pro Management + items: + - name: Getting started + items: + - name: Overview + href: rooms/rooms-pro-management.md + - name: Accessing the Pro Management portal + href: rooms/enrolling-mtrp-managed-service.md + - name: Enroll a device into Pro management + href: rooms/enroll-a-device.md + - name: Resource accounts + href: rooms/resource-accounts.md + - name: Manage + items: + - name: Managing your inventory + href: rooms/inventory.md + - name: Standards and Rooms Planner + href: rooms/standards-and-room-planner.md + - name: Settings management (to be written) + href: rooms/settings-management.md + - name: Remote access a Teams Room console + href: rooms/remotely-access-teams-rooms.md + - name: Analytics, reports, and insights + items: + - name: Monitoring and maintaining Teams Rooms + href: rooms/managed-meeting-rooms-portal.md + - name: Audit logs for activities + href: rooms/multi-tenant-auditing.md + - name: Alerting + items: + - name: Signal settings + href: rooms/signal-settings.md + - name: Configure ServiceNow + href: rooms/microsoft-teams-rooms-configure-servicenow.md + - name: Viewing events + href: rooms/view-events.md + - name: Record an issue + href: rooms/customer-reported-incidents.md + - name: Managed updates + href: rooms/update-management.md + - name: Role-based access control + href: rooms/rooms-pro-rbac.md + - name: Multi-tenant management for partners + href: rooms/multi-tenant-management-partner.md + - name: Multi-tenant management for customers + href: rooms/multi-tenant-management-customer.md + - name: Data and privacy information + href: rooms/data-and-privacy-info.md + - name: Configuration + items: + - name: Remotely configure layout, scale, and resolution + href: rooms/manage-front-room-scale-res.md + - name: Manage settings with an XML file + href: rooms/xml-config-file.md + - name: Remotely configure front row layout + href: rooms/manage-front-row.md + - name: Teams phones + items: + - name: Overview & planning items: - - name: Plan for SIP Gateway - href: sip-gateway-plan.md - - name: Configure SIP Gateway - href: sip-gateway-configure.md - - name: Dynamic filters - href: sip-gateway-dynamic-filters.md + - name: Teams phones overview + href: devices/phones-for-teams.md + - name: Plan a Teams phones deployment + href: devices/plan-device-deployment.md + - name: What's new in Teams phones + href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones - name: Deploy items: - - name: Plan phones and displays deployment + - name: Step 1 - Deployment overview href: devices/plan-device-deployment.md - - name: Set up common area phones - href: set-up-common-area-phones.md - - name: Set up a common area mobile phones - href: devices/common-area-mobile-phones.md - - name: Remote provisioning and sign-in - href: devices/remote-provision-remote-login.md - - name: Remote sign in and sign out - href: devices/remote-sign-in-and-sign-out.md - - name: Deploy Teams phones and Teams panels using Intune - href: devices/phones-panels-deploy.md - - name: Authentication best practices for Android devices - href: devices/authentication-best-practices-for-android-devices.md - - name: AOSP device management - href: rooms/android-migration-guide.md - - name: Android version support - href: devices/android-version-support.md + - name: Step 2 - Prepare your environment + items: + - name: Preparing your network + href: rooms/rooms-prep.md + - name: Intune Enrollment for Teams phones + items: + - name: Device administration + href: devices/phones-panels-deploy.md + - name: AOSP device management + href: rooms/android-migration-guide.md + - name: Authentication best practices for Teams phones + href: devices/authentication-best-practices-for-android-devices.md + - name: Step 3 - Set up and configure + items: + - name: Set up common area phones + href: set-up-common-area-phones.md + - name: Set up a common area mobile phones + href: devices/common-area-mobile-phones.md + - name: Step 4 - Teams phones device set up + items: + - name: Remote provisioning + href: devices/remote-provision-remote-login.md + - name: Remote sign in and sign out + href: devices/remote-sign-in-and-sign-out.md - name: Manage items: - - name: Manage your devices in Teams - href: devices/device-management.md - - name: Use administrative units to manage devices - href: administrative-unit.md - - name: Manage Teams device tags - href: devices/manage-device-tags.md - - name: Update your devices remotely - href: devices/remote-update.md - - name: Feature management - items: - - name: QoS on Teams devices - href: devices/qos-on-teams-devices.md - - name: RealWear for Teams - href: flw-realwear.md - - name: Monitor - items: - - name: Teams device health monitoring - href: alerts/device-health-status.md - - name: Teams devices and peripherals - href: teams-device-health.md + - name: Manage Teams phones + href: devices/manage-teams-phones.md + - name: Update management + href: devices/remote-update.md + - name: Bring your own device (BYOD) spaces + items: + - name: Bring Your Own Device (BYOD) + href: rooms/bring-your-own-device.md + - name: Bookable Desks + href: rooms/bookable-desks.md + - name: Add peripherals to inventory + href: rooms/get-peripheral-information.md + - name: SIP gateways + items: + - name: Plan for SIP Gateway + href: sip-gateway-plan.md + - name: Configure SIP Gateway + href: sip-gateway-configure.md + - name: Dynamic filters + href: sip-gateway-dynamic-filters.md - name: Reference items: - - name: Android version support - href: devices/android-version-support.md - name: Teams displays overview href: devices/teams-displays.md - name: Hot desking Teams Displays href: devices/hot-desking-teams-displays.md + - name: Manage apps in Teams items: - name: Understand apps in Teams From 19dfcbc07bd7f68701443064a89fb2d10dcf0121 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Tue, 24 Sep 2024 16:08:44 -0500 Subject: [PATCH 02/87] Update managed-meeting-rooms-portal.md Updated for supportability in GCC --- Teams/rooms/managed-meeting-rooms-portal.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/rooms/managed-meeting-rooms-portal.md b/Teams/rooms/managed-meeting-rooms-portal.md index 9a4d8dec2f..316aead4dd 100644 --- a/Teams/rooms/managed-meeting-rooms-portal.md +++ b/Teams/rooms/managed-meeting-rooms-portal.md @@ -25,7 +25,7 @@ f1keywords: ## Overview -The Teams Rooms Pro Management portal provides a view of the health of your meeting rooms and helps to facilitate your existing monitoring tools and practices. This feature is only available in public or commercial cloud. It's not available in GCC, GCC-H, or DoD government clouds. +The Teams Rooms Pro Management portal provides a view of the health of your meeting rooms and helps to facilitate your existing monitoring tools and practices. This feature is only available in the commercial & GCC clouds. It's not available in GCC-H or DoD clouds. The scope of the monitoring is: From d2bf74fde380042cf17e078d35e4dbfd742b3632 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 30 Sep 2024 16:25:27 -0500 Subject: [PATCH 03/87] Update teams-devices-feature-comparison.md Breakout rooms on MTRW --- Teams/rooms/teams-devices-feature-comparison.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Teams/rooms/teams-devices-feature-comparison.md b/Teams/rooms/teams-devices-feature-comparison.md index 0652c7c76f..5942ea7a7c 100644 --- a/Teams/rooms/teams-devices-feature-comparison.md +++ b/Teams/rooms/teams-devices-feature-comparison.md @@ -62,7 +62,7 @@ To help guide you as to what features are available on different platforms, you | | Live reactions | Available | Available | | | PowerPoint Live | Available | Available | | | Live closed captions | Available | Available | -| | Participate in breakout rooms | Not available | Not available | +| | Participate in breakout rooms | Available | Not available | | | Teams Premium meeting protection policies (watermark, E2E encryption for meetings, and sensitivity labels) | Available | Available | | | Start meeting recording and transcription | Not available | Not available | | | Teams Town Hall (Presenter role) | Not available | Not available | @@ -86,7 +86,7 @@ To help guide you as to what features are available on different platforms, you | | Rate my call report | Available | Not available | | | Net promoter score (NPS) at meeting end| Available | Not available | | | Meeting controls on touch enabled front of room displays | Not available | Available | -| | Smart Camera Controls | Available | Available| +| | Smart Camera Controls | Available | Available | | | Local pan tilt zoom (PTZ) controls | Not available | Not available | | | Remote Pan tilt zoom (PTZ) control | Available | Available | | | Switch between multiple in-room cameras | Available | Available| @@ -185,7 +185,7 @@ To help guide you as to what features are available on different platforms, you | | Live reactions | Available | Available | | | PowerPoint Live | Available | Available | | | Live closed captions | Available | Available | -| | Participate in breakout rooms | Not available | Not available | +| | Participate in breakout rooms | Available | Not available | | | Teams Premium meeting protection policies (watermark, E2E encryption for meetings, and sensitivity labels) | Available | Not available | | | Start meeting recording and transcription | Not available | Not available | | | Teams Town Hall (Presenter role) | Not available | Not available | From 2f480dc7b292d926562837bd8c46aeacae94f7bc Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 30 Sep 2024 16:39:20 -0500 Subject: [PATCH 04/87] Update teams-devices-feature-comparison.md --- Teams/rooms/teams-devices-feature-comparison.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/rooms/teams-devices-feature-comparison.md b/Teams/rooms/teams-devices-feature-comparison.md index 5942ea7a7c..cec8fb2d58 100644 --- a/Teams/rooms/teams-devices-feature-comparison.md +++ b/Teams/rooms/teams-devices-feature-comparison.md @@ -307,7 +307,7 @@ To help guide you as to what features are available on different platforms, you | | Live reactions | Available | Available | | | PowerPoint Live | Available | Available | | | Live closed captions | Available | Available | -| | Participate in breakout rooms | Not available | Not available | +| | Participate in breakout rooms | Available | Not available | | | Teams Premium meeting protection policies (watermark, E2E encryption for meetings, and sensitivity labels) | Available | Available | | | Start meeting recording and transcription | Not available | Not available | | | Teams Town Hall (Presenter role) | Not available | Not available | From 987b119f42c8cd18459274a179f55cae9b8fd18b Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 30 Sep 2024 17:37:54 -0500 Subject: [PATCH 05/87] Update supported-ca-and-compliance-policies.md Marked new authentication flows policy as not supported as DCF is required for Android devices. --- Teams/rooms/supported-ca-and-compliance-policies.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index ddf55fccce..9a906f927e 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -48,6 +48,7 @@ The following list includes the supported Conditional Access policies for Teams | Locations | Supported | Supported | Supported | | Client apps | Not supported | Not supported | Not supported | | Filter for devices | Supported | Supported | Supported | +| Authentication Flows | Not supported | Not supported | Not supported | | **Grant** | --- | --- | --- | | Block access | Supported | Supported | Supported | | Grant access | Supported | Supported | Supported | From 4a6335fa8147ca283f17e755147d33b5185a5dff Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 30 Sep 2024 17:42:44 -0500 Subject: [PATCH 06/87] Update supported-ca-and-compliance-policies.md --- Teams/rooms/supported-ca-and-compliance-policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index 9a906f927e..6d46d010dc 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -48,7 +48,7 @@ The following list includes the supported Conditional Access policies for Teams | Locations | Supported | Supported | Supported | | Client apps | Not supported | Not supported | Not supported | | Filter for devices | Supported | Supported | Supported | -| Authentication Flows | Not supported | Not supported | Not supported | +| Authentication Flows | Supported | Not supported

Device code flow is required for sign in | Not supported

Device code flow is required for sign in | | **Grant** | --- | --- | --- | | Block access | Supported | Supported | Supported | | Grant access | Supported | Supported | Supported | From 1b330930b88b47b6c17f6b7bbccabae1fbc76b59 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Tue, 1 Oct 2024 13:56:47 -0700 Subject: [PATCH 07/87] Update teams-devices-feature-comparison.md --- Teams/rooms/teams-devices-feature-comparison.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/rooms/teams-devices-feature-comparison.md b/Teams/rooms/teams-devices-feature-comparison.md index cec8fb2d58..5833348ee6 100644 --- a/Teams/rooms/teams-devices-feature-comparison.md +++ b/Teams/rooms/teams-devices-feature-comparison.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: mattslomka -ms.date: 4/24/2024 +ms.date: 10/01/2024 ms.topic: article audience: Admin ms.service: msteams From cfd886e6162de6223e3a283017410a49bc8dd0e2 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Thu, 3 Oct 2024 14:09:17 -0700 Subject: [PATCH 08/87] Update toc.yml --- Teams/toc.yml | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/Teams/toc.yml b/Teams/toc.yml index 2e3385e4e7..0ff8366d56 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1332,6 +1332,49 @@ items: - name: Supported Teams apps for Android devices (in process) href: devices/certified-device-apps.md + +- name: Rooms and devices + items: + - name: Teams device store + href: devices/device-store.md + - name: Teams device certification + items: + - name: Certification overview + href: devices/certification-overview.md + - name: Partners + items: + - name: Partners device certification + href: devices/certification-partners.md + - name: How to join the program + href: devices/certification-join.md + - name: Teams specifications + href: devices/certification-specifications.md + - name: IT admins and decision makers + href: devices/certification-it-admins.md + - name: End users + href: devices/certification-end-users.md + - name: Product lifecycle + items: + - name: Windows version support + href: rooms/rooms-lifecycle-support.md + - name: Android version support + href: devices/android-version-support.md + - name: Teams Certified Devices + items: + - name: Teams Rooms on Windows certified devices + href: rooms/certified-hardware.md + - name: Teams Rooms on Android certified devices + href: devices/certified-hardware-android.md + - name: Teams panels certified devices + href: devices/teams-panels-certified-hardware.md + - name: Teams phones certified devices + href: devices/teams-phones-certified-hardware.md + - name: Teams displays certified devices + href: devices/teams-displays-certified-hardware.md + - name: Personal peripherals + href: devices/usb-devices.md + - name: Management apps + href: devices/certified-device-apps.md - name: Teams Rooms & panels items: - name: Overview & planning @@ -1492,6 +1535,8 @@ items: href: rooms/android-app-firmware.md - name: Teams panels href: rooms/android-app-firmware.md + - name: Management apps + href: devices/certified-device-apps.md - name: Operations items: - name: Teams Rooms operations From bf0fb28e6cbf45cf1c9a95ed67a07796296c4def Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Thu, 3 Oct 2024 14:14:58 -0700 Subject: [PATCH 09/87] Update toc.yml --- Teams/toc.yml | 33 ++------------------------------- 1 file changed, 2 insertions(+), 31 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 0ff8366d56..5ea56184d8 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1298,7 +1298,7 @@ items: href: microsoft-teams-online-call-flows.md - name: Contact Center integrations href: teams-contact-center.md - + - name: Teams Rooms and devices items: - name: What's new in Teams devices @@ -1306,34 +1306,6 @@ items: - name: Teams device store href: devices/device-store.md - name: Teams device certification - items: - - name: Certification overview - href: devices/certification-overview.md - - name: Partners - items: - - name: Partners device certification - href: devices/certification-partners.md - - name: How to join the program - href: devices/certification-join.md - - name: IT admins and decision makers - href: devices/certification-it-admins.md - - name: End users - href: devices/certification-end-users.md - - name: Teams specifications - href: devices/certification-specifications.md - - name: Teams Rooms certified systems and peripherals - href: rooms/certified-hardware.md - - name: Personal peripherals - href: devices/usb-devices.md - - name: Teams certified Android devices - href: devices/teams-ip-phones.md - - name: Android version support - href: devices/android-version-support.md - - name: Supported Teams apps for Android devices (in process) - href: devices/certified-device-apps.md - - -- name: Rooms and devices items: - name: Teams device store href: devices/device-store.md @@ -1373,8 +1345,7 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md - - name: Management apps - href: devices/certified-device-apps.md + - name: Teams Rooms & panels items: - name: Overview & planning From d4ec98eaeed89b9fc3a1fff8c6333b24467c95c0 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Thu, 3 Oct 2024 14:34:26 -0700 Subject: [PATCH 10/87] Update toc.yml --- Teams/toc.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Teams/toc.yml b/Teams/toc.yml index 5ea56184d8..0bd4a1458c 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1345,6 +1345,8 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md + - name: Supported SIP Gateway devices + href: devices/supported-sip-gateways.md - name: Teams Rooms & panels items: From 9a1e4d3277adcc4b93c0b8bfe2c7257b9b93016c Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 3 Oct 2024 16:42:33 -0500 Subject: [PATCH 11/87] Update toc.yml Matt's revisions --- Teams/toc.yml | 64 ++++++++++++++++++++++----------------------------- 1 file changed, 28 insertions(+), 36 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 0bd4a1458c..98ab566af3 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1345,8 +1345,6 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md - - name: Supported SIP Gateway devices - href: devices/supported-sip-gateways.md - name: Teams Rooms & panels items: @@ -1354,41 +1352,41 @@ items: items: - name: Teams Rooms items: - - name: Copilot for Teams Rooms - href: copilot-admin.md - name: Overview href: rooms/index.md - name: Teams Rooms planning href: rooms/rooms-plan.md + - name: Copilot for Teams Rooms + href: copilot-admin.md - name: Features items: - name: Teams Room Home Screen and admin controls href: rooms/mtr-home-refresh.md - name: Teams In Meeting experiences (to be written) href: rooms/meeting experiences.md - - name: Meetings with SIP and H.323 devices + - name: Join a meeting using Proximity Join + href: rooms/proximity-join.md + - name: Join meetings with QR codes + href: rooms/teams-rooms-qr-codes.md + - name: SIP and H.323 Calling href: rooms/meetings-with-SIP-H323-devices.md - name: Join third-party meetings href: rooms/third-party-join.md - - name: Join meetings with QR codes - href: rooms/teams-rooms-qr-codes.md - name: Digital signage href: rooms/digital-signage.md - - name: Manage custom backgrounds on Android + - name: Custom backgrounds on Android href: rooms/custom-backgrounds-android.md - - name: Manage custom backgrounds on Windows + - name: Custom backgrounds on Windows href: rooms/custom-backgrounds.md - - name: Content cameras + - name: Content camera href: rooms/content-camera.md - - name: Set up coordinated meetings + - name: Coordinated meetings href: rooms/coordinated-meetings.md - - name: Join a meeting using Proximity Join - href: rooms/proximity-join.md - name: Intelligent speaker items: - name: Voice and face recognition href: rooms/voice-and-face-recognition.md - - name: Voice recognition controls for Intelligent speakers + - name: Voice recognition controls href: rooms/voice-recognition.md - name: IntelliFrame items: @@ -1408,13 +1406,13 @@ items: items: - name: Use Teams panels href: devices/use-teams-panels.md - - name: App support on Teams panels + - name: App support href: app-support-on-Teams-panels.md - name: Check-in and auto release href: devices/check-in-and-room-release.md - name: Reserve rooms with a QR code href: devices/reserving-rooms-with-a-qr-code.md - - name: Set custom backgrounds on Teams panels + - name: Custom backgrounds on Teams panels href: devices/custom-background-panels.md - name: Teams Rooms and devices feature comparison href: rooms/teams-devices-feature-comparison.md @@ -1424,8 +1422,6 @@ items: items: - name: Overview of Teams Rooms licensing href: rooms/rooms-licensing.md - - name: Teams Rooms admin center licensing - href: rooms/admin-center-license-overview.md - name: Teams Rooms legacy licensing href: rooms/rooms-legacy-licensing.md - name: Security @@ -1436,36 +1432,34 @@ items: href: rooms/conditional-access-and-compliance-for-devices.md - name: Supported Conditional Access and Intune compliance policies href: rooms/supported-ca-and-compliance-policies.md - - name: Authentication best practices for Android devices + - name: Authentication for Teams Rooms on Windows devices + href: rooms/rooms-authentication.md + - name: Authentication for Teams Android devices href: devices/authentication-best-practices-for-android-devices.md - name: Release notes items: - name: Teams Rooms release notes href: rooms/rooms-release-note.md - - name: Teams Panels release notes (to be written) - href: devices/teams-panels-release-notes.md + - name: Teams Panels release notes + href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels - name: Known issues items: - name: Teams Rooms on Windows href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-windows - name: Teams Rooms on Android href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-android - - name: Teams Panels (to be written) - href: devices/teams-panels-known-issues.md - - name: Deploy + - name: Deployment items: - name: Deployment overview href: rooms/rooms-deploy.md - - name: Step 1 - Select your devices (to be written) - href: rooms/select-devices.md + - name: Step 1 - Plan your rooms + href: rooms/rooms-plan.md - name: Step 2 - Prepare your environment items: - name: Preparing your network href: rooms/rooms-prep.md - name: QoS on Teams devices href: devices/qos-on-teams-devices.md - - name: Configure authentication - href: rooms/rooms-authentication.md - name: Intune Enrollment for Windows items: - name: AutoPilot and Autologin @@ -1514,26 +1508,24 @@ items: items: - name: Teams Rooms operations href: rooms/rooms-operations.md - - name: Teams Rooms for Window - Recovery + - name: Reset Teams Rooms on Windows href: rooms/recovery-tool.md - - name: Media creation for Teams Rooms on Windows + - name: OEM Image creation for Teams Rooms on Windows href: rooms/console.md - - name: Update a Teams Room for Windows + - name: Manually update Teams Rooms on Windows href: rooms/manual-update.md - name: Teams Admin Center items: - name: Overview href: rooms/rooms-manage.md - - name: Manage your devices in Teams + - name: Manage your devices href: devices/device-management.md - name: Manage Teams device tags href: devices/manage-device-tags.md - name: Update your devices remotely href: devices/remote-update.md - - name: Use administrative units to manage devices + - name: RBAC using administrative units href: administrative-unit.md - - name: Analytics, reports, & insights - items: - name: Teams device health href: teams-device-health.md - name: Teams device health monitoring @@ -1648,7 +1640,7 @@ items: href: rooms/bookable-desks.md - name: Add peripherals to inventory href: rooms/get-peripheral-information.md - - name: SIP gateways + - name: SIP Gateway items: - name: Plan for SIP Gateway href: sip-gateway-plan.md From 095e91abcc68dc04cd0dd95d19add066df913a4f Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 7 Oct 2024 11:57:15 -0500 Subject: [PATCH 12/87] Update toc.yml Moved configuration --- Teams/toc.yml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index f31e16aa23..cb9e059f89 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1535,6 +1535,14 @@ items: href: rooms/console.md - name: Manually update Teams Rooms on Windows href: rooms/manual-update.md + - name: Device configuration + items: + - name: Remotely configure layout, scale, and resolution + href: rooms/manage-front-room-scale-res.md + - name: Manage settings with an XML file + href: rooms/xml-config-file.md + - name: Remotely configure front row layout + href: rooms/manage-front-row.md - name: Teams Admin Center items: - name: Overview @@ -1601,14 +1609,6 @@ items: href: rooms/multi-tenant-management-customer.md - name: Data and privacy information href: rooms/data-and-privacy-info.md - - name: Configuration - items: - - name: Remotely configure layout, scale, and resolution - href: rooms/manage-front-room-scale-res.md - - name: Manage settings with an XML file - href: rooms/xml-config-file.md - - name: Remotely configure front row layout - href: rooms/manage-front-row.md - name: Teams phones items: - name: Overview & planning From 43a331e94ba8dd09c4d67d9cff5e182c176bed85 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 7 Oct 2024 12:06:10 -0500 Subject: [PATCH 13/87] Update toc.yml Fixing PMP section --- Teams/toc.yml | 52 +++++++++++++++++++++++++-------------------------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index cb9e059f89..3acadc99ef 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1583,32 +1583,32 @@ items: href: rooms/settings-management.md - name: Remote access a Teams Room console href: rooms/remotely-access-teams-rooms.md - - name: Analytics, reports, and insights - items: - - name: Monitoring and maintaining Teams Rooms - href: rooms/managed-meeting-rooms-portal.md - - name: Audit logs for activities - href: rooms/multi-tenant-auditing.md - - name: Alerting - items: - - name: Signal settings - href: rooms/signal-settings.md - - name: Configure ServiceNow - href: rooms/microsoft-teams-rooms-configure-servicenow.md - - name: Viewing events - href: rooms/view-events.md - - name: Record an issue - href: rooms/customer-reported-incidents.md - - name: Managed updates - href: rooms/update-management.md - - name: Role-based access control - href: rooms/rooms-pro-rbac.md - - name: Multi-tenant management for partners - href: rooms/multi-tenant-management-partner.md - - name: Multi-tenant management for customers - href: rooms/multi-tenant-management-customer.md - - name: Data and privacy information - href: rooms/data-and-privacy-info.md + - name: Managed updates + href: rooms/update-management.md + - name: Role-based access control + href: rooms/rooms-pro-rbac.md + - name: Multi-tenant management for partners + href: rooms/multi-tenant-management-partner.md + - name: Multi-tenant management for customers + href: rooms/multi-tenant-management-customer.md + - name: Alerting + items: + - name: Signal settings + href: rooms/signal-settings.md + - name: Configure ServiceNow + href: rooms/microsoft-teams-rooms-configure-servicenow.md + - name: Viewing events + href: rooms/view-events.md + - name: Record an issue + href: rooms/customer-reported-incidents.md + - name: Analytics, reports, and insights + items: + - name: Monitoring and maintaining Teams Rooms + href: rooms/managed-meeting-rooms-portal.md + - name: Audit logs for activities + href: rooms/multi-tenant-auditing.md + - name: Data and privacy information + href: rooms/data-and-privacy-info.md - name: Teams phones items: - name: Overview & planning From 0124a6401252379bef285b505f68691885588d5f Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 7 Oct 2024 12:11:25 -0500 Subject: [PATCH 14/87] Update toc.yml fixed formatting error --- Teams/toc.yml | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 3acadc99ef..ff81043853 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1307,10 +1307,6 @@ items: - name: Teams device store href: devices/device-store.md - name: Teams device certification - items: - - name: Teams device store - href: devices/device-store.md - - name: Teams device certification items: - name: Certification overview href: devices/certification-overview.md @@ -1592,7 +1588,7 @@ items: - name: Multi-tenant management for customers href: rooms/multi-tenant-management-customer.md - name: Alerting - items: + items: - name: Signal settings href: rooms/signal-settings.md - name: Configure ServiceNow From 1ee69215e15b7ad616c28eb6c385d11c6aabb405 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 7 Oct 2024 12:20:56 -0500 Subject: [PATCH 15/87] Update toc.yml --- Teams/toc.yml | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index ff81043853..d5214733e8 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1344,25 +1344,6 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md - - name: Microsoft Teams Rooms - items: - - name: Overview - href: rooms/index.md - - name: Plan - items: - - name: Teams Rooms on Windows certified devices - href: rooms/certified-hardware.md - - name: Teams Rooms on Android certified devices - href: devices/certified-hardware-android.md - - name: Teams panels certified devices - href: devices/teams-panels-certified-hardware.md - - name: Teams phones certified devices - href: devices/teams-phones-certified-hardware.md - - name: Teams displays certified devices - href: devices/teams-displays-certified-hardware.md - - name: Personal peripherals - href: devices/usb-devices.md - - name: Teams Rooms & panels items: - name: Overview & planning From 90783980e8d40155f770d089a6287a3cdeb1ff5f Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 7 Oct 2024 12:31:00 -0500 Subject: [PATCH 16/87] Update toc.yml Removed what's new in Teams Devices, that's linked elsewhere in ToC --- Teams/toc.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index d5214733e8..f7fca85ecd 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1302,8 +1302,6 @@ items: - name: Teams Rooms and devices items: - - name: What's new in Teams devices - href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2 - name: Teams device store href: devices/device-store.md - name: Teams device certification From 955dfb24be2b2b8ff6a9972b2e7bf461e20ebbc4 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Mon, 7 Oct 2024 12:41:23 -0500 Subject: [PATCH 17/87] Update toc.yml --- Teams/toc.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index f7fca85ecd..209b85fdf7 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1500,7 +1500,7 @@ items: href: rooms/android-app-firmware.md - name: Management apps href: devices/certified-device-apps.md - - name: Operations + - name: Operations & Configuration items: - name: Teams Rooms operations href: rooms/rooms-operations.md @@ -1510,12 +1510,10 @@ items: href: rooms/console.md - name: Manually update Teams Rooms on Windows href: rooms/manual-update.md - - name: Device configuration - items: - - name: Remotely configure layout, scale, and resolution - href: rooms/manage-front-room-scale-res.md - name: Manage settings with an XML file href: rooms/xml-config-file.md + - name: Remotely configure layout, scale, and resolution + href: rooms/manage-front-room-scale-res.md - name: Remotely configure front row layout href: rooms/manage-front-row.md - name: Teams Admin Center @@ -1536,7 +1534,7 @@ items: href: alerts/device-health-status.md - name: Health and usage reports href: rooms/health-and-usage-reports.md - - name: Microsoft Teams Rooms Pro Management + - name: Teams Rooms Pro Management items: - name: Getting started items: From f341fe09c7c3ef26b5a2ba6a2df2c950eed9d792 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Tue, 8 Oct 2024 14:38:19 -0700 Subject: [PATCH 18/87] Working on Teams Phones section --- .openpublishing.redirection.json | 11 +++++++++++ Teams/{devices => phones}/phones-for-teams.md | 0 .../plan-device-deployment.md | 0 Teams/toc.yml | 16 +++++----------- 4 files changed, 16 insertions(+), 11 deletions(-) rename Teams/{devices => phones}/phones-for-teams.md (100%) rename Teams/{devices => phones}/plan-device-deployment.md (100%) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index a2cd5bf2be..65ddb5dd1f 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5324,6 +5324,17 @@ "source_path": "Skype/SfbPartnerCertification/lync-cert/pcs-optimized-for-lync.md", "redirect_url": "/microsoftteams/devices/certification-overview", "redirect_document_id": false + }, + { + "source_path": "Teams/devices/phones-for-teams.md", + "redirect_url": "/microsoftteams/phones/phones-for-teams", + "redirect_document_id": false + }, + { + "source_path": "Teams/devices/plan-device-deployment.md", + "redirect_url": "/microsoftteams/phones/plan-device-deployment", + "redirect_document_id": false + } } ] } diff --git a/Teams/devices/phones-for-teams.md b/Teams/phones/phones-for-teams.md similarity index 100% rename from Teams/devices/phones-for-teams.md rename to Teams/phones/phones-for-teams.md diff --git a/Teams/devices/plan-device-deployment.md b/Teams/phones/plan-device-deployment.md similarity index 100% rename from Teams/devices/plan-device-deployment.md rename to Teams/phones/plan-device-deployment.md diff --git a/Teams/toc.yml b/Teams/toc.yml index 209b85fdf7..d81628a2f2 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1299,7 +1299,7 @@ items: href: microsoft-teams-online-call-flows.md - name: Contact Center integrations href: teams-contact-center.md - + - name: Teams Rooms and devices items: - name: Teams device store @@ -1314,7 +1314,7 @@ items: href: devices/certification-partners.md - name: How to join the program href: devices/certification-join.md - - name: Teams device specifications + - name: Teams specifications href: devices/certification-specifications.md - name: IT admins and decision makers href: devices/certification-it-admins.md @@ -1325,7 +1325,7 @@ items: - name: Windows version support href: rooms/rooms-lifecycle-support.md - name: Android version support - href: devices/android-version-support.md + href: devices/android-version-support.md - name: Teams Certified Devices items: - name: Overview of certified devices @@ -1352,14 +1352,10 @@ items: href: rooms/index.md - name: Teams Rooms planning href: rooms/rooms-plan.md - - name: Copilot for Teams Rooms - href: copilot-admin.md - name: Features items: - name: Teams Room Home Screen and admin controls href: rooms/mtr-home-refresh.md - - name: Teams In Meeting experiences (to be written) - href: rooms/meeting experiences.md - name: Join a meeting using Proximity Join href: rooms/proximity-join.md - name: Join meetings with QR codes @@ -1474,7 +1470,7 @@ items: items: - name: Teams Rooms on Windows items: - - name: Use AutoPilot + AutoLogin for Teams Rooms on Windows + - name: Use AutoPilot and AutoLogin for Teams Rooms on Windows href: rooms/autopilot-autologin.md - name: Create a one-time password href: rooms/create-otp.md @@ -1495,9 +1491,7 @@ items: - name: Teams Rooms on Windows href: rooms/rooms-lifecycle-support.md - name: Teams Rooms on Android - href: rooms/android-app-firmware.md - - name: Teams panels - href: rooms/android-app-firmware.md + href: devices/certified-hardware-android.md - name: Management apps href: devices/certified-device-apps.md - name: Operations & Configuration From 659dc0030952c2d13e5f01e0253d85b443191501 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Tue, 15 Oct 2024 17:20:47 +0530 Subject: [PATCH 19/87] as per 9446860 --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 13 +++++++ .../capacity-planning.md | 10 +++--- .../categories-chat-rooms-and-user-roles.md | 20 +++++------ .../hardware-and-software-requirements.md | 36 +++++++++---------- ...high-availability-and-disaster-recovery.md | 14 ++++---- .../persistent-chat-server.md | 18 +++++----- .../persistent-chat-server/topology.md | 14 ++++---- 7 files changed, 69 insertions(+), 56 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 233d7334e7..309ac1eb61 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -102,6 +102,19 @@ href: ../../SfbServer/plan-your-deployment/instant-messaging-and-presence.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Video Interop Server href: ../../SfbServer/plan-your-deployment/video-interop-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Server + href: ../plan-your-deployment/persistent-chat-server/persistent-chat-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: Hardware and software requirements + href: ../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Topology + href: ../plan-your-deployment/persistent-chat-server/topology.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: High availability and disaster recovery + href: ../plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Capacity planning + href: ../plan-your-deployment/persistent-chat-server/capacity-planning.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Categories, chat rooms, and user roles + href: ../plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Voice Solutions href: ../../SfbServer/plan-your-deployment/enterprise-voice-solution/enterprise-voice-solution.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md index ffc692125f..90114b04d1 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md @@ -1,5 +1,5 @@ --- -title: "Capacity planning for Persistent Chat Server in Skype for Business Server 2015" +title: "Capacity planning for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 7a850cd5-c789-4795-a8ff-083be21ae784 -description: "Summary: Read this topic to learn about capacity planning for Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Read this topic to learn about capacity planning for Persistent Chat Server in Skype for Business Server." --- -# Capacity planning for Persistent Chat Server in Skype for Business Server 2015 +# Capacity planning for Persistent Chat Server in Skype for Business Server -**Summary:** Read this topic to learn about capacity planning for Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Read this topic to learn about capacity planning for Persistent Chat Server in Skype for Business Server. Persistent Chat Server can perform multi-user, real-time chat that can persist for future retrieval and search. Unlike group instant messaging (IM) that is saved in a user's mailbox if conversation history is configured, a Persistent Chat Server session stays open longer, and the content is saved on a server, along with the messages, files, URLs, and other data that are part of an ongoing conversation. @@ -26,7 +26,7 @@ Capacity planning is an important part of preparing to deploy Persistent Chat Se Before reading this section, you should be familiar with Persistent Chat topologies. For more information, see [Plan Persistent Chat Server topology](topology.md). > [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. +> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Persistent Chat Server capacity planning diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md index 602ff7a270..c21885f67f 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md @@ -1,5 +1,5 @@ --- -title: "Persistent chat categories, chat rooms, and user roles in Skype for Business Server 2015" +title: "Persistent chat categories, chat rooms, and user roles in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 343a0563-9ca5-4ad0-b4f3-a72f1d7f1a81 -description: "Summary: Read this topic to learn about categories, chat rooms, and user and administrator roles for Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Read this topic to learn about categories, chat rooms, and user and administrator roles for Persistent Chat Server in Skype for Business Server." --- -# Persistent chat categories, chat rooms, and user roles in Skype for Business Server 2015 +# Persistent chat categories, chat rooms, and user roles in Skype for Business Server -**Summary:** Read this topic to learn about categories, chat rooms, and user and administrator roles for Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Read this topic to learn about categories, chat rooms, and user and administrator roles for Persistent Chat Server in Skype for Business Server. You can control access to chat rooms by creating chat room categories, then specifying access to categories and chat rooms within categories. You can also specify various administrator roles. This topic describes: @@ -28,7 +28,7 @@ You can control access to chat rooms by creating chat room categories, then spec - Administrator roles > [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. +> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Categories for organizing chat rooms @@ -63,11 +63,11 @@ In addition to Allowed and Denied Members for categories, you can also control a The following are administrator roles for Persistent Chat Server: -- **Persistent Chat Administrator**: The Persistent Chat Administrator role can manage chat rooms (modify all properties including membership, managers, categories, mark rooms as disabled), as well as create and manage chat room categories that define who can create and access chat rooms. Administrators can also mark chat rooms as disabled and clean up chat rooms that are no longer active. Administrators are not subject to the Creators or Allowed Members restrictions. Administrators can create any kind of chat room and add themselves as a member to any chat room. Administrators can also modify and manage Persistent Chat configuration (pool properties, global settings, and compliance configuration) and can also plan and implement migration from an older Group Chat Server deployment to Skype for Business Server 2015 Persistent Chat Server. +- **Persistent Chat Administrator**: The Persistent Chat Administrator role can manage chat rooms (modify all properties including membership, managers, categories, mark rooms as disabled), as well as create and manage chat room categories that define who can create and access chat rooms. Administrators can also mark chat rooms as disabled and clean up chat rooms that are no longer active. Administrators are not subject to the Creators or Allowed Members restrictions. Administrators can create any kind of chat room and add themselves as a member to any chat room. Administrators can also modify and manage Persistent Chat configuration (pool properties, global settings, and compliance configuration) and can also plan and implement migration from an older Group Chat Server deployment to Skype for Business Server Persistent Chat Server. Persistent Chat Administrators are able to administer Persistent Chat Server by using Windows PowerShell cmdlets remotely (that is, from a computer other than the Persistent Chat Server). Persistent Chat Server checks that the Persistent Chat Administrator is a member of the RTC Local administrator local group on the Persistent Chat Server Front End Server. -- **Skype for Business Server 2015 Administrator**: Overall enterprise administrator for Skype for Business Server 2015 responsible for deployment. +- **Skype for Business Server Administrator**: Overall enterprise administrator for Skype for Business Server responsible for deployment. - **Operations Manager**: User responsible for managing day-to-day operations. @@ -77,10 +77,10 @@ The following are administrator roles for Persistent Chat Server: For more information about configuring and managing chat rooms and user roles, see the following topics: -- [Create a Persistent Chat administrator in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md) +- [Create a Persistent Chat administrator in Skype for Business Server](../../deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md) -- [Manage categories in Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/categories.md) +- [Manage categories in Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/categories.md) -- [Manage chat rooms in Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/chat-rooms.md) +- [Manage chat rooms in Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/chat-rooms.md) diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md index f1ab238245..2a0489da48 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md @@ -1,5 +1,5 @@ --- -title: "Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015" +title: "Hardware and software requirements for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,53 +12,53 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 692b7d99-1bc9-4c99-a050-2bc2be8688b2 -description: "Summary: Read this topic to learn about hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Read this topic to learn about hardware and software requirements for Persistent Chat Server in Skype for Business Server." --- -# Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015 +# Hardware and software requirements for Persistent Chat Server in Skype for Business Server -**Summary:** Read this topic to learn about hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Read this topic to learn about hardware and software requirements for Persistent Chat Server in Skype for Business Server. -Persistent Chat Server can be installed with Skype for Business Server 2015 Enterprise Edition or Standard Edition. Requirements depend on which edition of Skype for Business Server 2015 you have installed, and the performance requirements of your business. Enterprise Edition can support up to 80,000 concurrent users; Standard Edition can support up to 20,000 concurrent users. Persistent Chat consists of a front-end component as well as a back-end SQL database component. +Persistent Chat Server can be installed with Skype for Business Server Enterprise Edition or Standard Edition. Requirements depend on which edition of Skype for Business Server you have installed, and the performance requirements of your business. Enterprise Edition can support up to 80,000 concurrent users; Standard Edition can support up to 20,000 concurrent users. Persistent Chat consists of a front-end component as well as a back-end SQL database component. Before you deploy Persistent Chat Server, you must ensure that the following hardware and software requirements are met: -- Hardware that meets minimum requirements to support Skype for Business Server 2015, Persistent Chat Server, database servers, and file servers. For more information, see [Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md). +- Hardware that meets minimum requirements to support Skype for Business Server, Persistent Chat Server, database servers, and file servers. For more information, see [Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md). - Supported operating system and database software. - For details about supported operating systems and database software, and Windows update requirements, see [Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md). + For details about supported operating systems and database software, and Windows update requirements, see [Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md). -- Skype for Business Server 2015 Front End Server. The Front End Server is the foundation for Session Initiation Protocol (SIP) routing, which makes communication between computers running Persistent Chat Server and the Persistent Chat functionality possible. +- Skype for Business Server Front End Server. The Front End Server is the foundation for Session Initiation Protocol (SIP) routing, which makes communication between computers running Persistent Chat Server and the Persistent Chat functionality possible. - Message Queuing software. Used by the Persistent Chat Server and Persistent Chat Compliance service, if deployed. The following sections describe the specific requirements for Persistent Chat Server and the database that stores the Persistent Chat data. > [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. +> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Front End Server requirements -Front End Server requirements depend on whether you are deploying Persistent Chat Server with Skype for Business Server 2015 Enterprise Edition or Standard Edition. +Front End Server requirements depend on whether you are deploying Persistent Chat Server with Skype for Business Server Enterprise Edition or Standard Edition. -- If you are deploying Persistent Chat Server with Skype for Business Server 2015 Enterprise Edition, you can deploy the Persistent Chat Server Front End Server on one or more standalone computers in the Enterprise Edition pool. You cannot collocate the Persistent Chat Front End Servers on the Skype for Business Server 2015 Front End Server. +- If you are deploying Persistent Chat Server with Skype for Business Server Enterprise Edition, you can deploy the Persistent Chat Server Front End Server on one or more standalone computers in the Enterprise Edition pool. You cannot collocate the Persistent Chat Front End Servers on the Skype for Business Server Front End Server. A single Persistent Chat Server Front End Server can support 20,000 active users. You can have a Persistent Chat Server pool with up to 4 active front ends thereby supporting a total of 80,000 concurrent users. -- If you are deploying Persistent Chat Server with Skype for Business Server 2015 Standard Edition, you can collocate Persistent Chat with the Front End Server. This single server deployment can support up to 20,000 users. +- If you are deploying Persistent Chat Server with Skype for Business Server Standard Edition, you can collocate Persistent Chat with the Front End Server. This single server deployment can support up to 20,000 users. ## Persistent Chat Server database requirements Persistent Chat Server requires SQL Server database software to store chat room history and content, configuration data, user provisioning data, and other relevant metadata. Optionally, it uses the Persistent Chat Compliance database to store compliance data. Persistent Chat databases can be collocated on the same SQL Server, or even the same SQL instance, as the back-end databases. -- If you are installing Persistent Chat Server with Skype for Business Server 2015 Enterprise Edition, to ensure optimum performance, it is recommended that you install the Persistent Chat file store. +- If you are installing Persistent Chat Server with Skype for Business Server Enterprise Edition, to ensure optimum performance, it is recommended that you install the Persistent Chat file store. -- If you are installing Persistent Chat Server with Skype for Business Server 2015 Standard edition, you can deploy the Persistent Chat Store Back End Server on the local SQL Server Express instance. +- If you are installing Persistent Chat Server with Skype for Business Server Standard edition, you can deploy the Persistent Chat Store Back End Server on the local SQL Server Express instance. - The Persistent Chat database (mgc) and the compliance database (mgccomp) can be located in the same instance of SQL Server or on different SQL Servers. -To prepare a database server platform, be sure that each computer meets the hardware requirements, and then install the prerequisite software. The server platform for the Persistent Chat database servers requires the same hardware as the Skype for Business Server 2015 back-end database server. For details, see [Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md). +To prepare a database server platform, be sure that each computer meets the hardware requirements, and then install the prerequisite software. The server platform for the Persistent Chat database servers requires the same hardware as the Skype for Business Server back-end database server. For details, see [Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md). On the database server, be sure that one of the following software applications is installed: @@ -72,12 +72,12 @@ On the database server, be sure that one of the following software applications ## Persistent Chat Server certificate requirements -For details about acquiring certificates, creating the SQL Server database, and creating file stores, see [Deploy Skype for Business Server 2015](../../deploy/deploy.md). +For details about acquiring certificates, creating the SQL Server database, and creating file stores, see [Deploy Skype for Business Server](../../deploy/deploy.md). ## For more information For more information about hardware and software requirements, see the following topics: -- [Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) +- [Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) -- [Environmental requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/environmental-requirements.md) +- [Environmental requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/environmental-requirements.md) diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md index 480b4bc1ce..66fd17d228 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md @@ -1,5 +1,5 @@ --- -title: "Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015" +title: "Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: d9aa622a-95a3-4d8e-8d49-cbfe183f25bf -description: "Summary: Read this topic to learn how to plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Read this topic to learn how to plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server." --- -# Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015 +# Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server -**Summary:** Read this topic to learn how to plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Read this topic to learn how to plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server. High availability and disaster recovery for Persistent Chat Server require additional resources beyond what is typically needed for full operation. @@ -25,7 +25,7 @@ High availability and disaster recovery for Persistent Chat Server require addit > Using SQL AlwaysOn Availability Groups is not supported with Persistent Chat Server databases. > [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. +> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Resource requirements @@ -45,11 +45,11 @@ Before configuring Persistent Chat Server for high availability and disaster rec ## Disaster recovery and high availability solutions -Skype for Business Server supports multiple modes of high availability for your Back End Servers, including database mirroring. For more information, see [Plan for high availability and disaster recovery in Skype for Business Server 2015](../../plan-your-deployment/high-availability-and-disaster-recovery/high-availability-and-disaster-recovery.md). +Skype for Business Server supports multiple modes of high availability for your Back End Servers, including database mirroring. For more information, see [Plan for high availability and disaster recovery in Skype for Business Server](../../plan-your-deployment/high-availability-and-disaster-recovery/high-availability-and-disaster-recovery.md). The disaster recovery solution for Persistent Chat Server described in this topic is built on a stretched Persistent Chat Server pool. There is no requirement for a stretched virtual local area network (VLAN). By stretching a Persistent Chat Server pool, you configure one pool in the topology logically, but you physically place the servers in the pool in two different data centers. You configure SQL Server mirroring for the database in the same way, and deploy the database and the mirror in the same data center. You need to configure a backup database in the secondary data center (with an optional mirror to provide high availability during disaster recovery). This is the backup database used for failover during disaster recovery. -For details about how to configure high availability and disaster recovery for Persistent Chat Server, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md). +For details about how to configure high availability and disaster recovery for Persistent Chat Server, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md). The following figures show how the Persistent Chat Server pool can be configured in two different stretched pool topologies: diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md index 432cb1f5ce..042a414361 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md @@ -1,5 +1,5 @@ --- -title: "Plan for Persistent Chat Server in Skype for Business Server 2015" +title: "Plan for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 9e652487-a123-40c0-ae61-47fb8ecc4a20 -description: "Summary: Read this topic to learn how to plan for Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Read this topic to learn how to plan for Persistent Chat Server in Skype for Business Server." --- -# Plan for Persistent Chat Server in Skype for Business Server 2015 +# Plan for Persistent Chat Server in Skype for Business Server -**Summary:** Read this topic to learn how to plan for Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Read this topic to learn how to plan for Persistent Chat Server in Skype for Business Server. Persistent Chat Server is an optional role that lets multiple users in your organization participate in chat room conversations that persist over time. Although users can communicate in real time during a chat session, the content of each session--including text, links, and files--is persistent, which means users can view and search all content of the session at any time. @@ -34,7 +34,7 @@ Persistent Chat Server can help improve communication within your organization b - Following compliance regulations by optionally deploying the Persistent Chat Compliance service > [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. +> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Persistent Chat Server high-level architecture @@ -42,11 +42,11 @@ The following diagram shows a high-level view of the Persistent Chat Server arch ![Persistent Chat Server High-Level Architecture.](../../media/0344f6e2-0c6d-4391-b4b3-ec31062b1576.png) -Persistent Chat consists of a front-end server role that provides the Persistent Chat services as well as a back-end SQL database component. Both front-end and back-end components are included in a dedicated Persistent Chat pool. Each computer that hosts Persistent Chat Server must have access to an existing Skype for Business Server 2015 topology. In this diagram, there is one Persistent Chat Server pool (A), which is dependent on Skype for Business Server Pool A for routing messages to it. +Persistent Chat consists of a front-end server role that provides the Persistent Chat services as well as a back-end SQL database component. Both front-end and back-end components are included in a dedicated Persistent Chat pool. Each computer that hosts Persistent Chat Server must have access to an existing Skype for Business Server topology. In this diagram, there is one Persistent Chat Server pool (A), which is dependent on Skype for Business Server Pool A for routing messages to it. You can deploy one or more Persistent Chat Server pools, each with up to four active Persistent Chat Servers supporting up to 80K concurrent users. -Skype for Business Server 2015 communicates with the Persistent Chat service using the Session Initiation Protocol (SIP) for registration and the Extensible Chat Communication Over SIP protocol (XCCOS) for chat. +Skype for Business Server communicates with the Persistent Chat service using the Session Initiation Protocol (SIP) for registration and the Extensible Chat Communication Over SIP protocol (XCCOS) for chat. ## Persistent Chat services @@ -109,8 +109,8 @@ If you decide to deploy Persistent Chat Server, you'll need to determine your or For more information about installing and configuring Persistent Chat Server, see the following topics: -- For details about how to deploy Persistent Chat Server, see [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md). +- For details about how to deploy Persistent Chat Server, see [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md). -- For details about how to configure settings on your Persistent Chat Server deployment, see [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). +- For details about how to configure settings on your Persistent Chat Server deployment, see [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/topology.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/topology.md index edf7df05c0..fe6cb20735 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/topology.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/topology.md @@ -12,17 +12,17 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 6a0a14a0-baad-44e9-b26e-4d192c0a0e70 -description: "Summary: Read this topic to learn about Persistent Chat Server components and topologies in Skype for Business Server 2015." +description: "Summary: Read this topic to learn about Persistent Chat Server components and topologies in Skype for Business Server." --- # Plan Persistent Chat Server topology -**Summary:** Read this topic to learn about Persistent Chat Server components and topologies in Skype for Business Server 2015. +**Summary:** Read this topic to learn about Persistent Chat Server components and topologies in Skype for Business Server. -Persistent Chat Server supports both single-server and multiple-server configurations. You can install Persistent Chat Server on either a Skype for Business Server 2015 Enterprise Edition or Standard Edition Server. +Persistent Chat Server supports both single-server and multiple-server configurations. You can install Persistent Chat Server on either a Skype for Business Server Enterprise Edition or Standard Edition Server. > [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. +> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Persistent Chat Server components @@ -41,7 +41,7 @@ Persistent Chat Server consists of the following components: - If compliance is enabled, one or more servers (more than one if mirroring is used) running the SQL Server back-end database for hosting the Persistent Chat Compliance database, where compliance events and chat content for the purpose of compliance are stored. -For details about hardware and software requirements for Persistent Chat Server, see [Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) and [Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](hardware-and-software-requirements.md). +For details about hardware and software requirements for Persistent Chat Server, see [Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) and [Hardware and software requirements for Persistent Chat Server in Skype for Business Server](hardware-and-software-requirements.md). ## Persistent Chat Server topologies @@ -57,9 +57,9 @@ You can deploy Persistent Chat Server in single-server or multiple-server pools, Although you can deploy Persistent Chat Server on a Standard Edition Server, be aware that performance and scale will be affected, and high availability is not an option. Therefore, it is recommended that you deploy Persistent Chat on a Standard Edition Server primarily for proof of concept and evaluation purposes. -Skype for Business Server 2015 supports a variety of collocation scenarios, providing you the flexibility to save hardware costs by running multiple components on one server (if you have a small organization), or to run individual components on different servers (if you have a larger organization that needs scalability and performance). You should consider scalability factors before deciding whether to collocate components. Collocation scenarios differ for Skype for Business Server 2015 Enterprise Edition and Standard Edition servers. +Skype for Business Server supports a variety of collocation scenarios, providing you the flexibility to save hardware costs by running multiple components on one server (if you have a small organization), or to run individual components on different servers (if you have a larger organization that needs scalability and performance). You should consider scalability factors before deciding whether to collocate components. Collocation scenarios differ for Skype for Business Server Enterprise Edition and Standard Edition servers. -The following sections describe the topologies in more detail, including collocation scenarios and options for the back-end database servers. For details about collocation of all server roles and databases, see [Topology Basics for Skype for Business Server 2015](../../plan-your-deployment/topology-basics/topology-basics.md). +The following sections describe the topologies in more detail, including collocation scenarios and options for the back-end database servers. For details about collocation of all server roles and databases, see [Topology Basics for Skype for Business Server](../../plan-your-deployment/topology-basics/topology-basics.md). ### Standard Edition Server with Persistent Chat Server collocated on the Front End Server From 5966c95a73c18633a17f9e823bb5ad3d20437ded Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Tue, 15 Oct 2024 17:32:48 +0530 Subject: [PATCH 20/87] fixed warnings --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 12 ++++++------ .../hardware-and-software-requirements.md | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 309ac1eb61..456f8fb7c2 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -103,18 +103,18 @@ - name: Video Interop Server href: ../../SfbServer/plan-your-deployment/video-interop-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Persistent Chat Server - href: ../plan-your-deployment/persistent-chat-server/persistent-chat-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: - name: Hardware and software requirements - href: ../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Topology - href: ../plan-your-deployment/persistent-chat-server/topology.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/plan-your-deployment/persistent-chat-server/topology.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: High availability and disaster recovery - href: ../plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Capacity planning - href: ../plan-your-deployment/persistent-chat-server/capacity-planning.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Categories, chat rooms, and user roles - href: ../plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Voice Solutions href: ../../SfbServer/plan-your-deployment/enterprise-voice-solution/enterprise-voice-solution.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md index 2a0489da48..4217fe63e5 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md @@ -64,9 +64,9 @@ On the database server, be sure that one of the following software applications - Microsoft SQL Server 2017 with the latest service pack. -- Microsoft SQL Server 2016 with Service Pack 1, and you must run with Skype for Business Server Cumulative Update 7 or later releases. We recommended running SQL Server 2016 with the latest service pack. For details about how to install Microsoft SQL Server 2016, see [Install SQL Server 2016](/sql/database-engine/install-windows/install-sql-server?view=sql-server-2016). +- Microsoft SQL Server 2016 with Service Pack 1, and you must run with Skype for Business Server Cumulative Update 7 or later releases. We recommended running SQL Server 2016 with the latest service pack. For details about how to install Microsoft SQL Server 2016, see [Install SQL Server 2016](/sql/database-engine/install-windows/install-sql-server). -- Microsoft SQL Server 2014, and you must run with Skype for Business Server Cumulative Update 6 or later releases. We recommended running SQL Server 2014 with the latest service pack. For details about how to install Microsoft SQL Server 2014, see [Install SQL Server 2014](/sql/database-engine/install-windows/install-sql-server?view=sql-server-2014). +- Microsoft SQL Server 2014, and you must run with Skype for Business Server Cumulative Update 6 or later releases. We recommended running SQL Server 2014 with the latest service pack. For details about how to install Microsoft SQL Server 2014, see [Install SQL Server 2014](/sql/database-engine/install-windows/install-sql-server). - Microsoft SQL Server 2012 (64-bit edition), and we recommended running with the latest service pack. For details about how to install Microsoft SQL Server 2012, see [Install SQL Server 2012](/previous-versions/sql/sql-server-2012/bb500395(v=sql.110)). From ff956230a98f73cdc52a45c61385f63090271ba6 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 10:28:46 -0700 Subject: [PATCH 21/87] Fixing Teams phones entries --- Teams/toc.yml | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 7f56e33445..dc10f800b8 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1439,6 +1439,8 @@ items: href: rooms/rooms-release-note.md - name: Teams Panels release notes href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels + - name: Teams device management Apps + href: devices/certified-device-apps.md - name: Known issues items: - name: Teams Rooms on Windows @@ -1551,8 +1553,6 @@ items: href: rooms/inventory.md - name: Standards and Rooms Planner href: rooms/standards-and-room-planner.md - - name: Settings management (to be written) - href: rooms/settings-management.md - name: Remote access a Teams Room console href: rooms/remotely-access-teams-rooms.md - name: Managed updates @@ -1605,15 +1605,15 @@ items: href: devices/phones-panels-deploy.md - name: AOSP device management href: rooms/android-migration-guide.md - - name: Authentication best practices for Teams phones - href: devices/authentication-best-practices-for-android-devices.md + - name: Authentication best practices for Teams phones + href: devices/authentication-best-practices-for-android-devices.md - name: Step 3 - Set up and configure items: - name: Set up common area phones href: set-up-common-area-phones.md - name: Set up a common area mobile phones href: devices/common-area-mobile-phones.md - - name: Step 4 - Teams phones device set up + - name: Step 4 - Teams phones set up items: - name: Remote provisioning href: devices/remote-provision-remote-login.md @@ -1621,8 +1621,6 @@ items: href: devices/remote-sign-in-and-sign-out.md - name: Manage items: - - name: Manage Teams phones - href: devices/manage-teams-phones.md - name: Update management href: devices/remote-update.md - name: Bring your own device (BYOD) spaces From aff10a7e19c3032e449aacf6a521ba42f0ab15be Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 10:30:13 -0700 Subject: [PATCH 22/87] Update toc.yml --- Teams/toc.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index dc10f800b8..02ebad3091 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1387,8 +1387,6 @@ items: href: rooms/voice-recognition.md - name: IntelliFrame items: - - name: IntelliFrame overview (to be written) - href: devices/overview.md - name: Multi-Stream IntelliFrame href: devices/smartvision-admin.md - name: Cloud IntelliFrame From 333b7e6aa2ed932f2ceaccf0ddb217e941f24a4f Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 10:56:12 -0700 Subject: [PATCH 23/87] Update toc.yml --- Teams/toc.yml | 49 ++++++++++++++++++++++--------------------------- 1 file changed, 22 insertions(+), 27 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 02ebad3091..00a637aeb8 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1326,7 +1326,7 @@ items: href: rooms/rooms-lifecycle-support.md - name: Android version support href: devices/android-version-support.md - - name: Teams Certified Devices + - name: Teams certified devices items: - name: Overview of certified devices href: devices/certified-devices-overview.md @@ -1342,20 +1342,15 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md - - name: Microsoft Teams Rooms + - name: Teams Rooms and panels items: - - name: Overview - href: rooms/index.md - - name: Plan - - name: Teams Rooms & panels - items: - - name: Overview & planning + - name: Overview and planning items: - name: Teams Rooms items: - - name: Overview + - name: Overview of Teams Rooms href: rooms/index.md - - name: Teams Rooms planning + - name: Planning for Teams Rooms href: rooms/rooms-plan.md - name: Features items: @@ -1365,7 +1360,7 @@ items: href: rooms/proximity-join.md - name: Join meetings with QR codes href: rooms/teams-rooms-qr-codes.md - - name: SIP and H.323 Calling + - name: SIP and H.323 calling with Teams Rooms href: rooms/meetings-with-SIP-H323-devices.md - name: Join third-party meetings href: rooms/third-party-join.md @@ -1393,9 +1388,9 @@ items: href: devices/cloud-intelliframe.md - name: Teams panels items: - - name: Teams panels overview + - name: Overview of Teams panels href: devices/overview-teams-panels.md - - name: Plan + - name: Planning for Teams panels href: devices/teams-panels.md - name: Features items: @@ -1435,9 +1430,9 @@ items: items: - name: Teams Rooms release notes href: rooms/rooms-release-note.md - - name: Teams Panels release notes + - name: Teams panels release notes href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels - - name: Teams device management Apps + - name: Teams device management apps href: devices/certified-device-apps.md - name: Known issues items: @@ -1447,7 +1442,7 @@ items: href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-android - name: Deployment items: - - name: Deployment overview + - name: Overview href: rooms/rooms-deploy.md - name: Step 1 - Plan your rooms href: rooms/rooms-plan.md @@ -1471,7 +1466,7 @@ items: href: rooms/android-migration-guide.md - name: Step 3 - Create room accounts href: rooms/create-resource-account.md - - name: Step 4 - Device setup + - name: Step 4 - Setting up Teams Rooms items: - name: Teams Rooms on Windows items: @@ -1483,13 +1478,13 @@ items: href: rooms/first-time-setup.md - name: Manual Join to Entra ID and Intune href: /entra/identity/devices/device-join-plan.md - - name: Teams Rooms on Android and Teams Panels + - name: Teams Rooms on Android and Teams panels items: - name: Remote provisioning and sign-in href: devices/remote-provision-remote-login.md - name: Manage items: - - name: Management overview + - name: Overview href: rooms/rooms-manage.md - name: Keep up to date items: @@ -1499,7 +1494,7 @@ items: href: devices/certified-hardware-android.md - name: Management apps href: devices/certified-device-apps.md - - name: Operations & Configuration + - name: Operations and configuration items: - name: Teams Rooms operations href: rooms/rooms-operations.md @@ -1581,17 +1576,17 @@ items: href: rooms/data-and-privacy-info.md - name: Teams phones items: - - name: Overview & planning + - name: Overview and planning items: - - name: Teams phones overview + - name: Overview of Teams phones href: devices/phones-for-teams.md - - name: Plan a Teams phones deployment + - name: Planning for Teams phones href: devices/plan-device-deployment.md - name: What's new in Teams phones href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones - name: Deploy items: - - name: Step 1 - Deployment overview + - name: Step 1 - Overview href: devices/plan-device-deployment.md - name: Step 2 - Prepare your environment items: @@ -1611,7 +1606,7 @@ items: href: set-up-common-area-phones.md - name: Set up a common area mobile phones href: devices/common-area-mobile-phones.md - - name: Step 4 - Teams phones set up + - name: Step 4 - Setting up Teams phones items: - name: Remote provisioning href: devices/remote-provision-remote-login.md @@ -1625,7 +1620,7 @@ items: items: - name: Bring Your Own Device (BYOD) href: rooms/bring-your-own-device.md - - name: Bookable Desks + - name: Bookable desks href: rooms/bookable-desks.md - name: Add peripherals to inventory href: rooms/get-peripheral-information.md @@ -1641,7 +1636,7 @@ items: items: - name: Teams displays overview href: devices/teams-displays.md - - name: Hot desking Teams Displays + - name: Hot desking Teams displays href: devices/hot-desking-teams-displays.md - name: Manage apps in Teams From 8d069e44e1a261f2e2be6ff6bb26a6b8e2ee8781 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 11:09:35 -0700 Subject: [PATCH 24/87] adding troubleshooting --- Teams/toc.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index d95cfedc48..7766111a4c 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1426,9 +1426,11 @@ items: href: rooms/rooms-authentication.md - name: Authentication for Teams Android devices href: devices/authentication-best-practices-for-android-devices.md + - name: Conditional Access-related issues + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-android-devices-conditional-access-issues - name: Release notes items: - - name: Teams Rooms release notes + - name: Teams Rooms release notesf href: rooms/rooms-release-note.md - name: Teams panels release notes href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels @@ -1574,6 +1576,8 @@ items: href: rooms/multi-tenant-auditing.md - name: Data and privacy information href: rooms/data-and-privacy-info.md + - name: Troubleshooting Teams Rooms Pro portal + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/get-support-teams-rooms-pro-management - name: Teams phones items: - name: Overview and planning @@ -1616,6 +1620,10 @@ items: items: - name: Update management href: devices/remote-update.md + - name: Troubleshooting + items: + - name: Troubleshooting Teams phones + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android - name: Bring your own device (BYOD) spaces items: - name: Bring Your Own Device (BYOD) From eed3719c90451481e28f8abf9e194a39cf26ada1 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 11:13:25 -0700 Subject: [PATCH 25/87] Adding known issues --- Teams/toc.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Teams/toc.yml b/Teams/toc.yml index 7766111a4c..0c9eac2eb7 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1342,6 +1342,9 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md + items: + - name: Known issues + href: /microsoftteams/troubleshoot/meetings/known-issues-teams-certified-peripherals - name: Teams Rooms and panels items: - name: Overview and planning @@ -1640,6 +1643,8 @@ items: href: sip-gateway-configure.md - name: Dynamic filters href: sip-gateway-dynamic-filters.md + - name: Known issues + href: /microsoftteams/troubleshoot/phone-system/sip-gateway-issues - name: Reference items: - name: Teams displays overview From 92ed82040f04972b2a3ffd34c8d7eefa3e310b70 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 12:22:31 -0700 Subject: [PATCH 26/87] Shuffling files and creating new articles --- .openpublishing.redirection.json | 19 +- ...panels-deploy.md => mtra-panels-deploy.md} | 20 +- .../authentication-best-practices-phones.md | 109 +++++++++ .../common-area-mobile-phones.md | 0 Teams/phones/manage-teams-phones.md | 135 +++++++++++ Teams/phones/phones-deploy.md | 77 +++++++ Teams/phones/phones-for-teams.md | 2 +- Teams/phones/prepare-network-teams-phones.md | 214 ++++++++++++++++++ .../{ => phones}/set-up-common-area-phones.md | 0 Teams/toc.yml | 16 +- 10 files changed, 573 insertions(+), 19 deletions(-) rename Teams/devices/{phones-panels-deploy.md => mtra-panels-deploy.md} (79%) create mode 100644 Teams/phones/authentication-best-practices-phones.md rename Teams/{devices => phones}/common-area-mobile-phones.md (100%) create mode 100644 Teams/phones/manage-teams-phones.md create mode 100644 Teams/phones/phones-deploy.md create mode 100644 Teams/phones/prepare-network-teams-phones.md rename Teams/{ => phones}/set-up-common-area-phones.md (100%) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index ac5a8d9f7b..45817b2e8a 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5344,6 +5344,21 @@ "source_path": "Teams/rooms/android-app-firmware.md", "redirect_url": "/microsoftteams/devices/certified-hardware-android", "redirect_document_id": false - } - ] + }, + { + "source_path": "Teams/devices/phones-panels-deploy.md", + "redirect_url": "/microsoftteams/devices/mtra-panels-deploy", + "redirect_document_id": false + }, + { + "source_path": "Teams/set-up-common-area-phones.md", + "redirect_url": "/microsoftteams/phones/set-up-common-area-phones", + "redirect_document_id": false +}, +{ + "source_path": "Teams/devices/common-area-mobile-phones.md", + "redirect_url": "/microsoftteams/phones/common-area-mobile-phones", + "redirect_document_id": false } + ] +} \ No newline at end of file diff --git a/Teams/devices/phones-panels-deploy.md b/Teams/devices/mtra-panels-deploy.md similarity index 79% rename from Teams/devices/phones-panels-deploy.md rename to Teams/devices/mtra-panels-deploy.md index cad1ac9dce..9f98f71839 100644 --- a/Teams/devices/phones-panels-deploy.md +++ b/Teams/devices/mtra-panels-deploy.md @@ -1,10 +1,10 @@ --- -title: Deploy Teams Phones, Teams panels, and Microsoft Teams Rooms on Android using Intune +title: Deploy Teams Rooms on Android and Teams panels author: mstonysmith ms.author: tonysmit manager: pamgreen -ms.date: 04/25/2024 -ms.reviewer: prashibadkur +ms.date: 10/16/2024 +ms.reviewer: eviegrimshaw ms.topic: article ms.service: msteams ms.subservice: itpro-devices @@ -20,16 +20,18 @@ ms.collection: - Tier1 search.appverid: MET150 ms.localizationpriority: medium -description: This article provides an overview of and features supported by Microsoft Teams Android devices. +description: This article gives you an overview of how to deploy Teams panels, and Microsoft Teams Rooms on Android using Conditional Access and Intune. --- -# Deploy Teams phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android using Intune +# Deploy Teams panels and Microsoft Teams Rooms on Android using Intune -This article gives you an overview of how to deploy Teams phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android using Intune. +**MATT: verify that this works for just Teams panels and MTRA.** + +This article gives you an overview of how to deploy Teams panels, and Microsoft Teams Rooms on Android using Conditional Access and Intune. ## Conditional Access -Conditional Access is a Microsoft Entra feature that helps you to ensure devices accessing your Office 365 resources are properly managed and secure. If you apply Conditional Access policies to the Teams service, all devices including Teams Phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android need to be enrolled into Intune and their settings need to comply with your organizational policies. If the device isn't enrolled into Intune, or if its enrolled, but its settings don't comply with your policies, Conditional Access prevents a user from signing in or using the Teams app on the device. +Conditional Access is a Microsoft Entra feature that helps you to ensure devices accessing your Office 365 resources are properly managed and secure. If you apply Conditional Access policies to the Teams service, all devices including Teams phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android need to be enrolled into Intune and their settings need to comply with your organizational policies. If the device isn't enrolled into Intune, or if its enrolled, but its settings don't comply with your policies, Conditional Access prevents a user from signing in or using the Teams app on the device. Typically, compliance policies defined within Intune are assigned to groups of users. This means that if you assign an Android compliance policy to user@contoso.com, that policy applies equally to their Android smartphone and to any Android-based Teams device that user@contoso.com signs into. @@ -38,9 +40,11 @@ If you use Conditional Access, which requires Intune enrollment to be enforced, - **Intune license** The user signing into the Teams device must be licensed for Intune. As long as the Teams device is signed in to a user account that has a valid Intune license, the device is automatically enrolled in Microsoft Intune as part of the sign in process. - **Configure Intune** You must have a properly configured Intune tenant set up for Android Device Administrator enrollment. +Teams Android-based devices including Teams panels and Teams Rooms on Android are managed by Intune using Android Device Administrator (DA) management. + ## Configure Intune to enroll Teams Android-based devices -Teams Android-based devices are managed by Intune via Android Device Administrator (DA) management. Customers must enroll their devices using Android Device Administrator. Before devices can be enrolled into Intune, there are a few basic steps to perform. If you're already managing devices with Intune today, you probably have already done all these things. If not, here's what to do: +Customers must enroll their devices using Android Device Administrator. Before devices can be enrolled into Intune, there are a few basic steps to perform. If you're already managing devices with Intune today, you probably have already done all these things. If not, here's what to do: > [!NOTE] > - If tenant admins want common area phones to be enrolled into Intune, they need to add an Intune license to the account and follow the steps for Intune enrollment. diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md new file mode 100644 index 0000000000..128320b3bc --- /dev/null +++ b/Teams/phones/authentication-best-practices-phones.md @@ -0,0 +1,109 @@ +--- +title: Authentication best practices for Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: dimehta +ms.date: 10/16/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +search.appverid: MET150 +f1.keywords: + - NOCSH +ms.localizationpriority: Medium +description: Best practices for Teams phones. This features Conditional Access, password policy, multifactor authentication advice and more. +--- + +# Authentication best practices for Teams phones + +The goals of devices used with Teams is to make different device management strategies necessary. For example, a personal business tablet used by a single sales person has a different set of needs from an on-call phone shared by many customer service people. Also, there are different requirements for a Teams phone that isn't shared with other people and another Teams phone that is used as a common area phone. See, [Set up common area phones for Microsoft Teams](/microsoftteams/set-up-common-area-phones). + +Security administrators and operations teams must plan for the devices that can be used in the organization. They must implement *security* measures best suited to each purpose. This article's recommendations make some of those decisions easier. + +>[!NOTE] +>Conditional Access requires a Microsoft Entra ID P1 or P2 subscription. + +>[!NOTE] +>Policies for Android mobile devices may not apply to Teams Android devices. + +## Authentication recommendations are different for personal versus shared android devices + +Shared Teams devices such as Teams phones can't use the same requirements for enrollment and compliance that are used on personal devices. Applying personal device authentication requirements to shared devices cause sign in issues. + +1. **Devices are signed out due to password policies.** + + Accounts used on Teams phones have a password-expiration policy. The accounts used with shared devices don't have a specific user to update and restore them to a working state when their passwords expire. If your organization requires passwords to expire and reset occasionally, these accounts stop working on Teams devices until a Teams administrator resets the password and signs back in. + + **Challenge**: When it comes to accessing. Teams from a device, a person's account has a password-expiration policy. When the password is going to expire, they change it. But accounts used on *shared devices*(Resource accounts) may not be connected to a single person who can change a password as required. This means a password can expire and leave workers on the spot, not knowing how to resume their work. + + When your organization requires a password reset or enforces password expiration, be sure a Teams administrator is prepared to reset the password so these shared accounts can sign back in. + +2. **Devices fail to sign in due to conditional access policies.** + + **Challenge**: Shared devices can't comply with Microsoft Entra Conditional Access policies for user accounts or personal devices. If shared devices are grouped with user accounts or personal devices for a Conditional Access policy, the sign-in will *fail*. + + For example, if multifactor authentication is required for accessing Teams, user entry of a code is needed to complete that authentication. Shared devices don't generally have a single user that can configure and complete multifactor authentication. Also, if the account must reauthenticate every X days, a shared device can't resolve the challenge without a user's intervention. + +## Best practices for the deployment of shared Teams phones + +Microsoft recommends the following settings when deploying Teams phones in your organization. + +### **Use a Resource account and curtail its password expiration** + +Teams shared phones should use an [Exchange resource mailbox](/exchange/recipients-in-exchange-online/manage-resource-mailboxes). Creating these mailboxes generates an account automatically. You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. + +Starting with Teams devices CY21 [Update #1](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones) (Teams version 1449/1.0.94.2021022403 for Teams phones) and [CY2021 Update #2](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_Rooms_on_Android) (Teams version 1449/1.0.96.2021051904 for Microsoft Teams Rooms on Android), tenant administrators can sign into Teams devices remotely. Instead of sharing passwords with technicians to set up devices, Tenant administrators should use remote sign-in to issue verification codes. You can sign into these devices from the Teams admin center. + +For more information, see [Remote provisioning and sign in for Teams Android devices](/MicrosoftTeams/devices/remote-provision-remote-login). + +### **Review these Conditional Access policies** + +Microsoft Entra Conditional Access sets other requirements that devices must meet in order to sign in. For Teams phones, review the guidance that follows to determine if you have authored the policies that allow shared device users to do their work. + +> [!TIP] +> For an overview of Conditional Access, see [What is Conditional Access](/azure/active-directory/conditional-access/overview)? + +>[!TIP] +>Use either [named location](/azure/active-directory/conditional-access/location-condition) or [require compliant device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device) to secure shared devices. + +### You can use location-based access with named locations + +If shared Teams phones are provisioned in a well-defined location that can be identified with a range of IP addresses, you can configure Conditional Access using [named locations](/azure/active-directory/conditional-access/location-condition) for these devices. This conditional will allow these devices to access your corporate resources only when they are within your network. + +### When and when not to require compliant shared devices + +>[!NOTE] +>Device compliance requires an Intune license. + +If you're enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams devices can be configured for Conditional Access policies based on device compliance. For more information, see [Conditional Access: Require compliant or Microsoft Entra hybrid joined device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device). + +To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/intune/protect/device-compliance-get-started). + +>[!NOTE] +> Shared devices being used for *hot-desking* should be excluded from compliance policies. Compliance polices prevent the devices from enrolling into the hot desk user account. **Instead, use named locations to secure these devices**. +> To increase security, you can also [require multi-factor authentication](/azure/active-directory/authentication/tutorial-enable-azure-mfa) for *hot-desking users / user accounts* in addition to the named location policies. + +### Exclude shared devices from sign-in frequency conditions + +In Conditional Access, you can [configure sign-in frequency](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency) to require users to sign in again to access a resource after a specified time period. If sign-in frequency is enforced for room accounts, shared devices sign out until they're signed in again by an admin. Microsoft recommends excluding shared devices from any sign-in frequency policies. + +### Using Filters for devices + +[Filters for devices](/azure/active-directory/conditional-access/concept-condition-filters-for-devices) is a feature in Conditional Access that allows you to configure more granular policies for devices based on device properties available in Microsoft Entra ID. You can also use your own custom values by setting extension attributes 1-15 on the device object and then using those. + +Use filters for devices to identify your common-area devices and enable policies in two key scenarios: + +1. Excluding shared devices from policies applied for personal devices. For example, requiring device compliance *isn't enforced* for shared devices used for hot-desking, but *is enforced* for all other devices, based on model number. + +2. Enforcing special policies on shared devices that *shouldn't* be applied to personal devices. For example, requiring named locations as policy only for common-area devices based on an extension attribute you set for these devices (for example: “CommonAreaPhone”). + +>[!NOTE] +> Some attributes such as **model**, **manufacturer**, and **operatingSystemVersion** can only be set when devices are managed by Intune. If your devices are not managed by Intune, use extension attributes. diff --git a/Teams/devices/common-area-mobile-phones.md b/Teams/phones/common-area-mobile-phones.md similarity index 100% rename from Teams/devices/common-area-mobile-phones.md rename to Teams/phones/common-area-mobile-phones.md diff --git a/Teams/phones/manage-teams-phones.md b/Teams/phones/manage-teams-phones.md new file mode 100644 index 0000000000..db7f37b806 --- /dev/null +++ b/Teams/phones/manage-teams-phones.md @@ -0,0 +1,135 @@ +--- +title: Manage Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: srpall +ms.date: 10/16/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - M365-collaboration + - m365initiative-deployteams + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - CSH +ms.custom: + - ms.teamsadmincenter.managedevices.overview + - ms.teamsadmincenter.devicemanagement.overview +description: Manage devices used with Microsoft Teams in your organization. +ms.localizationpriority: medium +search.appverid: MET150 +--- + +# Manage Teams phones + +You can manage Teams phones used with Microsoft Teams in your organization from the Microsoft Teams admin center or in Teams Rooms Pro Management. You can view and manage the device inventory for your organization and do tasks such as update, restart, and monitor diagnostics for devices. You can also create and assign configuration profiles to a device or groups of devices. + +To manage your phones, such as change device configuration, restart devices, manage updates, or view device and peripheral health, you need to be assigned one of the following Microsoft 365 admin roles: + +- Teams Service admin +- Teams Device admin + +For more information about admin roles in Teams, see [Use Teams administrator roles to manage Teams](../using-admin-roles.md). + +For more information about Teams Rooms Pro management role based access control, see [Role-based access control in the Microsoft Teams Rooms Pro Management Portal](../rooms/rooms-pro-rbac.md) + +## What Teams phones can you manage? + +You can manage any device that's certified for, and enrolled in, Teams. A device is automatically enrolled the first time a user signs in to Teams on the device. For a list of certified devices that can be managed, see: + +- [Microsoft Teams Rooms](https://www.microsoft.com/microsoft-365/microsoft-teams/across-devices/devices/category?devicetype=20) +- [Conference phones](https://products.office.com/microsoft-teams/across-devices/devices/category?devicetype=73) +- [Desk phones](https://products.office.com/microsoft-teams/across-devices/devices/category?devicetype=34) +- [Teams displays](https://www.microsoft.com/microsoft-365/microsoft-teams/across-devices/devices/category?devicetype=34) +- [Teams panels](teams-panels.md) + +To manage Teams phones, in the left navigation of the [Microsoft Teams admin center](https://admin.teams.microsoft.com), go to **Teams Devices**, and then select the device type. Each type of device has its own respective section, which lets you manage them separately. + +## Manage Teams Rooms in Teams Rooms Pro Management + +To manage phones in Teams Rooms Pro Management, see [Microsoft Teams Rooms Pro Management Portal](../rooms/managed-meeting-rooms-portal.md) + +## Manage Teams Rooms on Windows devices in Teams Admin Center + +You can use the Teams admin center to view and remotely manage your Teams phones across your organization. The Teams admin center makes it easy to see, at a glance, which devices are healthy and which need attention, and lets you focus on specific devices to see detailed information about device health, meeting performance, call quality, and peripherals. + +Here are some things you can do to manage your Teams phones. Teams phones devices can be found in the [Microsoft Teams admin center](https://admin.teams.microsoft.com) under **Teams Devices** > **Phones**. + +For details about how to manage your Teams Rooms devices, see [Manage Microsoft Teams Rooms](../rooms/rooms-manage.md). + +| To do this... | Do this | +|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Change settings on one or more devices | Select one or more devices > **Edit settings**. If you select multiple devices, the values you change will replace the values on all the selected devices. | +| Restart devices | Select one or more devices > **Restart**. When you restart a device, you can choose whether to restart the device immediately or select **Schedule restart** to restart the device at a specific date and time. The date and time you select are local to the device being restarted. | +| View meeting activity | Select a device name to open device details > **Activity**. When you open the **Activity** tab, you can see all the meetings that the device has participated in. This summary view shows the meeting start time, the number of participants, its duration, and the overall call quality. | +| View meeting details | Select a device name to open device details > **Activity** > select a meeting. When you open a meeting's details, you can see all of the participants in the meeting, how long they were in the call, the Teams session types, and their individual call quality. If you want to see technical information about a participant's call, select the participant's call start time. | + +## Manage Teams phones + +In the Teams admin center, you can view and manage phones, Teams Rooms on Android, Teams displays, and Teams panels enrolled in Teams in your organization. Information that you'll see for each device includes device name, manufacturer, model, user, status, action, last seen, and history. You can customize the view to show the information that fits your needs. + +Phones, Teams Rooms on Android, Teams displays, and Teams panels are automatically enrolled in Microsoft Intune if you've signed up for it. After a device is enrolled, device compliance is confirmed and conditional access policies are applied to the device. + +Here are some examples of how you can manage phones, Teams Rooms on Android, Teams displays, and Teams panels in your organization. + +| To do this... | Do this | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Change device information | Select a device > **Edit**. You can edit details such as device name, asset tag, and add notes. | +| Manage software updates | Select a device > **Update**. You can view the list of software and firmware updates available for the device and choose the updates to install. For more information about updating devices, see [Update Teams devices remotely](remote-update.md) | +| Assign or change configuration policies | Select one or more devices > **Assign configuration**. | +| Add or remove device tags | Select one or more devices > **Manage tags**. For more information about device tags, see [Manage Teams device tags](manage-device-tags.md). | +| Restart devices | Select one or more devices > **Restart**. | +| Filter devices using device tags | Select the filter icon, select the **Tag** field, specify a device tag to filter on, and select **Apply**. For more information about filtering devices using device tags, see [Use filters to return devices with a specific tag](manage-device-tags.md#use-filters-to-return-devices-with-a-specific-tag). | +|Schedule device actions|Actions like **Restart** and **Software update** can be scheduled for the preferred date and time.| +| View device history and diagnostics | Under the **History** column, click the **View** link for a device to view its update history and diagnostic details. | +|View device action details|In the **History** tab on the device page, select the action status to view the details of the action.| +|Cancel device actions|From the **History** section, you can cancel any action that is in a Queued or Scheduled state (not in progress or completed) to prevent execution. This option is accessible from the **History** tab in the device page and the **History** column in the list page. You can select multiple actions to cancel at once. Paired actions will be canceled together if execution hasn't started.| +|Actions on multiple devices|You can select multiple devices from the list page and perform an action on them at once. This is applicable for **Restart**, **Software update**, **Assign configuration**, **Manage tags**, **Remove device**, and **Sign-out**.| + +This video shows how to search for Teams devices. + +> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fHGQ?autoplay=false] + +### View issues with Android-based Teams devices + +You can view issues with Android-based Teams devices in the health status column of the device list. + +In addition to the health status of the device, the following issues are also surfaced in the health status column: + +1. **Sign-in errors exist** - There was an issue signing-in to the device. Select the health status of the device to view the time the sign-in failure occurred, the account that attempted to sign into the device, the reason for the failure, and a history of previous sign-in failures. +2. **No connection** - The connection between Teams admin center and the device has been lost. Restart or update the device through Teams admin center to resolve this error. +3. **Multiple issues** - One or more errors exist. Select the health status of the device to view the list of issues. + +> [!NOTE] +> If you don't see any issues for a device you're having trouble with, make sure the device's firmware is on the latest version. + +### Use configuration profiles in Teams + +Use configuration profiles to manage settings and features for different Teams devices including Teams phones in your organization. You can create or upload configuration profiles to include settings and features you want to enable or disable, and then assign a profile to a device or set of devices. + +#### Create a configuration profile + +To create a configuration profile for a Teams device type: + +1. In the left navigation, go to **Teams Devices** > select the Teams device type > **Configuration profiles**. For example, select **Teams Devices** > **Teams panels** > **Configuration profiles** to create a new configuration profile for Teams panels. +2. Click **Add**. +3. Enter a name for the profile and optionally add a friendly description. +4. Specify the settings you want for the profile, and then click **Save**. + The newly created configuration profile is displayed in the list of profiles. + +#### Assign a configuration profile + +After creating a configuration profile for a Teams device type, assign it to one or more devices. + +1. In the left navigation, go to **Teams Devices** > select the Teams device type. For example, to assign a configuration profile to a Teams panels device, select **Teams Devices** > **Teams phones**. +2. Select one or more devices, and then click **Assign configuration**. +3. In the **Assign a configuration** pane, search for configuration profile to assign to the selected devices. +4. Click **Apply**. + For the devices to which you applied the configuration policy, the **Action** column displays **Config Update** and the **Configuration profile** column displays the configuration profile name. \ No newline at end of file diff --git a/Teams/phones/phones-deploy.md b/Teams/phones/phones-deploy.md new file mode 100644 index 0000000000..c29427fd66 --- /dev/null +++ b/Teams/phones/phones-deploy.md @@ -0,0 +1,77 @@ +--- +title: Deploy Teams phones using Conditional Access and Intune +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.date: 04/25/2024 +ms.reviewer: prashibadkur +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +f1.keywords: + - NOCSH +ms.collection: + - teams-rooms-devices + - M365-voice + - Teams_ITAdmin_Devices + - Tier1 +search.appverid: MET150 +ms.localizationpriority: medium +description: This article provides an overview of and features supported by Microsoft Teams phones. +--- + +# Deploy Teams phones using Conditional Access and Intune + +This article gives you an overview of how to deploy Teams phones using Conditional Access and Intune. + +## Conditional Access + +Conditional Access is a Microsoft Entra feature that helps you to ensure devices accessing your Office 365 resources are properly managed and secure. If you apply Conditional Access policies to the Teams service, all devices including Teams Phones, Teams panels, and Microsoft Teams Rooms on Android need to be enrolled into Intune and their settings need to comply with your organizational policies. If the device isn't enrolled into Intune, or if its enrolled, but its settings don't comply with your policies, Conditional Access prevents a user from signing in or using the Teams app on the device. + +Typically, compliance policies defined within Intune are assigned to groups of users. This means that if you assign an Android compliance policy to user@contoso.com, that policy applies equally to their Android smartphone and to any Android-based Teams device that user@contoso.com signs into. + +If you use Conditional Access, which requires Intune enrollment to be enforced, in your organization, there are a couple things you need to set up to allow for a successful Intune enrollment: + +- **Intune license** The user signing into the Teams phone must be licensed for Intune. As long as the Teams device is signed in to a user account that has a valid Intune license, the device is automatically enrolled in Microsoft Intune as part of the sign in process. +- **Configure Intune** You must have a properly configured Intune tenant set up for Android Device Administrator enrollment. + +Teams Android-based devices, including Teams phones are managed by Intune using Android Device Administrator (DA) management. + +## Configure Intune to enroll Teams Android-based devices + + Customers must enroll their devices using Android Device Administrator. Before devices can be enrolled into Intune, there are a few basic steps to perform. If you're already managing devices with Intune today, you probably have already done all these things. If not, here's what to do: + +> [!NOTE] +> - If tenant admins want common area phones to be enrolled into Intune, they need to add an Intune license to the account and follow the steps for Intune enrollment. +> - If the user account used to sign into a Teams device isn't licensed for Intune, Intune compliance policies and enrollment restrictions need to be disabled for the account. +> - If the user account used to sign into a Teams device is licensed for Intune, the Teams device will be automatically enrolled in Intune. + +1. Set Intune MDM (mobile device management) Authority. + + If you've never used Intune before, you need to set the MDM authority before you can enroll devices. For more information, see [Set the mobile device management authority](/mem/intune/fundamentals/mdm-authority-set). This is a one-time step that has to be done upon creating a new Intune tenant. +1. Enable Android device administrator enrollment. + + Android-based Teams devices are managed as device administrator devices with Intune. Device administrator enrollment is off by default for newly created tenants. See [Android device administrator enrollment](/mem/intune/enrollment/android-enroll-device-administrator). +1. Assign licenses to users. + + Users of Teams devices enrolling to Intune must be assigned a valid Intune license. For more information, see [Assign licenses to users so they can enroll devices in Intune](/mem/intune/fundamentals/licenses-assign). +1. Assign Device Administrator compliance policies. + + 1. Create an Android Device Administrator compliance policy. + + 1. Assign it to the Microsoft Entra group that contains the users that are signing into the Teams devices. See [Use compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). + +## See also + +[Phones for Teams](phones-for-teams.md) + +[Certified Teams phones](teams-phones-certified-hardware.md) + +[Teams displays](teams-displays.md) + +[Manage your devices in Teams](device-management.md) + +[Teams Marketplace](https://office.com/teamsdevices) diff --git a/Teams/phones/phones-for-teams.md b/Teams/phones/phones-for-teams.md index f292f0ebd9..c73b7a5bad 100644 --- a/Teams/phones/phones-for-teams.md +++ b/Teams/phones/phones-for-teams.md @@ -64,7 +64,7 @@ For more information about getting Teams, check out [How do I get access to Micr ## Deploy your phones using Intune -To learn more about how to deploy Teams displays using Intune, see [Deploy Teams phones and Teams panels](phones-panels-deploy.md). +To learn more about how to deploy Teams displays using Intune, see [Deploy Teams phones and Teams panels](../phones/phones-panels-). ## Manage your phones diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md new file mode 100644 index 0000000000..67488c24db --- /dev/null +++ b/Teams/phones/prepare-network-teams-phones.md @@ -0,0 +1,214 @@ +--- +title: Prepare your network for Team phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: prashibadkur +ms.date: 10/16/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +search.appverid: MET150 +description: Learn about how to prepare your network infrastructure for deploying Microsoft Teams phonesso that you can take advantage of all of the available features. +--- + +# Plan your network environment for Teams Phones + +**MATT: THIS ARTICLE NEEDS EDITED FOR Teams phones only** + +This section contains an overview of the steps required to prepare your network environment so that you can use all of the features of Microsoft Teams Rooms. This section also includes information on configuring local administive access to your Teams Rooms devices. + +## Confirm network configuration + +In order to function properly, Microsoft Teams Rooms devices must have access to a network that meets these requirements: + +- Review access to: Microsoft Teams, SharePoint/OneDrive, Pro Management Portal, Microsoft Store, Windows Update, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Rooms Network Security](/microsoftteams/rooms/security?tabs=Windows#network-security) + +- Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Devices](/microsoftteams/devices/qos-on-teams-devices) + +- Review if your organization utilizes a proxy, you need the proxy address or proxy autoconfiguration (PAC) file url + +- Review if your organization utilizes certificates for network access, you need the certificates for a successful setup + +> [!IMPORTANT] +> Be sure to use a network connection with enough bandwidth (we recommend 10 mbps up/down per Teams Room) to ensure your meetings perform well. + + +### Certificates + +Your Microsoft Teams Rooms device uses certificates for Microsoft Teams, network usage, and authentication. If the related servers use public certificates, which is the case for online, there should be no further action required on the part of the admin to install certificates. If, on the other hand, the certificate authority is a private CA then the device needs to trust that CA. This means having the CA + CA chain certificates installed on the device. Certificates can be installed via Intune for your Teams Rooms devices or via OEM tooling. + + +### Proxy + +> [!IMPORTANT] +> Microsoft Teams Rooms does not support proxy authentication as it may interfere with regular operations of the room. Ensure that Microsoft Teams Rooms have been exempted from proxy authentication before going into production. If your proxy server utilizes internally signed certificates, you must install the internal certificate chain, including the root CA, on the Microsoft Teams Rooms device. + +#### Proxy for Teams Rooms on Windows + +This guidance is for manual configuration. This configuration can also be automated using Intune configurations on your devices ensure these configurations are consistent across a large scale deployment. + +##### Skype User Registry Hive + +1. In the Microsoft Teams Rooms UI, select on the Settings gear icon where you're prompted for the local Administrator password on the device (the default password is **sfb**) +1. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) +1. In the **Search** box, in the bottom left type in regedit (either long press the screen or right select and choose **Run as administrator**) +1. Select on the HKEY_USERS folder ensure the root folder HKEY_USERS is selected + +5. Select on File and then choose **Load Hive** +6. Browse to the **C:\Users\Skype** folder and type in the File name box NTUSER.dat and press the open button +1. You're prompted for a Key Name for your newly loaded Hive; type in Skype (you should now see the registry settings for the Skype User) + +8. Open the Skype key and browse to HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings then ensure these settings are entered: + + ```console + [HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings] + "MigrateProxy"=dword:00000001 + "ProxyEnable"=dword:00000001 + "ProxyServer"="xx.xx.xx.xx:8080" + ``` + + If ProxyServer doesn't exist you may have to add this key as a string, change the xx.xx.xx.xx:8080 to the ip/host and port of your Proxy server. + + A completed configuration would look like this example: + + ```console + [HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings] + "MigrateProxy"=dword:00000001 + "ProxyEnable"=dword:00000001 + "AutoConfigURL"=http://contosoproxy.corp.net/proxy.pac + ``` + +9. When finished making changes, highlight the Skype User key (root folder for Skype) and choose unload Hive from the Registry file menu (which prompts for confirmation - select **Yes**) +10. You can now close the registry editor and reboot your Teams Room + +##### Windows System Proxy + +1. In the Microsoft Teams Rooms UI, select on the Settings gear icon which prompts for the local Administrator password on the device (the default password is `sfb`) +1. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) +3. In the **Search Windows** box, type in 'Settings' +4. Select 'Network & internet' +5. Select 'Proxy' +6. Configure your proxy IP or proxy PAC file +7. Close Settings and reboot your Teams Room + +##### Pro Management Agent Proxy + +1. In the Microsoft Teams Rooms UI, select on the Settings gear icon which prompts for the local Administrator password on the device (the default password is `sfb`) +2. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) +3. In the Windows ***Search*** field (bottom-left section of the screen), enter **cmd** (either long press the screen or right select, and choose ***Run as administrator***). +4. Run the following command (double quotes at end of command are important): + + - If using single ***proxy server***: `bitsadmin /Util /SetIEProxy LOCALSYSTEM MANUAL_PROXY : ""` + + *Example:* + + ```cmd + bitsadmin /Util /SetIEProxy LOCALSYSTEM MANUAL_PROXY contosoproxy.corp.net:8080 "" + ``` + + - If using a ***pac*** file: `bitsadmin /Util /SetIEProxy LOCALSYSTEM AUTOSCRIPT ` + + *Example:* + + ```cmd + bitsadmin /Util /SetIEProxy LOCALSYSTEM AUTOSCRIPT http://contosoproxy.corp.net/proxy.pac + ``` + +#### Proxy on Teams Rooms on Android + +Proxy settings on Teams Rooms on Android vary by device manufacturer. Consult OEM documentation for how to best configure Teams Rooms on Android devices for a network with a proxy. + +## Wireless network considerations + +We strongly recommend that you connect your Teams Rooms devices to a wired network for greater stability and performance, ensuring a seamless meeting experience. If using a wired connection isn't available, you may opt to use a wireless connection. + +> [!IMPORTANT] +> Wireless networks can be prone to network interference leading to quality degradation. We strongly recommend that you follow your wireless equipment provider's best practices when configuring a wireless connection to improve video and audio quality. + +Here are some examples of wireless network configuration best practices recommended by various manufacturers: + +- Deploy wireless equipment, such as access points and routers, that can handle and distribute the bandwidth load across all connected devices in the network. +- As much as possible, use access points and routers from a single manufacturer to avoid further congesting the radio-spectrum. +- Ensure wireless equipment is installed in a way that reduces or eliminates interference from objects and other equipment. +- Ensure the wireless network shows strong signal strength (Wi-Fi signal showing full bars is preferred) on Teams Rooms and other device screens. +- Default to prioritizing 5-GHz coverage for devices to optimize for higher bandwidth. +- Enable band steering to ensure that 5 GHz is always given more priority when sharing the same network name as 2.4 GHz. +- Keep wireless channel utilization below 50%. +- Keep access point and router firmware up to date with the latest firmware versions and hot fixes. +- Verify that Teams Rooms devices and at least one access point see each other with a signal strength of -60 dBm or better. A dBm value closer to zero is preferred. Follow your equipment manufacturer's recommendations. +- Implement QoS whenever possible to allow monitoring and resolution of issues in real time. + +For more best practices specific to your wireless network hardware, check your manufacturer's documentation. + +You can also troubleshoot wireless network issues using the wireless network report built into Windows 10. For more information, see [Analyze the wireless network report - Microsoft Support](https://support.microsoft.com/windows/analyze-the-wireless-network-report-76da0daa-1db2-6049-d154-7bb679eb03ed). + +## Tenant Restrictions + +For organizations which utilize [tenant restrictions](/entra/identity/enterprise-apps/tenant-restrictions) features of Microsoft Entra ID, this is supported on some Teams Devices if your organization utilizes the proxy deployment variant with header injection. + +#### Teams Rooms on Windows + +To support tenant restrictions, ensure you have your proxy configuration on your Teams Rooms device completed per this Learn document and ensure the Teams Rooms on Windows device has the replacement SSL certificates installed on it to trust the header injected web traffic. + +#### Teams Rooms on Android + +Tenant restrictions aren't supported today on Teams Rooms on Android devices. Consult with your Android device OEM for potential workarounds. + +## Teams Rooms on Windows administrative access + +### Using an admin group + +If you choose to join a Teams Rooms on Windows device to a domain (Microsoft Entra ID or Active Directory), you can use Microsoft Intune, Group Policy, or Local Computer Management to set a Security Group as local administrator just like you would for a Windows PC in your domain. Anyone who is a member of that security group can enter their credentials and unlock Settings. + +> [!NOTE] +> If your Microsoft Teams Rooms device loses trust with the domain (for example, if you remove the Microsoft Teams Rooms from the domain after it is domain joined), you won't be able to authenticate into the device and open up Settings. The workaround is to log in with the local Admin account. + +### Local "Admin" User Account + +> [!CAUTION] +> Be sure to change the Microsoft Teams Rooms password as soon as possible. + +Microsoft Teams Rooms default password is set to `sfb`. The password can be changed in several ways: + +- Recommended: [Configuring LAPS on Teams Rooms on Windows](/microsoftteams/rooms/laps-authentication) +- Intune: [Set-LocalUser](/powershell/module/microsoft.powershell.localaccounts/set-localuser) +- Locally: [Change or reset your Windows password](https://support.microsoft.com/windows/change-or-reset-your-windows-password-8271d17c-9f9e-443f-835a-8318c8f68b9c) + +You can read more about the Admin account in the [Microsoft Teams Rooms security](security.md) article. + +### Local 'Skype' User Account + +> [!CAUTION] +> Any modifications to the "Skype" user account are not supported by Microsoft and will prevent your Teams Rooms on Windows device from functioning correctly. + +Teams Rooms on Windows include a local account named "Skype" which is passwordless. This account is used to sign in to Windows to launch the Teams Rooms app. For more information on how the "Skype" user is security, review [Microsoft Teams Rooms security](security.md). + +### Machine Account + +Much like any Windows device, the machine name can be renamed by right-clicking in **Settings** \> **About** \> **Rename PC**. + +If you would like to rename the computer after joining it to a domain, use [Rename-Computer](/powershell/module/microsoft.powershell.management/rename-computer), a PowerShell command, followed by the computer's new name. + +## Teams Rooms on Android administrative access + +Local administrative access to Teams Rooms on Android devices is controlled by the Teams device equipment manufacturer. Consult the device documentation for default accounts and passwords and instructions for how to change those passwords. + +## Related articles + +[Plan Microsoft Teams Rooms](rooms-plan.md) + +[Deploy Microsoft Teams Rooms](rooms-deploy.md) + +[Manage Microsoft Teams Rooms](rooms-manage.md) + +[Teams Rooms Security](/microsoftteams/rooms/security) diff --git a/Teams/set-up-common-area-phones.md b/Teams/phones/set-up-common-area-phones.md similarity index 100% rename from Teams/set-up-common-area-phones.md rename to Teams/phones/set-up-common-area-phones.md diff --git a/Teams/toc.yml b/Teams/toc.yml index 0c9eac2eb7..10997965f2 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1466,7 +1466,7 @@ items: - name: Intune Enrollment for Android items: - name: Device administrator - href: devices/phones-displays-deploy.md + href: devices/mtra-panels-deploy.md - name: AOSP device management href: rooms/android-migration-guide.md - name: Step 3 - Create room accounts @@ -1587,14 +1587,12 @@ items: items: - name: Overview of Teams phones href: devices/phones-for-teams.md - - name: Planning for Teams phones - href: devices/plan-device-deployment.md - name: What's new in Teams phones href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones - name: Deploy items: - name: Step 1 - Overview - href: devices/plan-device-deployment.md + href: phones/plan-device-deployment.md - name: Step 2 - Prepare your environment items: - name: Preparing your network @@ -1602,11 +1600,11 @@ items: - name: Intune Enrollment for Teams phones items: - name: Device administration - href: devices/phones-panels-deploy.md + href: phones/phones-deploy.md - name: AOSP device management href: rooms/android-migration-guide.md - name: Authentication best practices for Teams phones - href: devices/authentication-best-practices-for-android-devices.md + href: phones/authentication-best-practices-phones.md - name: Step 3 - Set up and configure items: - name: Set up common area phones @@ -1621,8 +1619,10 @@ items: href: devices/remote-sign-in-and-sign-out.md - name: Manage items: - - name: Update management - href: devices/remote-update.md + - name: Manage Teams phones + href: phones/manage-teams-phones.md + - name: Update management + href: devices/remote-update.md - name: Troubleshooting items: - name: Troubleshooting Teams phones From ca7c7f62c7e45cebb9f9073df9e3e8f86166f796 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Wed, 16 Oct 2024 15:22:13 -0500 Subject: [PATCH 27/87] Update proximity-join.md Fixing inclusive wording on the ultrasound section and adding some clarity to available controls today. --- Teams/rooms/proximity-join.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/Teams/rooms/proximity-join.md b/Teams/rooms/proximity-join.md index e2657f1640..7dbe122a43 100644 --- a/Teams/rooms/proximity-join.md +++ b/Teams/rooms/proximity-join.md @@ -24,14 +24,16 @@ f1keywords: NOCSH # Proximity Join using Bluetooth and ultrasound -Proximity Join is a feature that lets you use your Teams app on a desktop or mobile device to invite or nudge a Microsoft Teams Rooms console into a Teams meeting. Before you nudge the Teams Rooms console into the meeting, the room doesn't have to be already invited or added to the meeting. This feature uses wireless technologies that can be individually turned on or off depending on the requirements of the environment including: +Proximity Join is a feature that lets you use your Teams app on a desktop or mobile device to invite or nudge a Microsoft Teams Room into a Teams meeting. The Teams Room doesn't need to be invited to the meeting to be joined using proximity join. This feature uses wireless technologies that can be individually turned on or off depending on the requirements of the environment including: - [Bluetooth](#bluetooth) -- [Ultrasonic sound (Ultrasound)](#ultrasound) +- [Ultrasound (Ultrasonic)](#ultrasound) -The end user experience is the same if Bluetooth or ultrasound are used for Proximity Join to join a meeting. If they're both turned on, they operate together and in parallel. A Teams Room that is found with ultrasound turned on is always put in the meeting's prejoin screen at the top of the list of nearby rooms. You can see it's available in the room audio option. Teams Rooms that are found using Bluetooth are listed after the room that have ultrasound turned on in that list. +The end user experience is the same if Bluetooth or ultrasound are used for Proximity Join. If they're both turned on, they operate together to provide the most accuracy. A Teams Room that is found with ultrasound turned on is always put in the meeting's prejoin screen at the top of the list of nearby rooms (under the room audio option). Teams Rooms that are found using Bluetooth are listed after the room that have ultrasound turned on in that list. -Once a connection is established between a personal laptop or mobile device with the Teams app and a Teams Room console, the user's video won't appear in the room's display, and the room's video stream is hidden on the personal device's meeting stage. +When a users laptop or mobile device brings a Teams Rooms in via Proximity Join or if Proximity Join detects a user is joining while in a Teams Room already in the meeting, the user's video won't appear in the room's display, and the room's video stream is hidden on the personal device's meeting stage. Users can override the automatic hiding behavior by using the pin or spotlight functionality of Teams Meetings. + +Proximity join does not require a direct network connection between a users personal devices and the Teams Rooms device, all communication takes place through Microsoft Teams. ## Bluetooth @@ -52,7 +54,7 @@ The Proximity Join via ultrasound works by emitting an ultrasonic (19.5 kHz - 21 > Room Remote can't be used with ultrasound only because the ultrasound beacon is paused while the Teams Room is in a call. Room Remote can't use ultrasound to verify that the personal device is in proximity with the room, so Room Remote won't work if only ultrasound is turned on. > [!CAUTION] -> Some younger people and animals with sensitive hearing may be able to hear it. In our testing, this sound hasn't been distressing, but take note if young people or animals are in your meeting room environment. We recommend that younger people and animals aren't present in the meeting room environments. If the beacon can be heard outside of the space for which it is intended to represent, speak with your admin. While Microsoft works with partners to ensure volume levels are adequately capped, your admin may have overridden the volume for ultrasound emission on a console or audio peripheral that will in turn may have unintended consequences. +> Some younger people and animals with sensitive hearing may be able to hear the ultrasound tones. In our testing, this sound hasn't been distressing, and is only output prior to a call being initiated but take note if those who may hear the ultrasound tones are present in your environment. ### Ultrasound supported devices @@ -83,9 +85,8 @@ Management of proximity features is available in the Teams Rooms Pro Management - Automatically accept proximity-based meeting invitations -- Enable ultrasound beaconing - - - Remote control from personal devices +> [!NOTE] +> Ultrasound controls are not yet available within the Pro Management Portal. ### [Teams Rooms app settings](#tab/app-settings) @@ -97,13 +98,12 @@ Management of proximity features is available on Microsoft Teams Rooms admin set - Automatically accept proximity-based meeting invitations -- Enable ultrasound beaconing - - - Remote control from personal devices +> [!NOTE] +> Ultrasound controls are not yet available within the device settings. -### [XML configuration file](#tab/xml) +### [Teams Rooms on Windows (XML)](#tab/xml) -Like most Teams Rooms on Windows features, you can update the settings of your device with the Teams Rooms XML configuration file. The XML configuration file lets you remotely deploy configuration changes to one or more Teams Rooms on Windows devices in your organization. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). +You can update the settings of your device with a XML configuration file. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). |**Paramater**|**Type**|**Level**|**Usage**| |:-------- |:-------- |:-------- |:-------- | From 85d2f512e701f0faf8b712990fde936491b07097 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Wed, 16 Oct 2024 15:29:08 -0500 Subject: [PATCH 28/87] Update proximity-join.md --- Teams/rooms/proximity-join.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/rooms/proximity-join.md b/Teams/rooms/proximity-join.md index 7dbe122a43..78810d31f4 100644 --- a/Teams/rooms/proximity-join.md +++ b/Teams/rooms/proximity-join.md @@ -75,7 +75,7 @@ There are multiple ways and tools you can use to manage Proximity Join settings > [!NOTE] > The settings for ultrasound don't apply to Teams Room on Android but the Bluetooth settings are available for those devices. -### [Teams Rooms Pro portal](#tab/portal) +### [Pro Management Portal](#tab/portal) Management of proximity features is available in the Teams Rooms Pro Management portal: @@ -101,7 +101,7 @@ Management of proximity features is available on Microsoft Teams Rooms admin set > [!NOTE] > Ultrasound controls are not yet available within the device settings. -### [Teams Rooms on Windows (XML)](#tab/xml) +### [XML (Teams Rooms on Windows)](#tab/xml) You can update the settings of your device with a XML configuration file. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). From 6bede604893f73f4ace801e5b01e2edeba2bb4d0 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Wed, 16 Oct 2024 15:50:01 -0500 Subject: [PATCH 29/87] Update proximity-join.md --- Teams/rooms/proximity-join.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/rooms/proximity-join.md b/Teams/rooms/proximity-join.md index 78810d31f4..2a688c2ad4 100644 --- a/Teams/rooms/proximity-join.md +++ b/Teams/rooms/proximity-join.md @@ -54,7 +54,7 @@ The Proximity Join via ultrasound works by emitting an ultrasonic (19.5 kHz - 21 > Room Remote can't be used with ultrasound only because the ultrasound beacon is paused while the Teams Room is in a call. Room Remote can't use ultrasound to verify that the personal device is in proximity with the room, so Room Remote won't work if only ultrasound is turned on. > [!CAUTION] -> Some younger people and animals with sensitive hearing may be able to hear the ultrasound tones. In our testing, this sound hasn't been distressing, and is only output prior to a call being initiated but take note if those who may hear the ultrasound tones are present in your environment. +> People or animals with sensitive hearing may be able to hear the ultrasound tones. In our testing, this sound hasn't been distressing, and is only output prior to a call being initiated but take note if those who may hear the ultrasound tones are present in your environment to decide if this feature should be enabled or not. ### Ultrasound supported devices From fc440b6e49480e5e6cf6b982a321a6e5c4f50139 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 15:08:25 -0700 Subject: [PATCH 30/87] Acrolinx fixes --- Teams/rooms/proximity-join.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/Teams/rooms/proximity-join.md b/Teams/rooms/proximity-join.md index 2a688c2ad4..60cd863bb5 100644 --- a/Teams/rooms/proximity-join.md +++ b/Teams/rooms/proximity-join.md @@ -18,7 +18,7 @@ appliesto: - Microsoft Teams ms.localizationpriority: medium search.appverid: MET150 -description: Learn how to use the Proximity Join feature using Bluetooth and Ultrasound connnectivity to nudge a Microsoft Teams Room console into a meeting you are having for an optimum meeting room experience. +description: Learn how to use the Proximity Join feature using Bluetooth and Ultrasound connectivity to nudge a Microsoft Teams Room console into a meeting you're having for an optimum meeting room experience. f1keywords: NOCSH --- @@ -31,9 +31,9 @@ Proximity Join is a feature that lets you use your Teams app on a desktop or mob The end user experience is the same if Bluetooth or ultrasound are used for Proximity Join. If they're both turned on, they operate together to provide the most accuracy. A Teams Room that is found with ultrasound turned on is always put in the meeting's prejoin screen at the top of the list of nearby rooms (under the room audio option). Teams Rooms that are found using Bluetooth are listed after the room that have ultrasound turned on in that list. -When a users laptop or mobile device brings a Teams Rooms in via Proximity Join or if Proximity Join detects a user is joining while in a Teams Room already in the meeting, the user's video won't appear in the room's display, and the room's video stream is hidden on the personal device's meeting stage. Users can override the automatic hiding behavior by using the pin or spotlight functionality of Teams Meetings. +When a user's laptop or mobile device brings a Teams Rooms in using Proximity Join or if Proximity Join detects a user is joining while in a Teams Room already in the meeting, the user's video won't appear in the room's display, and the room's video stream is hidden on the personal device's meeting stage. Users can override the automatic hiding behavior by using the pin or spotlight functionality of Teams Meetings. -Proximity join does not require a direct network connection between a users personal devices and the Teams Rooms device, all communication takes place through Microsoft Teams. +Proximity join doesn't require a direct network connection between a user personal devices and the Teams Rooms device, all communication takes place through Microsoft Teams. ## Bluetooth @@ -48,7 +48,7 @@ Ultrasound signaling is available on Microsoft Teams Rooms on Windows, beacons f > [!NOTE] > Proximity Join using ultrasound isn't currently available for Teams Rooms on Android. -The Proximity Join via ultrasound works by emitting an ultrasonic (19.5 kHz - 21.5 kHz) signal from the Teams Room console that isn't audible to humans. It's more accurate than Bluetooth because at reasonable volume, it won't penetrate through walls. Plus, the signal is paused when the Microsoft Teams Room is either in a meeting or HDMI ingest is active. For example, you walk into a conference room with ultrasound turned on the Teams Rooms console, and you want to join your meeting to the Teams Room, you see it in the meeting's prejoin screen in the list of available rooms because those rooms are sorted and listed at the top of the screen. This lets someone select the exact Teams Rooms console and conference room they want to use for their meeting. +The Proximity Join using ultrasound works by emitting an ultrasonic (19.5 kHz - 21.5 kHz) signal from the Teams Room console that isn't audible to humans. It's more accurate than Bluetooth because at reasonable volume, it won't penetrate through walls. Plus, the signal is paused when the Microsoft Teams Room is either in a meeting or HDMI ingest is active. For example, you walk into a conference room with ultrasound turned on the Teams Rooms console, and you want to join your meeting to the Teams Room, you see it in the meeting's prejoin screen in the list of available rooms because those rooms are sorted and listed at the top of the screen. This lets someone select the exact Teams Rooms console and conference room they want to use for their meeting. > [!NOTE] > Room Remote can't be used with ultrasound only because the ultrasound beacon is paused while the Teams Room is in a call. Room Remote can't use ultrasound to verify that the personal device is in proximity with the room, so Room Remote won't work if only ultrasound is turned on. @@ -61,7 +61,7 @@ The Proximity Join via ultrasound works by emitting an ultrasonic (19.5 kHz - 21 |Sender (Consoles for Teams Rooms on Windows)|Receiver| | -------- | -------- | |Crestron UC-2 |Teams on Windows (minimum version 24193.1805.3040.8975)| -|Crestron MercuryX |Teams on MacOS (minimum version 24193.1707.3028.4282) | +|Crestron MercuryX |Teams on macOS (minimum version 24193.1707.3028.4282) | |Lenovo Hub 500|| |Lenovo ThinkSmart Audio G2|| |Logi Tap|| @@ -86,7 +86,7 @@ Management of proximity features is available in the Teams Rooms Pro Management - Automatically accept proximity-based meeting invitations > [!NOTE] -> Ultrasound controls are not yet available within the Pro Management Portal. +> Ultrasound controls aren't available yet within the Pro Management Portal. ### [Teams Rooms app settings](#tab/app-settings) @@ -99,13 +99,13 @@ Management of proximity features is available on Microsoft Teams Rooms admin set - Automatically accept proximity-based meeting invitations > [!NOTE] -> Ultrasound controls are not yet available within the device settings. +> Ultrasound controls aren't available yet within the device settings. ### [XML (Teams Rooms on Windows)](#tab/xml) -You can update the settings of your device with a XML configuration file. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). +You can update the settings of your device with an XML configuration file. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). -|**Paramater**|**Type**|**Level**|**Usage**| +|**Parameter**|**Type**|**Level**|**Usage**| |:-------- |:-------- |:-------- |:-------- | |BluetoothAdvertisementEnabled|Boolean ❷|First ❶|Enabled by default.| |AutoAcceptProximateMeetingInvitations|Boolean ❷|First ❶|If true, proximity based meeting invitations using Bluetooth are automatically accepted. Enabled by default.| From c4ba1e29c1312fd5209c9caca0861f217141f8f8 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 15:46:38 -0700 Subject: [PATCH 31/87] Fixing links --- Teams/devices/mtra-panels-deploy.md | 4 +--- Teams/phones/common-area-mobile-phones.md | 4 ++-- Teams/phones/manage-teams-phones.md | 10 ++++----- Teams/phones/phones-deploy.md | 6 +++--- Teams/phones/phones-for-teams.md | 8 +++---- Teams/phones/plan-device-deployment.md | 16 +++++++------- Teams/phones/prepare-network-teams-phones.md | 18 +++++++--------- Teams/toc.yml | 22 ++++++++++---------- 8 files changed, 41 insertions(+), 47 deletions(-) diff --git a/Teams/devices/mtra-panels-deploy.md b/Teams/devices/mtra-panels-deploy.md index 9f98f71839..a29ba6ccab 100644 --- a/Teams/devices/mtra-panels-deploy.md +++ b/Teams/devices/mtra-panels-deploy.md @@ -25,9 +25,7 @@ description: This article gives you an overview of how to deploy Teams panels, a # Deploy Teams panels and Microsoft Teams Rooms on Android using Intune -**MATT: verify that this works for just Teams panels and MTRA.** - -This article gives you an overview of how to deploy Teams panels, and Microsoft Teams Rooms on Android using Conditional Access and Intune. +This article gives you an overview of how to deploy Teams panels and Microsoft Teams Rooms on Android using Conditional Access and Intune. ## Conditional Access diff --git a/Teams/phones/common-area-mobile-phones.md b/Teams/phones/common-area-mobile-phones.md index 4a1fdb5a72..009b376f5d 100644 --- a/Teams/phones/common-area-mobile-phones.md +++ b/Teams/phones/common-area-mobile-phones.md @@ -30,7 +30,7 @@ description: Learn how to set up common area Android phones A Teams Android mobile app signed in with an account tied to **Microsoft Teams Shared Device** license is used as a shared device by frontline workers to make and receive calls as part of their daily work using Teams. > [!IMPORTANT] - > To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. + > To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. ## Step 1 - Buy the licenses @@ -48,7 +48,7 @@ To purchase the license: > [!NOTE] > If you're using Intune in your environment and have conditional access rules that require device compliance, you'll need to assign an **Microsoft Entra ID P1** and an **Intune** license to the device account that was used to sign in to the Teams mobile app. - > Teams-shared devices can be impacted by conditional access rules and other identity configurations, such as Multi-Factor Authentication. For more information, see [Authentication best practices for Teams Android devices](authentication-best-practices-for-android-devices.md). + > Teams-shared devices can be impacted by conditional access rules and other identity configurations, such as Multi-Factor Authentication. For more information, see [Authentication best practices for Teams Android devices](../devices/authentication-best-practices-for-android-devices.md). ## Step 2 - Create a new user account and assign licenses diff --git a/Teams/phones/manage-teams-phones.md b/Teams/phones/manage-teams-phones.md index db7f37b806..45ab28b5af 100644 --- a/Teams/phones/manage-teams-phones.md +++ b/Teams/phones/manage-teams-phones.md @@ -22,7 +22,7 @@ f1.keywords: ms.custom: - ms.teamsadmincenter.managedevices.overview - ms.teamsadmincenter.devicemanagement.overview -description: Manage devices used with Microsoft Teams in your organization. +description: Manage Teams phones you have deployed in your organization. ms.localizationpriority: medium search.appverid: MET150 --- @@ -48,7 +48,7 @@ You can manage any device that's certified for, and enrolled in, Teams. A device - [Conference phones](https://products.office.com/microsoft-teams/across-devices/devices/category?devicetype=73) - [Desk phones](https://products.office.com/microsoft-teams/across-devices/devices/category?devicetype=34) - [Teams displays](https://www.microsoft.com/microsoft-365/microsoft-teams/across-devices/devices/category?devicetype=34) -- [Teams panels](teams-panels.md) +- [Teams panels](../devices/teams-panels.md) To manage Teams phones, in the left navigation of the [Microsoft Teams admin center](https://admin.teams.microsoft.com), go to **Teams Devices**, and then select the device type. Each type of device has its own respective section, which lets you manage them separately. @@ -82,11 +82,11 @@ Here are some examples of how you can manage phones, Teams Rooms on Android, Tea | To do this... | Do this | |-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Change device information | Select a device > **Edit**. You can edit details such as device name, asset tag, and add notes. | -| Manage software updates | Select a device > **Update**. You can view the list of software and firmware updates available for the device and choose the updates to install. For more information about updating devices, see [Update Teams devices remotely](remote-update.md) | +| Manage software updates | Select a device > **Update**. You can view the list of software and firmware updates available for the device and choose the updates to install. For more information about updating devices, see [Update Teams devices remotely](../devices/remote-update.md) | | Assign or change configuration policies | Select one or more devices > **Assign configuration**. | -| Add or remove device tags | Select one or more devices > **Manage tags**. For more information about device tags, see [Manage Teams device tags](manage-device-tags.md). | +| Add or remove device tags | Select one or more devices > **Manage tags**. For more information about device tags, see [Manage Teams device tags](../devices/manage-device-tags.md). | | Restart devices | Select one or more devices > **Restart**. | -| Filter devices using device tags | Select the filter icon, select the **Tag** field, specify a device tag to filter on, and select **Apply**. For more information about filtering devices using device tags, see [Use filters to return devices with a specific tag](manage-device-tags.md#use-filters-to-return-devices-with-a-specific-tag). | +| Filter devices using device tags | Select the filter icon, select the **Tag** field, specify a device tag to filter on, and select **Apply**. For more information about filtering devices using device tags, see [Use filters to return devices with a specific tag](../devices/manage-device-tags.md#use-filters-to-return-devices-with-a-specific-tag). | |Schedule device actions|Actions like **Restart** and **Software update** can be scheduled for the preferred date and time.| | View device history and diagnostics | Under the **History** column, click the **View** link for a device to view its update history and diagnostic details. | |View device action details|In the **History** tab on the device page, select the action status to view the details of the action.| diff --git a/Teams/phones/phones-deploy.md b/Teams/phones/phones-deploy.md index c29427fd66..8c4065446a 100644 --- a/Teams/phones/phones-deploy.md +++ b/Teams/phones/phones-deploy.md @@ -68,10 +68,10 @@ Teams Android-based devices, including Teams phones are managed by Intune using [Phones for Teams](phones-for-teams.md) -[Certified Teams phones](teams-phones-certified-hardware.md) +[Certified Teams phones](../devices/teams-phones-certified-hardware.md) -[Teams displays](teams-displays.md) +[Teams displays](../devices/teams-displays.md) -[Manage your devices in Teams](device-management.md) +[Manage your devices in Teams](../devices/device-management.md) [Teams Marketplace](https://office.com/teamsdevices) diff --git a/Teams/phones/phones-for-teams.md b/Teams/phones/phones-for-teams.md index c73b7a5bad..19f2e95923 100644 --- a/Teams/phones/phones-for-teams.md +++ b/Teams/phones/phones-for-teams.md @@ -64,18 +64,18 @@ For more information about getting Teams, check out [How do I get access to Micr ## Deploy your phones using Intune -To learn more about how to deploy Teams displays using Intune, see [Deploy Teams phones and Teams panels](../phones/phones-panels-). +To learn more about how to deploy Teams displays using Intune, see [Deploy Teams phones and Teams panels](../phones/phones-deploy.md). ## Manage your phones -Manage and keep your Teams phones up-to-date using the Microsoft Teams admin center. For more information, see [Manage your devices in Teams](device-management.md). +Manage and keep your Teams phones up-to-date using the Microsoft Teams admin center. For more information, see [Manage your devices in Teams](../devices/device-management.md). ## Upgrade your phones to Teams displays -[Microsoft Teams displays](teams-displays.md) are a category of all-in-one dedicated Teams devices that feature an ambient touchscreen. With Teams displays, users can use a microphone, camera, and speakers (or Bluetooth headset) for a reliable calling and meeting experience. Teams displays integrates with users' Windows PCs to bring a companion experience that allows for seamless cross-device interaction. +[Microsoft Teams displays](../devices/teams-displays.md) are a category of all-in-one dedicated Teams devices that feature an ambient touchscreen. With Teams displays, users can use a microphone, camera, and speakers (or Bluetooth headset) for a reliable calling and meeting experience. Teams displays integrates with users' Windows PCs to bring a companion experience that allows for seamless cross-device interaction. ## See also [Teams Marketplace](https://office.com/teamsdevices) -[Certified Teams phones](teams-phones-certified-hardware.md) \ No newline at end of file +[Certified Teams phones](../devices/teams-phones-certified-hardware.md) \ No newline at end of file diff --git a/Teams/phones/plan-device-deployment.md b/Teams/phones/plan-device-deployment.md index e45d44ddda..496d963414 100644 --- a/Teams/phones/plan-device-deployment.md +++ b/Teams/phones/plan-device-deployment.md @@ -18,12 +18,12 @@ ms.collection: f1.keywords: - NOCSH search.appverid: MET150 -description: This article provides an overview of the tasks and steps to deploy Teams Phones in your organization. +description: This article provides an overview of the tasks and steps to deploy Teams phones in your organization. --- # Plan your deployment for Teams Phones -Teams Phone devices are a great way to stay connected and productive with your colleagues and customers. These devices are designed to provide a seamless calling and meeting experience. With just three easy steps, you can deploy a [Teams Phone device certified by Microsoft](https://www.microsoft.com/en-us/microsoft-teams/across-devices/devices/category/desk-phones-teams-displays/34?page=1&filterIds=), in your spaces and enjoy advanced calling features. +Teams phones are a great way to stay connected and productive with your colleagues and customers. These devices are designed to provide a seamless calling and meeting experience. With just three easy steps, you can deploy a [Teams Phone device certified by Microsoft](https://www.microsoft.com/en-us/microsoft-teams/across-devices/devices/category/desk-phones-teams-displays/34?page=1&filterIds=), in your spaces and enjoy advanced calling features. ## Step 1: Consider the space Teams Phone device will be used in @@ -56,7 +56,7 @@ The space you choose will determine the type of license you'll need. - **Walkie Talkie**: Users part of a Teams channel can broadcast messages to other users' part of the same channel. - **Calendar**: Schedule and join meetings. - :::image type="content" source="media/teams-apps-1.png" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: + :::image type="content" source="../media/teams-" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: ## Step 3: Setup desired phone device experience for your users @@ -86,17 +86,17 @@ In addition to the above, you can choose from the following experiences on touch ## Best Practices: -- **Manage firmware and Teams app updates**: Enable [auto updates](remote-update.md#automatic-updates) of firmware via Teams admin center and assign devices to different rings (Validation, General, Final) to roll out updates in phases. You can assign the Validation ring to a small set of test phones and assign other phones to General and Final rings. +- **Manage firmware and Teams app updates**: Enable [auto updates](../devices/remote-update.md#automatic-updates) of firmware via Teams admin center and assign devices to different rings (Validation, General, Final) to roll out updates in phases. You can assign the Validation ring to a small set of test phones and assign other phones to General and Final rings. > [!NOTE] - > Auto updates on Teams application is coming soon. Currently, you can [schedule](remote-update.md#manually-update-remote-devices) Teams application update via Teams admin center. + > Auto updates on Teams application is coming soon. Currently, you can [schedule](../devices/remote-update.md#manually-update-remote-devices) Teams application update via Teams admin center. -- **Manage Authentication**: For password management, review [Authentication best practices](authentication-best-practices-for-android-devices.md). +- **Manage Authentication**: For password management, review [Authentication best practices](../devices/authentication-best-practices-for-android-devices.md). - **Configure calling policies**: Configure different [calling policies](../teams-calling-policy.md) based on your needs. -- **Optimize phone memory usage**: To optimize phone performance, enable daily or automatic restart of Teams application on the phone device via [configuration profile](device-management.md#use-configuration-profiles-in-teams). +- **Optimize phone memory usage**: To optimize phone performance, enable daily or automatic restart of Teams application on the phone device via [configuration profile](../devices/device-management.md#use-configuration-profiles-in-teams). -- **Secure common area phones**: To provide secured access to settings on phone devices in shared spaces, set an Admin PIN on common area phones via [configuration profile](device-management.md#use-configuration-profiles-in-teams). +- **Secure common area phones**: To provide secured access to settings on phone devices in shared spaces, set an Admin PIN on common area phones via [configuration profile](../devices/device-management.md#use-configuration-profiles-in-teams). - **Secure personal phones**: Ask your users who use phones in personal spaces to set a phone device lock PIN for secured access instead of setting a default phone device lock PIN via configuration profile. diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md index 67488c24db..3b0efca454 100644 --- a/Teams/phones/prepare-network-teams-phones.md +++ b/Teams/phones/prepare-network-teams-phones.md @@ -18,14 +18,12 @@ ms.collection: f1.keywords: - NOCSH search.appverid: MET150 -description: Learn about how to prepare your network infrastructure for deploying Microsoft Teams phonesso that you can take advantage of all of the available features. +description: Learn about how to prepare your network infrastructure for deploying Microsoft Teams phones so that you can take advantage of all of the available features. --- # Plan your network environment for Teams Phones -**MATT: THIS ARTICLE NEEDS EDITED FOR Teams phones only** - -This section contains an overview of the steps required to prepare your network environment so that you can use all of the features of Microsoft Teams Rooms. This section also includes information on configuring local administive access to your Teams Rooms devices. +This section contains an overview of the steps required to prepare your network environment so that you can use all of the features of Microsoft Teams phones. This section also includes information on configuring local administive access to your Teams phones. ## Confirm network configuration @@ -42,12 +40,10 @@ In order to function properly, Microsoft Teams Rooms devices must have access to > [!IMPORTANT] > Be sure to use a network connection with enough bandwidth (we recommend 10 mbps up/down per Teams Room) to ensure your meetings perform well. - ### Certificates Your Microsoft Teams Rooms device uses certificates for Microsoft Teams, network usage, and authentication. If the related servers use public certificates, which is the case for online, there should be no further action required on the part of the admin to install certificates. If, on the other hand, the certificate authority is a private CA then the device needs to trust that CA. This means having the CA + CA chain certificates installed on the device. Certificates can be installed via Intune for your Teams Rooms devices or via OEM tooling. - ### Proxy > [!IMPORTANT] @@ -176,7 +172,7 @@ If you choose to join a Teams Rooms on Windows device to a domain (Microsoft Ent ### Local "Admin" User Account > [!CAUTION] -> Be sure to change the Microsoft Teams Rooms password as soon as possible. +> Be sure to change the Microsoft Teams Rooms password as soon as possible. Microsoft Teams Rooms default password is set to `sfb`. The password can be changed in several ways: @@ -191,7 +187,7 @@ You can read more about the Admin account in the [Microsoft Teams Rooms security > [!CAUTION] > Any modifications to the "Skype" user account are not supported by Microsoft and will prevent your Teams Rooms on Windows device from functioning correctly. -Teams Rooms on Windows include a local account named "Skype" which is passwordless. This account is used to sign in to Windows to launch the Teams Rooms app. For more information on how the "Skype" user is security, review [Microsoft Teams Rooms security](security.md). +Teams Rooms on Windows include a local account named "Skype" which is passwordless. This account is used to sign in to Windows to launch the Teams Rooms app. For more information on how the "Skype" user is security, review [Microsoft Teams Rooms security](../rooms/security.md). ### Machine Account @@ -205,10 +201,10 @@ Local administrative access to Teams Rooms on Android devices is controlled by t ## Related articles -[Plan Microsoft Teams Rooms](rooms-plan.md) +[Plan Microsoft Teams Rooms](../rooms/rooms-plan.md) -[Deploy Microsoft Teams Rooms](rooms-deploy.md) +[Deploy Microsoft Teams Rooms](../rooms/rooms-deploy.md) -[Manage Microsoft Teams Rooms](rooms-manage.md) +[Manage Microsoft Teams Rooms](../rooms/rooms-manage.md) [Teams Rooms Security](/microsoftteams/rooms/security) diff --git a/Teams/toc.yml b/Teams/toc.yml index 10997965f2..9bb58f57ec 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1343,11 +1343,11 @@ items: - name: Personal peripherals href: devices/usb-devices.md items: - - name: Known issues + - name: Troubleshooting and known issues href: /microsoftteams/troubleshoot/meetings/known-issues-teams-certified-peripherals - name: Teams Rooms and panels items: - - name: Overview and planning + - name: Plan items: - name: Teams Rooms items: @@ -1439,13 +1439,13 @@ items: href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels - name: Teams device management apps href: devices/certified-device-apps.md - - name: Known issues + - name: Troubleshooting and known issues items: - name: Teams Rooms on Windows href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-windows - name: Teams Rooms on Android href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-android - - name: Deployment + - name: Deploy items: - name: Overview href: rooms/rooms-deploy.md @@ -1573,13 +1573,13 @@ items: href: rooms/customer-reported-incidents.md - name: Analytics, reports, and insights items: - - name: Monitoring and maintaining Teams Rooms + - name: Monitor and maintain Teams Rooms href: rooms/managed-meeting-rooms-portal.md - name: Audit logs for activities href: rooms/multi-tenant-auditing.md - name: Data and privacy information href: rooms/data-and-privacy-info.md - - name: Troubleshooting Teams Rooms Pro portal + - name: Troubleshooting and known issues href: /microsoftteams/troubleshoot/teams-rooms-and-devices/get-support-teams-rooms-pro-management - name: Teams phones items: @@ -1595,8 +1595,8 @@ items: href: phones/plan-device-deployment.md - name: Step 2 - Prepare your environment items: - - name: Preparing your network - href: rooms/rooms-prep.md + - name: Prepare your network + href: phones/prepare-network-teams-phones.md - name: Intune Enrollment for Teams phones items: - name: Device administration @@ -1611,7 +1611,7 @@ items: href: set-up-common-area-phones.md - name: Set up a common area mobile phones href: devices/common-area-mobile-phones.md - - name: Step 4 - Setting up Teams phones + - name: Step 4 - Set up Teams phones items: - name: Remote provisioning href: devices/remote-provision-remote-login.md @@ -1623,9 +1623,9 @@ items: href: phones/manage-teams-phones.md - name: Update management href: devices/remote-update.md - - name: Troubleshooting + - name: Troubleshooting and known issues items: - - name: Troubleshooting Teams phones + - name: Troubleshooting and known issues href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android - name: Bring your own device (BYOD) spaces items: From 10ccc86ae53e575308b9bb5373fcc5a65364ea4b Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Wed, 16 Oct 2024 15:57:38 -0700 Subject: [PATCH 32/87] Fixing links --- ...tion-best-practices-for-android-devices.md | 2 +- Teams/phones/prepare-network-teams-phones.md | 2 +- Teams/phones/set-up-common-area-phones.md | 34 +++++++++---------- .../supported-ca-and-compliance-policies.md | 2 +- 4 files changed, 20 insertions(+), 20 deletions(-) diff --git a/Teams/devices/authentication-best-practices-for-android-devices.md b/Teams/devices/authentication-best-practices-for-android-devices.md index 7e26715039..c451af30db 100644 --- a/Teams/devices/authentication-best-practices-for-android-devices.md +++ b/Teams/devices/authentication-best-practices-for-android-devices.md @@ -86,7 +86,7 @@ If shared devices are provisioned in a well-defined location that can be identif If you're enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams devices can be configured for Conditional Access policies based on device compliance. For more information, see [Conditional Access: Require compliant or Microsoft Entra hybrid joined device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device). -To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/intune/protect/device-compliance-get-started). +To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). >[!NOTE] > Shared devices being used for *hot-desking* should be excluded from compliance policies. Compliance polices prevent the devices from enrolling into the hot desk user account. **Instead, use named locations to secure these devices**. diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md index 3b0efca454..54a4463d09 100644 --- a/Teams/phones/prepare-network-teams-phones.md +++ b/Teams/phones/prepare-network-teams-phones.md @@ -180,7 +180,7 @@ Microsoft Teams Rooms default password is set to `sfb`. The password can be chan - Intune: [Set-LocalUser](/powershell/module/microsoft.powershell.localaccounts/set-localuser) - Locally: [Change or reset your Windows password](https://support.microsoft.com/windows/change-or-reset-your-windows-password-8271d17c-9f9e-443f-835a-8318c8f68b9c) -You can read more about the Admin account in the [Microsoft Teams Rooms security](security.md) article. +You can read more about the Admin account in the [Microsoft Teams Rooms security](../rooms/security.md) article. ### Local 'Skype' User Account diff --git a/Teams/phones/set-up-common-area-phones.md b/Teams/phones/set-up-common-area-phones.md index 7425fcd79b..ea0358b669 100644 --- a/Teams/phones/set-up-common-area-phones.md +++ b/Teams/phones/set-up-common-area-phones.md @@ -33,7 +33,7 @@ description: Learn how to set up common area phones for lobbies, reception areas A common area phone is typically placed in an area like a lobby or another area that is available to many people to make a call: a reception area, lobby, or conference phone. Common area phones are signed in with accounts tied to a **Microsoft Teams Shared Devices** license. -This article provides an overview of how to deploy and configure Teams phone devices as common area phones for shared spaces. For a more complete meeting room experience, including audio conferencing, consider purchasing a dedicated **Teams Rooms** license with a Teams Rooms device instead. For more information about Teams Rooms, see [Microsoft Teams Rooms](rooms/index.md). +This article provides an overview of how to deploy and configure Teams phone devices as common area phones for shared spaces. For a more complete meeting room experience, including audio conferencing, consider purchasing a dedicated **Teams Rooms** license with a Teams Rooms device instead. For more information about Teams Rooms, see [Microsoft Teams Rooms](../rooms/index.md). > [!NOTE] > Accounts for common area phones objects created in Skype for Business Server can't be migrated to Microsoft Teams. Follow the steps in this article to recreate those accounts for Teams, and, if required, migrate your Public Switched Telephone Network (PSTN) connectivity. @@ -53,7 +53,7 @@ First, you need to purchase a **Teams Shared Devices** license and make sure tha > [!NOTE] > If you’re using Intune in your environment and have conditional access rules that require device compliance, you’ll need to assign an **Microsoft Entra ID P1**, and **Intune** license to the device account for the common area phone. > -> Common area phones can be impacted by conditional access rules and other identity configurations, like Multi-Factor Authentication. See [Authentication best practices for Teams Android devices](devices/authentication-best-practices-for-android-devices.md) to learn more. +> Common area phones can be impacted by conditional access rules and other identity configurations, like Multi-Factor Authentication. See [Authentication best practices for Teams Android devices](../devices/authentication-best-practices-for-android-devices.md) to learn more. ## Step 2 - Create a new user account and assign licenses @@ -81,7 +81,7 @@ If you're deploying one device: > [!NOTE] > You don't need to add a license with Phone System features. It's included with the **Teams Shared Devices** license. > -> If you aren't using Microsoft Phone System with Direct Routing or Operator Connect, you may want to add **Calling Plans** licenses. For more information on licenses, see [Microsoft Teams add-on licensing](./teams-add-on-licensing/microsoft-teams-add-on-licensing.md). +> If you aren't using Microsoft Phone System with Direct Routing or Operator Connect, you may want to add **Calling Plans** licenses. For more information on licenses, see [Microsoft Teams add-on licensing](/microsoftteams/teams-add-on-licensing/microsoft-teams-add-on-licensing.md). ### Using PowerShell @@ -101,16 +101,16 @@ To configure other parameters, consider creating an [IP phone policy](/powershel ### Calling policies -Use calling policies to enable private calls, using call forwarding, or simultaneous ring on common area phones. To learn more, see [Configure calling policies in Teams](teams-calling-policy.md). +Use calling policies to enable private calls, using call forwarding, or simultaneous ring on common area phones. To learn more, see [Configure calling policies in Teams](../teams-calling-policy.md). -By default, call park isn't enabled for common area phones. You'll need to create a policy to enable it. To learn more, see [Call park and retrieve in Microsoft Teams](call-park-and-retrieve.md). +By default, call park isn't enabled for common area phones. You'll need to create a policy to enable it. To learn more, see [Call park and retrieve in Microsoft Teams](../call-park-and-retrieve.md). > [!NOTE] > After you assign a policy, sign out of the phone and sign back in. It may take up to an hour for a policy assignment to take effect. ## Step 4 - Acquire and assign phone numbers -See [Manage telephone numbers for your organization](manage-phone-numbers-landing-page.md) to learn how to acquire and assign phone numbers based on your PSTN connectivity option. +See [Manage telephone numbers for your organization](../manage-phone-numbers-landing-page.md) to learn how to acquire and assign phone numbers based on your PSTN connectivity option. ## Step 5 - Sign in @@ -129,7 +129,7 @@ To sign in locally with a username and password: 3. Follow the sign-in directions on the device. Once signed in, the phone will display the common area phone user experience. > [!NOTE] -> If you are using a custom setup policy that unpins the calling app, the dial pad doesn't appear on the common area phone. For more information about Teams setup policies, see [Manage app setup policies in Microsoft Teams](teams-app-setup-policies.md). +> If you are using a custom setup policy that unpins the calling app, the dial pad doesn't appear on the common area phone. For more information about Teams setup policies, see [Manage app setup policies in Microsoft Teams](../teams-app-setup-policies.md). ### Sign in from another device @@ -149,13 +149,13 @@ By default, the basic calling experience will be on the common area phone's home The following advanced calling features are available for supported Teams phone device models with a **Teams Shared Devices** license and the latest Teams updates (minimum version: 1449/1.0.94.2022061702): -- [Call park and retrieve](call-park-and-retrieve.md). -- [Cloud-based voicemail through Exchange Online Plan 2](set-up-phone-system-voicemail.md). +- [Call park and retrieve](../call-park-and-retrieve.md). +- [Cloud-based voicemail through Exchange Online Plan 2](../set-up-phone-system-voicemail.md). - To disable cloud-based voicemail, see [Voicemail user settings using PowerShell](/powershell/module/teams/set-csonlinevoicemailusersettings). -- [Call queues](create-a-phone-system-call-queue.md). -- [Auto attendants](create-a-phone-system-auto-attendant.md). -- [Group call pickup](call-sharing-and-group-call-pickup.md). -- [Forwarding rules](user-call-settings.md). +- [Call queues](../create-a-phone-system-call-queue.md). +- [Auto attendants](../create-a-phone-system-auto-attendant.md). +- [Group call pickup](../call-sharing-and-group-call-pickup.md). +- [Forwarding rules](../user-call-settings.md). To use these advanced calling features on a supported Teams phone device model, you can turn on the **Advanced calling** toggle in the [Teams admin center](https://admin.teams.microsoft.com/) or on your Teams phone device that is signed into your Teams Shared Devices account. Once you turn on advanced calling home screen experience on the phone, the device will update. @@ -198,10 +198,10 @@ You can set up common area phones as hotline phones also known as PLAR (Private ## Next steps -Now that you've set up and signed in common area phones for your organization, you can manage them in the Teams admin center. See [Microsoft Teams: Managing your devices](devices/device-management.md) to learn more. +Now that you've set up and signed in common area phones for your organization, you can manage them in the Teams admin center. See [Microsoft Teams: Managing your devices](../devices/device-management.md) to learn more. ## Related articles -- [Update Microsoft Teams devices remotely](devices/remote-update.md). -- [Manage Microsoft Teams device tags](devices/manage-device-tags.md). -- [Microsoft Teams device health monitoring](alerts/device-health-status.md). +- [Update Microsoft Teams devices remotely](../devices/remote-update.md). +- [Manage Microsoft Teams device tags](../devices/manage-device-tags.md). +- [Microsoft Teams device health monitoring](../alerts/device-health-status.md). diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index d0c1fd0506..2b4eb19386 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -37,7 +37,7 @@ for more information. The following list includes the supported Conditional Access policies for Teams Rooms on Windows and Android, and for policies on Teams panels, phones, and displays. -| Assignment | Teams Rooms on Windows | Teams Rooms on Android and panels | Teams phones and displays | +| **Assignment** | **Teams Rooms on Windows** | **Teams Rooms on Android and panels** | **Teams phones and displays** | |------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | User or workload identities | Supported | Supported | Supported | | Cloud apps or actions | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | From d672153c9d13baa9566c587ffa985386e3058a5b Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Wed, 16 Oct 2024 18:21:40 -0500 Subject: [PATCH 33/87] Update prepare-network-teams-phones.md Editing to be Teams Phone specific --- Teams/phones/prepare-network-teams-phones.md | 146 ++----------------- 1 file changed, 9 insertions(+), 137 deletions(-) diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md index 54a4463d09..fa0046dbce 100644 --- a/Teams/phones/prepare-network-teams-phones.md +++ b/Teams/phones/prepare-network-teams-phones.md @@ -27,9 +27,9 @@ This section contains an overview of the steps required to prepare your network ## Confirm network configuration -In order to function properly, Microsoft Teams Rooms devices must have access to a network that meets these requirements: +In order to function properly, Microsoft Phone devices must have access to a network that meets these requirements: -- Review access to: Microsoft Teams, SharePoint/OneDrive, Pro Management Portal, Microsoft Store, Windows Update, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Rooms Network Security](/microsoftteams/rooms/security?tabs=Windows#network-security) +- Review access to: Microsoft Teams, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Rooms Network Security](/microsoftteams/rooms/security?tabs=Android#network-security) - Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Devices](/microsoftteams/devices/qos-on-teams-devices) @@ -38,91 +38,18 @@ In order to function properly, Microsoft Teams Rooms devices must have access to - Review if your organization utilizes certificates for network access, you need the certificates for a successful setup > [!IMPORTANT] -> Be sure to use a network connection with enough bandwidth (we recommend 10 mbps up/down per Teams Room) to ensure your meetings perform well. +> Be sure to use a network connection with enough bandwidth (we recommend 100 kbps up/down per Teams Phone) to ensure your calls perform well. ### Certificates -Your Microsoft Teams Rooms device uses certificates for Microsoft Teams, network usage, and authentication. If the related servers use public certificates, which is the case for online, there should be no further action required on the part of the admin to install certificates. If, on the other hand, the certificate authority is a private CA then the device needs to trust that CA. This means having the CA + CA chain certificates installed on the device. Certificates can be installed via Intune for your Teams Rooms devices or via OEM tooling. +Your Microsoft Teams Phone device uses certificates for Microsoft Teams, network usage, and authentication. If the related servers use public certificates, which is the case for online, there should be no further action required on the part of the admin to install certificates. If, on the other hand, the certificate authority is a private CA then the device needs to trust that CA. This means having the CA + CA chain certificates installed on the device. Certificates can be installed via Intune or via OEM tooling. ### Proxy > [!IMPORTANT] -> Microsoft Teams Rooms does not support proxy authentication as it may interfere with regular operations of the room. Ensure that Microsoft Teams Rooms have been exempted from proxy authentication before going into production. If your proxy server utilizes internally signed certificates, you must install the internal certificate chain, including the root CA, on the Microsoft Teams Rooms device. +> Microsoft Teams Phones does not support proxy authentication as it may interfere with regular operations of the room. Ensure that Microsoft Teams Phones have been exempted from proxy authentication before going into production. If your proxy server utilizes internally signed certificates, you must install the internal certificate chain, including the root CA, on the Microsoft Teams Phone. -#### Proxy for Teams Rooms on Windows - -This guidance is for manual configuration. This configuration can also be automated using Intune configurations on your devices ensure these configurations are consistent across a large scale deployment. - -##### Skype User Registry Hive - -1. In the Microsoft Teams Rooms UI, select on the Settings gear icon where you're prompted for the local Administrator password on the device (the default password is **sfb**) -1. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) -1. In the **Search** box, in the bottom left type in regedit (either long press the screen or right select and choose **Run as administrator**) -1. Select on the HKEY_USERS folder ensure the root folder HKEY_USERS is selected - -5. Select on File and then choose **Load Hive** -6. Browse to the **C:\Users\Skype** folder and type in the File name box NTUSER.dat and press the open button -1. You're prompted for a Key Name for your newly loaded Hive; type in Skype (you should now see the registry settings for the Skype User) - -8. Open the Skype key and browse to HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings then ensure these settings are entered: - - ```console - [HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings] - "MigrateProxy"=dword:00000001 - "ProxyEnable"=dword:00000001 - "ProxyServer"="xx.xx.xx.xx:8080" - ``` - - If ProxyServer doesn't exist you may have to add this key as a string, change the xx.xx.xx.xx:8080 to the ip/host and port of your Proxy server. - - A completed configuration would look like this example: - - ```console - [HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings] - "MigrateProxy"=dword:00000001 - "ProxyEnable"=dword:00000001 - "AutoConfigURL"=http://contosoproxy.corp.net/proxy.pac - ``` - -9. When finished making changes, highlight the Skype User key (root folder for Skype) and choose unload Hive from the Registry file menu (which prompts for confirmation - select **Yes**) -10. You can now close the registry editor and reboot your Teams Room - -##### Windows System Proxy - -1. In the Microsoft Teams Rooms UI, select on the Settings gear icon which prompts for the local Administrator password on the device (the default password is `sfb`) -1. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) -3. In the **Search Windows** box, type in 'Settings' -4. Select 'Network & internet' -5. Select 'Proxy' -6. Configure your proxy IP or proxy PAC file -7. Close Settings and reboot your Teams Room - -##### Pro Management Agent Proxy - -1. In the Microsoft Teams Rooms UI, select on the Settings gear icon which prompts for the local Administrator password on the device (the default password is `sfb`) -2. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) -3. In the Windows ***Search*** field (bottom-left section of the screen), enter **cmd** (either long press the screen or right select, and choose ***Run as administrator***). -4. Run the following command (double quotes at end of command are important): - - - If using single ***proxy server***: `bitsadmin /Util /SetIEProxy LOCALSYSTEM MANUAL_PROXY : ""` - - *Example:* - - ```cmd - bitsadmin /Util /SetIEProxy LOCALSYSTEM MANUAL_PROXY contosoproxy.corp.net:8080 "" - ``` - - - If using a ***pac*** file: `bitsadmin /Util /SetIEProxy LOCALSYSTEM AUTOSCRIPT ` - - *Example:* - - ```cmd - bitsadmin /Util /SetIEProxy LOCALSYSTEM AUTOSCRIPT http://contosoproxy.corp.net/proxy.pac - ``` - -#### Proxy on Teams Rooms on Android - -Proxy settings on Teams Rooms on Android vary by device manufacturer. Consult OEM documentation for how to best configure Teams Rooms on Android devices for a network with a proxy. +Proxy settings on Teams Phones vary by device manufacturer. Consult OEM documentation for how to best configure Teams Phone devices for a network with a proxy. ## Wireless network considerations @@ -146,65 +73,10 @@ Here are some examples of wireless network configuration best practices recommen For more best practices specific to your wireless network hardware, check your manufacturer's documentation. -You can also troubleshoot wireless network issues using the wireless network report built into Windows 10. For more information, see [Analyze the wireless network report - Microsoft Support](https://support.microsoft.com/windows/analyze-the-wireless-network-report-76da0daa-1db2-6049-d154-7bb679eb03ed). - ## Tenant Restrictions -For organizations which utilize [tenant restrictions](/entra/identity/enterprise-apps/tenant-restrictions) features of Microsoft Entra ID, this is supported on some Teams Devices if your organization utilizes the proxy deployment variant with header injection. - -#### Teams Rooms on Windows - -To support tenant restrictions, ensure you have your proxy configuration on your Teams Rooms device completed per this Learn document and ensure the Teams Rooms on Windows device has the replacement SSL certificates installed on it to trust the header injected web traffic. - -#### Teams Rooms on Android - -Tenant restrictions aren't supported today on Teams Rooms on Android devices. Consult with your Android device OEM for potential workarounds. - -## Teams Rooms on Windows administrative access - -### Using an admin group - -If you choose to join a Teams Rooms on Windows device to a domain (Microsoft Entra ID or Active Directory), you can use Microsoft Intune, Group Policy, or Local Computer Management to set a Security Group as local administrator just like you would for a Windows PC in your domain. Anyone who is a member of that security group can enter their credentials and unlock Settings. - -> [!NOTE] -> If your Microsoft Teams Rooms device loses trust with the domain (for example, if you remove the Microsoft Teams Rooms from the domain after it is domain joined), you won't be able to authenticate into the device and open up Settings. The workaround is to log in with the local Admin account. - -### Local "Admin" User Account - -> [!CAUTION] -> Be sure to change the Microsoft Teams Rooms password as soon as possible. - -Microsoft Teams Rooms default password is set to `sfb`. The password can be changed in several ways: - -- Recommended: [Configuring LAPS on Teams Rooms on Windows](/microsoftteams/rooms/laps-authentication) -- Intune: [Set-LocalUser](/powershell/module/microsoft.powershell.localaccounts/set-localuser) -- Locally: [Change or reset your Windows password](https://support.microsoft.com/windows/change-or-reset-your-windows-password-8271d17c-9f9e-443f-835a-8318c8f68b9c) - -You can read more about the Admin account in the [Microsoft Teams Rooms security](../rooms/security.md) article. - -### Local 'Skype' User Account - -> [!CAUTION] -> Any modifications to the "Skype" user account are not supported by Microsoft and will prevent your Teams Rooms on Windows device from functioning correctly. - -Teams Rooms on Windows include a local account named "Skype" which is passwordless. This account is used to sign in to Windows to launch the Teams Rooms app. For more information on how the "Skype" user is security, review [Microsoft Teams Rooms security](../rooms/security.md). - -### Machine Account - -Much like any Windows device, the machine name can be renamed by right-clicking in **Settings** \> **About** \> **Rename PC**. - -If you would like to rename the computer after joining it to a domain, use [Rename-Computer](/powershell/module/microsoft.powershell.management/rename-computer), a PowerShell command, followed by the computer's new name. - -## Teams Rooms on Android administrative access - -Local administrative access to Teams Rooms on Android devices is controlled by the Teams device equipment manufacturer. Consult the device documentation for default accounts and passwords and instructions for how to change those passwords. - -## Related articles - -[Plan Microsoft Teams Rooms](../rooms/rooms-plan.md) - -[Deploy Microsoft Teams Rooms](../rooms/rooms-deploy.md) +For organizations which utilize [tenant restrictions](/entra/identity/enterprise-apps/tenant-restrictions) features of Microsoft Entra ID, this is supported on some Teams Devices if your organization utilizes the proxy deployment variant with header injection. However, tenant restrictions aren't supported today on Teams Phone devices. Consult with your Android device OEM for potential workarounds. -[Manage Microsoft Teams Rooms](../rooms/rooms-manage.md) +## Device administrative access -[Teams Rooms Security](/microsoftteams/rooms/security) +Local administrative access to Teams Phone devices is controlled by the Teams device equipment manufacturer. Consult the device documentation for default accounts and passwords and instructions for how to change those passwords. From 9e3d3d581c30309da1ff31ee1dfc0324deb462e8 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Thu, 17 Oct 2024 15:03:17 +0530 Subject: [PATCH 34/87] as per 9446860 --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 42 ++++++++++++++++++- .../add-persistent-chat-server.md | 19 ++++----- .../configure-hadr-for-persistent-chat.md | 15 +++---- ...onfigure-persistent-chat-server-options.md | 11 ++--- ...configure-persistent-chat-user-policies.md | 11 ++--- .../create-a-persistent-chat-administrator.md | 11 ++--- .../deploy-persistent-chat-server.md | 23 +++++----- .../install-persistent-chat-components.md | 15 +++---- .../back-up-and-restore-databases.md | 10 ++--- .../manage/persistent-chat/categories.md | 14 +++---- .../manage/persistent-chat/chat-rooms.md | 17 ++++---- .../persistent-chat/configure-add-ins.md | 13 +++--- .../persistent-chat/configure-compliance.md | 10 ++--- ...high-availability-and-disaster-recovery.md | 14 +++---- .../monitor-start-and-stop-services.md | 14 +++---- .../manage/persistent-chat/persistent-chat.md | 14 +++---- .../planning-tool/persistent-chat.md | 4 +- .../capacity-planning.md | 3 -- .../categories-chat-rooms-and-user-roles.md | 3 -- .../hardware-and-software-requirements.md | 3 -- ...high-availability-and-disaster-recovery.md | 3 -- .../persistent-chat-server.md | 2 - 22 files changed, 129 insertions(+), 142 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 456f8fb7c2..3d20aa6b0d 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -18,7 +18,7 @@ href: ../../SfbServer/sfb-server-updates.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Hybrid solutions for Teams and Skype for Business href: ../../SfbHybrid/hybrid/plan-hybrid-connectivity.md?toc=/SkypeForBusiness/sfbhybridtoc/toc.json - - name: Plan + - name: Plan your deployment items: - name: Topology Basics href: ../../SfbServer/plan-your-deployment/topology-basics/topology-basics.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json @@ -339,6 +339,21 @@ href: ../../SfbServer/deploy/install/verify-the-topology.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Deploy Call Via Work href: ../../SfbServer/deploy/deploy-call-via-work.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Deploy Persistent Chat Server + href: ../../SfbServer/deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: Add Persistent Chat Server + href: ../../SfbServer/deploy/deploy-persistent-chat-server/add-persistent-chat-server.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Install Persistent Chat components + href: ../../SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Create a Persistent Chat administrator + href: ../../SfbServer/deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure Persistent Chat Server options + href: ../../SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-server-options.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure Persistent Chat user policies + href: ../../SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-user-policies.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure HADR for Persistent Chat + href: ../../SfbServer/deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Deploy archiving href: ../../SfbServer/deploy/deploy-archiving/deploy-archiving.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: @@ -774,6 +789,23 @@ href: ../../SfbServer/manage/topology/move-file-store-data.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Disable TLS 1.0/1.1 href: ../../SfbServer/manage/topology/disable-tls-1.0-1.1.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat + href: ../../SfbServer/manage/persistent-chat/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: Categories + href: ../../SfbServer/manage/persistent-chat/categories.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Chat rooms + href: ../../SfbServer/manage/persistent-chat/chat-rooms.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure add-ins + href: ../../SfbServer/manage/persistent-chat/configure-add-ins.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure Compliance + href: ../../SfbServer/manage/persistent-chat/configure-compliance.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Back up and restore databases + href: ../../SfbServer/manage/persistent-chat/back-up-and-restore-databases.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: High availability and disaster recovery + href: ../../SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Monitor, start, and stop services + href: ../../SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Health and monitoring href: ../../SfbServer/manage/health-and-monitoring/health-and-monitoring.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: @@ -1106,3 +1138,11 @@ href: ../tools/test-users-and-settings-2019.md - name: Skype for Business Server Capacity Planning Calculator href: ../../SfbServer/management-tools/capacity-planning-calculator.md + - name: Planning Tool + href: ../../SfbServer/management-tools/planning-tool/planning-tool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: UI Reference + href: ../../SfbServer/management-tools/planning-tool/ui-reference.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: Persistent Chat + href: ../../SfbServer/management-tools/planning-tool/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/add-persistent-chat-server.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/add-persistent-chat-server.md index e1ea9e1067..e5abdad5fe 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/add-persistent-chat-server.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/add-persistent-chat-server.md @@ -1,5 +1,5 @@ --- -title: "Add Persistent Chat Server to your Skype for Business Server 2015 topology" +title: "Add Persistent Chat Server to your Skype for Business Server topology" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 6b4f4d69-3c9d-4bc7-bc9b-46427a095de2 -description: "Summary: Read this topic to learn how to add Persistent Chat Server to your Skype for Business Server 2015 topology." +description: "Summary: Read this topic to learn how to add Persistent Chat Server to your Skype for Business Server topology." --- -# Add Persistent Chat Server to your Skype for Business Server 2015 topology +# Add Persistent Chat Server to your Skype for Business Server topology -**Summary:** Read this topic to learn how to add Persistent Chat Server to your Skype for Business Server 2015 topology. +**Summary:** Read this topic to learn how to add Persistent Chat Server to your Skype for Business Server topology. After you install the prerequisite software on each server on which you plan to deploy Persistent Chat Server, you use Topology Builder to: @@ -25,12 +25,9 @@ After you install the prerequisite software on each server on which you plan to - Publish the updated topology -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Update your topology to include Persistent Chat Server -Perform the following steps for installing a single Persistent Chat Server pool without a disaster recovery configuration. For configuring a stretched Persistent Chat Server pool for high availability and disaster recovery, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-high-availability-and-disaster-recovery/configure-hadr-for-persistent-chat.md). +Perform the following steps for installing a single Persistent Chat Server pool without a disaster recovery configuration. For configuring a stretched Persistent Chat Server pool for high availability and disaster recovery, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-high-availability-and-disaster-recovery/configure-hadr-for-persistent-chat.md). To deploy multiple Persistent Chat Server pools, repeat the same process for each pool. @@ -70,12 +67,12 @@ To deploy multiple Persistent Chat Server pools, repeat the same process for eac - Either select **Default Instance** to use the default instance or, to specify a different instance, select **Named Instance**, and specify the instance that you want to use. > [!NOTE] - > For details about how to configure SQL Server backup databases for disaster recovery, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-high-availability-and-disaster-recovery/configure-hadr-for-persistent-chat.md). + > For details about how to configure SQL Server backup databases for disaster recovery, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-high-availability-and-disaster-recovery/configure-hadr-for-persistent-chat.md). 9. Define the SQL Server compliance store if you enabled Compliance. > [!IMPORTANT] - > For details about how to configure SQL Server mirrors for high availability for the Persistent Chat Server database and the Persistent Chat Server compliance database, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-high-availability-and-disaster-recovery/configure-hadr-for-persistent-chat.md). + > For details about how to configure SQL Server mirrors for high availability for the Persistent Chat Server database and the Persistent Chat Server compliance database, see [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-high-availability-and-disaster-recovery/configure-hadr-for-persistent-chat.md). 10. Define the file store. A file store is a folder where a copy of any file uploaded to the file repository is stored (for example, storing file attachments posted to a chat room). In the case of a multiple-server Persistent Chat Server topology, this must be a Universal Naming Convention (UNC) path; and for a single-server Persistent Chat Server topology, it can be a local file path. @@ -108,7 +105,7 @@ Before you publish your topology, install the databases for Persistent Chat Serv 2. Start Topology Builder. Select **Open Topology from a local file** if you saved it locally. -3. In the console tree, right-click **Skype for Business Server 2015**, and then click **Publish Topology**. +3. In the console tree, right-click **Skype for Business Server**, and then click **Publish Topology**. 4. On the **Publish the topology** page, click **Next**. diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md index ffa33ade56..0adf0117cb 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md @@ -1,5 +1,5 @@ --- -title: "Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015" +title: "Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,22 +12,19 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 5fb5b189-56c1-49cf-92c8-e4fd6e2fdd5c -description: "Summary: Read this topic to learn how to configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Read this topic to learn how to configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server." --- -# Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015 +# Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server -**Summary:** Read this topic to learn how to configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Read this topic to learn how to configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server. -Skype for Business Server supports multiple modes of high availability for your Back End Servers, including database mirroring. For more information, see [Plan for high availability and disaster recovery in Skype for Business Server 2015](../../plan-your-deployment/high-availability-and-disaster-recovery/high-availability-and-disaster-recovery.md). +Skype for Business Server supports multiple modes of high availability for your Back End Servers, including database mirroring. For more information, see [Plan for high availability and disaster recovery in Skype for Business Server](../../plan-your-deployment/high-availability-and-disaster-recovery/high-availability-and-disaster-recovery.md). > [!NOTE] > AlwaysOn Availability Groups are not supported with Persistent Chat Servers. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - -Before you configure your Persistent Chat deployment for high availability and disaster recovery, be sure you are familiar with the concepts in [Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md). The disaster recovery solution for Persistent Chat Server described in these topics is built on a stretched Persistent Chat Server pool. The planning content describes resource requirements, and the stretched pool topology that enables high availability and disaster recovery for Persistent Chat Server, including using SQL Server mirroring for high availability and SQL Server log shipping for disaster recovery. +Before you configure your Persistent Chat deployment for high availability and disaster recovery, be sure you are familiar with the concepts in [Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md). The disaster recovery solution for Persistent Chat Server described in these topics is built on a stretched Persistent Chat Server pool. The planning content describes resource requirements, and the stretched pool topology that enables high availability and disaster recovery for Persistent Chat Server, including using SQL Server mirroring for high availability and SQL Server log shipping for disaster recovery. ## Use Topology Builder to configure high availability and disaster recovery diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-server-options.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-server-options.md index ee10bbe39c..6747b9c14c 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-server-options.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-server-options.md @@ -1,5 +1,5 @@ --- -title: "Configure Persistent Chat Server options in Skype for Business Server 2015" +title: "Configure Persistent Chat Server options in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 19ced8de-8867-4152-b38a-891f3bc2a5ea -description: "Summary: Learn how to configure Persistent Chat Server options at the global, site, or pool level in Skype for Business Server 2015." +description: "Summary: Learn how to configure Persistent Chat Server options at the global, site, or pool level in Skype for Business Server." --- -# Configure Persistent Chat Server options in Skype for Business Server 2015 +# Configure Persistent Chat Server options in Skype for Business Server -**Summary:** Learn how to configure Persistent Chat Server options at the global, site, or pool level in Skype for Business Server 2015. +**Summary:** Learn how to configure Persistent Chat Server options at the global, site, or pool level in Skype for Business Server. You can specify several options for Persistent Chat Server that can be applied globally, to all pools within a site, or to a specific pool within a site. Persistent Chat server options include the following: @@ -29,9 +29,6 @@ You can specify several options for Persistent Chat Server that can be applied g - Room Management URL. The URL used for custom chat room management. The setting allows the use of a custom room management solution. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Configure Persistent Chat Server global options To configure Persistent Chat Server global options: diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-user-policies.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-user-policies.md index c117b5c1d9..33eebd61aa 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-user-policies.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-user-policies.md @@ -1,5 +1,5 @@ --- -title: "Configure Persistent Chat user policies in Skype for Business Server 2015" +title: "Configure Persistent Chat user policies in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: e5862480-95f8-4d76-a2b5-940cd995e93c -description: "Summary: Read this topic to learn how to create initial user policies for Persistent Chat Server in Skype for Business Server 2015. Persistent Chat user policies determine whether or not users are allowed access to chat rooms." +description: "Summary: Read this topic to learn how to create initial user policies for Persistent Chat Server in Skype for Business Server. Persistent Chat user policies determine whether or not users are allowed access to chat rooms." --- -# Configure Persistent Chat user policies in Skype for Business Server 2015 +# Configure Persistent Chat user policies in Skype for Business Server -**Summary:** Read this topic to learn how to create initial user policies for Persistent Chat Server in Skype for Business Server 2015. Persistent Chat user policies determine whether or not users are allowed access to chat rooms. +**Summary:** Read this topic to learn how to create initial user policies for Persistent Chat Server in Skype for Business Server. Persistent Chat user policies determine whether or not users are allowed access to chat rooms. You can manage Persistent Chat Server user policies at the following levels: global, site, or user. Initially, you configure the global policy to enable Persistent Chat settings for all users in your deployment, and then create additional user and site policies to control whether Persistent Chat is turned on for specific users and sites. @@ -31,9 +31,6 @@ This topic contains the following sections: - Apply a policy to a user or user group -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Configure the global policy To configure the global policy: diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md index 7ac9fd06d2..a6da2cfa0a 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md @@ -1,5 +1,5 @@ --- -title: "Create a Persistent Chat administrator in Skype for Business Server 2015" +title: "Create a Persistent Chat administrator in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,20 +12,17 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 5c3892e4-ebae-453e-8107-f42ec0436ea2 -description: "Summary: Read this topic to learn how to create a Persistent Chat Server administrator role to enable initial configuration and management of Persistent Chat services in Skype for Business Server 2015." +description: "Summary: Read this topic to learn how to create a Persistent Chat Server administrator role to enable initial configuration and management of Persistent Chat services in Skype for Business Server." --- -# Create a Persistent Chat administrator in Skype for Business Server 2015 +# Create a Persistent Chat administrator in Skype for Business Server -**Summary:** Read this topic to learn how to create a Persistent Chat Server administrator role to enable initial configuration and management of Persistent Chat services in Skype for Business Server 2015. +**Summary:** Read this topic to learn how to create a Persistent Chat Server administrator role to enable initial configuration and management of Persistent Chat services in Skype for Business Server. In Skype for Business Server, users who perform specific tasks must be assigned as members of one or more specific groups. Role-Based Access Control (RBAC) is used to grant privileges by assigning users to predefined Skype for Business Server administrative roles. These roles correspond to universal security groups in Active Directory Domain Services. Members of the Persistent Chat Administrator security group, CsPersistentChatAdministrator, are granted access to the Persistent Chat Server cmdlets, which can be executed using either the Skype for Business Server Management Shell or the Skype for Business Server Control Panel. Before configuring and administering Persistent Chat Server, be sure that the appropriate user rights and permissions are in place, and that any users who will act as Persistent Chat administrators are added to the Persistent Chat Administrator security group. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Create a Persistent Chat administrator To add a user to the Persistent Chat Administrator security group, CsPersistentChatAdministrator, perform the following steps: diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md index 5e2741264a..a788b2c4ca 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md @@ -1,5 +1,5 @@ --- -title: "Deploy Persistent Chat Server in Skype for Business Server 2015" +title: "Deploy Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 8373c93b-92a7-4932-bc1f-00fc08955426 -description: "Summary: Read this topic to learn how to deploy Skype for Business Server 2015 Persistent Chat Server." +description: "Summary: Read this topic to learn how to deploy Skype for Business Server Persistent Chat Server." --- -# Deploy Persistent Chat Server in Skype for Business Server 2015 +# Deploy Persistent Chat Server in Skype for Business Server -**Summary:** Read this topic to learn how to deploy Skype for Business Server 2015 Persistent Chat Server. +**Summary:** Read this topic to learn how to deploy Skype for Business Server Persistent Chat Server. To deploy Persistent Chat Server, you: @@ -27,11 +27,8 @@ To deploy Persistent Chat Server, you: - Install and configure Persistent Chat Server components for your deployment -Before you deploy Persistent Chat Server, you should read [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). The planning topics describe hardware and software requirements, possible topologies, and collocation scenarios. +Before you deploy Persistent Chat Server, you should read [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). The planning topics describe hardware and software requirements, possible topologies, and collocation scenarios. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Deployment checklist You can deploy Persistent Chat Server after you deploy your initial topology, including at least one Skype for Business Server Front End pool or one Skype for Business Standard Edition Server. The deployment checklist describes the basic steps required to deploy Persistent Chat Server and provides links for more details. @@ -40,10 +37,10 @@ You can deploy Persistent Chat Server after you deploy your initial topology, in |**Task**|**Steps**|**Required roles and group memberships**|**Related topics**| |:-----|:-----|:-----|:-----| -|**Install prerequisite hardware and software**
| On hardware that meets system requirements, install the following:
On the Persistent Chat Server Front End Servers:
An operating system that meets system requirements
Software prerequisites for computers running Skype for Business Server
On the server that will host the Persistent Chat Server database:
A supported version of SQL Server
If Persistent Chat Server compliance is required:
SQL Server on the server that will host the Persistent Chat Server compliance database
|Any user who is a member of the local Administrators group.
|[Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md)
[Environmental requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/environmental-requirements.md)
[Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md)
| -|**Create the appropriate internal topology to support Persistent Chat Server (and optionally, Persistent Chat compliance)**
| Run Topology Builder to add a Persistent Chat Server pool to your topology:
Add Persistent Chat Server components to the topology
Create a SQL Server database for the Persistent Chat Server store (and a backup SQL Server for disaster recovery)
Define a new Skype for Business File Store or use an existing Skype for Business File Store for Persistent Chat Server files
Associate the Skype for Business Server pool that can route requests to this Persistent Chat Server pool
If Persistent Chat compliance is required:
Add Persistent Chat Compliance Store
Click the Persistent Chat Server pool definition check box for enabling compliance
Publish the topology.
If you install Persistent Chat Server on Standard Edition, the fully qualified domain name (FQDN) of the Persistent Chat Server pool must match the Standard Edition server, and the SQL Server databases are collocated on the SQL Server Express instance on the Standard Edition server
|To define a topology, an account that is a member of the local Users group.
To publish the topology, an account that is a member of the Domain Admins group and RTCUniversalServerAdmins group, and the user should also have full control permissions (read/write/modify) on the Skype for Business File Store for Persistent Chat Server files (so that Topology Builder can configure the required DACLs).
|[Create and publish new topology in Skype for Business Server 2015](../../deploy/install/create-and-publish-new-topology.md)
[Add Persistent Chat Server to your Skype for Business Server 2015 topology](add-persistent-chat-server.md)
| -|**Deploy Persistent Chat Server**
| Run the Skype for Business Server setup on all the computers running Persistent Chat Server. The Persistent Chat Server setup is integrated into the Skype for Business Server Deployment wizard that provides the following instructions:
Deploy local management store
Install Persistent Chat services
Request and assign certificates
Run and start the services
|Any user who is a member of the local Administrators group.
|[Deploy Persistent Chat Server in Skype for Business Server 2015](deploy-persistent-chat-server.md)
| -|**Create a Persistent Chat administrator**
|Add users to the CsPersistentChatAdministrator security group.
|Any user who is a member of domain administrators.
|[Create a Persistent Chat administrator in Skype for Business Server 2015](create-a-persistent-chat-administrator.md)
| -|**Configure Persistent Chat Server**
| Configure users:
User has to be enabled by policy to access Persistent Chat Server. By default, the policy is turned off for all users and can be defined at global/site/pool/user scopes.
Configure settings
|User must be a member of CsPersistentChatAdministrator. To change policy, user must be in CsUserAdministrator, at a minimum.
|[Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md)
| +|**Install prerequisite hardware and software**
| On hardware that meets system requirements, install the following:
On the Persistent Chat Server Front End Servers:
An operating system that meets system requirements
Software prerequisites for computers running Skype for Business Server
On the server that will host the Persistent Chat Server database:
A supported version of SQL Server
If Persistent Chat Server compliance is required:
SQL Server on the server that will host the Persistent Chat Server compliance database
|Any user who is a member of the local Administrators group.
|[Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md)
[Environmental requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/environmental-requirements.md)
[Hardware and software requirements for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md)
| +|**Create the appropriate internal topology to support Persistent Chat Server (and optionally, Persistent Chat compliance)**
| Run Topology Builder to add a Persistent Chat Server pool to your topology:
Add Persistent Chat Server components to the topology
Create a SQL Server database for the Persistent Chat Server store (and a backup SQL Server for disaster recovery)
Define a new Skype for Business File Store or use an existing Skype for Business File Store for Persistent Chat Server files
Associate the Skype for Business Server pool that can route requests to this Persistent Chat Server pool
If Persistent Chat compliance is required:
Add Persistent Chat Compliance Store
Click the Persistent Chat Server pool definition check box for enabling compliance
Publish the topology.
If you install Persistent Chat Server on Standard Edition, the fully qualified domain name (FQDN) of the Persistent Chat Server pool must match the Standard Edition server, and the SQL Server databases are collocated on the SQL Server Express instance on the Standard Edition server
|To define a topology, an account that is a member of the local Users group.
To publish the topology, an account that is a member of the Domain Admins group and RTCUniversalServerAdmins group, and the user should also have full control permissions (read/write/modify) on the Skype for Business File Store for Persistent Chat Server files (so that Topology Builder can configure the required DACLs).
|[Create and publish new topology in Skype for Business Server](../../deploy/install/create-and-publish-new-topology.md)
[Add Persistent Chat Server to your Skype for Business Server topology](add-persistent-chat-server.md)
| +|**Deploy Persistent Chat Server**
| Run the Skype for Business Server setup on all the computers running Persistent Chat Server. The Persistent Chat Server setup is integrated into the Skype for Business Server Deployment wizard that provides the following instructions:
Deploy local management store
Install Persistent Chat services
Request and assign certificates
Run and start the services
|Any user who is a member of the local Administrators group.
|[Deploy Persistent Chat Server in Skype for Business Server](deploy-persistent-chat-server.md)
| +|**Create a Persistent Chat administrator**
|Add users to the CsPersistentChatAdministrator security group.
|Any user who is a member of domain administrators.
|[Create a Persistent Chat administrator in Skype for Business Server](create-a-persistent-chat-administrator.md)
| +|**Configure Persistent Chat Server**
| Configure users:
User has to be enabled by policy to access Persistent Chat Server. By default, the policy is turned off for all users and can be defined at global/site/pool/user scopes.
Configure settings
|User must be a member of CsPersistentChatAdministrator. To change policy, user must be in CsUserAdministrator, at a minimum.
|[Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md)
| diff --git a/Skype/SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md b/Skype/SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md index 3e10648130..364f838178 100644 --- a/Skype/SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md +++ b/Skype/SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md @@ -1,5 +1,5 @@ --- -title: "Install Persistent Chat components in Skype for Business Server 2015" +title: "Install Persistent Chat components in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,18 +12,15 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 61370aa6-9708-4ff8-b531-b258a928806f -description: "Summary: Read this topic to learn how to use the Skype for Business Server Deployment Wizard to install Skype for Business Server 2015 components and services." +description: "Summary: Read this topic to learn how to use the Skype for Business Server Deployment Wizard to install Skype for Business Server components and services." --- -# Install Persistent Chat components in Skype for Business Server 2015 +# Install Persistent Chat components in Skype for Business Server -**Summary:** Read this topic to learn how to use the Skype for Business Server Deployment Wizard to install Skype for Business Server 2015 components and services. +**Summary:** Read this topic to learn how to use the Skype for Business Server Deployment Wizard to install Skype for Business Server components and services. -Before you install Persistent Chat components, be sure you have already installed prerequisite hardware and software, and created the appropriate topology to support Persistent Chat Server. For details about planning and requirements, see [Requirements for your Skype for Business environment](../../plan-your-deployment/requirements-for-your-environment/requirements-for-your-environment.md) and [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). For information about how to update and publish your topology to include Persistent Chat Server, see [Add Persistent Chat Server to your Skype for Business Server 2015 topology](add-persistent-chat-server.md). +Before you install Persistent Chat components, be sure you have already installed prerequisite hardware and software, and created the appropriate topology to support Persistent Chat Server. For details about planning and requirements, see [Requirements for your Skype for Business environment](../../plan-your-deployment/requirements-for-your-environment/requirements-for-your-environment.md) and [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). For information about how to update and publish your topology to include Persistent Chat Server, see [Add Persistent Chat Server to your Skype for Business Server topology](add-persistent-chat-server.md). -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Install and start services Using the Skype for Business Server Deployment Wizard, choose Install or Update Skype for Business Server System to perform the following steps: @@ -36,6 +33,6 @@ Using the Skype for Business Server Deployment Wizard, choose Install or Update 4. Start services -For details on how to use the Deployment Wizard to install components, assign certificates, and start services, see [Install Skype for Business Server 2015](../../deploy/install/install.md) and [Install Skype for Business Server 2015 on servers in the topology](../../deploy/install/install-skype-for-business-server.md). +For details on how to use the Deployment Wizard to install components, assign certificates, and start services, see [Install Skype for Business Server](../../deploy/install/install.md) and [Install Skype for Business Server on servers in the topology](../../deploy/install/install-skype-for-business-server.md). diff --git a/Skype/SfbServer/manage/persistent-chat/back-up-and-restore-databases.md b/Skype/SfbServer/manage/persistent-chat/back-up-and-restore-databases.md index 647ab5df03..306963b221 100644 --- a/Skype/SfbServer/manage/persistent-chat/back-up-and-restore-databases.md +++ b/Skype/SfbServer/manage/persistent-chat/back-up-and-restore-databases.md @@ -1,5 +1,5 @@ --- -title: "Back up and restore Persistent Chat databases in Skype for Business Server 2015" +title: "Back up and restore Persistent Chat databases in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,17 +12,15 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 4f2b689b-7f15-48dc-a069-da7bc8527def -description: "Summary: Learn how to back up and restore Persistent Chat Server databases in Skype for Business Server 2015." +description: "Summary: Learn how to back up and restore Persistent Chat Server databases in Skype for Business Server." --- -# Back up and restore Persistent Chat databases in Skype for Business Server 2015 +# Back up and restore Persistent Chat databases in Skype for Business Server -**Summary:** Learn how to back up and restore Persistent Chat Server databases in Skype for Business Server 2015. +**Summary:** Learn how to back up and restore Persistent Chat Server databases in Skype for Business Server. Persistent Chat Server requires SQL Server database software to store chat room data, such as history and content, configuration, user provisioning, and other relevant metadata. In addition, if your organization has regulations that require Persistent Chat activity to be archived, and the optional Compliance service is enabled, SQL Server database software is used to store compliance data, including chat content and events, such as joining and leaving rooms. Chat room content is stored in the Persistent Chat database (mgc). Compliance data is stored in the Compliance database (mgccomp). This is business-critical data that should be backed up regularly. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. ## Back up the databases diff --git a/Skype/SfbServer/manage/persistent-chat/categories.md b/Skype/SfbServer/manage/persistent-chat/categories.md index 4c22b9c7c5..bec63d8f85 100644 --- a/Skype/SfbServer/manage/persistent-chat/categories.md +++ b/Skype/SfbServer/manage/persistent-chat/categories.md @@ -1,5 +1,5 @@ --- -title: "Manage categories in Persistent Chat Server in Skype for Business Server 2015" +title: "Manage categories in Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: b0c834b9-b5c8-41d5-865b-c8b180e76d13 -description: "Summary: Learn how to manage Persistent Chat Server categories in Skype for Business Server 2015." +description: "Summary: Learn how to manage Persistent Chat Server categories in Skype for Business Server." --- -# Manage categories in Persistent Chat Server in Skype for Business Server 2015 +# Manage categories in Persistent Chat Server in Skype for Business Server -**Summary:** Learn how to manage Persistent Chat Server categories in Skype for Business Server 2015. +**Summary:** Learn how to manage Persistent Chat Server categories in Skype for Business Server. A category is a logical structure for organizing chat rooms. A category defines a default set of access control lists (ACLs) for controlling the users and user groups who can create or join the chat rooms. Chat room categories contain chat rooms, but not other categories. Each category describes its contents with metadata, such as Name and Description. The category has properties that can be set to control the behavior of the chat rooms belonging to it; for example, whether the chat rooms allow Invitations or File Uploads, or contain Chat History. @@ -31,12 +31,10 @@ Defining AllowedMembers and Creators for a category has the following benefits: Users, Organization Units (OUs), and user groups that are identified as Creators of the category are the only individuals and groups that are allowed to create rooms in the category. After the category is created, you can choose users, OUs, and user groups from the category's AllowedMembers list as chat room managers and members to manage and participate in the room. -Before you configure categories, be sure to read [Persistent chat categories, chat rooms, and user roles in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md). +Before you configure categories, be sure to read [Persistent chat categories, chat rooms, and user roles in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md). You can configure and manage categories by using the Control Panel or by using Windows PowerShell cmdlets. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. ## Configure categories by using the Control Panel @@ -100,7 +98,7 @@ You can configure the following parameters for categories: - DeniedMembers. Lists the users who are not allowed to access chat rooms within the category. -For complete information about cmdlet syntax, including all parameters, see [Skype for Business Server 2015 Management Shell](../management-shell.md). +For complete information about cmdlet syntax, including all parameters, see [Skype for Business Server Management Shell](../management-shell.md). ### Create a new category diff --git a/Skype/SfbServer/manage/persistent-chat/chat-rooms.md b/Skype/SfbServer/manage/persistent-chat/chat-rooms.md index dbe1c2e5d0..548290d1c2 100644 --- a/Skype/SfbServer/manage/persistent-chat/chat-rooms.md +++ b/Skype/SfbServer/manage/persistent-chat/chat-rooms.md @@ -1,5 +1,5 @@ --- -title: "Manage chat rooms in Persistent Chat Server in Skype for Business Server 2015" +title: "Manage chat rooms in Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,18 +12,15 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 7b2e1302-280c-4efe-9ec8-787687b414da -description: "Summary: Learn how to manage Persistent Chat Server chat rooms in Skype for Business Server 2015." +description: "Summary: Learn how to manage Persistent Chat Server chat rooms in Skype for Business Server." --- -# Manage chat rooms in Persistent Chat Server in Skype for Business Server 2015 +# Manage chat rooms in Persistent Chat Server in Skype for Business Server -**Summary:** Learn how to manage Persistent Chat Server chat rooms in Skype for Business Server 2015. +**Summary:** Learn how to manage Persistent Chat Server chat rooms in Skype for Business Server. -Creating and managing chat rooms is much easier with the correct use of categories. A category defines who can create or join the chat rooms. Before you attempt to manage chat rooms, be sure to read [Persistent chat categories, chat rooms, and user roles in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md) and [Manage categories in Persistent Chat Server in Skype for Business Server 2015](categories.md). +Creating and managing chat rooms is much easier with the correct use of categories. A category defines who can create or join the chat rooms. Before you attempt to manage chat rooms, be sure to read [Persistent chat categories, chat rooms, and user roles in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md) and [Manage categories in Persistent Chat Server in Skype for Business Server](categories.md). -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - You can configure and manage chat rooms by using the Windows PowerShell command-line interface, or by using the Skype for Business client if you are a member of the chat room. This topic describes how to manage chat rooms by using the Windows PowerShell command-line interface. If you want to manage chat rooms by using the Skype for Business client, see the client help. Chat rooms can be one of two types: Normal and Auditorium. A Normal chat room allows all members to post and read messages. An Auditorium is a type of chat room where only Presenters can post, but everyone can read. @@ -74,7 +71,7 @@ In addition to the above parameters, the **Set-CsPersistentChatRoom** cmdlet let - Presenters. Lets you assign presenters to an Auditorium chat room. - For details about syntax, including all parameters, see [Skype for Business Server 2015 Management Shell](../management-shell.md). + For details about syntax, including all parameters, see [Skype for Business Server Management Shell](../management-shell.md). ## Create a new room @@ -118,7 +115,7 @@ Set-CsPersistentChatRoom -PersistentChatPoolFqdn "atl-cs-001.contoso.com\NorthAm If the topic of a Persistent Chat room is no longer relevant, you can make the chat room unavailable to users by disabling it. When a chat room is disabled, all members are immediately disconnected from the room. After a chat room is disabled, users cannot rejoin it or find it in chat room searches. -If the chat room's history persists, the content is preserved when the chat room is disabled. However, that content will not appear in searches during the time that the chat room remains in a disabled state. If you later enable the chat room, users can search for messages that were posted before the chat room was disabled. For information about configuring chat room history, see [Manage categories in Persistent Chat Server in Skype for Business Server 2015](categories.md). +If the chat room's history persists, the content is preserved when the chat room is disabled. However, that content will not appear in searches during the time that the chat room remains in a disabled state. If you later enable the chat room, users can search for messages that were posted before the chat room was disabled. For information about configuring chat room history, see [Manage categories in Persistent Chat Server in Skype for Business Server](categories.md). If a chat room is disabled, its membership list and other settings are preserved. As an administrator, you can enable a room that has been disabled, and you do not need to manually re-create the settings. diff --git a/Skype/SfbServer/manage/persistent-chat/configure-add-ins.md b/Skype/SfbServer/manage/persistent-chat/configure-add-ins.md index 643d0fb6f7..b976b3b74c 100644 --- a/Skype/SfbServer/manage/persistent-chat/configure-add-ins.md +++ b/Skype/SfbServer/manage/persistent-chat/configure-add-ins.md @@ -1,5 +1,5 @@ --- -title: "Configure add-ins for Persistent Chat rooms in Skype for Business Server 2015" +title: "Configure add-ins for Persistent Chat rooms in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,20 +12,17 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: c1037909-0750-411a-98c1-3a327eed4ae8 -description: "Summary: Learn how to configure add-ins for Persistent Chat Server chat rooms in Skype for Business Server 2015." +description: "Summary: Learn how to configure add-ins for Persistent Chat Server chat rooms in Skype for Business Server." --- -# Configure add-ins for Persistent Chat rooms in Skype for Business Server 2015 +# Configure add-ins for Persistent Chat rooms in Skype for Business Server -**Summary:** Learn how to configure add-ins for Persistent Chat Server chat rooms in Skype for Business Server 2015. +**Summary:** Learn how to configure add-ins for Persistent Chat Server chat rooms in Skype for Business Server. Add-ins are used to extend the in-room experience by associating URLs with chat rooms. These URLs appear in the client conversation extensibility pane. A typical add-in might include a URL pointing to a Silverlight application that intercepts when a stock ticker is posted to a chat room, and shows the stock history in the extensibility pane. Other examples include embedding a OneNote 2013 URL in the chat room as an add-in to include some shared context, such as "Top of mind" or "Topic of the day." Before users can see an add-in in the client, you must add the add-in to the list of registered add-ins, and chat room Managers or Creators need to associate rooms with the add-in. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. - ## Configure add-ins for chat rooms by using the Control Panel To configure add-ins for chat rooms by using the Control Panel: @@ -52,7 +49,7 @@ To configure add-ins for chat rooms by using the Control Panel: ## Configure add-ins by using Windows PowerShell -You can configure add-ins for chat rooms by using the following Windows PowerShell cmdlets. For details about syntax, including all available parameters, see [Skype for Business Server 2015 Management Shell](../management-shell.md). +You can configure add-ins for chat rooms by using the following Windows PowerShell cmdlets. For details about syntax, including all available parameters, see [Skype for Business Server Management Shell](../management-shell.md). |**Cmdlet**|**Description**| diff --git a/Skype/SfbServer/manage/persistent-chat/configure-compliance.md b/Skype/SfbServer/manage/persistent-chat/configure-compliance.md index 74c108badc..eba0007999 100644 --- a/Skype/SfbServer/manage/persistent-chat/configure-compliance.md +++ b/Skype/SfbServer/manage/persistent-chat/configure-compliance.md @@ -1,5 +1,5 @@ --- -title: "Configure the Compliance service for Persistent Chat Server in Skype for Business Server 2015" +title: "Configure the Compliance service for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,12 +12,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 24e36ea3-fb8a-45a4-b6b7-38c2e256b218 -description: "Summary: Learn how to configure the Persistent Chat Server Compliance service in Skype for Business Server 2015." +description: "Summary: Learn how to configure the Persistent Chat Server Compliance service in Skype for Business Server." --- -# Configure the Compliance service for Persistent Chat Server in Skype for Business Server 2015 +# Configure the Compliance service for Persistent Chat Server in Skype for Business Server -**Summary:** Learn how to configure the Persistent Chat Server Compliance service in Skype for Business Server 2015. +**Summary:** Learn how to configure the Persistent Chat Server Compliance service in Skype for Business Server. Persistent Chat compliance lets administrators maintain an archive of Persistent Chat messages as well as activities. The Compliance service records and archives data related to each Persistent Chat Server conversation, including when a participant: @@ -35,8 +35,6 @@ Persistent Chat compliance lets administrators maintain an archive of Persistent This information can be retrieved from the Compliance SQL database as needed. -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. ## Configure the Compliance service by using Windows PowerShell diff --git a/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md b/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md index 63bb968fb4..ea700180ef 100644 --- a/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md +++ b/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md @@ -1,5 +1,5 @@ --- -title: "Manage high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015" +title: "Manage high availability and disaster recovery for Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,17 +12,15 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: 4346e70b-ac48-4ab9-853e-3cdd6dcfe678 -description: "Summary: Learn how to manage Persistent Chat Server high availability and disaster recovery in Skype for Business Server 2015." +description: "Summary: Learn how to manage Persistent Chat Server high availability and disaster recovery in Skype for Business Server." --- -# Manage high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015 +# Manage high availability and disaster recovery for Persistent Chat Server in Skype for Business Server -**Summary:** Learn how to manage Persistent Chat Server high availability and disaster recovery in Skype for Business Server 2015. +**Summary:** Learn how to manage Persistent Chat Server high availability and disaster recovery in Skype for Business Server. -This topic describes how to fail over and fail back Persistent Chat Server. Before reading this topic, be sure to read [Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md) and [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md). +This topic describes how to fail over and fail back Persistent Chat Server. Before reading this topic, be sure to read [Plan for high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md) and [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md). -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. ## Fail over Persistent Chat Server @@ -158,7 +156,7 @@ These steps are designed to recover configuration as it existed prior to the dis - Click **OK** to begin the restoration process. -5. Configure SQL Server Log Shipping for the primary database. Follow the procedures in [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) to establish log shipping for the primary mgc database. +5. Configure SQL Server Log Shipping for the primary database. Follow the procedures in [Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) to establish log shipping for the primary mgc database. 6. Set the Persistent Chat Server active servers. From the Skype for Business Server Management Shell, use the **Set-CsPersistentChatActiveServer** cmdlet to set the list of active servers. diff --git a/Skype/SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md b/Skype/SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md index 9df0689987..e3f9a5e573 100644 --- a/Skype/SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md +++ b/Skype/SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md @@ -1,5 +1,5 @@ --- -title: "Monitor, start, and stop the Persistent Chat services in Skype for Business Server 2015" +title: "Monitor, start, and stop the Persistent Chat services in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,24 +12,22 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: b6b28595-f702-4ecf-8115-e4104b87da89 -description: "Summary: Learn how to start, stop, and monitor the Persistent Chat services in Skype for Business Server 2015." +description: "Summary: Learn how to start, stop, and monitor the Persistent Chat services in Skype for Business Server." --- -# Monitor, start, and stop the Persistent Chat services in Skype for Business Server 2015 +# Monitor, start, and stop the Persistent Chat services in Skype for Business Server -**Summary:** Learn how to start, stop, and monitor the Persistent Chat services in Skype for Business Server 2015. +**Summary:** Learn how to start, stop, and monitor the Persistent Chat services in Skype for Business Server. The Persistent Chat services and Persistent Chat Compliance services are part of the Skype for Business Server topology and can therefore be monitored, stopped, and started by using the following cmdlets: |Cmdlet|Function| |:-----|:-----| -|get-CsWindowsService
|Returns detailed information about Skype for Business Server 2015 components that run as Windows services.
| +|get-CsWindowsService
|Returns detailed information about Skype for Business Server components that run as Windows services.
| |start-CsWindowsService
|Starts the service.
| |stop-CsWindowsService
|Stops the service.
| -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. -For detailed information about how to use the cmdlets, see [Skype for Business Server 2015 Management Shell](../management-shell.md). +For detailed information about how to use the cmdlets, see [Skype for Business Server Management Shell](../management-shell.md). diff --git a/Skype/SfbServer/manage/persistent-chat/persistent-chat.md b/Skype/SfbServer/manage/persistent-chat/persistent-chat.md index 6be4124396..8d9f930919 100644 --- a/Skype/SfbServer/manage/persistent-chat/persistent-chat.md +++ b/Skype/SfbServer/manage/persistent-chat/persistent-chat.md @@ -1,5 +1,5 @@ --- -title: "Manage Persistent Chat Server in Skype for Business Server 2015" +title: "Manage Persistent Chat Server in Skype for Business Server" ms.reviewer: ms.author: serdars author: SerdarSoysal @@ -12,17 +12,15 @@ f1.keywords: - NOCSH ms.localizationpriority: medium ms.assetid: c58ee4f4-563b-4d0c-be91-c62df886caa9 -description: "Summary: Learn how to manage Persistent Chat Server in Skype for Business Server 2015." +description: "Summary: Learn how to manage Persistent Chat Server in Skype for Business Server." --- -# Manage Persistent Chat Server in Skype for Business Server 2015 +# Manage Persistent Chat Server in Skype for Business Server -**Summary:** Learn how to manage Persistent Chat Server in Skype for Business Server 2015. +**Summary:** Learn how to manage Persistent Chat Server in Skype for Business Server. -When you set up Persistent Chat Server for your organization, you specify the initial configuration during deployment. However, there may be times when you want to change how you implement Persistent Chat Server support. For example you may need to set up Persistent Chat Server support and controls differently for a specific team or group within your organization. This section provides information and procedures to help you customize your Persistent Chat Server deployment. For details about the features and functionality that you can configure for Persistent Chat Server, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). For details about deploying Persistent Chat Server, see [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md). +When you set up Persistent Chat Server for your organization, you specify the initial configuration during deployment. However, there may be times when you want to change how you implement Persistent Chat Server support. For example you may need to set up Persistent Chat Server support and controls differently for a specific team or group within your organization. This section provides information and procedures to help you customize your Persistent Chat Server deployment. For details about the features and functionality that you can configure for Persistent Chat Server, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). For details about deploying Persistent Chat Server, see [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md). -> [!NOTE] -> Persistent chat is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server 2015. You can manage Persistent Chat Server by using the Control Panel or by using Windows PowerShell cmdlets. @@ -34,7 +32,7 @@ To use the Control Panel: 3. In the left navigation bar, click **Persistent Chat**. -The following table summarizes the Windows PowerShell cmdlets available to help you manage Persistent Chat Server. For details about syntax, including all available parameters, see [Skype for Business Server 2015 Management Shell](../management-shell.md). +The following table summarizes the Windows PowerShell cmdlets available to help you manage Persistent Chat Server. For details about syntax, including all available parameters, see [Skype for Business Server Management Shell](../management-shell.md). |**Cmdlet**|**Description**| diff --git a/Skype/SfbServer/management-tools/planning-tool/persistent-chat.md b/Skype/SfbServer/management-tools/planning-tool/persistent-chat.md index 4224b9b106..ed09c3f106 100644 --- a/Skype/SfbServer/management-tools/planning-tool/persistent-chat.md +++ b/Skype/SfbServer/management-tools/planning-tool/persistent-chat.md @@ -4,7 +4,7 @@ ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars -ms.date: 3/27/2015 +ms.date: 11/08/2024 audience: ITPro ms.topic: article f1.keywords: @@ -20,5 +20,5 @@ description: "With Persistent Chat Server, users can participate in multiparty, Persistent Chat Server enables users to participate in multiparty, topic-based conversations that persist over time. -For more details about preparing your environment for Persistent Chat Server, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). +For more details about preparing your environment for Persistent Chat Server, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md). diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md index 90114b04d1..e39894eca4 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/capacity-planning.md @@ -25,9 +25,6 @@ Capacity planning is an important part of preparing to deploy Persistent Chat Se Before reading this section, you should be familiar with Persistent Chat topologies. For more information, see [Plan Persistent Chat Server topology](topology.md). -> [!NOTE] -> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. - ## Persistent Chat Server capacity planning The following tables can help you with capacity planning for Persistent Chat Server by modeling how various Persistent Chat Server settings affect capacity. diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md index c21885f67f..f713096c6c 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/categories-chat-rooms-and-user-roles.md @@ -27,9 +27,6 @@ You can control access to chat rooms by creating chat room categories, then spec - Administrator roles -> [!NOTE] -> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. - ## Categories for organizing chat rooms Categories let you organize chat rooms and control which users and groups are permitted to create or join the chat rooms within those categories. Each category has associated properties that determine the options available for the chat rooms within the category. You control access to a particular category by specifying whether a user is Allowed or Denied access. diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md index 4217fe63e5..9807955151 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md @@ -35,9 +35,6 @@ Before you deploy Persistent Chat Server, you must ensure that the following har The following sections describe the specific requirements for Persistent Chat Server and the database that stores the Persistent Chat data. -> [!NOTE] -> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. - ## Front End Server requirements Front End Server requirements depend on whether you are deploying Persistent Chat Server with Skype for Business Server Enterprise Edition or Standard Edition. diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md index 66fd17d228..a813968126 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/high-availability-and-disaster-recovery.md @@ -24,9 +24,6 @@ High availability and disaster recovery for Persistent Chat Server require addit > [!NOTE] > Using SQL AlwaysOn Availability Groups is not supported with Persistent Chat Server databases. -> [!NOTE] -> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. - ## Resource requirements Before configuring Persistent Chat Server for high availability and disaster recovery, ensure that you have the following additional resources. diff --git a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md index 042a414361..209ff654d6 100644 --- a/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md +++ b/Skype/SfbServer/plan-your-deployment/persistent-chat-server/persistent-chat-server.md @@ -33,8 +33,6 @@ Persistent Chat Server can help improve communication within your organization b - Following compliance regulations by optionally deploying the Persistent Chat Compliance service -> [!NOTE] -> Persistent chat is available in Skype for Business Server and in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here). If you need to use Persistent chat, your choices are to either migrate users requiring this functionality to Teams, or to continue using Skype for Business Server. ## Persistent Chat Server high-level architecture From c63ef53c436e66c236cdf9ed259866c4fa06f667 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Thu, 17 Oct 2024 15:15:46 +0530 Subject: [PATCH 35/87] fixed warnings and suggestion --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 32 +++++++++---------- ...high-availability-and-disaster-recovery.md | 2 +- 2 files changed, 17 insertions(+), 17 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 3d20aa6b0d..5528dd3335 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -790,22 +790,22 @@ - name: Disable TLS 1.0/1.1 href: ../../SfbServer/manage/topology/disable-tls-1.0-1.1.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Persistent Chat - href: ../../SfbServer/manage/persistent-chat/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - items: - - name: Categories - href: ../../SfbServer/manage/persistent-chat/categories.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Chat rooms - href: ../../SfbServer/manage/persistent-chat/chat-rooms.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Configure add-ins - href: ../../SfbServer/manage/persistent-chat/configure-add-ins.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Configure Compliance - href: ../../SfbServer/manage/persistent-chat/configure-compliance.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Back up and restore databases - href: ../../SfbServer/manage/persistent-chat/back-up-and-restore-databases.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: High availability and disaster recovery - href: ../../SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Monitor, start, and stop services - href: ../../SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + href: ../../SfbServer/manage/persistent-chat/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: Categories + href: ../../SfbServer/manage/persistent-chat/categories.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Chat rooms + href: ../../SfbServer/manage/persistent-chat/chat-rooms.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure add-ins + href: ../../SfbServer/manage/persistent-chat/configure-add-ins.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure Compliance + href: ../../SfbServer/manage/persistent-chat/configure-compliance.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Back up and restore databases + href: ../../SfbServer/manage/persistent-chat/back-up-and-restore-databases.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: High availability and disaster recovery + href: ../../SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Monitor, start, and stop services + href: ../../SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Health and monitoring href: ../../SfbServer/manage/health-and-monitoring/health-and-monitoring.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: diff --git a/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md b/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md index ea700180ef..78a67c2896 100644 --- a/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md +++ b/Skype/SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md @@ -169,4 +169,4 @@ To restore the pool to its normal state run the following Windows PowerShell com Set-CsPersistentChatState -Identity "service: lyncpc.dci.discovery.com" -PoolState Normal ``` -For more information, see the help topic for the [Set-CsPersistentChatState](/powershell/module/skype/set-cspersistentchatstate?view=skype-ps) cmdlet. +For more information, see the help topic for the [Set-CsPersistentChatState](/powershell/module/skype/set-cspersistentchatstate) cmdlet. From ca0af3cd3ef0f41320eb29774f3c64148ed0a8eb Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Thu, 17 Oct 2024 15:35:20 +0530 Subject: [PATCH 36/87] fixed aligning --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 34 ++++++++++++------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 5528dd3335..01578717ac 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -789,23 +789,23 @@ href: ../../SfbServer/manage/topology/move-file-store-data.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Disable TLS 1.0/1.1 href: ../../SfbServer/manage/topology/disable-tls-1.0-1.1.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat - href: ../../SfbServer/manage/persistent-chat/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - items: - - name: Categories - href: ../../SfbServer/manage/persistent-chat/categories.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Chat rooms - href: ../../SfbServer/manage/persistent-chat/chat-rooms.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Configure add-ins - href: ../../SfbServer/manage/persistent-chat/configure-add-ins.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Configure Compliance - href: ../../SfbServer/manage/persistent-chat/configure-compliance.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Back up and restore databases - href: ../../SfbServer/manage/persistent-chat/back-up-and-restore-databases.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: High availability and disaster recovery - href: ../../SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Monitor, start, and stop services - href: ../../SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat + href: ../../SfbServer/manage/persistent-chat/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: Categories + href: ../../SfbServer/manage/persistent-chat/categories.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Chat rooms + href: ../../SfbServer/manage/persistent-chat/chat-rooms.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure add-ins + href: ../../SfbServer/manage/persistent-chat/configure-add-ins.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Configure Compliance + href: ../../SfbServer/manage/persistent-chat/configure-compliance.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Back up and restore databases + href: ../../SfbServer/manage/persistent-chat/back-up-and-restore-databases.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: High availability and disaster recovery + href: ../../SfbServer/manage/persistent-chat/high-availability-and-disaster-recovery.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Monitor, start, and stop services + href: ../../SfbServer/manage/persistent-chat/monitor-start-and-stop-services.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Health and monitoring href: ../../SfbServer/manage/health-and-monitoring/health-and-monitoring.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: From 04604426f0b333e6d1cb05dae25c90c94ab311b1 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Thu, 17 Oct 2024 15:42:01 +0530 Subject: [PATCH 37/87] correction in levels --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 01578717ac..4dbe9883b3 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -1139,10 +1139,8 @@ - name: Skype for Business Server Capacity Planning Calculator href: ../../SfbServer/management-tools/capacity-planning-calculator.md - name: Planning Tool - href: ../../SfbServer/management-tools/planning-tool/planning-tool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: - name: UI Reference - href: ../../SfbServer/management-tools/planning-tool/ui-reference.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json items: - name: Persistent Chat href: ../../SfbServer/management-tools/planning-tool/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json From 7a05b8694184e1d03e55b18774d370154ae9291d Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 09:35:15 -0700 Subject: [PATCH 38/87] Adding new articles for Teams Phones --- Teams/phones/qos-on-teams-phones.md | 112 +++++++++ .../remote-provision-remote-login-phones.md | 116 +++++++++ .../remote-sign-in-and-sign-out-phones.md | 53 ++++ Teams/phones/remote-update-teams-phones.md | 226 ++++++++++++++++++ Teams/toc.yml | 6 +- 5 files changed, 510 insertions(+), 3 deletions(-) create mode 100644 Teams/phones/qos-on-teams-phones.md create mode 100644 Teams/phones/remote-provision-remote-login-phones.md create mode 100644 Teams/phones/remote-sign-in-and-sign-out-phones.md create mode 100644 Teams/phones/remote-update-teams-phones.md diff --git a/Teams/phones/qos-on-teams-phones.md b/Teams/phones/qos-on-teams-phones.md new file mode 100644 index 0000000000..a5233139a7 --- /dev/null +++ b/Teams/phones/qos-on-teams-phones.md @@ -0,0 +1,112 @@ +--- +title: Quality of service (QoS) configuration on Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: mattslomka +ms.date: 10/17/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn about the key considerations for deploying Quality of Service (QoS) on your network to support Teams phones. +--- + +# Quality of service (QoS) set up on Teams phones + +Deploying one or many Microsoft Teams Rooms devices requires planning. One of the key considerations is your organization's network capacity and quality of service (QoS) configuration. + +This article explains: + +1. [How much bandwidth does a Microsoft Teams Rooms device use?](#how-much-bandwidth-does-a-microsoft-teams-rooms-device-use) +1. [How to control that bandwidth usage?](#how-do-i-control-microsoft-teams-rooms-bandwidth-usage) +1. [How to ensure your devices are optimized with the right quality of service (QoS) configuration to align to your organizations requirements?](#quality-of-service-qos-with-microsoft-teams-rooms) + +Wired network connectivity is recommended for Microsoft Teams Rooms devices. If wireless network connectivity is the only option, see best practice guidance [here](../rooms/rooms-prep.md#wireless-network-considerations). + +## How much bandwidth does a Microsoft Teams Rooms device use? + +Microsoft Teams Rooms is designed to give the best audio, video, and content-sharing experience regardless of your network conditions. That said, when bandwidth is insufficient, Teams prioritizes traffic in the following order: audio, content sharing, lastly participant video. + +Where bandwidth isn't limited, Teams optimizes media quality, including high-fidelity audio, up to 1080p video resolution, and up to 30 fps (frames per second) for video and content. + +The following table provides rough estimates of bandwidth utilized for the various streams in *kbps* (down/up) + + +|Feature |Standard |Advanced | +|---------|---------|---------| +|Audio | 128/128 | 256/256 | +|Video | 2000/4000 |8000/4000 | +|Screen share | 2000/2000 | 2000/2000 | +|**Total** | **4128/6128** |**10256/6256** | + + +Teams Rooms can support up to 18 individual incoming video streams, up to five outbound video streams, and content sharing either inbound or outbound. The number of streams consumed by the Teams Rooms device can have a large impact on the downstream bandwidth consumed, and the capabilities of the connected Teams Rooms camera can impact the outbound bandwidth usage. Bandwidth consumption can also vary with the number and resolution of the videos from remote participants connected to the meeting. + +## How do I control Microsoft Teams Rooms bandwidth usage? + +By default, Teams Rooms don't have a bandwidth-limiting policy. If you wish to implement one, we recommend allocating 10 Mbps to each Teams Rooms resource account. This implementation can be accomplished by assigning a Teams meeting policy with a media bitrate limit configured. When setting the meeting policy at 10 Mbps, Teams Rooms still only use the bandwidth required for the meeting (typically 3-4 Mbps), and dynamically adjusts if its network connection isn't able to sustain 10 Mbps. + +For information on how to configure a Teams meeting policy, see [Meeting policy settings for audio and video](../meeting-policies-audio-and-video.md). You want to create a custom policy and assign it to all Microsoft Teams Rooms resource accounts, with the limit for media bitrate configured for 10,000 kbps. + +## Quality of Service (QoS) with Microsoft Teams Rooms + +Microsoft Teams Rooms supports Quality of Service (QoS) Differentiated Services Code Point (DSCP) markings to ensure you can manage the media traffic on your corporate network. + +We recommend the following QoS markings and port ranges for the audio, video, and application/screen sharing types of media traffic: + +**Audio**: + +- Client source port range: **50,000-50,019** +- Protocol: **TCP/UDP** +- DSCP value: **46** +- DSCP class: **Expedited Forwarding (EF)** + +**Video**: + +- Client source port range: **50,020-50,039** +- Protocol: **TCP/UDP** +- DSCP value: **34** +- DSCP class: **Assured Forwarding (AF41)** + +**Application/screen sharing**: + +- Client source port range: **50,040-50,059** +- Protocol: **TCP/UDP** +- DSCP value: **18** +- DSCP class: **Assured Forwarding (AF21)** + +For more information on Teams Media and implementing QoS, see [Implement Quality of Service (QoS) in Microsoft Teams](../QoS-in-Teams.md). + +### QoS with Microsoft Teams Rooms on Windows devices + +For Teams Rooms on Windows devices, you must configure Windows to add DSCP markings to the Teams Rooms application traffic. We recommend using Microsoft Intune to apply a Network QoS policy to Teams Rooms devices. You can use the Intune `NetworkQoSPolicy` configuration service provider (CSP) to apply the configuration based on the port ranges and DSCP value shown in [Quality of Service (QoS) with Microsoft Teams Rooms](#quality-of-service-qos-with-microsoft-teams-rooms). + +For more information on this Intune CSP, see [NetworkQoSPolicy CSP](/windows/client-management/mdm/networkqospolicy-csp). + +If your Teams Rooms devices are joined to Active Directory, you can use Group Policy to apply the markings. Follow the instructions for the Teams Desktop application, but don't specify the application name in the configuration; only specify the port range and the DSCP value in the configuration. + +For more information, see [Implement Quality of Service (QoS) in Microsoft Teams clients](../QoS-in-Teams-clients.md). + +### QoS with Microsoft Teams Rooms on Android devices + +For Teams Rooms on Android devices, you need to configure your Microsoft Teams tenant to insert QoS markings. Teams Rooms on Android devices honor this policy and apply the markings defined earlier in [Quality of Service (QoS) with Microsoft Teams Rooms](#quality-of-service-qos-with-microsoft-teams-rooms) with one exception, Application/screen sharing uses a DSCP value of 34 (AF41) aligned to video traffic. + +For instructions on how to configure your tenant to insert QoS markings, see [Teams settings and policies reference](../settings-policies-reference.md). + +## Related articles + +- [Implement Quality of Service (QoS) in Microsoft Teams](../QoS-in-Teams.md) +- [Implement Quality of Service (QoS) in Microsoft Teams clients](../QoS-in-Teams-clients.md) +- [Configure the NetworkQoSPolicy CSP](/windows/client-management/mdm/networkqospolicy-csp) +- [Prepare your organization's network for Microsoft Teams](../prepare-network.md) diff --git a/Teams/phones/remote-provision-remote-login-phones.md b/Teams/phones/remote-provision-remote-login-phones.md new file mode 100644 index 0000000000..2b4ff9f88b --- /dev/null +++ b/Teams/phones/remote-provision-remote-login-phones.md @@ -0,0 +1,116 @@ +--- +title: Remote provisioning and sign in for Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: vapati +ms.date: 10/17/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn how to remotely provision and sign in to Teams phones that are deployed in your organization. +--- + +# Remote provisioning and sign in for Teams phones + +IT admins can remotely provision and sign in to a Teams Android device includiong Teams phones. To provision a Teams pohone remotely, the admin needs to upload the MAC IDs of the devices being provisioned and create a verification code. The entire process can be completed remotely from the Teams admin center. + +> [!NOTE] +> Once you've signed in to a Teams phone, this feature isn't available. To use it again, the device must be reset to factory default settings. + +## Supported devices + +All Android and SIP devices certified by Microsoft can be provisioned remotely from Teams admin center. + +Refer to the following for the list of certified hardware: + +Teams phones - [Certified Teams phones](../devices/teams-phones-certified-hardware.md) +Teams panels - [Certified Teams panels](../devices/teams-panels-certified-hardware.md) +Microsoft Teams Rooms on Android - [Teams Rooms on Android certified devices](../devices/certified-hardware-android.md?tabs=Android) +SIP devices - [Teams compatible devices](./sip-gateway-plan.md#compatible-devices) + +## Add a device MAC address + +Complete the following steps to provision a new device. + +1. Sign in to the Teams admin center. +2. Expand **Teams Devices**. +3. Select **Provision new device** from the **Actions** tab. + +In the **Provision new devices** window, you can either add the MAC address manually or upload a file. + +### Manually add a device MAC address + +1. From the **Waiting on activation** tab, select **Add MAC ID**. + + :::image type="content" alt-text="Screenshot of 'Add MAC address' for manually adding a the MAC address for a device." source="../media/remote-provision-6-new.png" lightbox="../media/remote-provision-6-new.png"::: + +1. Enter the MAC ID. +1. Enter a location, which helps technicians identify where to install the devices. +1. Select **Apply** when finished. + +### Upload a file to add a device MAC address + +1. From the **Waiting on activation** tab, select **Upload MAC IDs**. +2. Download the file template. +3. Enter the MAC ID and location, and then save the file. +4. **Select file**, and then select **Upload**. + +## Generate a verification code + +You need a verification code for the devices. The verification code is generated in bulk or at the device level and is valid for 24 hours. + +1. From the **Waiting on activation** tab, select an existing MAC ID. + A password is created for the MAC address and is shown in the **Verification Code** column. + +2. Provide the list of MAC IDs and verification codes to the field technicians. You can export the detail directly in a file and share the file with the technician who is doing the actual installation work. + +## Provision the device + +When the device is powered on and connected to the network, the technician provisions the device. These steps are completed on the Teams device. + +1. The technician selects **Provision device** from the **Settings**. + + ![Provision new device option from the Actions tab.](../media/provision-device1.png) + +2. The technician enters the device-specific verification code in the provided input field. + + ![Provision new device verification.](../media/provision-device-verification1.png) + + Once the device is provisioned successfully, the tenant name appears on the sign-in page. + + ![Tenant name on sign-in page.](../media/provision-code.png) + +## First time remote sign in + +The provisioned device appears in the **Waiting for sign in** tab. Start the remote sign-in process by selecting the individual device. + +1. Select a device from the **Waiting for sign in** tab. + + ![The window with a list of devices ready for sign in.](../media/remote-device1.png) + +2. Follow the instructions in **Sign in a user**, and then select **Close**. + + ![The Sign in a user window for individual device.](../media/sign-in-user.png) + + This video shows how admins can remotely provision Android-based and SIP devices. + + > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fRYe?autoplay=false] + +## Related articles + +- [Manage your devices in Teams](../rooms/device-management.md) +- [Remote sign in and sign out](../devices/remote-sign-in-and-sign-out.md) +- [Update Teams devices remotely](../devices/remote-update.md) + diff --git a/Teams/phones/remote-sign-in-and-sign-out-phones.md b/Teams/phones/remote-sign-in-and-sign-out-phones.md new file mode 100644 index 0000000000..f740ea40ac --- /dev/null +++ b/Teams/phones/remote-sign-in-and-sign-out-phones.md @@ -0,0 +1,53 @@ +--- +title: Remote sign in and sign out for Teams Android devices +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: ayerragangu +ms.date: 09/17/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn how to remotely sign in and sign out of Teams Android devices. +--- + +# Remote sign in and sign out for Teams Android devices + +This article describes how to remote sign in and sign out Teams Android devices from the Teams admin center. If you haven't provisioned a device yet, or the device is provisioned but has never been signed-in, see [Remote provisioning and sign in for Teams Android devices](remote-provision-remote-login.md). + +This video shows how to sign into Teams devices. + +> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fHGR?autoplay=false] + +## Remote sign in + +After a device is provisioned and signed in for the first time, it will appear on its corresponding page under the **Teams devices** node of the Teams admin center. + +To sign in a device that has been signed out, go to the corresponding device page. + +1. Select the device you want to sign in. + +2. Go to the **Actions** menu, and select **Sign in a user**. + +## Remote sign out + +1. Select the device you want to sign out from the corresponding page. + +2. Go to the **Actions** menu, and select **Sign out**. + +## Related articles + +- [Remote provisioning and sign in for Teams Android devices](remote-provision-remote-login.md) +- [Manage your devices in Teams](device-management.md) +- [Update Teams devices remotely](remote-update.md) diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md new file mode 100644 index 0000000000..eb3f3c32cd --- /dev/null +++ b/Teams/phones/remote-update-teams-phones.md @@ -0,0 +1,226 @@ +--- +title: Updating Teams phones remotely +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: vapati +ms.date: 09/13/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +description: Learn how to remotely update the firmware and apps for Teams phones using the Teams admin center. +--- + +# Remotely update firmware and software on Teams phones + +Using Teams admin center, you can update your Teams devices, including Teams phones, Teams panels, and Teams Rooms that run on Android remotely. The following software components on your device can be updated from within Teams admin center: + +- **Teams app** - available for Manual and Automatic updates + +- **Device firmware** - available for Manual and Automatic updates + +- **Company Portal app** - available for Manual updates only + +Updates for Teams app and device firmware happen automatically by default. However, you can update them manually as well. When you're applying updates manually, they can be applied immediately or scheduled to be updated on a future date and time that you set. + +> [!IMPORTANT] +> Microsoft strongly recommends using Teams Admin Center for managing and updating your Teams devices. Teams admin center ensures that all firmware and app updates installed on your Teams devices are validated and supported by Microsoft, which is essential for optimal performance and reliability of your Teams devices. By exclusively using firmware and app updates from the Teams Admin Center, you can avoid the risks and disruptions associated with alternative update methods. If customers use any other way to update, Microsoft can't guarantee to provide regular updates for those devices. +## Software versions on Teams admin center + +All new software versions for Teams devices are made available on Teams admin center once they're published by Microsoft. New releases might have minimum software version requirements. In such cases, the new version is only made available if the device meets the requirements. Verify that the device is meeting those requirements, but especially the firmware is current and updated. + +Only software versions that have been tested by Microsoft are available for automatic or manual updates using Teams admin center. Software versions tested by Microsoft are labeled **Verified by Microsoft**. + +Additionally, earlier versions of the software may also be made available and are labeled as **Microsoft Preview**. Devices can be manually updated to Microsoft Preview versions that are released, and those devices running on these versions are also eligible for receiving automatic updates in future. + +Firmware versions that have not been tested by Microsoft are labeled **Unknown version**. Devices running an unknown firmware version can't be automatically updated. These devices can only be updated manually. + +Refer to this list for the details on new releases and the requirements that must be met. + +**Phone** - [Phone - Devices for Teams | Product release information](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-phones) + +**Displays** - [Displays - Devices for Teams | Product release information](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-displays) + +**Panels** - [Panels - Devices for Teams | Product release information](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-panels) + +**Microsoft Teams Rooms on Android** - [Microsoft Teams Rooms on Android Product release information](/microsoftteams/rooms/android-app-firmware) + +## Automatic updates + +### Assign devices to update phases + +Assigning devices to an automatic update phase is a Teams Rooms Pro feature for Teams Rooms on Android devices. Devices with a Teams Rooms Basic license are assigned to the General phase. Any preconfigured phases are maintained, and no further changes are allowed. For more information, see [Microsoft Teams Rooms licenses](../rooms/rooms-licensing.md). + +Automatic updates of Teams devices using the Teams admin center isn't available in GCC High and DoD. Organizations in GCC High and DoD can, however, [manually update Teams devices](#manually-update-remote-devices) using the Teams admin center. + +> [!NOTE] +> Some devices don't support automatic updates yet. Applying automatic update settings on devices that don't support automatic updates won't have any effect on those devices. For questions about whether your device will support automatic updates, contact your device manufacturer. +Devices within a phase will be updated gradually over a few weeks rather than all at once. To choose the automatic update phase for your devices, do the following steps: + +1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. +2. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +3. Select one or more devices and then select **Update**. +1. Under **Automatic updates**, select one of the following phases: + - **Validation** This option is best for lab or test devices on which you can carry out any validation you need to perform. Updates start deployment as soon as the latest software version is released. Previously called **As soon as possible**. + - **General** This is the default option and is best for most of your general-purpose devices. Firmware updates start deployment only after **30 days** from the release of the new firmware version. Teams app updates start deployment only after **15 days** from the release of the new Teams app version. Previously called **Defer by 30 days** (applicable for firmware updates). + - **Final** This option is best for devices used by VIPs and in large settings after large-scale validation is complete. Firmware updates start deployment only after **90 days** from the release of the new firmware version. Teams app updates start deployment only after **45 days** from the release of the new Teams app version. Previously called **Defer by 90 days** (applicable for firmware updates). + +5. Select **Update**. + +To see which phase a device is in, see the **Automatic updates** column in the Teams admin center. To see which devices are part of a specific phase, use the **Filter** option then select **Auto-update phase**. + +If you need to revert or remove firmware from a device that has been updated, you need to reset your device to its factory settings. Reset your device using the instructions from its manufacturer. + +### Configure Maintenance window +If you want to configure the Maintenance window for a device, do the following steps: + +1. Sign in to Microsoft Teams admin center by going to *https://admin.teams.microsoft.com*. + +1. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +1. Follow the steps for [editing or creating a new configuration profile.](../devices/device-management.md#use-configuration-profiles-in-teams) + +1. Specify a suitable **Time window** by selecting a **Start time** and an **End time**. This time window follows the local timezone of the device. + + 1. The default Time Window is from **01:00 Hrs** to **04:00 Hrs**. + + 1. A minimum time window of 3 hours must be selected. + +1. Specify the **Update frequency** by selecting the days of the week that are suitable for carrying out updates on the devices when available. + +1. Default selection is for **Sunday**. + +1. Once the selection is done, **Save** the profile. If it's a new profile, you can **Assign** it to devices. If you're editing an existing profile, it automatically gets reapplied to the devices to which it's assigned. + +1. You can check the selected Maintenance window settings under the **Details** tab on the device page. + + +Automatic updates, when they happen, utilize the maintenance window configured for the device, that is, the **Time window** on the selected days for **Update frequency**. Maintenance window can also be utilized for scheduling manual updates. + +Option to configure maintenance window isn't available in GCC-High and DoD. + +> [!NOTE] +> If an update operation is unable to start execution within the maintenance window it is scheduled for, it is cancelled and rescheduled for the next available maintenance window. + +### Track automatic updates + +If you want to check which software versions are currently rolling out for your devices, do the following steps: + +1. Sign in to Microsoft Teams admin center by going to *https://admin.teams.microsoft.com*. +2. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +3. Refer to the widget titled **Software auto-updates** to determine the number of active update paths. +4. On this widget, select **View details**. A dialogue box opens showing the list of active update paths with the following details: + + - Device model and manufacturer + - Current version and new version + - Number of eligible devices + - Active phase + - Devices assigned to this update phase are being currently updated. Any device from a previous phase that isn't updated yet will also be included. + - Software component name + +> [!NOTE] +> The new version may not always be the latest available version. Devices running older versions may be updated in a step-wise approach, until they reach the latest version. + +### Pause automatic updates + +You can temporarily pause automatic updates for your tenant. When paused, Android based devices aren't automatically updated for the next 15 days. To pause the updates, do the following steps: + +1. Sign in to Microsoft Teams admin center by visiting https://admin.teams.microsoft.com. +2. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +3. Under the **Actions** menu, select **Pause auto-updates**. +1. Updates automatically resume after 15 days. If you want to resume the updates before that, select **Resume auto-updates** from under the **Actions** menu. + +## Manually update remote devices + +If you want to manually update devices using the Teams admin center, you can decide whether to update the devices immediately or schedule an update for a future date and time. + +To manually update remote devices, do the following steps: + +1. Sign in to Microsoft Teams admin center by visiting https://admin.teams.microsoft.com. +1. Navigate to **Teams Devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +3. Select one or more devices and then select **Update**. +1. Under **Manual updates**, select **Schedule** if you want to schedule the update for the upcoming **Maintenance window** or a future date and time. The updates are applied at the date and time in the timezone selected in **Timezone**. + +What you see depends on whether you have one, or multiple, devices selected. The left image below shows a single device selected while the image on the right shows multiple devices selected. + +![Device status update panel with single and multiple devices selected.](../media/mtr-devices/update-manual-together.png) + +When you select multiple devices, you can choose which update types to apply to each selected device. Select the update types you want to apply and select **Update**. + +When you select a single device, updates that are available for the device are shown. If multiple update types are available for the device, select each update type to apply. You can view the **Current version** applied on the device and the **New version** that will be applied. Select the update(s) you want to apply and select **Update**. + +After you select **Update**, updates are applied to your devices at the date and time of the selected scheduling option. If you didn't select a future date and time, updates are applied to your devices within a few minutes. + +To manage devices, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](./using-admin-roles.md). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +This video shows how to update Teams devices. + +> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fxbK?autoplay=false] + +## App updates for paired devices + +The app updates for paired Microsoft Teams Rooms running Android and their paired touch consoles happen in sync to ensure a streamlined experience. This is applicable for the following software components - + +- Teams app + +- Company Portal app + +This is applicable for both automatic and manual updates. + +**For manual updates** - Whenever an update is being done for Microsoft Teams Rooms running Android or a Touch console, the paired device will also be updated. If an update is being scheduled for later, it will be scheduled for the same time on the paired device. + +**For automatic updates** - Automatic updates for Microsoft Teams Rooms on Android and their paired consoles also happen in sync. Automatic updates rollout according to the timeline dictated by the [Update phases](../devices/remote-update.md#assign-devices-to-update-phases). Touch consoles are updated according to the update phase of their paired Microsoft Teams Rooms on Android. There is no impact if both devices are in the same phase. If they are in different phases, the phase of the Teams Rooms on Android takes precedence. + +#### Conditions for updates to happen during sync + +- If Microsoft Teams Rooms on Android device and the paired touch console(s) are on the same version and have an update available, they are both updated in sync when one of them is updated. +- If Microsoft Teams Rooms on Android and the paired touch console(s) are on different versions - + - **Manual updates** - Administrators should ensure that the device(s) on the lower version is brought to parity for the devices to be updated in sync to the new version. + - **Automatic updates** - The device(s) on the lower version will be first brought to parity automatically. Once the devices are on the same version, they will be updated to the new version together. In this scenario, the move to the new version may be delayed as the parity updates will happen first. This is done to minimize conflicts between MTRoA and the paired console(s). + +#### Tracking update status + +Administrators can track the status of these update operations from the 'History' section in the device page. Details for each operation are shown in the relevant row, including, if the operation was carried out for a paired device. More details are available on selecting the operation status. + +## Frequently asked questions about automatic updates + +1. **Which software components are automatically updated?** Both Firmware and Teams app are automatically updated for eligible devices. Automatic updates for Teams app is a feature still in early phase, therefore you might see some delays in device reaching the update phase. The gradual roll out of the feature is being done to ensure minimal impact on devices. + +1. **What makes a device eligible to receive automatic updates?** The following conditions should be satisfied for the device to be eligible for automatic updates: + - Device model should be certified. See: + - Teams phones - [Certified Teams phones](../devices/teams-phones-certified-hardware.md) + - Teams panels - [Certified Teams panels](../devices/teams-panels-certified-hardware.md) + - Microsoft Teams Rooms on Android - [Teams Rooms on Android certified systems and peripherals](../devices/certified-hardware-android.md?tabs=Android) + - Current version should be 'Verified by Microsoft'. For more details, see [Software versions](#software-versions-on-teams-admin-center). + - Devices on versions that were released before 2022 generally do not have auto-update support. + +1. **How fast does the rollout happen?** Eligible devices receive updates in weekly cycles based on the update phase they are in. For example, devices in General phase start receiving updates only after 15/30 days elapse since the new version was published. To ensure a stable rollout, the devices are updated gradually for a tenant and not all at once. Overall, the rollout of each new version takes a few weeks after the start of each update phase. + +Also, if the device is on an older version, like N-3. It is updated step-wise to intermediate versions, like N-2 and N-1, before it is updated to the latest version (N). Therefore, this device may take longer to reach the latest version than usual, but no intervention is required. + +1. **How do I check if a device has received an update?** Whenever a device receives an update (or has one scheduled), the History tab on the device page shows corresponding details for a software update operation. + +1. **I see that the updates are happening but they are failing. What do I do?** Sometimes the updates can fail due to transient conditions. In such cases, no intervention is required. Updates are automatically retried on the devices. If updates are consistently failing across your inventory, you can check a few things: + + - Devices are online at the time when updates are scheduled. + - Network configuration is done appropriately to allow download of updates. Refer to [URLs and IP address ranges for Microsoft Teams](/microsoft-365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams) for the URLs and IP address ranges that need to be allowed for Teams. + - If this doesn't help, reach out to Microsoft support with the logs. Device logs can be found in the History tab of the device page. They are linked to the Device diagnostics operation that is run with the software update operation. + +1. **The eligible count of devices does not seem to match the available devices.** The device count in **Automatic software updates** section shows the number of eligible devices that are ready to be updated. The devices that are already updated to the **New version** are not counted. It can also include devices from the previous phase that are not updated. + +1. **When do automatic updates happen?** The updates are scheduled to happen during the Maintenance window to minimize impact. If the device is offline at that time, the updates get executed when the device comes back online the next time. If the Maintenance window is already over, the update is rescheduled for the next available window. + +1. **Why do Teams app and Firmware follow a different cadence in update phases?** Updates phases allow Firmware auto-updates to start immediately (Validation phase), only after 30 days (General phase), or only after 90 days (Final phase). Since Firmware changes include significant changes, their rollout through auto-update is done at a slow pace to ensure minimal impact. On the other hand, the update phases allow Teams app to start immediately (for Validation phase), only after 15 days (for General phase), or only after 45 days (for Final phase). Teams app versions include smaller scope of changes for the devices than the Firmware and hence their auto-update rollout is done at a faster pace to bring the devices to recent versions. + diff --git a/Teams/toc.yml b/Teams/toc.yml index 9bb58f57ec..bb4854e876 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1614,15 +1614,15 @@ items: - name: Step 4 - Set up Teams phones items: - name: Remote provisioning - href: devices/remote-provision-remote-login.md + href: phones/remote-provision-remote-login-phones.md - name: Remote sign in and sign out - href: devices/remote-sign-in-and-sign-out.md + href: phones/remote-sign-in-and-sign-out-phones.md - name: Manage items: - name: Manage Teams phones href: phones/manage-teams-phones.md - name: Update management - href: devices/remote-update.md + href: phones/remote-update-phones.md - name: Troubleshooting and known issues items: - name: Troubleshooting and known issues From d0a6e6501911ef50c5fa8334bd92416d151b4f68 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 09:44:48 -0700 Subject: [PATCH 39/87] Update toc.yml --- Teams/toc.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Teams/toc.yml b/Teams/toc.yml index bb4854e876..ca51689341 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1597,6 +1597,8 @@ items: items: - name: Prepare your network href: phones/prepare-network-teams-phones.md + - name: Quality of Service (QOS) for Teams phones + href: phones/qos-teams-phones.md - name: Intune Enrollment for Teams phones items: - name: Device administration From 817104f78b14d6157b215efcb470e90a993e7b87 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 09:48:25 -0700 Subject: [PATCH 40/87] Update toc.yml --- Teams/toc.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index ca51689341..ffd8f8e37a 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1631,11 +1631,11 @@ items: href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android - name: Bring your own device (BYOD) spaces items: - - name: Bring Your Own Device (BYOD) + - name: BYOD rooms href: rooms/bring-your-own-device.md - name: Bookable desks href: rooms/bookable-desks.md - - name: Add peripherals to inventory + - name: Set up your BYOD inventory href: rooms/get-peripheral-information.md - name: SIP Gateway items: From b179aff21eb953744647f8d179b15bca261651d3 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 11:28:27 -0700 Subject: [PATCH 41/87] fixing links and errors --- .openpublishing.redirection.json | 15 +++++++++++++++ Teams/{ => devices}/sip-gateway-configure.md | 0 .../{ => devices}/sip-gateway-dynamic-filters.md | 0 Teams/{ => devices}/sip-gateway-plan.md | 0 .../authentication-best-practices-phones.md | 2 +- .../{devices => phones}/media/sign-in-teams.png | Bin Teams/{devices => phones}/media/teams-apps-1.png | Bin Teams/phones/plan-device-deployment.md | 4 ++-- .../remote-provision-remote-login-phones.md | 4 ++-- .../phones/remote-sign-in-and-sign-out-phones.md | 14 +++++++------- Teams/phones/remote-update-teams-phones.md | 3 +-- Teams/toc.yml | 4 ++-- 12 files changed, 30 insertions(+), 16 deletions(-) rename Teams/{ => devices}/sip-gateway-configure.md (100%) rename Teams/{ => devices}/sip-gateway-dynamic-filters.md (100%) rename Teams/{ => devices}/sip-gateway-plan.md (100%) rename Teams/{devices => phones}/media/sign-in-teams.png (100%) rename Teams/{devices => phones}/media/teams-apps-1.png (100%) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 45817b2e8a..1e9f2c2df8 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5359,6 +5359,21 @@ "source_path": "Teams/devices/common-area-mobile-phones.md", "redirect_url": "/microsoftteams/phones/common-area-mobile-phones", "redirect_document_id": false +}, +{ + "source_path": "Teams/sip-gateway-configure.md", + "redirect_url": "/microsoftteams/devices/sip-gateway-configure", + "redirect_document_id": false +}, +{ + "source_path": "Teams/sip-gateway-plan.md", + "redirect_url": "/microsoftteams/devices/sip-gateway-plan", + "redirect_document_id": false +}, +{ + "source_path": "Teams/sip-gateway-dynamic-filters.md", + "redirect_url": "/microsoftteams/devices/sip-gateway-dynamic-filters", + "redirect_document_id": false } ] } \ No newline at end of file diff --git a/Teams/sip-gateway-configure.md b/Teams/devices/sip-gateway-configure.md similarity index 100% rename from Teams/sip-gateway-configure.md rename to Teams/devices/sip-gateway-configure.md diff --git a/Teams/sip-gateway-dynamic-filters.md b/Teams/devices/sip-gateway-dynamic-filters.md similarity index 100% rename from Teams/sip-gateway-dynamic-filters.md rename to Teams/devices/sip-gateway-dynamic-filters.md diff --git a/Teams/sip-gateway-plan.md b/Teams/devices/sip-gateway-plan.md similarity index 100% rename from Teams/sip-gateway-plan.md rename to Teams/devices/sip-gateway-plan.md diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md index 128320b3bc..0b7579bde2 100644 --- a/Teams/phones/authentication-best-practices-phones.md +++ b/Teams/phones/authentication-best-practices-phones.md @@ -85,7 +85,7 @@ If shared Teams phones are provisioned in a well-defined location that can be id If you're enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams devices can be configured for Conditional Access policies based on device compliance. For more information, see [Conditional Access: Require compliant or Microsoft Entra hybrid joined device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device). -To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/intune/protect/device-compliance-get-started). +To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). >[!NOTE] > Shared devices being used for *hot-desking* should be excluded from compliance policies. Compliance polices prevent the devices from enrolling into the hot desk user account. **Instead, use named locations to secure these devices**. diff --git a/Teams/devices/media/sign-in-teams.png b/Teams/phones/media/sign-in-teams.png similarity index 100% rename from Teams/devices/media/sign-in-teams.png rename to Teams/phones/media/sign-in-teams.png diff --git a/Teams/devices/media/teams-apps-1.png b/Teams/phones/media/teams-apps-1.png similarity index 100% rename from Teams/devices/media/teams-apps-1.png rename to Teams/phones/media/teams-apps-1.png diff --git a/Teams/phones/plan-device-deployment.md b/Teams/phones/plan-device-deployment.md index 496d963414..22e3cf2883 100644 --- a/Teams/phones/plan-device-deployment.md +++ b/Teams/phones/plan-device-deployment.md @@ -56,9 +56,9 @@ The space you choose will determine the type of license you'll need. - **Walkie Talkie**: Users part of a Teams channel can broadcast messages to other users' part of the same channel. - **Calendar**: Schedule and join meetings. - :::image type="content" source="../media/teams-" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: + :::image type="content" source="media/teams-apps-1" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: -## Step 3: Setup desired phone device experience for your users +## Step 3: Setup desired phone device experience for your users First, configure IP Phone Policy [SignInMode](/powershell/module/teams/new-csteamsipphonepolicy#-signinmode) parameter via PowerShell to enable associated apps on phone device. diff --git a/Teams/phones/remote-provision-remote-login-phones.md b/Teams/phones/remote-provision-remote-login-phones.md index 2b4ff9f88b..e0164c1c5c 100644 --- a/Teams/phones/remote-provision-remote-login-phones.md +++ b/Teams/phones/remote-provision-remote-login-phones.md @@ -38,7 +38,7 @@ Refer to the following for the list of certified hardware: Teams phones - [Certified Teams phones](../devices/teams-phones-certified-hardware.md) Teams panels - [Certified Teams panels](../devices/teams-panels-certified-hardware.md) Microsoft Teams Rooms on Android - [Teams Rooms on Android certified devices](../devices/certified-hardware-android.md?tabs=Android) -SIP devices - [Teams compatible devices](./sip-gateway-plan.md#compatible-devices) +SIP devices - [Teams compatible devices](../devices/sip-gateway-plan.md#compatible-devices) ## Add a device MAC address @@ -110,7 +110,7 @@ The provisioned device appears in the **Waiting for sign in** tab. Start the rem ## Related articles -- [Manage your devices in Teams](../rooms/device-management.md) +- [Manage your devices in Teams](../devices/device-management.md) - [Remote sign in and sign out](../devices/remote-sign-in-and-sign-out.md) - [Update Teams devices remotely](../devices/remote-update.md) diff --git a/Teams/phones/remote-sign-in-and-sign-out-phones.md b/Teams/phones/remote-sign-in-and-sign-out-phones.md index f740ea40ac..c166f1085f 100644 --- a/Teams/phones/remote-sign-in-and-sign-out-phones.md +++ b/Teams/phones/remote-sign-in-and-sign-out-phones.md @@ -1,5 +1,5 @@ --- -title: Remote sign in and sign out for Teams Android devices +title: Remote sign in and sign out for Teams phones author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -19,12 +19,12 @@ f1.keywords: - NOCSH ms.localizationpriority: medium search.appverid: MET150 -description: Learn how to remotely sign in and sign out of Teams Android devices. +description: Learn how to remotely sign in and sign out of Teams phones. --- -# Remote sign in and sign out for Teams Android devices +# Remote sign in and sign out for Teams phones -This article describes how to remote sign in and sign out Teams Android devices from the Teams admin center. If you haven't provisioned a device yet, or the device is provisioned but has never been signed-in, see [Remote provisioning and sign in for Teams Android devices](remote-provision-remote-login.md). +This article describes how to remote sign in and sign out Teams phones from the Teams admin center. If you haven't provisioned a device yet, or the device is provisioned but has never been signed-in, see [Remote provisioning and sign in for Teams Android devices](../devices/remote-provision-remote-login.md). This video shows how to sign into Teams devices. @@ -48,6 +48,6 @@ To sign in a device that has been signed out, go to the corresponding device pag ## Related articles -- [Remote provisioning and sign in for Teams Android devices](remote-provision-remote-login.md) -- [Manage your devices in Teams](device-management.md) -- [Update Teams devices remotely](remote-update.md) +- [Remote provisioning and sign in for Teams Android devices]../devices/(remote-provision-remote-login.md) +- [Manage your devices in Teams](../devices/device-management.md) +- [Update Teams devices remotely](../devices/remote-update.md) diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index eb3f3c32cd..ea87798f50 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -103,7 +103,6 @@ If you want to configure the Maintenance window for a device, do the following s 1. You can check the selected Maintenance window settings under the **Details** tab on the device page. - Automatic updates, when they happen, utilize the maintenance window configured for the device, that is, the **Time window** on the selected days for **Update frequency**. Maintenance window can also be utilized for scheduling manual updates. Option to configure maintenance window isn't available in GCC-High and DoD. @@ -160,7 +159,7 @@ When you select a single device, updates that are available for the device are s After you select **Update**, updates are applied to your devices at the date and time of the selected scheduling option. If you didn't select a future date and time, updates are applied to your devices within a few minutes. -To manage devices, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](./using-admin-roles.md). +To manage devices, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](/teams/using-admin-roles.md). > [!IMPORTANT] > Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. diff --git a/Teams/toc.yml b/Teams/toc.yml index ffd8f8e37a..e92afb817e 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1598,7 +1598,7 @@ items: - name: Prepare your network href: phones/prepare-network-teams-phones.md - name: Quality of Service (QOS) for Teams phones - href: phones/qos-teams-phones.md + href: phones/qos-on-teams-phones.md - name: Intune Enrollment for Teams phones items: - name: Device administration @@ -1624,7 +1624,7 @@ items: - name: Manage Teams phones href: phones/manage-teams-phones.md - name: Update management - href: phones/remote-update-phones.md + href: phones/remote-update-teams-phones.md - name: Troubleshooting and known issues items: - name: Troubleshooting and known issues From f036f43fda09ff4299375560c20b077bc9363560 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 11:46:40 -0700 Subject: [PATCH 42/87] Fixing build errors --- Teams/{ => devices}/media/edit-filter.png | Bin .../media/exclude-attribute-set.png | Bin .../media/include-all-apps-settings.png | Bin .../media/powershell-output-expected.png | Bin .../media/require-mfa-selection.png | Bin Teams/devices/remote-sign-in-and-sign-out.md | 4 +-- Teams/devices/sip-gateway-plan.md | 6 ++-- Teams/phones/plan-device-deployment.md | 2 +- Teams/phones/remote-update-teams-phones.md | 2 +- Teams/phones/set-up-common-area-phones.md | 4 +-- .../supported-ca-and-compliance-policies.md | 27 ++++++++---------- 11 files changed, 21 insertions(+), 24 deletions(-) rename Teams/{ => devices}/media/edit-filter.png (100%) rename Teams/{ => devices}/media/exclude-attribute-set.png (100%) rename Teams/{ => devices}/media/include-all-apps-settings.png (100%) rename Teams/{ => devices}/media/powershell-output-expected.png (100%) rename Teams/{ => devices}/media/require-mfa-selection.png (100%) diff --git a/Teams/media/edit-filter.png b/Teams/devices/media/edit-filter.png similarity index 100% rename from Teams/media/edit-filter.png rename to Teams/devices/media/edit-filter.png diff --git a/Teams/media/exclude-attribute-set.png b/Teams/devices/media/exclude-attribute-set.png similarity index 100% rename from Teams/media/exclude-attribute-set.png rename to Teams/devices/media/exclude-attribute-set.png diff --git a/Teams/media/include-all-apps-settings.png b/Teams/devices/media/include-all-apps-settings.png similarity index 100% rename from Teams/media/include-all-apps-settings.png rename to Teams/devices/media/include-all-apps-settings.png diff --git a/Teams/media/powershell-output-expected.png b/Teams/devices/media/powershell-output-expected.png similarity index 100% rename from Teams/media/powershell-output-expected.png rename to Teams/devices/media/powershell-output-expected.png diff --git a/Teams/media/require-mfa-selection.png b/Teams/devices/media/require-mfa-selection.png similarity index 100% rename from Teams/media/require-mfa-selection.png rename to Teams/devices/media/require-mfa-selection.png diff --git a/Teams/devices/remote-sign-in-and-sign-out.md b/Teams/devices/remote-sign-in-and-sign-out.md index f740ea40ac..66649e350f 100644 --- a/Teams/devices/remote-sign-in-and-sign-out.md +++ b/Teams/devices/remote-sign-in-and-sign-out.md @@ -1,5 +1,5 @@ --- -title: Remote sign in and sign out for Teams Android devices +title: Remotely sign in and sign out for Teams Android devices author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -22,7 +22,7 @@ search.appverid: MET150 description: Learn how to remotely sign in and sign out of Teams Android devices. --- -# Remote sign in and sign out for Teams Android devices +# Remotely sign in and sign out for Teams Android devices This article describes how to remote sign in and sign out Teams Android devices from the Teams admin center. If you haven't provisioned a device yet, or the device is provisioned but has never been signed-in, see [Remote provisioning and sign in for Teams Android devices](remote-provision-remote-login.md). diff --git a/Teams/devices/sip-gateway-plan.md b/Teams/devices/sip-gateway-plan.md index 04eb6009a6..3ed51bfae1 100644 --- a/Teams/devices/sip-gateway-plan.md +++ b/Teams/devices/sip-gateway-plan.md @@ -61,7 +61,7 @@ Teams users must have a phone number with PSTN calling enabled to use SIP Gatewa > DND - > \*30\* (Set DND From SIP Device) > \*31\* (Reset Teams DND Status from SIP Device) -> Call Forwarding - (https://support.microsoft.com/en-us/office/call-forwarding-call-groups-and-simultaneous-ring-in-microsoft-teams-a88da9e8-1343-4d3c-9bda-4b9615e4183e) +> Call Forwarding - (https://support.microsoft.com/office/call-forwarding-call-groups-and-simultaneous-ring-in-microsoft-teams-a88da9e8-1343-4d3c-9bda-4b9615e4183e) > \*32\* - Reset Call Forwarding Status > \*33\* (Set "Call Forwarded To" Number) > \*34\* (Set "Forward on Timeout") @@ -78,8 +78,8 @@ If you have a 3PIP or SIP device, you must have the following: - [Microsoft Teams](https://www.microsoft.com/microsoft-teams/group-chat-software) - Skype for Business Online (Plan 2) - *Skype for Business Online (Plan 2)* isn't a standalone license that can be purchased. -- [Microsoft Phone System](what-is-phone-system-in-office-365.md) -- [PSTN Connectivity](pstn-connectivity.md) +- [Microsoft Phone System](../what-is-phone-system-in-office-365.md) +- [PSTN Connectivity](../pstn-connectivity.md) ## Compatible devices diff --git a/Teams/phones/plan-device-deployment.md b/Teams/phones/plan-device-deployment.md index 22e3cf2883..751929e696 100644 --- a/Teams/phones/plan-device-deployment.md +++ b/Teams/phones/plan-device-deployment.md @@ -56,7 +56,7 @@ The space you choose will determine the type of license you'll need. - **Walkie Talkie**: Users part of a Teams channel can broadcast messages to other users' part of the same channel. - **Calendar**: Schedule and join meetings. - :::image type="content" source="media/teams-apps-1" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: + :::image type="content" source="media/teams-apps-1.png" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: ## Step 3: Setup desired phone device experience for your users diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index ea87798f50..4b474318b6 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -159,7 +159,7 @@ When you select a single device, updates that are available for the device are s After you select **Update**, updates are applied to your devices at the date and time of the selected scheduling option. If you didn't select a future date and time, updates are applied to your devices within a few minutes. -To manage devices, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](/teams/using-admin-roles.md). +To manage devices, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](../using-admin-roles.md). > [!IMPORTANT] > Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. diff --git a/Teams/phones/set-up-common-area-phones.md b/Teams/phones/set-up-common-area-phones.md index ea0358b669..f8ca77de85 100644 --- a/Teams/phones/set-up-common-area-phones.md +++ b/Teams/phones/set-up-common-area-phones.md @@ -81,7 +81,7 @@ If you're deploying one device: > [!NOTE] > You don't need to add a license with Phone System features. It's included with the **Teams Shared Devices** license. > -> If you aren't using Microsoft Phone System with Direct Routing or Operator Connect, you may want to add **Calling Plans** licenses. For more information on licenses, see [Microsoft Teams add-on licensing](/microsoftteams/teams-add-on-licensing/microsoft-teams-add-on-licensing.md). +> If you aren't using Microsoft Phone System with Direct Routing or Operator Connect, you may want to add **Calling Plans** licenses. For more information on licenses, see [Microsoft Teams add-on licensing](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md). ### Using PowerShell @@ -141,7 +141,7 @@ You can also sign into to a common area phone from another device using a code. ### Sign in using the Teams admin center -As an admin, you can remotely provision and sign into common area phones from the [Teams admin center](https://go.microsoft.com/fwlink/p/?linkid=2066851). This method is the most efficient sign-in method when you're deploying a large number of phones at once. See [Remote provisioning and sign in for Teams Android devices](devices/remote-provision-remote-login.md) to learn more. +As an admin, you can remotely provision and sign into common area phones from the [Teams admin center](https://go.microsoft.com/fwlink/p/?linkid=2066851). This method is the most efficient sign-in method when you're deploying a large number of phones at once. See [Remote provisioning and sign in for Teams Android devices](../devices/remote-provision-remote-login.md) to learn more. ## Step 6 - Set up Advanced calling on common area phones (optional) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index 2b4eb19386..583e7100d9 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -38,10 +38,10 @@ for more information. The following list includes the supported Conditional Access policies for Teams Rooms on Windows and Android, and for policies on Teams panels, phones, and displays. | **Assignment** | **Teams Rooms on Windows** | **Teams Rooms on Android and panels** | **Teams phones and displays** | -|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| User or workload identities | Supported | Supported | Supported | -| Cloud apps or actions | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | -| **Conditions** | --- | --- | --- | +|:----------|:----------|:----------|:----------| +| User or workload identities | Supported | Supported | Supported | +| Cloud apps or actions | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | +| **Conditions** | | User risk | Supported | Supported | Supported | | Sign-in risk | Supported | Supported | Supported | | Device platforms | Supported | Supported | Supported | @@ -61,12 +61,12 @@ The following list includes the supported Conditional Access policies for Teams | Require password change | Not supported | Not supported | Not supported | **Sessions** | --- | --- | --- | Use app enforced restrictions | Not supported | Not supported | Not Supported | -| Use Conditional Access App Control | Not supported | Not Supported | Not supported -| Sign-in frequency | Supported | Supported | Supported | -| Persistent browser session | Not supported | Not supported | Not supported | -| Customize conditional access evaluation | Not supported | Not supported | Not supported | -| Disable resiliency defaults | Not supported | Not supported | Not supported -| Require token protection for sign-in sessions (Preview) | Not supported | Not supported | Not supported +| Use Conditional Access App Control | Not supported | Not Supported | Not supported +| Sign-in frequency | Supported| Supported | Supported | +| Persistent browser session | Not supported | Not supported | Not supported | +| Customize conditional access evaluation | Not supported | Not supported | Not supported | +| Disable resiliency defaults | Not supported | Not supported | Not supported +| Require token protection for sign-in sessions (Preview) | Not supported | Not supported | Not supported > [!NOTE] > Using Conditional Access policies with Sign-in frequency configured, will make all Teams Android devices periodicly sign out. This is expected behavior. @@ -89,7 +89,7 @@ their use with Teams Rooms. | Require BitLocker | Supported | Only use if you have first enabled BitLocker on Teams Rooms. | | Require Secure Boot to be enabled on the device | Supported | Secure Boot is a requirement for Teams Rooms. | | Require code integrity | Supported | Code integrity is already a requirement for Teams Rooms. | -| [**Device Properties**](/mem/intune/protect/compliance-policy-create-windows#device-properties) | -- | -- | +| [**Device Properties**](/mem/intune/protect/compliance-policy-create-windows#device-properties) -- | | | Operating System Version (minimum, maximum) | Not supported | Teams Rooms automatically updates to newer versions of Windows and setting values here could prevent successful sign-in after an OS update. | | OS version for mobile devices (minimum, maximum) | Not supported. | | | Valid operating system builds | Not supported | | @@ -137,8 +137,7 @@ their use with Teams Rooms. | Restricted apps | Not supported | | | Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | -| Maximum minutes of inactivity before password are required | Not supported | - | +| Maximum minutes of inactivity before password are required | Not supported | | Require a password to unlock mobile devices | Not supported | | | [**Android 10 and later**](/mem/intune/protect/compliance-policy-create-android#android-10-and-later) | -- | -- | | [**Android 9 and earlier or Samsung Knox**](/mem/intune/protect/compliance-policy-create-android#android-9-and-earlier-or-samsung-knox) | -- | -- | @@ -177,8 +176,6 @@ Below is a table of device compliance settings and recommendations for their use | [**Android 9 and earlier or Samsung Knox**](/mem/intune/protect/compliance-policy-create-android#android-9-and-earlier-or-samsung-knox) | -- | -- | | Required password type | Not supported | | - - #### [Teams panels](#tab/panels) Below is a table of device compliance settings and recommendations for their use with Teams panels. From b72a50fcce538698787fd6b11c4b9452ee3e06cc Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 11:51:14 -0700 Subject: [PATCH 43/87] Update remote-sign-in-and-sign-out-phones.md --- Teams/phones/remote-sign-in-and-sign-out-phones.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Teams/phones/remote-sign-in-and-sign-out-phones.md b/Teams/phones/remote-sign-in-and-sign-out-phones.md index c166f1085f..3c33f6fa14 100644 --- a/Teams/phones/remote-sign-in-and-sign-out-phones.md +++ b/Teams/phones/remote-sign-in-and-sign-out-phones.md @@ -24,7 +24,7 @@ description: Learn how to remotely sign in and sign out of Teams phones. # Remote sign in and sign out for Teams phones -This article describes how to remote sign in and sign out Teams phones from the Teams admin center. If you haven't provisioned a device yet, or the device is provisioned but has never been signed-in, see [Remote provisioning and sign in for Teams Android devices](../devices/remote-provision-remote-login.md). +This article describes how to remote sign in and sign out Teams phones from the Teams admin center. This video shows how to sign into Teams devices. @@ -32,22 +32,22 @@ This video shows how to sign into Teams devices. ## Remote sign in -After a device is provisioned and signed in for the first time, it will appear on its corresponding page under the **Teams devices** node of the Teams admin center. +After a phone is provisioned and signed in for the first time, it will appear on its corresponding page under the **Teams devices** node of the Teams admin center. -To sign in a device that has been signed out, go to the corresponding device page. +To sign in a phone, go to the corresponding device page. -1. Select the device you want to sign in. +1. Select the phone you want to sign in. 2. Go to the **Actions** menu, and select **Sign in a user**. ## Remote sign out -1. Select the device you want to sign out from the corresponding page. +1. Select the phone you want to sign out from the corresponding page. 2. Go to the **Actions** menu, and select **Sign out**. ## Related articles -- [Remote provisioning and sign in for Teams Android devices]../devices/(remote-provision-remote-login.md) +- [Remotely provisioning and sign in for Teams Android devices](../devices/remote-provision-remote-login.md) - [Manage your devices in Teams](../devices/device-management.md) - [Update Teams devices remotely](../devices/remote-update.md) From 0082e2b0ce332f0397d79a9d5e58e1eed963e212 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 12:27:45 -0700 Subject: [PATCH 44/87] Update supported-ca-and-compliance-policies.md --- .../supported-ca-and-compliance-policies.md | 50 +++++++++---------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index 583e7100d9..e5802c2724 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -37,29 +37,31 @@ for more information. The following list includes the supported Conditional Access policies for Teams Rooms on Windows and Android, and for policies on Teams panels, phones, and displays. -| **Assignment** | **Teams Rooms on Windows** | **Teams Rooms on Android and panels** | **Teams phones and displays** | -|:----------|:----------|:----------|:----------| +| **Assignment**|**Teams Rooms on Windows**|**Teams Rooms on Android and panels**|**Teams phones and displays**| +|:-----|:-----|:-----|:-----| | User or workload identities | Supported | Supported | Supported | + | Cloud apps or actions | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | + | **Conditions** | | User risk | Supported | Supported | Supported | | Sign-in risk | Supported | Supported | Supported | | Device platforms | Supported | Supported | Supported | | Locations | Supported | Supported | Supported | | Client apps | Not supported | Not supported | Not supported | -| Filter for devices | Supported | Supported | Supported | | Not supported

Device code flow is required for sign in | Not supported

Device code flow is required for sign in +| Filter for devices | Supported | Supported | Supported | | Not supported

Device code flow is required for sign in | Not supported

Device code flow is required for sign in | Authentication flows | Supported | Not supported

Device code flow is required for sign in. | Not supported

Device code flow is required for sign in. | | **Grant** | --- | --- | --- | | Block access | Supported | Supported | Supported | | Grant access | Supported | Supported | Supported | | Require multi-factor authentication | Not supported | Not supported | Supported | -| Require authentication strength | Not supported | Not Supported | Not supported +| Require authentication strength | Not supported | Not Supported | Not supported | Require device to be marked as compliant | Supported | Supported | Supported | | Require Microsoft Entra hybrid joined device | Not supported | Not supported | Not supported | | Require approved client app | Not supported | Not supported | Not supported | | Require app protection policy | Not supported | Not supported | Not supported | -| Require password change | Not supported | Not supported | Not supported -| **Sessions** | --- | --- | --- +| Require password change | Not supported | Not supported | Not supported | +| **Sessions** | --- | --- | --- | | Use app enforced restrictions | Not supported | Not supported | Not Supported | | Use Conditional Access App Control | Not supported | Not Supported | Not supported | Sign-in frequency | Supported| Supported | Supported | @@ -70,7 +72,7 @@ The following list includes the supported Conditional Access policies for Teams > [!NOTE] > Using Conditional Access policies with Sign-in frequency configured, will make all Teams Android devices periodicly sign out. This is expected behavior. -> + > [!NOTE] > Authentication Strength including but not limited to, FIDO2 Security keys, is not supported for use with Conditional Access policys that will affect all Teams Devices. @@ -80,11 +82,10 @@ Microsoft Teams Rooms on Windows and Teams Rooms on Android support different de #### [Teams Rooms on Windows](#tab/mtr-w) -Below is a table of device compliance settings and recommendations for -their use with Teams Rooms. +Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| **Policy** | **Availability** | **Notes** | +|---------------------------------------------------------------|----------------|--------------------------------------| | [**Device health**](/mem/intune/protect/compliance-policy-create-windows#device-health) | -- | -- | | Require BitLocker | Supported | Only use if you have first enabled BitLocker on Teams Rooms. | | Require Secure Boot to be enabled on the device | Supported | Secure Boot is a requirement for Teams Rooms. | @@ -111,11 +112,10 @@ their use with Teams Rooms. #### [Teams Rooms on Android](#tab/mtr-a) -Below is a table of device compliance settings and recommendations for -their use with Teams Rooms. +Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| +| **Policy** | **Availability** | **Notes** | +|------------------------------------|---------------|----------------------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | | [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | @@ -147,8 +147,8 @@ their use with Teams Rooms. Below is a table of device compliance settings and recommendations for their use with Teams phones and displays. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| +| **Policy** | **Availability** | **Notes** | +|--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | | [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | @@ -180,14 +180,14 @@ Below is a table of device compliance settings and recommendations for their use Below is a table of device compliance settings and recommendations for their use with Teams panels. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| -| [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | -| Require the device to be at or under the machine risk score | Not supported | | -| [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | -| Device managed with device administrator | Required | Teams Android devices management requires device administrator to be enabled. | -| Rooted devices | Supported | | -| Require the device to be at or under the device threat level | Not supported | | +| Policy | Availability | Notes | +|--------------------------------|---------------|------------------------------| +| [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | +| Require the device to be at or under the machine risk score | Not supported | | +| [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | +| Device managed with device administrator | Required | Teams Android devices management requires device administrator to be enabled. | +| Rooted devices | Supported | | +| Require the device to be at or under the device threat level | Not supported | | | [**Google Play Protect**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | | Google Play Services is configured | Not supported | Google play isn't installed on Teams Android devices. | | Up-to-date security provider | Not supported | Google play isn't installed on Teams Android devices. | From fe80b1e53c4a206c11f32460d9e031f3f4384fa2 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 12:33:21 -0700 Subject: [PATCH 45/87] Update supported-ca-and-compliance-policies.md --- .../supported-ca-and-compliance-policies.md | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index e5802c2724..345c0149e9 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -27,10 +27,7 @@ This article provides supported Conditional Access and Intune device compliance [!INCLUDE [teams-pro-license-requirement](../includes/teams-pro-license-requirement.md)] > [!NOTE] -> Teams Rooms must already be deployed on the devices you want to assign -Conditional Access policies to. If you haven't deployed Teams Rooms yet, -see [Create resource accounts for rooms and shared Teams devices](create-resource-account.md) -and [Deploy Microsoft Teams Rooms on Android](../devices/collab-bar-deploy.md) +> Teams Rooms must be already deployed on the devices if you want to assign Conditional Access policies. If you haven't deployed Teams Rooms yet, see [Create resource accounts for rooms and shared Teams devices](create-resource-account.md) and [Deploy Microsoft Teams Rooms on Android](../devices/collab-bar-deploy.md) for more information. ## Supported Conditional Access policies @@ -87,11 +84,11 @@ Below is a table of device compliance settings and recommendations for their use | **Policy** | **Availability** | **Notes** | |---------------------------------------------------------------|----------------|--------------------------------------| | [**Device health**](/mem/intune/protect/compliance-policy-create-windows#device-health) | -- | -- | -| Require BitLocker | Supported | Only use if you have first enabled BitLocker on Teams Rooms. | +| Require BitLocker | Supported | Only use if you have enabled BitLocker first on Teams Rooms. | | Require Secure Boot to be enabled on the device | Supported | Secure Boot is a requirement for Teams Rooms. | | Require code integrity | Supported | Code integrity is already a requirement for Teams Rooms. | | [**Device Properties**](/mem/intune/protect/compliance-policy-create-windows#device-properties) -- | | -| Operating System Version (minimum, maximum) | Not supported | Teams Rooms automatically updates to newer versions of Windows and setting values here could prevent successful sign-in after an OS update. | +| Operating System Version (minimum, maximum) | Not supported | Teams Rooms automatically will update to newer versions of Windows and setting values here could prevent successful sign-in after an OS update. | | OS version for mobile devices (minimum, maximum) | Not supported. | | | Valid operating system builds | Not supported | | | [**Configuration Manager Compliance**](/mem/intune/protect/compliance-policy-create-windows#device-properties) | -- | -- | @@ -104,7 +101,7 @@ Below is a table of device compliance settings and recommendations for their use | Antivirus | Supported | Antivirus (Windows Defender) is already a requirement for Teams Rooms. | | Antispyware | Supported | Antispyware (Windows Defender) is already a requirement for Teams Rooms. | | Microsoft Defender Antimalware | Supported | Microsoft Defender Antimalware is already a requirement for Teams Rooms. | -| Microsoft Defender Antimalware minimum version | Not supported. | Teams Rooms automatically updates this component so there's no need to set compliance policies. | +| Microsoft Defender Antimalware minimum version | Not supported. | Teams Rooms will automatically update this component so there's no need to set compliance policies. | | Microsoft Defender Antimalware security intelligence up-to-date | Supported | Validate that Microsoft Defender Antimalware is already a requirement for Teams Rooms. | | Real-time protection | Supported | Real-time protections are already a requirement for Teams Rooms. | | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-windows#microsoft-defender-for-endpoint) | -- | -- | @@ -135,7 +132,7 @@ Below is a table of device compliance settings and recommendations for their use | Block apps from unknown sources | Not supported | Only Teams admins install apps or OEM tools | | Company Portal app runtime integrity | Supported | | | Restricted apps | Not supported | | -| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | +| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement isn't allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | | Maximum minutes of inactivity before password are required | Not supported | | Require a password to unlock mobile devices | Not supported | | @@ -168,7 +165,7 @@ Below is a table of device compliance settings and recommendations for their use | Block apps from unknown sources | Not supported | Only Teams admins install apps or OEM tools | | Company Portal app runtime integrity | Supported | | | Restricted apps | Not supported | | -| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | +| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement isn't allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | | Maximum minutes of inactivity before password are required | Not supported | | | Require a password to unlock mobile devices | Not supported | | @@ -201,7 +198,7 @@ Below is a table of device compliance settings and recommendations for their use | Block apps from unknown sources | Not supported | Only Teams admins install apps or OEM tools | | Company Portal app runtime integrity | Supported | | | Restricted apps | Not supported | | -| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | +| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement isn't allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | | Maximum minutes of inactivity before password are required | Not supported | | | Require a password to unlock mobile devices | Not supported | | From 7f4c3b24c5ab7e9c4551ea2e55f80bb0817802fd Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 12:46:46 -0700 Subject: [PATCH 46/87] Update supported-ca-and-compliance-policies.md --- .../supported-ca-and-compliance-policies.md | 30 +++++++++---------- 1 file changed, 14 insertions(+), 16 deletions(-) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index 345c0149e9..07170a762d 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -37,18 +37,16 @@ The following list includes the supported Conditional Access policies for Teams | **Assignment**|**Teams Rooms on Windows**|**Teams Rooms on Android and panels**|**Teams phones and displays**| |:-----|:-----|:-----|:-----| | User or workload identities | Supported | Supported | Supported | - | Cloud apps or actions | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | - -| **Conditions** | -| User risk | Supported | Supported | Supported | -| Sign-in risk | Supported | Supported | Supported | -| Device platforms | Supported | Supported | Supported | -| Locations | Supported | Supported | Supported | -| Client apps | Not supported | Not supported | Not supported | -| Filter for devices | Supported | Supported | Supported | | Not supported

Device code flow is required for sign in | Not supported

Device code flow is required for sign in -| Authentication flows | Supported | Not supported

Device code flow is required for sign in. | Not supported

Device code flow is required for sign in. | -| **Grant** | --- | --- | --- | +| **Conditions** |---|---|---| +| User risk | Supported | Supported | Supported | +| Sign-in risk | Supported | Supported | Supported | +| Device platforms | Supported | Supported | Supported | +| Locations | Supported | Supported | Supported | +| Client apps | Not supported | Not supported| Not supported | +| Filter for devices | Supported | Supported | Supported | +| Authentication flows | Supported | Not supported

Device code flow is required for sign in. | Not supported

Device code flow is required for sign in. | +| **Grant** | --- |--- | --- | | Block access | Supported | Supported | Supported | | Grant access | Supported | Supported | Supported | | Require multi-factor authentication | Not supported | Not supported | Supported | @@ -81,8 +79,8 @@ Microsoft Teams Rooms on Windows and Teams Rooms on Android support different de Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| **Policy** | **Availability** | **Notes** | -|---------------------------------------------------------------|----------------|--------------------------------------| +| **Policy** | **Availability** | **Notes** | +|--------------|---------------|----------------| | [**Device health**](/mem/intune/protect/compliance-policy-create-windows#device-health) | -- | -- | | Require BitLocker | Supported | Only use if you have enabled BitLocker first on Teams Rooms. | | Require Secure Boot to be enabled on the device | Supported | Secure Boot is a requirement for Teams Rooms. | @@ -112,7 +110,7 @@ Below is a table of device compliance settings and recommendations for their use Below is a table of device compliance settings and recommendations for their use with Teams Rooms. | **Policy** | **Availability** | **Notes** | -|------------------------------------|---------------|----------------------------| +|--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | | [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | @@ -177,8 +175,8 @@ Below is a table of device compliance settings and recommendations for their use Below is a table of device compliance settings and recommendations for their use with Teams panels. -| Policy | Availability | Notes | -|--------------------------------|---------------|------------------------------| +| **Policy** | **Availability** | **Notes** | +|--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | | [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | From ee638408a42c2fb273c88f0fbc9b815850162096 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Thu, 17 Oct 2024 15:08:33 -0700 Subject: [PATCH 47/87] Update toc.yml --- Teams/toc.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 9b7df28fd1..2bdf750523 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1439,8 +1439,6 @@ items: href: rooms/rooms-release-note.md - name: Teams panels release notes href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels - - name: Teams device management apps - href: devices/certified-device-apps.md - name: Troubleshooting and known issues items: - name: Teams Rooms on Windows @@ -1461,7 +1459,7 @@ items: href: devices/qos-on-teams-devices.md - name: Intune Enrollment for Windows items: - - name: AutoPilot and Autologin + - name: Autopilot and Autologin href: rooms/autopilot-autologin.md - name: Deploy LAPs href: rooms/laps-authentication.md @@ -1642,11 +1640,11 @@ items: - name: SIP Gateway items: - name: Plan for SIP Gateway - href: sip-gateway-plan.md + href: devices/sip-gateway-plan.md - name: Configure SIP Gateway - href: sip-gateway-configure.md + href: devices/sip-gateway-configure.md - name: Dynamic filters - href: sip-gateway-dynamic-filters.md + href: devices/sip-gateway-dynamic-filters.md - name: Known issues href: /microsoftteams/troubleshoot/phone-system/sip-gateway-issues - name: Reference From 8aacf9acd6c0809e6d514cb5757ae324cfefbe02 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 17 Oct 2024 17:26:17 -0500 Subject: [PATCH 48/87] Update prepare-network-teams-phones.md Fixing links. --- Teams/phones/prepare-network-teams-phones.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md index fa0046dbce..cbe08a939c 100644 --- a/Teams/phones/prepare-network-teams-phones.md +++ b/Teams/phones/prepare-network-teams-phones.md @@ -29,9 +29,9 @@ This section contains an overview of the steps required to prepare your network In order to function properly, Microsoft Phone devices must have access to a network that meets these requirements: -- Review access to: Microsoft Teams, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Rooms Network Security](/microsoftteams/rooms/security?tabs=Android#network-security) +- Review access to: Microsoft Teams, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Android Device - Network Security](/microsoftteams/rooms/security?tabs=Android#network-security) -- Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Devices](/microsoftteams/devices/qos-on-teams-devices) +- Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Phones](/microsoftteams/devices/qos-on-teams-phones) - Review if your organization utilizes a proxy, you need the proxy address or proxy autoconfiguration (PAC) file url From 1b0a78290ed60df77d5dd92fc36b0d082346f6d3 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 17 Oct 2024 17:36:55 -0500 Subject: [PATCH 49/87] Update qos-on-teams-phones.md Rephrased to Teams phone QoS from Rooms --- Teams/phones/qos-on-teams-phones.md | 64 ++++++++--------------------- 1 file changed, 18 insertions(+), 46 deletions(-) diff --git a/Teams/phones/qos-on-teams-phones.md b/Teams/phones/qos-on-teams-phones.md index a5233139a7..985d14c600 100644 --- a/Teams/phones/qos-on-teams-phones.md +++ b/Teams/phones/qos-on-teams-phones.md @@ -24,42 +24,33 @@ description: Learn about the key considerations for deploying Quality of Service # Quality of service (QoS) set up on Teams phones -Deploying one or many Microsoft Teams Rooms devices requires planning. One of the key considerations is your organization's network capacity and quality of service (QoS) configuration. +Deploying one or many Microsoft Teams phone devices requires planning. One of the key considerations is your organization's network capacity and quality of service (QoS) configuration. This article explains: -1. [How much bandwidth does a Microsoft Teams Rooms device use?](#how-much-bandwidth-does-a-microsoft-teams-rooms-device-use) -1. [How to control that bandwidth usage?](#how-do-i-control-microsoft-teams-rooms-bandwidth-usage) -1. [How to ensure your devices are optimized with the right quality of service (QoS) configuration to align to your organizations requirements?](#quality-of-service-qos-with-microsoft-teams-rooms) +1. [How much bandwidth does a Microsoft Teams phone device use?](#how-much-bandwidth-does-a-microsoft-teams-phone-device-use) +1. [How to control that bandwidth usage?](#how-do-i-control-microsoft-teams-phone-bandwidth-usage) +1. [How to ensure your devices are optimized with the right quality of service (QoS) configuration to align to your organizations requirements?](#quality-of-service-qos-with-microsoft-teams-phones) -Wired network connectivity is recommended for Microsoft Teams Rooms devices. If wireless network connectivity is the only option, see best practice guidance [here](../rooms/rooms-prep.md#wireless-network-considerations). +Wired network connectivity is recommended for Microsoft Teams phone devices. If wireless network connectivity is the only option, see best practice guidance [here](../Phones/prepare-network-teams-phones.md#wireless-network-considerations). -## How much bandwidth does a Microsoft Teams Rooms device use? +## How much bandwidth does a Microsoft Teams phone device use? -Microsoft Teams Rooms is designed to give the best audio, video, and content-sharing experience regardless of your network conditions. That said, when bandwidth is insufficient, Teams prioritizes traffic in the following order: audio, content sharing, lastly participant video. - -Where bandwidth isn't limited, Teams optimizes media quality, including high-fidelity audio, up to 1080p video resolution, and up to 30 fps (frames per second) for video and content. +Microsoft Teams phone is designed to give the best audio experience regardless of your network conditions. The following table provides rough estimates of bandwidth utilized for the various streams in *kbps* (down/up) - |Feature |Standard |Advanced | |---------|---------|---------| -|Audio | 128/128 | 256/256 | -|Video | 2000/4000 |8000/4000 | -|Screen share | 2000/2000 | 2000/2000 | -|**Total** | **4128/6128** |**10256/6256** | - - -Teams Rooms can support up to 18 individual incoming video streams, up to five outbound video streams, and content sharing either inbound or outbound. The number of streams consumed by the Teams Rooms device can have a large impact on the downstream bandwidth consumed, and the capabilities of the connected Teams Rooms camera can impact the outbound bandwidth usage. Bandwidth consumption can also vary with the number and resolution of the videos from remote participants connected to the meeting. +|Audio | 58/58 | 76/75 | -## How do I control Microsoft Teams Rooms bandwidth usage? +## How do I control Microsoft Teams phone bandwidth usage? -By default, Teams Rooms don't have a bandwidth-limiting policy. If you wish to implement one, we recommend allocating 10 Mbps to each Teams Rooms resource account. This implementation can be accomplished by assigning a Teams meeting policy with a media bitrate limit configured. When setting the meeting policy at 10 Mbps, Teams Rooms still only use the bandwidth required for the meeting (typically 3-4 Mbps), and dynamically adjusts if its network connection isn't able to sustain 10 Mbps. +If you wish to implement a bandwidth policy on your common area phones, we recommend allocating 100 kbps to each Teams phone resource account. This implementation can be accomplished by assigning a Teams meeting policy with a media bitrate limit configured. When setting the meeting policy at 100 kbps, Teams phones still only use the bandwidth required for the call, and dynamically adjusts if its network connection isn't able to sustain 100 kbps. For user signed in devices, the meeting policy assigned to the users account will also apply to the Teams phone device. -For information on how to configure a Teams meeting policy, see [Meeting policy settings for audio and video](../meeting-policies-audio-and-video.md). You want to create a custom policy and assign it to all Microsoft Teams Rooms resource accounts, with the limit for media bitrate configured for 10,000 kbps. +For information on how to configure a Teams meeting policy, see [Meeting policy settings for audio and video](../meeting-policies-audio-and-video.md). You want to create a custom policy and assign it to all Microsoft Teams phone resource accounts, with the limit for media bitrate configured for 100 kbps. -## Quality of Service (QoS) with Microsoft Teams Rooms +## Quality of Service (QoS) with Microsoft Teams phones Microsoft Teams Rooms supports Quality of Service (QoS) Differentiated Services Code Point (DSCP) markings to ensure you can manage the media traffic on your corporate network. @@ -72,35 +63,16 @@ We recommend the following QoS markings and port ranges for the audio, video, an - DSCP value: **46** - DSCP class: **Expedited Forwarding (EF)** -**Video**: - -- Client source port range: **50,020-50,039** -- Protocol: **TCP/UDP** -- DSCP value: **34** -- DSCP class: **Assured Forwarding (AF41)** - -**Application/screen sharing**: +**Calling and Meetings Signaling**: -- Client source port range: **50,040-50,059** -- Protocol: **TCP/UDP** -- DSCP value: **18** -- DSCP class: **Assured Forwarding (AF21)** +- Client source port range: **50,070-50,089** +- Protocol: **UDP** +- DSCP value: **40** +- DSCP class: **CS5** For more information on Teams Media and implementing QoS, see [Implement Quality of Service (QoS) in Microsoft Teams](../QoS-in-Teams.md). -### QoS with Microsoft Teams Rooms on Windows devices - -For Teams Rooms on Windows devices, you must configure Windows to add DSCP markings to the Teams Rooms application traffic. We recommend using Microsoft Intune to apply a Network QoS policy to Teams Rooms devices. You can use the Intune `NetworkQoSPolicy` configuration service provider (CSP) to apply the configuration based on the port ranges and DSCP value shown in [Quality of Service (QoS) with Microsoft Teams Rooms](#quality-of-service-qos-with-microsoft-teams-rooms). - -For more information on this Intune CSP, see [NetworkQoSPolicy CSP](/windows/client-management/mdm/networkqospolicy-csp). - -If your Teams Rooms devices are joined to Active Directory, you can use Group Policy to apply the markings. Follow the instructions for the Teams Desktop application, but don't specify the application name in the configuration; only specify the port range and the DSCP value in the configuration. - -For more information, see [Implement Quality of Service (QoS) in Microsoft Teams clients](../QoS-in-Teams-clients.md). - -### QoS with Microsoft Teams Rooms on Android devices - -For Teams Rooms on Android devices, you need to configure your Microsoft Teams tenant to insert QoS markings. Teams Rooms on Android devices honor this policy and apply the markings defined earlier in [Quality of Service (QoS) with Microsoft Teams Rooms](#quality-of-service-qos-with-microsoft-teams-rooms) with one exception, Application/screen sharing uses a DSCP value of 34 (AF41) aligned to video traffic. +For Teams phones, you need to configure your Microsoft Teams tenant to insert QoS markings. Teams phone devices honor this policy and apply the markings defined earlier in this document. For instructions on how to configure your tenant to insert QoS markings, see [Teams settings and policies reference](../settings-policies-reference.md). From 27b7fae397a7c0b76a162d7b6fa6974836570b7a Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 17 Oct 2024 17:46:27 -0500 Subject: [PATCH 50/87] Update authentication-best-practices-phones.md Adjusted for Teams phone --- .../authentication-best-practices-phones.md | 19 +++++-------------- 1 file changed, 5 insertions(+), 14 deletions(-) diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md index 0b7579bde2..c58b343ab1 100644 --- a/Teams/phones/authentication-best-practices-phones.md +++ b/Teams/phones/authentication-best-practices-phones.md @@ -56,23 +56,16 @@ Shared Teams devices such as Teams phones can't use the same requirements for en Microsoft recommends the following settings when deploying Teams phones in your organization. -### **Use a Resource account and curtail its password expiration** +### **Use a resource account and curtail its password expiration** -Teams shared phones should use an [Exchange resource mailbox](/exchange/recipients-in-exchange-online/manage-resource-mailboxes). Creating these mailboxes generates an account automatically. You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. - -Starting with Teams devices CY21 [Update #1](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones) (Teams version 1449/1.0.94.2021022403 for Teams phones) and [CY2021 Update #2](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_Rooms_on_Android) (Teams version 1449/1.0.96.2021051904 for Microsoft Teams Rooms on Android), tenant administrators can sign into Teams devices remotely. Instead of sharing passwords with technicians to set up devices, Tenant administrators should use remote sign-in to issue verification codes. You can sign into these devices from the Teams admin center. - -For more information, see [Remote provisioning and sign in for Teams Android devices](/MicrosoftTeams/devices/remote-provision-remote-login). +Teams shared phones should use an [resource account](/set-up-common-area-phones). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. ### **Review these Conditional Access policies** Microsoft Entra Conditional Access sets other requirements that devices must meet in order to sign in. For Teams phones, review the guidance that follows to determine if you have authored the policies that allow shared device users to do their work. > [!TIP] -> For an overview of Conditional Access, see [What is Conditional Access](/azure/active-directory/conditional-access/overview)? - ->[!TIP] ->Use either [named location](/azure/active-directory/conditional-access/location-condition) or [require compliant device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device) to secure shared devices. +> For an overview of Conditional Access, see [What is Conditional Access](/azure/active-directory/conditional-access/overview)? Use either [named location](/azure/active-directory/conditional-access/location-condition) or [require compliant device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device) to secure shared device resource accounts. ### You can use location-based access with named locations @@ -83,9 +76,7 @@ If shared Teams phones are provisioned in a well-defined location that can be id >[!NOTE] >Device compliance requires an Intune license. -If you're enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams devices can be configured for Conditional Access policies based on device compliance. For more information, see [Conditional Access: Require compliant or Microsoft Entra hybrid joined device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device). - -To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). +When enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams phones can be configured for Conditional Access policies based on device compliance. For more information, see [AOSP Device Management Compliance Policy](/microsoftteams/rooms/android-migration-guide#creating-a-aosp-management-compliance-policy). >[!NOTE] > Shared devices being used for *hot-desking* should be excluded from compliance policies. Compliance polices prevent the devices from enrolling into the hot desk user account. **Instead, use named locations to secure these devices**. @@ -93,7 +84,7 @@ To set compliance setting for your devices using Intune, see [Use compliance pol ### Exclude shared devices from sign-in frequency conditions -In Conditional Access, you can [configure sign-in frequency](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency) to require users to sign in again to access a resource after a specified time period. If sign-in frequency is enforced for room accounts, shared devices sign out until they're signed in again by an admin. Microsoft recommends excluding shared devices from any sign-in frequency policies. +In Conditional Access, you can [configure sign-in frequency](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency) to require users to sign in again to access a resource after a specified time period. If sign-in frequency is enforced for phone resource accounts, shared devices sign out until they're signed in again by an admin. Microsoft recommends excluding shared devices from any sign-in frequency policies. ### Using Filters for devices From 995de4d9566362fc9ebd2052524bca080c59e224 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 17 Oct 2024 17:52:26 -0500 Subject: [PATCH 51/87] Update remote-provision-remote-login-phones.md Adjusted to current GUI labels and for Phones --- .../remote-provision-remote-login-phones.md | 31 ++++++++----------- 1 file changed, 13 insertions(+), 18 deletions(-) diff --git a/Teams/phones/remote-provision-remote-login-phones.md b/Teams/phones/remote-provision-remote-login-phones.md index e0164c1c5c..82a96d7007 100644 --- a/Teams/phones/remote-provision-remote-login-phones.md +++ b/Teams/phones/remote-provision-remote-login-phones.md @@ -24,57 +24,52 @@ description: Learn how to remotely provision and sign in to Teams phones that ar # Remote provisioning and sign in for Teams phones -IT admins can remotely provision and sign in to a Teams Android device includiong Teams phones. To provision a Teams pohone remotely, the admin needs to upload the MAC IDs of the devices being provisioned and create a verification code. The entire process can be completed remotely from the Teams admin center. +IT admins can remotely provision and sign in to a Teams phone devices. To provision a Teams phone remotely, the admin needs to upload the MAC addresses of the devices being provisioned and create a verification code. The entire process can be completed remotely from Teams admin center. > [!NOTE] > Once you've signed in to a Teams phone, this feature isn't available. To use it again, the device must be reset to factory default settings. ## Supported devices -All Android and SIP devices certified by Microsoft can be provisioned remotely from Teams admin center. +All Teams phone devices certified by Microsoft can be provisioned remotely from Teams admin center. -Refer to the following for the list of certified hardware: - -Teams phones - [Certified Teams phones](../devices/teams-phones-certified-hardware.md) -Teams panels - [Certified Teams panels](../devices/teams-panels-certified-hardware.md) -Microsoft Teams Rooms on Android - [Teams Rooms on Android certified devices](../devices/certified-hardware-android.md?tabs=Android) -SIP devices - [Teams compatible devices](../devices/sip-gateway-plan.md#compatible-devices) +Refer to the following for the list of certified hardware: [Certified Teams phones](../devices/teams-phones-certified-hardware.md) ## Add a device MAC address Complete the following steps to provision a new device. 1. Sign in to the Teams admin center. -2. Expand **Teams Devices**. -3. Select **Provision new device** from the **Actions** tab. +2. Expand **Teams Devices** and select "Phones" +3. Select the **Actions** tab and then **Provision devices**. -In the **Provision new devices** window, you can either add the MAC address manually or upload a file. +In the **Provision devices** window, you can either add the MAC address manually or upload a file. ### Manually add a device MAC address -1. From the **Waiting on activation** tab, select **Add MAC ID**. +1. From the **Waiting on activation** tab, select **Add MAC addesses manually**. :::image type="content" alt-text="Screenshot of 'Add MAC address' for manually adding a the MAC address for a device." source="../media/remote-provision-6-new.png" lightbox="../media/remote-provision-6-new.png"::: -1. Enter the MAC ID. +1. Enter the MAC address. 1. Enter a location, which helps technicians identify where to install the devices. -1. Select **Apply** when finished. +1. Select **Save** when finished. ### Upload a file to add a device MAC address -1. From the **Waiting on activation** tab, select **Upload MAC IDs**. +1. From the **Waiting on activation** tab, select **Upload multiple MAC addresses**. 2. Download the file template. 3. Enter the MAC ID and location, and then save the file. -4. **Select file**, and then select **Upload**. +4. **Select a file**, and then select **Upload**. ## Generate a verification code You need a verification code for the devices. The verification code is generated in bulk or at the device level and is valid for 24 hours. -1. From the **Waiting on activation** tab, select an existing MAC ID. +1. From the **Waiting on activation** tab, select an existing MAC address. A password is created for the MAC address and is shown in the **Verification Code** column. -2. Provide the list of MAC IDs and verification codes to the field technicians. You can export the detail directly in a file and share the file with the technician who is doing the actual installation work. +2. Provide the list of MAC addresses and verification codes to the field technicians. You can export the detail directly in a file and share the file with the technician who is doing the actual installation work. ## Provision the device From c20334767fe9c82f7788c985c08a926f3ae6349e Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 17 Oct 2024 17:58:57 -0500 Subject: [PATCH 52/87] Update manage-teams-phones.md Updated for Phones --- Teams/phones/manage-teams-phones.md | 51 +++++++---------------------- 1 file changed, 11 insertions(+), 40 deletions(-) diff --git a/Teams/phones/manage-teams-phones.md b/Teams/phones/manage-teams-phones.md index 45ab28b5af..8eb2eca745 100644 --- a/Teams/phones/manage-teams-phones.md +++ b/Teams/phones/manage-teams-phones.md @@ -29,7 +29,7 @@ search.appverid: MET150 # Manage Teams phones -You can manage Teams phones used with Microsoft Teams in your organization from the Microsoft Teams admin center or in Teams Rooms Pro Management. You can view and manage the device inventory for your organization and do tasks such as update, restart, and monitor diagnostics for devices. You can also create and assign configuration profiles to a device or groups of devices. +You can manage Teams phones used with Microsoft Teams in your organization from Microsoft Teams admin center. You can view and manage the device inventory for your organization and do tasks such as update, restart, and monitor diagnostics for devices. You can also create and assign configuration profiles to a device or groups of devices. To manage your phones, such as change device configuration, restart devices, manage updates, or view device and peripheral health, you need to be assigned one of the following Microsoft 365 admin roles: @@ -38,46 +38,17 @@ To manage your phones, such as change device configuration, restart devices, man For more information about admin roles in Teams, see [Use Teams administrator roles to manage Teams](../using-admin-roles.md). -For more information about Teams Rooms Pro management role based access control, see [Role-based access control in the Microsoft Teams Rooms Pro Management Portal](../rooms/rooms-pro-rbac.md) - ## What Teams phones can you manage? -You can manage any device that's certified for, and enrolled in, Teams. A device is automatically enrolled the first time a user signs in to Teams on the device. For a list of certified devices that can be managed, see: - -- [Microsoft Teams Rooms](https://www.microsoft.com/microsoft-365/microsoft-teams/across-devices/devices/category?devicetype=20) -- [Conference phones](https://products.office.com/microsoft-teams/across-devices/devices/category?devicetype=73) -- [Desk phones](https://products.office.com/microsoft-teams/across-devices/devices/category?devicetype=34) -- [Teams displays](https://www.microsoft.com/microsoft-365/microsoft-teams/across-devices/devices/category?devicetype=34) -- [Teams panels](../devices/teams-panels.md) - -To manage Teams phones, in the left navigation of the [Microsoft Teams admin center](https://admin.teams.microsoft.com), go to **Teams Devices**, and then select the device type. Each type of device has its own respective section, which lets you manage them separately. - -## Manage Teams Rooms in Teams Rooms Pro Management - -To manage phones in Teams Rooms Pro Management, see [Microsoft Teams Rooms Pro Management Portal](../rooms/managed-meeting-rooms-portal.md) +You can manage any Teams phone that's certified for, and enrolled in, Teams. Each Teams phone is automatically enrolled the first time it's signed into Teams on the device. For a list of certified devices that can be managed, see: [Certified Teams phones](/microsoftteams/devices/teams-phones-certified-hardware) -## Manage Teams Rooms on Windows devices in Teams Admin Center - -You can use the Teams admin center to view and remotely manage your Teams phones across your organization. The Teams admin center makes it easy to see, at a glance, which devices are healthy and which need attention, and lets you focus on specific devices to see detailed information about device health, meeting performance, call quality, and peripherals. - -Here are some things you can do to manage your Teams phones. Teams phones devices can be found in the [Microsoft Teams admin center](https://admin.teams.microsoft.com) under **Teams Devices** > **Phones**. - -For details about how to manage your Teams Rooms devices, see [Manage Microsoft Teams Rooms](../rooms/rooms-manage.md). - -| To do this... | Do this | -|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Change settings on one or more devices | Select one or more devices > **Edit settings**. If you select multiple devices, the values you change will replace the values on all the selected devices. | -| Restart devices | Select one or more devices > **Restart**. When you restart a device, you can choose whether to restart the device immediately or select **Schedule restart** to restart the device at a specific date and time. The date and time you select are local to the device being restarted. | -| View meeting activity | Select a device name to open device details > **Activity**. When you open the **Activity** tab, you can see all the meetings that the device has participated in. This summary view shows the meeting start time, the number of participants, its duration, and the overall call quality. | -| View meeting details | Select a device name to open device details > **Activity** > select a meeting. When you open a meeting's details, you can see all of the participants in the meeting, how long they were in the call, the Teams session types, and their individual call quality. If you want to see technical information about a participant's call, select the participant's call start time. | +To manage Teams phones, in the left navigation of the [Microsoft Teams admin center](https://admin.teams.microsoft.com), go to **Teams Devices**, and then select **Phones**. ## Manage Teams phones -In the Teams admin center, you can view and manage phones, Teams Rooms on Android, Teams displays, and Teams panels enrolled in Teams in your organization. Information that you'll see for each device includes device name, manufacturer, model, user, status, action, last seen, and history. You can customize the view to show the information that fits your needs. - -Phones, Teams Rooms on Android, Teams displays, and Teams panels are automatically enrolled in Microsoft Intune if you've signed up for it. After a device is enrolled, device compliance is confirmed and conditional access policies are applied to the device. +In the Teams admin center, you can view and manage phones enrolled in Teams in your organization. Information that you'll see for each device includes device name, manufacturer, model, user, status, action, last seen, and history. You can customize the view to show the information that fits your needs. Teams Phones are automatically enrolled in Microsoft Intune if you've signed up for it. After a device is enrolled, device compliance is confirmed and conditional access policies are applied to the device. -Here are some examples of how you can manage phones, Teams Rooms on Android, Teams displays, and Teams panels in your organization. +Here are some examples of how you can manage phones in your organization. | To do this... | Do this | |-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -97,9 +68,9 @@ This video shows how to search for Teams devices. > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fHGQ?autoplay=false] -### View issues with Android-based Teams devices +### View issues with Teams phones -You can view issues with Android-based Teams devices in the health status column of the device list. +You can view issues with Teams phones in the health status column of the device list. In addition to the health status of the device, the following issues are also surfaced in the health status column: @@ -112,13 +83,13 @@ In addition to the health status of the device, the following issues are also su ### Use configuration profiles in Teams -Use configuration profiles to manage settings and features for different Teams devices including Teams phones in your organization. You can create or upload configuration profiles to include settings and features you want to enable or disable, and then assign a profile to a device or set of devices. +Use configuration profiles to manage settings and features for different Teams phones in your organization. You can create or upload configuration profiles to include settings and features you want to enable or disable, and then assign a profile to a device or set of devices. #### Create a configuration profile To create a configuration profile for a Teams device type: -1. In the left navigation, go to **Teams Devices** > select the Teams device type > **Configuration profiles**. For example, select **Teams Devices** > **Teams panels** > **Configuration profiles** to create a new configuration profile for Teams panels. +1. In the left navigation, go to **Teams Devices** > **Phone** > **Configuration profiles** to create a new configuration profile for Teams phone. 2. Click **Add**. 3. Enter a name for the profile and optionally add a friendly description. 4. Specify the settings you want for the profile, and then click **Save**. @@ -128,8 +99,8 @@ To create a configuration profile for a Teams device type: After creating a configuration profile for a Teams device type, assign it to one or more devices. -1. In the left navigation, go to **Teams Devices** > select the Teams device type. For example, to assign a configuration profile to a Teams panels device, select **Teams Devices** > **Teams phones**. +1. In the left navigation, go to **Teams Devices** > **Phones**. 2. Select one or more devices, and then click **Assign configuration**. 3. In the **Assign a configuration** pane, search for configuration profile to assign to the selected devices. 4. Click **Apply**. - For the devices to which you applied the configuration policy, the **Action** column displays **Config Update** and the **Configuration profile** column displays the configuration profile name. \ No newline at end of file + For the devices to which you applied the configuration policy, the **Action** column displays **Config Update** and the **Configuration profile** column displays the configuration profile name. From f61eb13817bbc968b41717bcdb90ed1194198cf4 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Thu, 17 Oct 2024 18:10:23 -0500 Subject: [PATCH 53/87] Update remote-update-teams-phones.md Adjusted for Teams phone --- Teams/phones/remote-update-teams-phones.md | 83 ++++++---------------- 1 file changed, 22 insertions(+), 61 deletions(-) diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index 4b474318b6..dc1af44bf0 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -23,7 +23,7 @@ description: Learn how to remotely update the firmware and apps for Teams phones # Remotely update firmware and software on Teams phones -Using Teams admin center, you can update your Teams devices, including Teams phones, Teams panels, and Teams Rooms that run on Android remotely. The following software components on your device can be updated from within Teams admin center: +Using Teams admin center, you can update your Teams devices, including Teams phones, remotely. The following software components on your device can be updated from within Teams admin center: - **Teams app** - available for Manual and Automatic updates @@ -31,11 +31,14 @@ Using Teams admin center, you can update your Teams devices, including Teams pho - **Company Portal app** - available for Manual updates only +- **Admin agent app** - available for Manual updates only + Updates for Teams app and device firmware happen automatically by default. However, you can update them manually as well. When you're applying updates manually, they can be applied immediately or scheduled to be updated on a future date and time that you set. > [!IMPORTANT] -> Microsoft strongly recommends using Teams Admin Center for managing and updating your Teams devices. Teams admin center ensures that all firmware and app updates installed on your Teams devices are validated and supported by Microsoft, which is essential for optimal performance and reliability of your Teams devices. By exclusively using firmware and app updates from the Teams Admin Center, you can avoid the risks and disruptions associated with alternative update methods. If customers use any other way to update, Microsoft can't guarantee to provide regular updates for those devices. -## Software versions on Teams admin center +> Microsoft strongly recommends using Teams Admin Center for managing and updating your Teams devices. Teams Admin Center ensures that all firmware and app updates installed on your Teams devices are validated and supported by Microsoft, which is essential for optimal performance and reliability of your Teams devices. By exclusively using firmware and app updates from the Teams Admin Center, you can avoid the risks and disruptions associated with alternative update methods. If customers use any other way to update, Microsoft can't guarantee to provide regular updates for those devices. + +## Software versions on Teams Admin Center All new software versions for Teams devices are made available on Teams admin center once they're published by Microsoft. New releases might have minimum software version requirements. In such cases, the new version is only made available if the device meets the requirements. Verify that the device is meeting those requirements, but especially the firmware is current and updated. @@ -45,36 +48,24 @@ Additionally, earlier versions of the software may also be made available and ar Firmware versions that have not been tested by Microsoft are labeled **Unknown version**. Devices running an unknown firmware version can't be automatically updated. These devices can only be updated manually. -Refer to this list for the details on new releases and the requirements that must be met. - -**Phone** - [Phone - Devices for Teams | Product release information](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-phones) - -**Displays** - [Displays - Devices for Teams | Product release information](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-displays) - -**Panels** - [Panels - Devices for Teams | Product release information](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-panels) - -**Microsoft Teams Rooms on Android** - [Microsoft Teams Rooms on Android Product release information](/microsoftteams/rooms/android-app-firmware) +Refer to this list for the details on new releases and the requirements that must be met: [Certified Teams phones - Firmware](/microsoftteams/devices/teams-phones-certified-hardware&tabs=firmware) ## Automatic updates -### Assign devices to update phases - -Assigning devices to an automatic update phase is a Teams Rooms Pro feature for Teams Rooms on Android devices. Devices with a Teams Rooms Basic license are assigned to the General phase. Any preconfigured phases are maintained, and no further changes are allowed. For more information, see [Microsoft Teams Rooms licenses](../rooms/rooms-licensing.md). - -Automatic updates of Teams devices using the Teams admin center isn't available in GCC High and DoD. Organizations in GCC High and DoD can, however, [manually update Teams devices](#manually-update-remote-devices) using the Teams admin center. +### Assign phones to update phases > [!NOTE] -> Some devices don't support automatic updates yet. Applying automatic update settings on devices that don't support automatic updates won't have any effect on those devices. For questions about whether your device will support automatic updates, contact your device manufacturer. -Devices within a phase will be updated gradually over a few weeks rather than all at once. To choose the automatic update phase for your devices, do the following steps: +> Devices within a phase will be updated gradually over a few weeks rather than all at once. Also, automatic updates of Teams devices using the Teams admin center isn't available in GCC High and DoD. Organizations in GCC High and DoD can, however, [manually update](#manually-update-remote-devices) using the Teams admin center. + +To choose the automatic update phase for your phones, do the following steps: 1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. -2. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +2. Navigate to **Teams devices** and then select **Phones**. 3. Select one or more devices and then select **Update**. -1. Under **Automatic updates**, select one of the following phases: +4. Under **Automatic updates**, select one of the following phases: - **Validation** This option is best for lab or test devices on which you can carry out any validation you need to perform. Updates start deployment as soon as the latest software version is released. Previously called **As soon as possible**. - **General** This is the default option and is best for most of your general-purpose devices. Firmware updates start deployment only after **30 days** from the release of the new firmware version. Teams app updates start deployment only after **15 days** from the release of the new Teams app version. Previously called **Defer by 30 days** (applicable for firmware updates). - - **Final** This option is best for devices used by VIPs and in large settings after large-scale validation is complete. Firmware updates start deployment only after **90 days** from the release of the new firmware version. Teams app updates start deployment only after **45 days** from the release of the new Teams app version. Previously called **Defer by 90 days** (applicable for firmware updates). - + - **Final** This option is best for devices used by VIPs and in large settings after large-scale validation is complete. Firmware updates start deployment only after **90 days** from the release of the new firmware version. Teams app updates start deployment only after **45 days** from the release of the new Teams app version. Previously called **Defer by 90 days** (applicable for firmware updates). 5. Select **Update**. To see which phase a device is in, see the **Automatic updates** column in the Teams admin center. To see which devices are part of a specific phase, use the **Filter** option then select **Auto-update phase**. @@ -84,10 +75,9 @@ If you need to revert or remove firmware from a device that has been updated, yo ### Configure Maintenance window If you want to configure the Maintenance window for a device, do the following steps: -1. Sign in to Microsoft Teams admin center by going to *https://admin.teams.microsoft.com*. - -1. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. -1. Follow the steps for [editing or creating a new configuration profile.](../devices/device-management.md#use-configuration-profiles-in-teams) +1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. +1. Navigate to **Teams devices** and then select **Phones**. +1. Follow the steps for [editing or creating a new configuration profile.](/phones/manage-teams-phones#use-configuration-profiles-in-teams) 1. Specify a suitable **Time window** by selecting a **Start time** and an **End time**. This time window follows the local timezone of the device. @@ -114,8 +104,8 @@ Option to configure maintenance window isn't available in GCC-High and DoD. If you want to check which software versions are currently rolling out for your devices, do the following steps: -1. Sign in to Microsoft Teams admin center by going to *https://admin.teams.microsoft.com*. -2. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. +2. Navigate to **Teams devices** and then select **Phones**. 3. Refer to the widget titled **Software auto-updates** to determine the number of active update paths. 4. On this widget, select **View details**. A dialogue box opens showing the list of active update paths with the following details: @@ -134,7 +124,7 @@ If you want to check which software versions are currently rolling out for your You can temporarily pause automatic updates for your tenant. When paused, Android based devices aren't automatically updated for the next 15 days. To pause the updates, do the following steps: 1. Sign in to Microsoft Teams admin center by visiting https://admin.teams.microsoft.com. -2. Navigate to **Teams devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +2. Navigate to **Teams devices** and then select **Phones**. 3. Under the **Actions** menu, select **Pause auto-updates**. 1. Updates automatically resume after 15 days. If you want to resume the updates before that, select **Resume auto-updates** from under the **Actions** menu. @@ -145,7 +135,7 @@ If you want to manually update devices using the Teams admin center, you can dec To manually update remote devices, do the following steps: 1. Sign in to Microsoft Teams admin center by visiting https://admin.teams.microsoft.com. -1. Navigate to **Teams Devices** and then select **Phones**, **Displays**, **Panels**, or **Teams Rooms on Android**. +1. Navigate to **Teams Devices** and then select **Phones**. 3. Select one or more devices and then select **Update**. 1. Under **Manual updates**, select **Schedule** if you want to schedule the update for the upcoming **Maintenance window** or a future date and time. The updates are applied at the date and time in the timezone selected in **Timezone**. @@ -167,43 +157,14 @@ To manage devices, you need to be a Global admin, Teams Service admin, or Teams This video shows how to update Teams devices. > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fxbK?autoplay=false] - -## App updates for paired devices - -The app updates for paired Microsoft Teams Rooms running Android and their paired touch consoles happen in sync to ensure a streamlined experience. This is applicable for the following software components - - -- Teams app - -- Company Portal app - -This is applicable for both automatic and manual updates. - -**For manual updates** - Whenever an update is being done for Microsoft Teams Rooms running Android or a Touch console, the paired device will also be updated. If an update is being scheduled for later, it will be scheduled for the same time on the paired device. - -**For automatic updates** - Automatic updates for Microsoft Teams Rooms on Android and their paired consoles also happen in sync. Automatic updates rollout according to the timeline dictated by the [Update phases](../devices/remote-update.md#assign-devices-to-update-phases). Touch consoles are updated according to the update phase of their paired Microsoft Teams Rooms on Android. There is no impact if both devices are in the same phase. If they are in different phases, the phase of the Teams Rooms on Android takes precedence. - -#### Conditions for updates to happen during sync - -- If Microsoft Teams Rooms on Android device and the paired touch console(s) are on the same version and have an update available, they are both updated in sync when one of them is updated. -- If Microsoft Teams Rooms on Android and the paired touch console(s) are on different versions - - - **Manual updates** - Administrators should ensure that the device(s) on the lower version is brought to parity for the devices to be updated in sync to the new version. - - **Automatic updates** - The device(s) on the lower version will be first brought to parity automatically. Once the devices are on the same version, they will be updated to the new version together. In this scenario, the move to the new version may be delayed as the parity updates will happen first. This is done to minimize conflicts between MTRoA and the paired console(s). #### Tracking update status -Administrators can track the status of these update operations from the 'History' section in the device page. Details for each operation are shown in the relevant row, including, if the operation was carried out for a paired device. More details are available on selecting the operation status. +Administrators can track the status of these update operations from the 'History' section in the device page. Details for each operation are shown in the relevant row. More details are available on selecting the operation status. ## Frequently asked questions about automatic updates 1. **Which software components are automatically updated?** Both Firmware and Teams app are automatically updated for eligible devices. Automatic updates for Teams app is a feature still in early phase, therefore you might see some delays in device reaching the update phase. The gradual roll out of the feature is being done to ensure minimal impact on devices. - -1. **What makes a device eligible to receive automatic updates?** The following conditions should be satisfied for the device to be eligible for automatic updates: - - Device model should be certified. See: - - Teams phones - [Certified Teams phones](../devices/teams-phones-certified-hardware.md) - - Teams panels - [Certified Teams panels](../devices/teams-panels-certified-hardware.md) - - Microsoft Teams Rooms on Android - [Teams Rooms on Android certified systems and peripherals](../devices/certified-hardware-android.md?tabs=Android) - - Current version should be 'Verified by Microsoft'. For more details, see [Software versions](#software-versions-on-teams-admin-center). - - Devices on versions that were released before 2022 generally do not have auto-update support. 1. **How fast does the rollout happen?** Eligible devices receive updates in weekly cycles based on the update phase they are in. For example, devices in General phase start receiving updates only after 15/30 days elapse since the new version was published. To ensure a stable rollout, the devices are updated gradually for a tenant and not all at once. Overall, the rollout of each new version takes a few weeks after the start of each update phase. From e955b71d68c0d13584a36fab66e380f7638604cb Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 14:40:23 +0530 Subject: [PATCH 54/87] added help topics and schema reference --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 132 ++++++++++++++++++ .../persistent-chat-add-in-main-page.md | 6 +- .../help-lscp/persistent-chat-add-in.md | 6 +- .../persistent-chat-category-main-page.md | 4 +- .../help-lscp/persistent-chat-category.md | 4 +- ...persistent-chat-configuration-main-page.md | 2 +- .../persistent-chat-configuration.md | 2 +- .../persistent-chat-policy-main-page.md | 2 +- .../help-lscp/persistent-chat-policy.md | 2 +- ...persistent-chat-backup-sql-server-store.md | 8 +- ...chat-compliance-backup-sql-server-store.md | 10 +- ...istent-chat-compliance-sql-server-store.md | 8 +- .../add-persistent-chat-file-store.md | 10 +- .../add-persistent-chat-next-hop-page.md | 4 +- .../add-persistent-chat-sql-server-store.md | 12 +- ...all-admission-control-settings-expander.md | 2 +- ...eate-persistent-chat-servers-scope-node.md | 4 +- ...efine-computers-in-persistent-chat-pool.md | 4 +- .../define-persistent-chat-fqdn.md | 4 +- ...es-and-options-for-persistent-chat-pool.md | 4 +- ...rsistent-chat-general-settings-expander.md | 6 +- .../persistent-chat-machines-expander.md | 4 +- ...sistent-chat-next-hop-settings-expander.md | 4 +- .../persistent-chat-scope-node.md | 4 +- 24 files changed, 190 insertions(+), 58 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 4dbe9883b3..907fdaf860 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -1144,3 +1144,135 @@ items: - name: Persistent Chat href: ../../SfbServer/management-tools/planning-tool/persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Schema reference + items: + - name: Persistent Chat database schema + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/persistent-chat-database-schema.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: List of Persistent Chat Server tables + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/list-of-persistent-chat-server-tables.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: List of Persistent Chat Server compliance tables + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/list-of-persistent-chat-server-compliance-tables.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Server table details + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/persistent-chat-server-table-details.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + items: + - name: tblADCookie + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tbladcookie.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalMemberDifference + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipalmemberdifference.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblADUpdates + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tbladupdates.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalMembers + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipalmembers.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalMeta + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipalmeta.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblSkippedAffiliations + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblskippedaffiliations.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalType + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipaltype.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipal + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipal.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalAffiliations + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipalaffiliations.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblNode + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblnode.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblRoleType + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblroletype.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblScopePrincipal + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblscopeprincipal.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalRole + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipalrole.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblSiopWhiteList + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblsiopwhitelist.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblEnumAttribute + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblenumattribute.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblEnumValue + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblenumvalue.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPrincipalInvites + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblprincipalinvites.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblChat + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblchat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblLastInviteId + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tbllastinviteid.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblLastChatId + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tbllastchatid.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblPreference + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblpreference.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblFileToken + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblfiletoken.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblServerIdentity + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblserveridentity.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblAdminLock + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tbladminlock.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblSystemRevision + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblsystemrevision.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblActivePeers + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblactivepeers.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblConfig + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblconfig.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblComplianceData + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblcompliancedata.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblComplianceFanout + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblcompliancefanout.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblComplianceParticipant + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblcomplianceparticipant.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: tblComplianceState + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblcompliancestate.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Sample Persistent Chat database queries + href: ../../SfbServer/schema-reference/persistent-chat-database-schema/sample-persistent-chat-database-queries.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Help topics + items: + - name: Help-LSCP + items: + - name: Persistent Chat Add-in + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Add-in Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Category + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Category Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Configuration + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Configuration Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Policy + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Policy Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: "Users: View Persistent Chat" + href: ../../SfbServer/help-topics/help-lscp/users-view-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Help-TopoBld + items: + - name: Add Persistent Chat Compliance Backup SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat Backup SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat Compliance SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat File Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Define Persistent Chat FQDN + href: ../../SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Define Computers in Persistent Chat Pool + href: ../../SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Define Properties and Options for Persistent Chat Pool + href: ../../SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Call Admission Control Settings Expander + href: ../../SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat General Settings Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Machines Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Next Hop Settings Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Scope Node + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Settings Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Create Persistent Chat Servers Scope Node + href: ../../SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat Next Hop Page + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json \ No newline at end of file diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md index 59e64b25b7..5cedbe1178 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md @@ -23,13 +23,13 @@ You can use the **Add-in** section of the **Persistent Chat** page to associate Add-ins are used to extend the in-room experience. A typical add-in might include a URL pointing to a Silverlight application that intercepts when a stock ticker is posted to a chat room, and shows the stock history in the extensibility pane. Other examples include embedding a OneNote 2013 URL in the chat room as an add-in to include some shared context, such as "Top of mind" or "Topic of the day." -To create Add-ins for Persistent Chat rooms, see [Configure add-ins for Persistent Chat rooms in Skype for Business Server 2015](../../manage/persistent-chat/configure-add-ins.md). If you are a Persistent Chat Administrator, you can create add-ins by using the control panel or Windows PowerShell cmdlets. +To create Add-ins for Persistent Chat rooms, see [Configure add-ins for Persistent Chat rooms in Skype for Business Server](../../manage/persistent-chat/configure-add-ins.md). If you are a Persistent Chat Administrator, you can create add-ins by using the control panel or Windows PowerShell cmdlets. ## Tasks you can perform You can perform the following tasks on the **Add-in** page: -- [Configure add-ins for Persistent Chat rooms in Skype for Business Server 2015](../../manage/persistent-chat/configure-add-ins.md) +- [Configure add-ins for Persistent Chat rooms in Skype for Business Server](../../manage/persistent-chat/configure-add-ins.md) ## To configure Add-ins for chat rooms @@ -57,4 +57,4 @@ The following lists describe the menus, command, fields, and properties on the p ## See also -For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). \ No newline at end of file +For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). \ No newline at end of file diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md index f32ea2379c..5ac9c381cc 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md @@ -23,13 +23,13 @@ You can use the **Add-in** section of the **Persistent Chat** page to associate Add-ins are used to extend the in-room experience. A typical add-in might include a URL pointing to a Silverlight application that intercepts when a stock ticker is posted to a chat room, and shows the stock history in the extensibility pane. Other examples include embedding a OneNote 2013 URL in the chat room as an add-in to include some shared context, such as "Top of mind" or "Topic of the day." -To create Add-ins for Persistent Chat rooms, see [Configure add-ins for Persistent Chat rooms in Skype for Business Server 2015](../../manage/persistent-chat/configure-add-ins.md). If you are a Persistent Chat Administrator, you can create add-ins by using the control panel or Windows PowerShell cmdlets. +To create Add-ins for Persistent Chat rooms, see [Configure add-ins for Persistent Chat rooms in Skype for Business Server](../../manage/persistent-chat/configure-add-ins.md). If you are a Persistent Chat Administrator, you can create add-ins by using the control panel or Windows PowerShell cmdlets. ## Tasks that you can perform You can perform the following tasks on the **Add-in** page: -- [Configure add-ins for Persistent Chat rooms in Skype for Business Server 2015](../../manage/persistent-chat/configure-add-ins.md) +- [Configure add-ins for Persistent Chat rooms in Skype for Business Server](../../manage/persistent-chat/configure-add-ins.md) ## To configure Add-ins for chat rooms @@ -57,4 +57,4 @@ The following lists describe the menus, command, fields, and properties on the p ## See also -For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). \ No newline at end of file +For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). \ No newline at end of file diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md index fc306d3056..e2a3465a95 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md @@ -23,7 +23,7 @@ You can use the **Category** section of the **Persistent Chat** page to configur Chat room categories may contain chat rooms, but not other categories. Each category describes its contents with metadata, such as _Name_ and _Description_. In addition, the category has properties which can be set to control the behavior of the chat rooms belonging to it, such as if the chat rooms allow _Invitations_ or _File Uploads_, or contain _Chat History_. -To create a new category, see [Manage categories in Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/categories.md). If you are a Persistent Chat Administrator, you can create categories by using the control panel or Windows PowerShell cmdlets. +To create a new category, see [Manage categories in Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/categories.md). If you are a Persistent Chat Administrator, you can create categories by using the control panel or Windows PowerShell cmdlets. ## Tasks that you can perform @@ -73,6 +73,6 @@ You can perform the following tasks on the **Category** page: ## See also -For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). +For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category.md index 365a1055e0..30ea375e6f 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category.md @@ -23,7 +23,7 @@ You can use the **Category** section of the **Persistent Chat** page to configur Chat room categories may contain chat rooms, but not other categories. Each category describes its contents with metadata, such as _Name_ and _Description_. In addition, the category has properties which can be set to control the behavior of the chat rooms belonging to it, such as if the chat rooms allow _Invitations_ or _File Uploads_, or contain _Chat History_. -To create a new category, see [Manage categories in Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/categories.md). If you are a Persistent Chat Administrator, you can create categories by using the control panel or Windows PowerShell cmdlets. +To create a new category, see [Manage categories in Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/categories.md). If you are a Persistent Chat Administrator, you can create categories by using the control panel or Windows PowerShell cmdlets. ## Tasks that you can perform @@ -76,6 +76,6 @@ You can perform the following tasks on the **Category** page: ## See also -For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). +For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md index f61123ff18..01cae41314 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md @@ -119,6 +119,6 @@ You can perform the following tasks on the **Persistent Chat Configuration** pag ## See also -For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). +For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration.md index d9d8d956fc..aeadfb87e6 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration.md @@ -121,6 +121,6 @@ You can perform the following tasks on the **Persistent Chat Configuration** pag ## See also -For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/persistent-chat.md). +For details about Persistent Chat Server features and capabilities, see [Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md), [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md), and [Manage Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/persistent-chat.md). diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md index 2697082117..1dfbaaede4 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md @@ -29,7 +29,7 @@ The global policy is created automatically when you deploy Persistent Chat Serve You can create and configure multiple site and user policies which, together with the global policy, enable users for Persistent Chat Server. Pool and site Persistent Chat Server policies override the global Persistent Chat Server policy, but only for users of that site. User policies override both global, pool, and site policies for the users to whom the user policy is assigned. > [!NOTE] -> To configure and use Persistent Chat Server, you must first use Topology Builder to add Persistent Chat Server support to the topology, and then publish the topology. For details, see [Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md). +> To configure and use Persistent Chat Server, you must first use Topology Builder to add Persistent Chat Server support to the topology, and then publish the topology. For details, see [Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md). ## Tasks that you can perform diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy.md index b0ab30a7f9..219954cf77 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy.md @@ -26,7 +26,7 @@ The global policy is created automatically when you deploy Persistent Chat Serve You can create and configure multiple site and user policies which, together with the global policy, enable users for Persistent Chat Server. Pool and site Persistent Chat Server policies override the global Persistent Chat Server policy, but only for users of that site. User policies override both global, pool, and site policies for the users to whom the user policy is assigned. > [!NOTE] -> To configure and use Persistent Chat Server, you must first use Topology Builder to add Persistent Chat Server support to the topology, and then publish the topology. For details, see [Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md). +> To configure and use Persistent Chat Server, you must first use Topology Builder to add Persistent Chat Server support to the topology, and then publish the topology. For details, see [Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md). ## Tasks that you can perform diff --git a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md index c2857eef6f..a64133950a 100644 --- a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md +++ b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md @@ -45,10 +45,10 @@ Click **Help** to access context sensitive help, such as this page. ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) +[Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) -[Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) +[Hardware and software requirements for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) -[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) +[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md index 2e500596ca..4647800f01 100644 --- a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md +++ b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md @@ -45,12 +45,12 @@ Click **Help** to access context sensitive help, such as this page. ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) +[Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) -[Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) +[Hardware and software requirements for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) -[Configure the Compliance service for Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/configure-compliance.md) +[Configure the Compliance service for Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/configure-compliance.md) -[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) +[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md index 4e9e09236f..aa3fd51674 100644 --- a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md +++ b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md @@ -45,10 +45,10 @@ Click **Help** to access context sensitive help, such as this page. ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) +[Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) -[Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) +[Hardware and software requirements for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) -[Configure the Compliance service for Persistent Chat Server in Skype for Business Server 2015](../../manage/persistent-chat/configure-compliance.md) +[Configure the Compliance service for Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/configure-compliance.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md index 85e90fec73..761745096a 100644 --- a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md +++ b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md @@ -32,12 +32,12 @@ You must specify a file share to be used as the file store for the Standard Edit ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) -[Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) +[Hardware and software requirements for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) -[Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) +[Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) -[Topology Basics for Skype for Business Server 2015](../../plan-your-deployment/topology-basics/topology-basics.md) +[Topology Basics for Skype for Business Server](../../plan-your-deployment/topology-basics/topology-basics.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md index 6f51ca41eb..7eafc5269a 100644 --- a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md +++ b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md @@ -14,11 +14,11 @@ ms.custom: ms.service: skype-for-business-server ms.localizationpriority: medium ms.assetid: a47c824d-a76a-413b-9335-bfe5ffef15db -description: "Use this page to define the Next Hop from the Persistent Chat Server server in your deployment. For more information about how to deploy Persistent Chat Server, see Deploy Persistent Chat Server in Skype for Business Server 2015." +description: "Use this page to define the Next Hop from the Persistent Chat Server server in your deployment. For more information about how to deploy Persistent Chat Server, see Deploy Persistent Chat Server in Skype for Business Server." --- # Add Persistent Chat Next Hop Page -Use this page to define the Next Hop from the Persistent Chat Server server in your deployment. For more information about how to deploy Persistent Chat Server, see [Deploy Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md). +Use this page to define the Next Hop from the Persistent Chat Server server in your deployment. For more information about how to deploy Persistent Chat Server, see [Deploy Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md). diff --git a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md index 0dfc1120a7..27bd2f5cdc 100644 --- a/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md +++ b/Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md @@ -45,14 +45,14 @@ Click **Help** to access context sensitive help, such as this page. ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) -[Hardware and software requirements for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) +[Hardware and software requirements for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/hardware-and-software-requirements.md) -[Server requirements for Skype for Business Server 2015](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) +[Server requirements for Skype for Business Server](../../plan-your-deployment/requirements-for-your-environment/server-requirements.md) -[Topology Basics for Skype for Business Server 2015](../../plan-your-deployment/topology-basics/topology-basics.md) +[Topology Basics for Skype for Business Server](../../plan-your-deployment/topology-basics/topology-basics.md) -[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) +[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md b/Skype/SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md index e18fd68758..4a763cd396 100644 --- a/Skype/SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md +++ b/Skype/SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md @@ -26,7 +26,7 @@ Call admission control (CAC) is a network of regions, sites, and subnets that en In the **Call Admission Control Setting** section of the **Edit Properties** dialog box for your site, you can change the following settings: -- **Enable Call Admission Control** Select this setting to enable CAC. Clear this setting to disable CAC for your entire network. To enable CAC, you must have configured your network for CAC. For details, see [Deploy call admission control in Skype for Business Server 2015](../../deploy/deploy-enterprise-voice/deploy-call-admission-control.md) in the Deployment documentation. +- **Enable Call Admission Control** Select this setting to enable CAC. Clear this setting to disable CAC for your entire network. To enable CAC, you must have configured your network for CAC. For details, see [Deploy call admission control in Skype for Business Server](../../deploy/deploy-enterprise-voice/deploy-call-admission-control.md) in the Deployment documentation. - **Front End pool to run Call Admission Control** If you enabled CAC, you can change the pool that runs it. Select the pool from the drop-down list. diff --git a/Skype/SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md b/Skype/SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md index 120ee3a26f..abf1958dbe 100644 --- a/Skype/SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md +++ b/Skype/SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md @@ -31,6 +31,6 @@ In addition to the New Persistent Chat Pool option, you can perform the followin ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md b/Skype/SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md index 0197cc6045..063dab18a3 100644 --- a/Skype/SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md +++ b/Skype/SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md @@ -37,6 +37,6 @@ Click **Help** to access context sensitive help, such as this page. ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md b/Skype/SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md index 60f1322b28..f6ca478776 100644 --- a/Skype/SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md +++ b/Skype/SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md @@ -25,6 +25,6 @@ You must also define a **Pool FQDN** for the Persistent Chat Server or Persisten ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md b/Skype/SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md index f18894ddb4..f593e42e7b 100644 --- a/Skype/SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md +++ b/Skype/SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md @@ -47,6 +47,6 @@ Click **Help** to access context sensitive help, such as this page. ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md index 3e2f845c51..aadf4e8cb8 100644 --- a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md +++ b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md @@ -111,8 +111,8 @@ You edit the **Associations** settings for the Persistent Chat Server or Persist ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) -[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server 2015](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) +[Configure high availability and disaster recovery for Persistent Chat Server in Skype for Business Server](../../deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md index f98131598a..0eb8829899 100644 --- a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md +++ b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md @@ -31,6 +31,6 @@ You set a deployed Persistent Chat Server or Persistent Chat Server pool to inac ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md index 9967090af6..8d44bbaaba 100644 --- a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md +++ b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md @@ -29,6 +29,6 @@ You configure the Persistent Chat **Next hop pool** by selecting a Front End Ser ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) diff --git a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md index e6c65f5179..be31f999bd 100644 --- a/Skype/SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md +++ b/Skype/SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md @@ -27,6 +27,6 @@ To begin the creation of a new Persistent Chat Server or Persistent Chat Server ## See also -[Plan for Persistent Chat Server in Skype for Business Server 2015](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) +[Plan for Persistent Chat Server in Skype for Business Server](../../plan-your-deployment/persistent-chat-server/persistent-chat-server.md) -[Add Persistent Chat Server to your Skype for Business Server 2015 topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) +[Add Persistent Chat Server to your Skype for Business Server topology](../../deploy/deploy-persistent-chat-server/add-persistent-chat-server.md) From c96f0bb917fecf186241c2b7cae923ab6107ff1d Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 14:52:15 +0530 Subject: [PATCH 55/87] added schema reference --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 57 +------------------------ 1 file changed, 1 insertion(+), 56 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 907fdaf860..f9a45845a6 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -1220,59 +1220,4 @@ href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblcompliancestate.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Sample Persistent Chat database queries href: ../../SfbServer/schema-reference/persistent-chat-database-schema/sample-persistent-chat-database-queries.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Help topics - items: - - name: Help-LSCP - items: - - name: Persistent Chat Add-in - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Add-in Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Category - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Category Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Configuration - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Configuration Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Policy - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Policy Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: "Users: View Persistent Chat" - href: ../../SfbServer/help-topics/help-lscp/users-view-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Help-TopoBld - items: - - name: Add Persistent Chat Compliance Backup SQL Server Store - href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Add Persistent Chat Backup SQL Server Store - href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Add Persistent Chat Compliance SQL Server Store - href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Add Persistent Chat File Store - href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Define Persistent Chat FQDN - href: ../../SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Define Computers in Persistent Chat Pool - href: ../../SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Define Properties and Options for Persistent Chat Pool - href: ../../SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Add Persistent Chat SQL Server Store - href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Call Admission Control Settings Expander - href: ../../SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat General Settings Expander - href: ../../SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Machines Expander - href: ../../SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Next Hop Settings Expander - href: ../../SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Scope Node - href: ../../SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Settings Expander - href: ../../SfbServer/help-topics/help-topobld/persistent-chat-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Create Persistent Chat Servers Scope Node - href: ../../SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Add Persistent Chat Next Hop Page - href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json \ No newline at end of file + \ No newline at end of file From 050378ea24c0a18090c020683d976eff47177940 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 14:57:07 +0530 Subject: [PATCH 56/87] fixed acrolinx --- .../persistent-chat-category-main-page.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md index e2a3465a95..1d47f334e1 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md @@ -23,7 +23,7 @@ You can use the **Category** section of the **Persistent Chat** page to configur Chat room categories may contain chat rooms, but not other categories. Each category describes its contents with metadata, such as _Name_ and _Description_. In addition, the category has properties which can be set to control the behavior of the chat rooms belonging to it, such as if the chat rooms allow _Invitations_ or _File Uploads_, or contain _Chat History_. -To create a new category, see [Manage categories in Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/categories.md). If you are a Persistent Chat Administrator, you can create categories by using the control panel or Windows PowerShell cmdlets. +To create a new category, see [Manage categories in Persistent Chat Server in Skype for Business Server](../../manage/persistent-chat/categories.md). If you're a Persistent Chat Administrator, you can create categories by using the control panel or Windows PowerShell cmdlets. ## Tasks that you can perform @@ -37,17 +37,17 @@ You can perform the following tasks on the **Category** page: ## To configure categories for Persistent Chat rooms -1. From a user account that is assigned to the CsPersistentChatAdministrator or CsAdministrator role, log on to any computer in your internal deployment. +1. From a user account that is assigned to the CsPersistentChatAdministrator or CsAdministrator role, sign in any computer in your internal deployment. -2. From the **Start** menu, select the Skype for Business Server Control Panel or open a browser window, and then enter the Admin URL. . +2. From the **Start** menu, select the Skype for Business Server Control Panel or open a browser window, and then enter the Admin URL. -3. In the left navigation bar, click **Persistent Chat**, and then click **Category**. +3. In the left navigation bar, select **Persistent Chat**, and then select **Category**. For multiple Persistent Chat Server pool deployments, select the appropriate pool from the drop-down list. -4. On the **Category** page, click **New** or **Edit**. +4. On the **Category** page, select **New** or **Edit**. -5. In **Select a Service**, select the service corresponding to the Persistent Chat Server pool on which the category needs to be created. The service is the Persistent Chat Server pool that the Persistent Chat (client) uses to identify which pool the category belongs to. A category can belong to only one Persistent Chat Server pool, and cannot be moved to another one, or shared with another pool. +5. In **Select a Service**, select the service corresponding to the Persistent Chat Server pool on which the category needs to be created. The service is the Persistent Chat Server pool that the Persistent Chat (client) uses to identify which pool the category belongs to. A category can belong to only one Persistent Chat Server pool, and can't be moved to another one, or shared with another pool. 6. In **New Category**, do the following: @@ -55,11 +55,11 @@ You can perform the following tasks on the **Category** page: 8. In **Description**, provide a detailed description for the room category (for example, a room category for Contoso). -9. To control whether invitations can be enabled for chat rooms that belong to this category, select or clear the **Enable invitations** check box. If selected, rooms in this category may have invitations on or off; if cleared, the rooms in this category are not allowed to have invitations. If a room has invitations on, when a new member is added to a room, he or she gets a notification of the new room in their Persistent Chat client. +9. To control whether invitations can be enabled for chat rooms that belong to this category, select or clear the **Enable invitations** check box. If selected, rooms in this category may have invitations on or off; if cleared, the rooms in this category aren't allowed to have invitations. If a room has invitations on, when a new member is added to a room, he or she gets a notification of the new room in their Persistent Chat client. -10. To control file uploads in chat rooms belonging to this category, select or clear the **Enable file upload** check box. If selected, the rooms of this category can enable or disable file uploads; if cleared, the rooms of this category are not allowed to have file uploads. +10. To control file uploads in chat rooms belonging to this category, select or clear the **Enable file upload** check box. If selected, the rooms of this category can enable or disable file uploads; if cleared, the rooms of this category aren't allowed to have file uploads. -11. To control chat history, select or clear the **Enable chat history** check box. If selected, room chats become persistent; otherwise, chat messages are not persisted. If compliance is enabled, room chats will be saved in compliance, but users will not be able to access older messages. This option can be used for rooms designated for real-time, ad hoc collaborations that don't need chat history to be persisted. +11. To control chat history, select or clear the **Enable chat history** check box. If selected, room chats become persistent; otherwise, chat messages aren't persisted. If compliance is enabled, room chats will be saved in compliance, but users won't be able to access older messages. This option can be used for rooms designated for real-time, ad hoc collaborations that don't need chat history to be persisted. 12. In **Edit Category**, do the following: @@ -69,7 +69,7 @@ You can perform the following tasks on the **Category** page: - In **Membership**, in the **Creators** section, add or remove users and other Active Directory principals associated with creators for the category. A creator is a user who has permissions to create chat rooms and assign chat room managers and members. -13. Click **Commit**. +13. Select **Commit**. ## See also From 2b681f0d26a28d087dc632ea1fe7774808827209 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 15:09:17 +0530 Subject: [PATCH 57/87] fixed suggestions --- Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md | 2 +- .../help-topics/help-lscp/persistent-chat-category-main-page.md | 2 +- .../help-lscp/persistent-chat-configuration-main-page.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md index 5ac9c381cc..3b04054db5 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md @@ -14,7 +14,7 @@ ms.custom: ms.service: skype-for-business-server ms.localizationpriority: medium ms.assetid: 66124a70-67e8-4bda-9da5-8ab13afccf49 -description: "You can use the Add-in section of the Persistent Chat page to associate URLs with Persistent Chat rooms. These URLs appear in the client in the chat room in the conversation extensibility pane. An administrator must add Add-ins to the list of registered add-ins, and chat room managers/Creators must associate rooms with one of the registered add-ins before users can see this upgrade in their client." +description: "Use the Add-in section of the Persistent Chat page to associate URLs with Persistent Chat rooms. These URLs appear in the client in the chat room in the conversation extensibility pane. An administrator must add Add-ins to the list of registered add-ins, and chat room managers/Creators must associate rooms with one of the registered add-ins before users can see this upgrade in their client." --- # Persistent Chat Add-in diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md index 1d47f334e1..6055532a11 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md @@ -14,7 +14,7 @@ ms.custom: ms.service: skype-for-business-server ms.localizationpriority: medium ms.assetid: b71c6e6f-681c-4230-954d-3e95ab64ca00 -description: "You can use the Category section of the Persistent Chat page to configure categories. A Persistent Chat room category is a logical structure for organizing chat rooms. A category defines a default set of access control lists (ACLs) for controlling the users and user groups who may create or join the chat rooms. You can use categories enforce ethical walls between different subdivisions within their organizations." +description: "Use the Category section of the Persistent Chat page to configure categories. A Persistent Chat room category is a logical structure for organizing chat rooms. A category defines a default set of access control lists (ACLs) for controlling the users and user groups who may create or join the chat rooms. You can use categories enforce ethical walls between different subdivisions within their organizations." --- # Persistent Chat Category Main Page diff --git a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md index 01cae41314..c5d6c4d880 100644 --- a/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md +++ b/Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md @@ -14,7 +14,7 @@ ms.custom: ms.service: skype-for-business-server ms.localizationpriority: medium ms.assetid: 1e75d352-12cf-4548-9301-5d4c0e1c8f46 -description: "Your Persistent Chat Server deployment can host many concurrent Persistent Chat rooms. Chat rooms can be organized into a set of categories on the server. Each chat room belongs to one category, and inherits some settings from that category. This organization creates a useful structure for identifying conversations, based on their business purpose, and facilitates delegated administration and simplified management." +description: "Persistent Chat Server deployment can host many concurrent Persistent Chat rooms. Chat rooms are organized into a set of categories on the server. Each chat room belongs to one category, and inherits some settings from that category. This organization creates a useful structure for identifying conversations, based on their business purpose, and facilitates delegated administration and simplified management." --- # Persistent Chat Configuration Main Page From 7c4fa510a38b73ecf729863fdbcfc171586525c6 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 15:15:41 +0530 Subject: [PATCH 58/87] adding help lscp --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index f9a45845a6..2a6a17dd3b 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -1220,4 +1220,25 @@ href: ../../SfbServer/schema-reference/persistent-chat-database-schema/tblcompliancestate.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Sample Persistent Chat database queries href: ../../SfbServer/schema-reference/persistent-chat-database-schema/sample-persistent-chat-database-queries.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - \ No newline at end of file + - name: Help topics + items: + - name: Help-LSCP + items: + - name: Persistent Chat Add-in + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Add-in Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Category + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Category Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Configuration + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Configuration Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Policy + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Policy Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: "Users: View Persistent Chat" + href: ../../SfbServer/help-topics/help-lscp/users-view-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json From d19f3d656567bb7c806e13cb4afe8d0d59aaecc5 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 15:20:18 +0530 Subject: [PATCH 59/87] fixed error --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 28 ++++++++++++------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 2a6a17dd3b..065c2db412 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -1228,17 +1228,17 @@ href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: Persistent Chat Add-in Main Page href: ../../SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Category - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Category Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Configuration - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Configuration Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Policy - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: Persistent Chat Policy Main Page - href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - - name: "Users: View Persistent Chat" - href: ../../SfbServer/help-topics/help-lscp/users-view-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Category + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Category Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Configuration + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Configuration Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Policy + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Policy Main Page + href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: "Users: View Persistent Chat" + href: ../../SfbServer/help-topics/help-lscp/users-view-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json From 3f966470abafbd89f93031962e72bdb1aab6b020 Mon Sep 17 00:00:00 2001 From: Meghana Athavale Date: Fri, 18 Oct 2024 15:26:22 +0530 Subject: [PATCH 60/87] added help-topobld --- Skype/SfBServer2019/sfbs2019toc/toc.yml | 34 +++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/Skype/SfBServer2019/sfbs2019toc/toc.yml b/Skype/SfBServer2019/sfbs2019toc/toc.yml index 065c2db412..65d154675f 100644 --- a/Skype/SfBServer2019/sfbs2019toc/toc.yml +++ b/Skype/SfBServer2019/sfbs2019toc/toc.yml @@ -1242,3 +1242,37 @@ href: ../../SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json - name: "Users: View Persistent Chat" href: ../../SfbServer/help-topics/help-lscp/users-view-persistent-chat.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Help-TopoBld + items: + - name: Add Persistent Chat Compliance Backup SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat Backup SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat Compliance SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat File Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Define Persistent Chat FQDN + href: ../../SfbServer/help-topics/help-topobld/define-persistent-chat-fqdn.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Define Computers in Persistent Chat Pool + href: ../../SfbServer/help-topics/help-topobld/define-computers-in-persistent-chat-pool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Define Properties and Options for Persistent Chat Pool + href: ../../SfbServer/help-topics/help-topobld/define-properties-and-options-for-persistent-chat-pool.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat SQL Server Store + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Call Admission Control Settings Expander + href: ../../SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat General Settings Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-general-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Machines Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-machines-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Next Hop Settings Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-next-hop-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Scope Node + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-scope-node.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Persistent Chat Settings Expander + href: ../../SfbServer/help-topics/help-topobld/persistent-chat-settings-expander.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Create Persistent Chat Servers Scope Node + href: ../../SfbServer/help-topics/help-topobld/create-persistent-chat-servers-scope-node.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json + - name: Add Persistent Chat Next Hop Page + href: ../../SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md?toc=/SkypeForBusiness/sfbs2019toc/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json \ No newline at end of file From dd7f42bf2ee136fafbda47c81cb9ea58918f4346 Mon Sep 17 00:00:00 2001 From: Matt Slomka Date: Fri, 18 Oct 2024 10:31:38 -0500 Subject: [PATCH 61/87] Update remote-update-teams-phones.md --- Teams/phones/remote-update-teams-phones.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index dc1af44bf0..f88b787d22 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -77,7 +77,7 @@ If you want to configure the Maintenance window for a device, do the following s 1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. 1. Navigate to **Teams devices** and then select **Phones**. -1. Follow the steps for [editing or creating a new configuration profile.](/phones/manage-teams-phones#use-configuration-profiles-in-teams) +1. Follow the steps for [editing or creating a new configuration profile.](/manage-teams-phones.md#use-configuration-profiles-in-teams) 1. Specify a suitable **Time window** by selecting a **Start time** and an **End time**. This time window follows the local timezone of the device. From c682b4b51e5cd3ec0bac871950f1136bde6cecd7 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 09:50:55 -0700 Subject: [PATCH 62/87] Update manage-teams-phones.md --- Teams/phones/manage-teams-phones.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/Teams/phones/manage-teams-phones.md b/Teams/phones/manage-teams-phones.md index 8eb2eca745..9f70928ca9 100644 --- a/Teams/phones/manage-teams-phones.md +++ b/Teams/phones/manage-teams-phones.md @@ -22,7 +22,7 @@ f1.keywords: ms.custom: - ms.teamsadmincenter.managedevices.overview - ms.teamsadmincenter.devicemanagement.overview -description: Manage Teams phones you have deployed in your organization. +description: Manage Teams phones you deployed in your organization. ms.localizationpriority: medium search.appverid: MET150 --- @@ -40,7 +40,7 @@ For more information about admin roles in Teams, see [Use Teams administrator ro ## What Teams phones can you manage? -You can manage any Teams phone that's certified for, and enrolled in, Teams. Each Teams phone is automatically enrolled the first time it's signed into Teams on the device. For a list of certified devices that can be managed, see: [Certified Teams phones](/microsoftteams/devices/teams-phones-certified-hardware) +You can manage any Teams phone certified for, and enrolled in, Teams. Each Teams phone is automatically enrolled the first time it's signed into Teams on the device. For a list of certified devices that can be managed, see: [Certified Teams phones](/microsoftteams/devices/teams-phones-certified-hardware) To manage Teams phones, in the left navigation of the [Microsoft Teams admin center](https://admin.teams.microsoft.com), go to **Teams Devices**, and then select **Phones**. @@ -50,7 +50,7 @@ In the Teams admin center, you can view and manage phones enrolled in Teams in y Here are some examples of how you can manage phones in your organization. -| To do this... | Do this | +| **Task** | **Action** | |-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Change device information | Select a device > **Edit**. You can edit details such as device name, asset tag, and add notes. | | Manage software updates | Select a device > **Update**. You can view the list of software and firmware updates available for the device and choose the updates to install. For more information about updating devices, see [Update Teams devices remotely](../devices/remote-update.md) | @@ -59,9 +59,9 @@ Here are some examples of how you can manage phones in your organization. | Restart devices | Select one or more devices > **Restart**. | | Filter devices using device tags | Select the filter icon, select the **Tag** field, specify a device tag to filter on, and select **Apply**. For more information about filtering devices using device tags, see [Use filters to return devices with a specific tag](../devices/manage-device-tags.md#use-filters-to-return-devices-with-a-specific-tag). | |Schedule device actions|Actions like **Restart** and **Software update** can be scheduled for the preferred date and time.| -| View device history and diagnostics | Under the **History** column, click the **View** link for a device to view its update history and diagnostic details. | +| View device history and diagnostics | Under the **History** column, select the **View** link for a device to view its update history and diagnostic details. | |View device action details|In the **History** tab on the device page, select the action status to view the details of the action.| -|Cancel device actions|From the **History** section, you can cancel any action that is in a Queued or Scheduled state (not in progress or completed) to prevent execution. This option is accessible from the **History** tab in the device page and the **History** column in the list page. You can select multiple actions to cancel at once. Paired actions will be canceled together if execution hasn't started.| +|Cancel device actions|From the **History** section, you can cancel any action that is in a Queued or Scheduled state (not in progress or completed) to prevent execution. This option is accessible from the **History** tab in the device page and the **History** column in the list page. You can select multiple actions to cancel at once. Paired actions are canceled together if execution didn't start.| |Actions on multiple devices|You can select multiple devices from the list page and perform an action on them at once. This is applicable for **Restart**, **Software update**, **Assign configuration**, **Manage tags**, **Remove device**, and **Sign-out**.| This video shows how to search for Teams devices. @@ -74,8 +74,8 @@ You can view issues with Teams phones in the health status column of the device In addition to the health status of the device, the following issues are also surfaced in the health status column: -1. **Sign-in errors exist** - There was an issue signing-in to the device. Select the health status of the device to view the time the sign-in failure occurred, the account that attempted to sign into the device, the reason for the failure, and a history of previous sign-in failures. -2. **No connection** - The connection between Teams admin center and the device has been lost. Restart or update the device through Teams admin center to resolve this error. +1. **Sign-in errors exist** - There was an issue signing in to the device. Select the health status of the device to view the time the sign-in failure occurred, the account that attempted to sign into the device, the reason for the failure, and a history of previous sign-in failures. +2. **No connection** - The connection between Teams admin center and the device was lost. Restart or update the device through Teams admin center to resolve this error. 3. **Multiple issues** - One or more errors exist. Select the health status of the device to view the list of issues. > [!NOTE] @@ -90,9 +90,9 @@ Use configuration profiles to manage settings and features for different Teams p To create a configuration profile for a Teams device type: 1. In the left navigation, go to **Teams Devices** > **Phone** > **Configuration profiles** to create a new configuration profile for Teams phone. -2. Click **Add**. +2. Select **Add**. 3. Enter a name for the profile and optionally add a friendly description. -4. Specify the settings you want for the profile, and then click **Save**. +4. Specify the settings you want for the profile, and then Select **Save**. The newly created configuration profile is displayed in the list of profiles. #### Assign a configuration profile @@ -100,7 +100,7 @@ To create a configuration profile for a Teams device type: After creating a configuration profile for a Teams device type, assign it to one or more devices. 1. In the left navigation, go to **Teams Devices** > **Phones**. -2. Select one or more devices, and then click **Assign configuration**. +2. Select one or more devices, and then Select **Assign configuration**. 3. In the **Assign a configuration** pane, search for configuration profile to assign to the selected devices. -4. Click **Apply**. +4. Select **Apply**. For the devices to which you applied the configuration policy, the **Action** column displays **Config Update** and the **Configuration profile** column displays the configuration profile name. From 69a98d5d37eda71e530795de4781d8bbe66727c9 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 09:53:58 -0700 Subject: [PATCH 63/87] Updating build errors --- Teams/phones/authentication-best-practices-phones.md | 2 +- Teams/phones/prepare-network-teams-phones.md | 2 +- Teams/phones/remote-update-teams-phones.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md index c58b343ab1..63a4314556 100644 --- a/Teams/phones/authentication-best-practices-phones.md +++ b/Teams/phones/authentication-best-practices-phones.md @@ -58,7 +58,7 @@ Microsoft recommends the following settings when deploying Teams phones in your ### **Use a resource account and curtail its password expiration** -Teams shared phones should use an [resource account](/set-up-common-area-phones). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. +Teams shared phones should use an [resource account](set-up-common-area-phones). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. ### **Review these Conditional Access policies** diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md index cbe08a939c..4437475525 100644 --- a/Teams/phones/prepare-network-teams-phones.md +++ b/Teams/phones/prepare-network-teams-phones.md @@ -31,7 +31,7 @@ In order to function properly, Microsoft Phone devices must have access to a net - Review access to: Microsoft Teams, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Android Device - Network Security](/microsoftteams/rooms/security?tabs=Android#network-security) -- Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Phones](/microsoftteams/devices/qos-on-teams-phones) +- Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Phones](qos-on-teams-phones.md) - Review if your organization utilizes a proxy, you need the proxy address or proxy autoconfiguration (PAC) file url diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index f88b787d22..4a92ea1c80 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -48,7 +48,7 @@ Additionally, earlier versions of the software may also be made available and ar Firmware versions that have not been tested by Microsoft are labeled **Unknown version**. Devices running an unknown firmware version can't be automatically updated. These devices can only be updated manually. -Refer to this list for the details on new releases and the requirements that must be met: [Certified Teams phones - Firmware](/microsoftteams/devices/teams-phones-certified-hardware&tabs=firmware) +Refer to this list for the details on new releases and the requirements that must be met: [Certified Teams phones - Firmware](../devices/teams-phones-certified-hardware&tabs=firmware) ## Automatic updates @@ -77,7 +77,7 @@ If you want to configure the Maintenance window for a device, do the following s 1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. 1. Navigate to **Teams devices** and then select **Phones**. -1. Follow the steps for [editing or creating a new configuration profile.](/manage-teams-phones.md#use-configuration-profiles-in-teams) +1. Follow the steps for [editing or creating a new configuration profile.](manage-teams-phones.md#use-configuration-profiles-in-teams) 1. Specify a suitable **Time window** by selecting a **Start time** and an **End time**. This time window follows the local timezone of the device. From efbcfe511e9b7e49b0b43dc8b72ef2c307583f08 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 10:00:55 -0700 Subject: [PATCH 64/87] Final fixes --- Teams/phones/authentication-best-practices-phones.md | 2 +- Teams/phones/remote-update-teams-phones.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md index 63a4314556..aa340a134a 100644 --- a/Teams/phones/authentication-best-practices-phones.md +++ b/Teams/phones/authentication-best-practices-phones.md @@ -58,7 +58,7 @@ Microsoft recommends the following settings when deploying Teams phones in your ### **Use a resource account and curtail its password expiration** -Teams shared phones should use an [resource account](set-up-common-area-phones). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. +Teams shared phones should use an [resource account](set-up-common-area-phones.md). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. ### **Review these Conditional Access policies** diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index 4a92ea1c80..9a789784dc 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -48,7 +48,7 @@ Additionally, earlier versions of the software may also be made available and ar Firmware versions that have not been tested by Microsoft are labeled **Unknown version**. Devices running an unknown firmware version can't be automatically updated. These devices can only be updated manually. -Refer to this list for the details on new releases and the requirements that must be met: [Certified Teams phones - Firmware](../devices/teams-phones-certified-hardware&tabs=firmware) +Refer to this list for the details on new releases and the requirements that must be met: [Certified Teams phones - Firmware](../devices/teams-phones-certified-hardware.md&tabs=firmware) ## Automatic updates From f7ca7ea11cc62e0980a394de2e141c01e0dde8a6 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 10:11:54 -0700 Subject: [PATCH 65/87] Update toc.yml --- Teams/toc.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 2bdf750523..5996435ad8 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1404,7 +1404,7 @@ items: - name: App support href: app-support-on-Teams-panels.md - name: Check-in and auto release - href: devices/check-in-and-room-release.md + href: devices/check-in-and-auto-release.md - name: Reserve rooms with a QR code href: devices/reserving-rooms-with-a-qr-code.md - name: Custom backgrounds on Teams panels @@ -1431,11 +1431,11 @@ items: href: rooms/rooms-authentication.md - name: Authentication for Teams Android devices href: devices/authentication-best-practices-for-android-devices.md - - name: Conditional Access-related issues + - name: Conditional Access-related known issues href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-android-devices-conditional-access-issues - name: Release notes items: - - name: Teams Rooms release notesf + - name: Teams Rooms release notes href: rooms/rooms-release-note.md - name: Teams panels release notes href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels From 8540beb916a9c3da96d157922162baf751bee948 Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 10:14:14 -0700 Subject: [PATCH 66/87] Update remote-update-teams-phones.md --- Teams/phones/remote-update-teams-phones.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md index 9a789784dc..938535ec4c 100644 --- a/Teams/phones/remote-update-teams-phones.md +++ b/Teams/phones/remote-update-teams-phones.md @@ -48,7 +48,7 @@ Additionally, earlier versions of the software may also be made available and ar Firmware versions that have not been tested by Microsoft are labeled **Unknown version**. Devices running an unknown firmware version can't be automatically updated. These devices can only be updated manually. -Refer to this list for the details on new releases and the requirements that must be met: [Certified Teams phones - Firmware](../devices/teams-phones-certified-hardware.md&tabs=firmware) +Refer to this list for the details on new releases and the requirements that must be met. See [Certified Teams phones - Firmware](../devices/teams-phones-certified-hardware.md?tabs=firmware) ## Automatic updates From 9a8b6d2f24c026f19ad23d2dcfd552cb51cc0b9b Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 10:35:43 -0700 Subject: [PATCH 67/87] Update toc.yml --- Teams/toc.yml | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 5996435ad8..94b65bdd96 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1442,9 +1442,9 @@ items: - name: Troubleshooting and known issues items: - name: Teams Rooms on Windows - href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-windows + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-windows - name: Teams Rooms on Android - href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues-android + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android - name: Deploy items: - name: Overview @@ -1481,8 +1481,6 @@ items: href: rooms/create-otp.md - name: Set up using one-time passwords href: rooms/first-time-setup.md - - name: Manual Join to Entra ID and Intune - href: /entra/identity/devices/device-join-plan.md - name: Teams Rooms on Android and Teams panels items: - name: Remote provisioning and sign-in @@ -1586,7 +1584,7 @@ items: - name: Overview and planning items: - name: Overview of Teams phones - href: devices/phones-for-teams.md + href: phones/phones-for-teams.md - name: What's new in Teams phones href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones - name: Deploy @@ -1610,9 +1608,9 @@ items: - name: Step 3 - Set up and configure items: - name: Set up common area phones - href: set-up-common-area-phones.md + href: phones/set-up-common-area-phones.md - name: Set up a common area mobile phones - href: devices/common-area-mobile-phones.md + href: phones/common-area-mobile-phones.md - name: Step 4 - Set up Teams phones items: - name: Remote provisioning @@ -1628,7 +1626,7 @@ items: - name: Troubleshooting and known issues items: - name: Troubleshooting and known issues - href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android.md#issues-with-teams-phones - name: Bring your own device (BYOD) spaces items: - name: BYOD rooms From ee5bf0bda1b8837a9fbbcacf120f84810e3be82f Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:01:54 -0700 Subject: [PATCH 68/87] Update toc.yml --- Teams/toc.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 94b65bdd96..8c3228322d 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1409,7 +1409,7 @@ items: href: devices/reserving-rooms-with-a-qr-code.md - name: Custom backgrounds on Teams panels href: devices/custom-background-panels.md - - name: Teams Rooms and devices feature comparison + - name: Teams Rooms and panels feature comparison href: rooms/teams-devices-feature-comparison.md - name: Meeting room guidance for Teams href: rooms/room-planning-guidance.md @@ -1455,13 +1455,13 @@ items: items: - name: Preparing your network href: rooms/rooms-prep.md - - name: QoS on Teams devices + - name: Quality of Service (QoS) for Teams Rooms href: devices/qos-on-teams-devices.md - name: Intune Enrollment for Windows items: - name: Autopilot and Autologin href: rooms/autopilot-autologin.md - - name: Deploy LAPs + - name: Deploy LAPS href: rooms/laps-authentication.md - name: Intune Enrollment for Android items: @@ -1595,7 +1595,7 @@ items: items: - name: Prepare your network href: phones/prepare-network-teams-phones.md - - name: Quality of Service (QOS) for Teams phones + - name: Quality of Service (QoS) for Teams phone href: phones/qos-on-teams-phones.md - name: Intune Enrollment for Teams phones items: @@ -1603,7 +1603,7 @@ items: href: phones/phones-deploy.md - name: AOSP device management href: rooms/android-migration-guide.md - - name: Authentication best practices for Teams phones + - name: Authentication best practices for Teams phone href: phones/authentication-best-practices-phones.md - name: Step 3 - Set up and configure items: From 0c8d93db9f8468320fea6773b7416aeb3e09854e Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <31015534+tonysmit@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:10:40 -0700 Subject: [PATCH 69/87] Unpublishing RealWear for Teams --- .openpublishing.redirection.json | 5 +++ Teams/flw-realwear.md | 53 -------------------------------- Teams/toc.yml | 2 -- 3 files changed, 5 insertions(+), 55 deletions(-) delete mode 100644 Teams/flw-realwear.md diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 9ade48af34..71f7feef05 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5334,6 +5334,11 @@ "source_path": "Teams/rooms/android-app-firmware.md", "redirect_url": "/microsoftteams/devices/certified-hardware-android", "redirect_document_id": false + }, + { + "source_path": "Teams/rooms/flw-realwear.md", + "redirect_url": "/microsoftteams/devices/usb-devices", + "redirect_document_id": false } ] } diff --git a/Teams/flw-realwear.md b/Teams/flw-realwear.md deleted file mode 100644 index 288ba9c3b6..0000000000 --- a/Teams/flw-realwear.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: IT admin information for Microsoft Teams for RealWear client (Preview) -author: MicrosoftHeidi -ms.author: heidip -manager: jtremper -ms.topic: reference -ms.service: msteams -audience: admin -ms.reviewer: -ms.date: 03/30/2020 -description: IT admin walkthrough of the Microsoft Teams for RealWear client. -ms.localizationpriority: high -search.appverid: MET150 -f1.keywords: - - NOCSH -ms.collection: - - M365-collaboration - - remotework - - m365-frontline - - tier2 - - highpri -appliesto: - - Microsoft Teams ---- -# Microsoft Teams for RealWear - -This article covers the Microsoft Teams client for RealWear head-mounted wearables. Frontline workers using RealWear HMT-1 and HMT-1Z1 can now collaborate with a remote expert using video calling on Teams. Through a voice-controlled user interface, Teams for RealWear allows field workers to remain 100% hands-free while maintaining situational awareness in loud and hazardous environments. By showing what they see in real-time, field workers can accelerate the time to resolve issues and reduce the risk of an expensive downtime. - -## How to deploy Microsoft Teams for RealWear - -- RealWear devices updated to release 11.2 or above. More information [here](https://realwear.com/knowledge-center/configure-on-release-10/wireless-update/). -- Access to [RealWear Foresight](https://cloud.realwear.com/) for distributing the Microsoft Teams client for Realwear. - -## Required Licenses - -Microsoft Teams licenses are part of Microsoft 365 and Office 365 subscriptions. No additional licensing is required to use Teams for RealWear. For more information about getting Teams, check out [How do I get access to Microsoft Teams](https://support.office.com/article/fc7f1634-abd3-4f26-a597-9df16e4ca65b). - -## Managing RealWear devices - -### Microsoft Endpoint Manager - -RealWear devices can be managed using Android Device Administrator mode. Support for management via Android Enterprise is limited, as the devices currently don't have Google Mobile Services (GMS) available. - -- To learn more about managing RealWear devices on Microsoft Endpoint Manager, see [Android device administrator enrollment in Intune](/mem/intune/enrollment/android-enroll-device-administrator). -- For more details on policies, see [How to use Intune in environments without Google Mobile Services](/mem/intune/apps/manage-without-gms). - -### Third-party Enterprise Mobility Managers (EMMs) - -For guidance on third-party EMMs, see [Supported Enterprise Mobility Management Providers](https://www.realwear.com/knowledge-center/configure-on-release-10/remote-from-a-web-browser/emm/). - -## End-user content - -For further reading on this from an end-user perspective, check out [Using Microsoft Teams for RealWear](https://support.office.com/article/using-microsoft-teams-for-realwear-af20d232-d18c-476f-8031-843a4edccd5f). diff --git a/Teams/toc.yml b/Teams/toc.yml index a374c7e658..6789188e71 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1569,8 +1569,6 @@ items: items: - name: QoS on Teams devices href: devices/qos-on-teams-devices.md - - name: RealWear for Teams - href: flw-realwear.md - name: Monitor items: - name: Teams device health monitoring From 32b5a108cfc3ee95752b286ac472a701d399501d Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:18:15 -0700 Subject: [PATCH 70/87] Update toc.yml --- Teams/toc.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Teams/toc.yml b/Teams/toc.yml index 30287cd2ac..9d0e990b23 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1367,6 +1367,8 @@ items: href: rooms/rooms-legacy-licensing.md - name: Release notes href: rooms/rooms-release-note.md + - name: Management apps + href: devices/certified-device-apps.md - name: Deploy items: - name: Deployment overview From c61947a205b2735c945fa8dffac7d0391c46c33e Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:19:52 -0700 Subject: [PATCH 71/87] Update toc.yml --- Teams/toc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 8c3228322d..c784468e46 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -1411,7 +1411,7 @@ items: href: devices/custom-background-panels.md - name: Teams Rooms and panels feature comparison href: rooms/teams-devices-feature-comparison.md - - name: Meeting room guidance for Teams + - name: Meeting room design guidance href: rooms/room-planning-guidance.md - name: Licensing items: From e12d6dff51b00c9e72f9689e3fc865bfb436ccce Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Fri, 18 Oct 2024 12:09:05 -0700 Subject: [PATCH 72/87] Update .openpublishing.redirection.json --- .openpublishing.redirection.json | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 71f7feef05..bf14f45c33 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5325,20 +5325,20 @@ "redirect_url": "/microsoftteams/devices/certification-overview", "redirect_document_id": false }, - { - "source_path": "Teams/devices/teams-ip-phones.md", - "redirect_url": "/microsoftteams/devices/certified-devices-overview", - "redirect_document_id": false - }, - { - "source_path": "Teams/rooms/android-app-firmware.md", - "redirect_url": "/microsoftteams/devices/certified-hardware-android", - "redirect_document_id": false - }, - { - "source_path": "Teams/rooms/flw-realwear.md", - "redirect_url": "/microsoftteams/devices/usb-devices", - "redirect_document_id": false - } + { + "source_path": "Teams/devices/teams-ip-phones.md", + "redirect_url": "/microsoftteams/devices/certified-devices-overview", + "redirect_document_id": false + }, + { + "source_path": "Teams/rooms/android-app-firmware.md", + "redirect_url": "/microsoftteams/devices/certified-hardware-android", + "redirect_document_id": false + }, + { + "source_path": "Teams/flw-realwear.md", + "redirect_url": "/microsoftteams/devices/usb-devices", + "redirect_document_id": false + } ] } From 3452abb2a00fd7a60e71b17052be210b8f698948 Mon Sep 17 00:00:00 2001 From: "Daniel H. Brown" <32883970+DHB-MSFT@users.noreply.github.com> Date: Fri, 18 Oct 2024 12:29:53 -0700 Subject: [PATCH 73/87] Add section for Webview2 Fix some links and references --- Teams/privacy/teams-privacy-oce-overview.md | 30 ++++++++++++--------- 1 file changed, 17 insertions(+), 13 deletions(-) diff --git a/Teams/privacy/teams-privacy-oce-overview.md b/Teams/privacy/teams-privacy-oce-overview.md index 06dc6ed418..d39363cee8 100644 --- a/Teams/privacy/teams-privacy-oce-overview.md +++ b/Teams/privacy/teams-privacy-oce-overview.md @@ -10,22 +10,22 @@ ms.collection: - M365-collaboration - privacy-teams ms.reviewer: -ms.date: 10/04/2023 +ms.date: 10/18/2024 ms.localizationpriority: high search.appverid: MET150 -description: This article outlines the optional connected experiences you'll see in Microsoft Teams. +description: This article outlines the optional connected experiences you see in Microsoft Teams. appliesto: - Microsoft Teams --- # Overview of optional connected experiences in Microsoft Teams -If you have a work or school account, your organization's admin may have provided you with the ability to use one or more cloud-backed services (also referred to as **optional connected experiences**) while using Microsoft Teams, like GIPHY and/or URL Preview service. These cloud-backed services are optional. Whether you use them is up to you. They're offered to you under terms that differ from the [Microsoft Online Service Terms](https://www.microsoft.com/licensing/product-licensing/products), as described separately for each optional service. This article lists our Teams cloud-backed services. +If you have a work or school account, your organization's admin may have provided you with the ability to use one or more cloud-backed services (also referred to as **optional connected experiences**) while using Microsoft Teams, like GIPHY and/or URL Preview service. These cloud-backed services are optional. Whether you use them is up to you. They're offered to you under terms that differ from the [Microsoft Product Terms](https://www.microsoft.com/licensing/docs/view/Product-Terms), as described separately for each optional service. This article lists our Teams cloud-backed services. If your admin has given you the ability to use optional connected experiences in Teams, you can go to **Settings** > **Privacy** in Teams and choose whether you want to use optional connected experiences. > [!NOTE] -> If you're an admin, you can give or restrict your users' ability to use optional connected experiences. You can do this by using the [Office cloud policy service](/deployoffice/overview-office-cloud-policy-service) and configuring the *Allow the use of additional optional connected experiences in Office* policy setting. This is the same policy setting that controls whether optional connected experiences are available to your users in the Office apps (such as Word, Excel, and PowerPoint) that come with Microsoft 365 Apps for enterprise. +> If you're an admin, you can give or restrict your users' ability to use optional connected experiences. You can do this by using the [Cloud Policy service for Microsoft 365](/microsoft-365-apps/admin-center/overview-cloud-policy) and configuring the **Allow the use of additional optional connected experiences in Office** policy setting. This is the same policy setting that controls whether optional connected experiences are available to your users in Microsoft 365 Apps, such as Word, Excel, and PowerPoint. ## GIPHY @@ -33,31 +33,35 @@ GIPHY is a cloud-backed service that lets you use GIFs in your Teams chats. If y ## Ratings and reviews for Teams apps -Ratings and reviews allow Teams users to provide feedback about their experience with using a Teams app. Reviews are anonymous unless the user chooses otherwise. All Teams users can view these ratings and reviews on the details page for the app. Users are only allowed to provide ratings and reviews for apps they’ve installed and only for apps that are publicly available from Microsoft or other companies. The ratings are powered by Microsoft AppSource and are shown on the app’s page on the [AppSource website](https://appsource.microsoft.com/). AppSource is provided under the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Microsoft Commercial Marketplace Terms of Use](/legal/marketplace/marketplace-terms). +Ratings and reviews allow Teams users to provide feedback about their experience with using a Teams app. Reviews are anonymous unless the user chooses otherwise. All Teams users can view these ratings and reviews on the details page for the app. Users are only allowed to provide ratings and reviews for apps they’ve installed and only for apps that are publicly available from Microsoft or other companies. The ratings are powered by Microsoft AppSource and are shown on the app’s page on the [AppSource website](https://appsource.microsoft.com/). AppSource is provided under the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement) and the [Microsoft Commercial Marketplace Terms of Use](/legal/marketplace/marketplace-terms). ## Search Coach Tab App -The Search Coach Teams tab app available in Microsoft EDU Class Teams makes search requests to Bing search through the Bing API when a user sends a query, returning ad-free SafeSearch results. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [privacy statement](https://privacy.microsoft.com/privacystatement). +The Search Coach Teams tab app available in Microsoft EDU Class Teams makes search requests to Bing search through the Bing API when a user sends a query, returning ad-free SafeSearch results. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). ## Teams apps link previews -The Teams app link previews service generates a preview snippet of the app's adaptive card and attaches it under the URL when a user sends a URL string that maps to the app in the Teams store. If the URLP setting is turned on, this service will make a request to the service URL as the user is typing the message to unfurl a card preview. Tenant admin and user settings for apps would be honored. +The Teams app link previews service generates a preview snippet of the app's adaptive card and attaches it under the URL when a user sends a URL string that maps to the app in the Teams store. If the URLP setting is turned on, this service makes a request to the service URL as the user is typing the message to unfurl a card preview. Tenant admin and user settings for apps would be honored. ## Teams device store checkout Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the terms of service and privacy statement of UnifiedCommunications.com. -To learn more about Teams device store, see [Purchase devices in the Teams device store](../devices/device-store.md). +To learn more about Teams device store, see [Purchase devices in the Microsoft Teams device store](../devices/device-store.md). ## URL Preview service -The URL Preview service automatically generates a preview snippet and attaches under the snippet the URL when a user sends a URL string. This service will make a request to the service URL as the user is typing the message. If the service URL doesn't have any schema.org data, it will send a request to Bing search to get the data it needs to generate the preview snippet. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [privacy statement](https://privacy.microsoft.com/privacystatement). Any URLs you provide to Microsoft Teams while using these services can be sent to Microsoft Bing, including Bing Content Validation Service for evaluation of harmful content. They aren't linked to you by the Bing organization. +The URL Preview service automatically generates a preview snippet and attaches under the snippet the URL when a user sends a URL string. This service makes a request to the service URL as the user is typing the message. If the service URL doesn't have any schema.org data, it sends a request to Bing search to get the data it needs to generate the preview snippet. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). Any URLs you provide to Microsoft Teams while using these services can be sent to Microsoft Bing, including Bing Content Validation Service for evaluation of harmful content. They aren't linked to you by the Bing organization. :::image type="content" source="../media/url-preview.png" alt-text="A screen showing a sample of a URL preview for the Microsoft home page in a text box."::: +## Webview2 + +Webview2 is a component that developers use to build their applications, and the developers can deploy a self-updating Evergreen WebView2 Runtime onto user devices to power their applications. Webview2 collects its own telemetry to help them maintain and improve the Webview2 component. If the policy turned off, the diagnostic data collection from Webview2 will be disabled. + ## Related articles -- [Overview of policy controls for Teams](policy-control-overview.md) -- [Overview of optional connected experiences in Office](/deployoffice/privacy/optional-connected-experiences) -- [Required service data for Office](/deployoffice/privacy/required-service-data) -- [Account Privacy Settings](https://support.microsoft.com/office/3e7bc183-bf52-4fd0-8e6b-78978f7f121b) +- [Policy control overview for Microsoft Teams](policy-control-overview.md) +- [Overview of optional connected experiences in Office](/microsoft-365-apps/privacy/optional-connected-experiences) +- [Required service data for Office](/microsoft-365-apps/privacy/required-service-data) +- [Access your Account Privacy Settings](https://support.microsoft.com/office/3e7bc183-bf52-4fd0-8e6b-78978f7f121b) From 7eadebdd29db235d549466db14b441fb4605b3b2 Mon Sep 17 00:00:00 2001 From: "Daniel H. Brown" <32883970+DHB-MSFT@users.noreply.github.com> Date: Fri, 18 Oct 2024 12:40:25 -0700 Subject: [PATCH 74/87] Add links for UC.com stuff --- Teams/privacy/teams-privacy-oce-overview.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Teams/privacy/teams-privacy-oce-overview.md b/Teams/privacy/teams-privacy-oce-overview.md index d39363cee8..bf94e0f264 100644 --- a/Teams/privacy/teams-privacy-oce-overview.md +++ b/Teams/privacy/teams-privacy-oce-overview.md @@ -20,12 +20,12 @@ appliesto: # Overview of optional connected experiences in Microsoft Teams -If you have a work or school account, your organization's admin may have provided you with the ability to use one or more cloud-backed services (also referred to as **optional connected experiences**) while using Microsoft Teams, like GIPHY and/or URL Preview service. These cloud-backed services are optional. Whether you use them is up to you. They're offered to you under terms that differ from the [Microsoft Product Terms](https://www.microsoft.com/licensing/docs/view/Product-Terms), as described separately for each optional service. This article lists our Teams cloud-backed services. +If you have a work or school account, your organization's admin may have provided you with the ability to use one or more cloud-backed services (also referred to as "optional connected experiences") while using Microsoft Teams, like GIPHY and/or URL Preview service. These cloud-backed services are optional. Whether you use them is up to you. They're offered to you under terms that differ from the [Microsoft Product Terms](https://www.microsoft.com/licensing/docs/view/Product-Terms), as described separately for each optional service. This article lists our Teams cloud-backed services. If your admin has given you the ability to use optional connected experiences in Teams, you can go to **Settings** > **Privacy** in Teams and choose whether you want to use optional connected experiences. > [!NOTE] -> If you're an admin, you can give or restrict your users' ability to use optional connected experiences. You can do this by using the [Cloud Policy service for Microsoft 365](/microsoft-365-apps/admin-center/overview-cloud-policy) and configuring the **Allow the use of additional optional connected experiences in Office** policy setting. This is the same policy setting that controls whether optional connected experiences are available to your users in Microsoft 365 Apps, such as Word, Excel, and PowerPoint. +> If you're an admin, you can give or restrict your users' ability to use optional connected experiences. You can do this by using [Cloud Policy service for Microsoft 365](/microsoft-365-apps/admin-center/overview-cloud-policy) and configuring the **Allow the use of additional optional connected experiences in Office** policy setting. This is the same policy setting that controls whether optional connected experiences are available to your users in Microsoft 365 Apps, such as Word, Excel, and PowerPoint. ## GIPHY @@ -45,7 +45,7 @@ The Teams app link previews service generates a preview snippet of the app's ada ## Teams device store checkout -Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the terms of service and privacy statement of UnifiedCommunications.com. +Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the [terms of service](https://new.unifiedcommunications.com/about/terms-of-service/) and [privacy policy](https://new.unifiedcommunications.com/about/privacy-policy/) of UnifiedCommunications.com. To learn more about Teams device store, see [Purchase devices in the Microsoft Teams device store](../devices/device-store.md). From e01e5866afe409c364ed3b03110249f31fc64eca Mon Sep 17 00:00:00 2001 From: "Daniel H. Brown" <32883970+DHB-MSFT@users.noreply.github.com> Date: Fri, 18 Oct 2024 12:46:28 -0700 Subject: [PATCH 75/87] Minor changes to link text --- Teams/privacy/teams-privacy-oce-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/privacy/teams-privacy-oce-overview.md b/Teams/privacy/teams-privacy-oce-overview.md index bf94e0f264..18a1b0d4a6 100644 --- a/Teams/privacy/teams-privacy-oce-overview.md +++ b/Teams/privacy/teams-privacy-oce-overview.md @@ -29,7 +29,7 @@ If your admin has given you the ability to use optional connected experiences in ## GIPHY -GIPHY is a cloud-backed service that lets you use GIFs in your Teams chats. If you're in **Teams** > **GIF** > **Search**, the search terms are sent to GIPHY. These experiences, if allowed by your admin and after you choose to use them, are subject to the [GIPHY Privacy Policy](https://support.giphy.com/hc/articles/360032872931-GIPHY-Privacy-Policy) and [Terms of Service](https://support.giphy.com/hc/articles/360020027752-GIPHY-User-Terms-of-Service). +GIPHY is a cloud-backed service that lets you use GIFs in your Teams chats. If you're in **Teams** > **GIF** > **Search**, the search terms are sent to GIPHY. These experiences, if allowed by your admin and after you choose to use them, are subject to the [GIPHY Privacy Policy](https://support.giphy.com/hc/articles/360032872931-GIPHY-Privacy-Policy) and the [GIPHY User Terms of Service](https://support.giphy.com/hc/articles/360020027752-GIPHY-User-Terms-of-Service). ## Ratings and reviews for Teams apps @@ -45,7 +45,7 @@ The Teams app link previews service generates a preview snippet of the app's ada ## Teams device store checkout -Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the [terms of service](https://new.unifiedcommunications.com/about/terms-of-service/) and [privacy policy](https://new.unifiedcommunications.com/about/privacy-policy/) of UnifiedCommunications.com. +Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the [Terms of Service](https://new.unifiedcommunications.com/about/terms-of-service/) and [Privacy Policy](https://new.unifiedcommunications.com/about/privacy-policy/) of UnifiedCommunications.com. To learn more about Teams device store, see [Purchase devices in the Microsoft Teams device store](../devices/device-store.md). From 48122776a5f4b7cce7730d7ec3c0e9936996c8d6 Mon Sep 17 00:00:00 2001 From: "Daniel H. Brown" <32883970+DHB-MSFT@users.noreply.github.com> Date: Fri, 18 Oct 2024 12:52:34 -0700 Subject: [PATCH 76/87] Fix capitalization of WebView2 --- Teams/privacy/teams-privacy-oce-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/privacy/teams-privacy-oce-overview.md b/Teams/privacy/teams-privacy-oce-overview.md index 18a1b0d4a6..701a6fe817 100644 --- a/Teams/privacy/teams-privacy-oce-overview.md +++ b/Teams/privacy/teams-privacy-oce-overview.md @@ -55,9 +55,9 @@ The URL Preview service automatically generates a preview snippet and attaches u :::image type="content" source="../media/url-preview.png" alt-text="A screen showing a sample of a URL preview for the Microsoft home page in a text box."::: -## Webview2 +## WebView2 -Webview2 is a component that developers use to build their applications, and the developers can deploy a self-updating Evergreen WebView2 Runtime onto user devices to power their applications. Webview2 collects its own telemetry to help them maintain and improve the Webview2 component. If the policy turned off, the diagnostic data collection from Webview2 will be disabled. +WebView2 is a component that developers use to build their applications, and the developers can deploy a self-updating Evergreen WebView2 Runtime onto user devices to power their applications. WebView2 collects its own telemetry to help them maintain and improve the WebView2 component. If the policy turned off, the diagnostic data collection from WebView2 will be disabled. ## Related articles From 41752fc4d27fcc11b3dcc62ceaa657aab7988db7 Mon Sep 17 00:00:00 2001 From: PPAARRIISS <168596979+PPAARRIISS@users.noreply.github.com> Date: Fri, 18 Oct 2024 13:30:52 -0700 Subject: [PATCH 77/87] Learn Editor: Update voice-and-face-recognition.md --- Teams/rooms/voice-and-face-recognition.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Teams/rooms/voice-and-face-recognition.md b/Teams/rooms/voice-and-face-recognition.md index 2a9d294445..031588a3e4 100644 --- a/Teams/rooms/voice-and-face-recognition.md +++ b/Teams/rooms/voice-and-face-recognition.md @@ -139,6 +139,10 @@ Set-CsTeamsMeetingPolicy -Identity -PolicyName -EnrollUserOverride Disabled +> [!NOTE] +> A new `csTeamsAIPolicy` for Microsoft Teams, now available via Microsoft PowerShell, will take effect in mid-January 2025. This policy will replace the existing enrollment setting in `csTeamsMeetingPolicy` and includes two settings: `EnrollFace` and `EnrollVoice`. +> To help you get started, review: +> - [Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn](/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy?view=teams-ps") Admins can manage how voice and face profiles are used to turn off Voice Isolation for users to enhance noise and voice background reduction admins can switch off voice isolation with PowerShell in the meeting policy. ```powershell From 2a070d28a18eeddb4d96da369bccb3c461396da2 Mon Sep 17 00:00:00 2001 From: PPAARRIISS <168596979+PPAARRIISS@users.noreply.github.com> Date: Fri, 18 Oct 2024 13:31:01 -0700 Subject: [PATCH 78/87] Learn Editor: Update voice-and-face-recognition.md From a7882bda493fa20af373fbda32c748ca8bb5ef60 Mon Sep 17 00:00:00 2001 From: Dmitry Kirilov Date: Fri, 18 Oct 2024 13:53:18 -0700 Subject: [PATCH 79/87] Learn Editor: Update certified-hardware.md --- Teams/rooms/certified-hardware.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/rooms/certified-hardware.md b/Teams/rooms/certified-hardware.md index b383f7069d..b65924ec13 100644 --- a/Teams/rooms/certified-hardware.md +++ b/Teams/rooms/certified-hardware.md @@ -225,7 +225,7 @@ The following devices are certified under the Microsoft Teams Rooms peripherals | [Microsoft Surface Hub Smart Camera](https://www.microsoft.com/d/surface-hub-smart-camera/8n983ctks176) | FW: 1.8.1 | | | | [Microsoft Surface Hub 2 Camera](https://www.microsoft.com/d/surface-hub-2-camera/8tzgfl7z18ph) | FW: 24.712.159 | | | | [Nureva HDL300](https://www.nureva.com/audio-conferencing/hdl300) | 2.3.6 | | | -| [Nureva HDL310](https://www.nureva.com/audio-conferencing/hdl310) | 1.5.0.0 | | | +| [Nureva HDL310](https://www.nureva.com/audio-conferencing/hdl310) | 1.8.269710 | | | ✔ | | | [Nureva HDL410](https://www.nureva.com/audio-conferencing/hdl410) | 1.5.243554 | | | | [Owl Labs Meeting Owl 3](https://owllabs.com/products/meeting-owl-3) | 6.4.10.42 | | | | [Panasonic 360 degree camera speakerphone PressIT360](https://panasonic.net/cns/prodisplays/products/ty-csp1/) | 0.0.7904.54 | | | From 0dd06cc1fd6f199044a45e5d521de62fd24719a7 Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:16:05 -0700 Subject: [PATCH 80/87] Correct indentation of contents in list items --- Teams/devices/sip-gateway-configure.md | 77 +++++++++++++------------- 1 file changed, 38 insertions(+), 39 deletions(-) diff --git a/Teams/devices/sip-gateway-configure.md b/Teams/devices/sip-gateway-configure.md index bbfe6f8129..01e51f8ee8 100644 --- a/Teams/devices/sip-gateway-configure.md +++ b/Teams/devices/sip-gateway-configure.md @@ -128,15 +128,15 @@ Conditional Access is a Microsoft Entra feature that helps ensure that devices t 1. Exclude your site public IP addresses and the following SIP Gateway service IP addresses from Conditional Access checks: -- North America: - - East US: 52.170.38.140 - - West US: 40.112.144.212 -- EMEA region: - - North EU: 40.112.71.149 - - West EU: 40.113.112.67 -- APAC region: - - Australia East: 20.92.120.71 - - Australia Southeast: 13.73.115.90 + - North America: + - East US: 52.170.38.140 + - West US: 40.112.144.212 + - EMEA region: + - North EU: 40.112.71.149 + - West EU: 40.113.112.67 + - APAC region: + - Australia East: 20.92.120.71 + - Australia Southeast: 13.73.115.90 2. Exclude the Teams app from Conditional Access checks. @@ -259,21 +259,21 @@ Bulk sign-in is very helpful and can be used in these scenarios. 1. You must add your site public IP address or ranges to the [trusted IPs for the tenant](/microsoftteams/manage-your-network-topology) in Teams admin center at least 24 hours prior to running the bulk sign in cmdlets. 2. You must add your organization's tenant ID to the provisioning URL for the devices. - > [!NOTE] - > The examples below are for the North America region. + > [!NOTE] + > The examples below are for the North America region. -- For Alcatel-Lucent Enterprise, AudioCodes, and Yealink IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid/` -- For Cisco IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//$PSN.xml` -- For analog devices that connect to AudioCodes ATAs use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//mac.ini` + - For Alcatel-Lucent Enterprise, AudioCodes, and Yealink IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid/` + - For Cisco IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//$PSN.xml` + - For analog devices that connect to AudioCodes ATAs use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//mac.ini` - > [!IMPORTANT] - > For Cisco ATA replace mac.ini with mac.cfg. - > For Poly ATA replace mac.ini with $mac.cfg. + > [!IMPORTANT] + > For Cisco ATA replace mac.ini with mac.cfg. + > For Poly ATA replace mac.ini with $mac.cfg. 3. You must install Microsoft Teams Power Shell 5.6.0 or later. - > [!NOTE] - > The bulk sign in cmdlets aren't included with previous versions. + > [!NOTE] + > The bulk sign in cmdlets aren't included with previous versions. 4. You must apply [CommonAreaPhone policy](/microsoftteams/set-up-common-area-phones) to the accounts that are part of a bulk sign in request. 5. The accounts must not have Multi Factor Authentication (MFA) enabled. @@ -281,13 +281,13 @@ Bulk sign-in is very helpful and can be used in these scenarios. 7. The accounts must have the SIP device calling policy assigned. [AllowSIPDevicesCalling policy](/microsoftteams/sip-gateway-configure) 8. You must use an account that has the **Global Administrator, Privileged Authentication Administrator or the Authentication Administrator** role to run the cmdlets. -> [!IMPORTANT] ->Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + > [!IMPORTANT] + > Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. 1. The **BulkSignIn** attribute must be set to `Enabled` in [TeamsSipDevicesConfiguration](/powershell/module/teams/set-csteamssipdevicesconfiguration) -> [!NOTE] -> As a best practice, try running bulk sign in cmdlet at least 1 hour and at most 70 hours after device provisioning. + > [!NOTE] + > As a best practice, try running bulk sign in cmdlet at least 1 hour and at most 70 hours after device provisioning. ### How to create a bulk sign in request @@ -306,24 +306,24 @@ Bulk sign-in is very helpful and can be used in these scenarios. 3. Run the following: - ```PowerShell - Import-Module MicrosoftTeams - $credential = Get-Credential // Enter your admin’s email and password - Connect-MicrosoftTeams –Credential $credential - $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC - ``` + ```PowerShell + Import-Module MicrosoftTeams + $credential = Get-Credential // Enter your admin’s email and password + Connect-MicrosoftTeams –Credential $credential + $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC + ``` The `DeviceDetailsFilePath` parameter specifies the location of the CSV you created and saved. The `Region` parameter specifies the SIP gateway provisioning region where the devices are being deployed. The values are: APAC, EMEA, NOAM. 4. To check the status of a bulk sign-in batch, run the following: - ```PowerShell -$newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC -$newBatchResponse.BatchId -$getBatchStatusResponse = Get-CsSdgBulkSignInRequestStatus -Batchid $newBatchResponse.BatchId -$getBatchStatusResponse | ft -$getBatchStatusResponse.BatchItem -``` + ```PowerShell + $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC + $newBatchResponse.BatchId + $getBatchStatusResponse = Get-CsSdgBulkSignInRequestStatus -Batchid $newBatchResponse.BatchId + $getBatchStatusResponse | ft + $getBatchStatusResponse.BatchItem + ``` ### Bulk sign in error messages To help you troubleshoot and fix common issues, these are common error messages that you might see and what you should do to fix it. @@ -400,9 +400,8 @@ How to set Japanese for Cisco phones: > > - If **Sign in to make an emergency call** text is not translated to other languages, an abbreviated version in English only will be presented on **Press Sign In** on the following IP phone models due to a screensize limitations: > - -> - Poly VVX 150, VVX 201 -> - Cisco CP-6821, CP-7811, CP-7821, CP-7841, CP-7861 +> - Poly VVX 150, VVX 201 +> - Cisco CP-6821, CP-7811, CP-7821, CP-7841, CP-7861 > > - Voice mail softkey label is hardcoded with **VM** text across all languages for Poly VVX because of a limitation of string length. From b7661aa9877a754f7961f378c0607d7910de93ab Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:20:27 -0700 Subject: [PATCH 81/87] Correct indentations in list items, add lightbox for readability --- Teams/devices/sip-gateway-dynamic-filters.md | 34 ++++++++++++-------- 1 file changed, 21 insertions(+), 13 deletions(-) diff --git a/Teams/devices/sip-gateway-dynamic-filters.md b/Teams/devices/sip-gateway-dynamic-filters.md index 66fb6f9cb6..f5ee8d2f56 100644 --- a/Teams/devices/sip-gateway-dynamic-filters.md +++ b/Teams/devices/sip-gateway-dynamic-filters.md @@ -45,12 +45,13 @@ To add or deactivate custom security attributes definitions, you must have: 2. Browse to **Protection** > **Custom security attributes**. 3. Select **Add attribute set** to add a new attribute set. - >[!NOTE] - >If **Add attribute set** is disabled, ensure that you're assigned the Attribute Definition Administrator role. For more information, see [Troubleshoot custom security attributes](/entra/fundamentals/custom-security-attributes-troubleshoot). + > [!NOTE] + > If **Add attribute set** is disabled, ensure that you're assigned the Attribute Definition Administrator role. For more information, see [Troubleshoot custom security attributes](/entra/fundamentals/custom-security-attributes-troubleshoot). 4. Enter a name, description, and maximum number of attributes. - > [!TIP] - > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). + + > [!TIP] + > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). 5. When finished, select **Add**. 6. The new attribute set appears in the list of attribute sets. @@ -63,25 +64,31 @@ To add or deactivate custom security attributes definitions, you must have: 4. Select to open the selected attribute set. 5. Select **Add attribute** to add a new custom security attribute to the attribute set. 6. In the **Attribute name** box, enter a custom security attribute name. - > [!TIP] - > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). - :::image type="content" source="media/exclude-attribute-set.png" alt-text="Screenshot displaying the Exclude attribute set."::: + > [!TIP] + > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). + + :::image type="content" source="media/exclude-attribute-set.png" alt-text="Screenshot displaying the Exclude attribute set." lightbox="media/exclude-attribute-set.png"::: 7. In the **Description** box, enter an optional description. + > [!TIP] > A description can be 128 characters long. If necessary, you can later change the description. + 8. From the **Data type** list, select the data type for the custom security attribute. - - Data type: A description. - - Boolean: A Boolean value that can be true or false. - - Integer: A 32-bit integer. - - String: A string that can be X characters long. + - Data type: A description. + - Boolean: A Boolean value that can be true or false. + - Integer: A 32-bit integer. + - String: A string that can be X characters long. + 9. For **Allow multiple values to be assigned**, select **Yes** or **No**. - - Select **Yes** to allow multiple values to be assigned to this custom security attribute. - - Select **No** to only allow a single value to be assigned to this custom security attribute. + - Select **Yes** to allow multiple values to be assigned to this custom security attribute. + - Select **No** to only allow a single value to be assigned to this custom security attribute. + 10. For **Only allow predefined values to be assigned**, select **Yes** or **No**. - Select **Yes**, if custom security attribute can be assigned values from a predefined values list. - Select **No** to allow this custom security attribute to be assigned user-defined values or potentially predefined values. + 11. If **Only allow predefined values to be assigned** is selected Yes, then select **Add value** to add predefined values. An active value is available for assignment of objects. A value that isn't active is defined, but not yet available for assignment. 12. When finished, select **Save**. 13. The new custom security attribute appears in the list of custom security attributes. @@ -186,6 +193,7 @@ New-MgServicePrincipal -AppId "61c8fd69-c13e-4ee6-aaa6-24ff71c09bca" - From **Select what this policy applies to** list, choose **Cloud apps**. - On the **Include** tab, select **All** apps option. - Change tab to **Exclude** and under **Select excluded cloud apps**, search for **Microsoft Teams Services** and click on **Select**. + 5. Select **Edit filter**. 6. On the **Edit filter** page, set **Configure** to **Yes**. 7. Select the attribute you created earlier (in this case 'exclAttrAllowMultiple'). From 1c50073f1f71cda83ae662e6a62fc812aac749eb Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:25:03 -0700 Subject: [PATCH 82/87] Correct indentation of alerts --- Teams/phones/common-area-mobile-phones.md | 31 ++++++++++++----------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/Teams/phones/common-area-mobile-phones.md b/Teams/phones/common-area-mobile-phones.md index 009b376f5d..e8452f1dbe 100644 --- a/Teams/phones/common-area-mobile-phones.md +++ b/Teams/phones/common-area-mobile-phones.md @@ -29,15 +29,15 @@ description: Learn how to set up common area Android phones A Teams Android mobile app signed in with an account tied to **Microsoft Teams Shared Device** license is used as a shared device by frontline workers to make and receive calls as part of their daily work using Teams. - > [!IMPORTANT] - > To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. +> [!IMPORTANT] +> To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. ## Step 1 - Buy the licenses First, you need to purchase a **Teams Shared Devices** license. - > [!NOTE] - > Chat is not supported with a **Teams Shared Devices** license. +> [!NOTE] +> Chat is not supported with a **Teams Shared Devices** license. To purchase the license: @@ -46,17 +46,18 @@ To purchase the license: 1. In the product list, find **Microsoft Teams Shared Devices**, and select **Details**. 1. Enter the number of licenses you need, and select **Buy**. - > [!NOTE] - > If you're using Intune in your environment and have conditional access rules that require device compliance, you'll need to assign an **Microsoft Entra ID P1** and an **Intune** license to the device account that was used to sign in to the Teams mobile app. - > Teams-shared devices can be impacted by conditional access rules and other identity configurations, such as Multi-Factor Authentication. For more information, see [Authentication best practices for Teams Android devices](../devices/authentication-best-practices-for-android-devices.md). + > [!NOTE] + > If you're using Intune in your environment and have conditional access rules that require device compliance, you'll need to assign an **Microsoft Entra ID P1** and an **Intune** license to the device account that was used to sign in to the Teams mobile app. + > + > Teams-shared devices can be impacted by conditional access rules and other identity configurations, such as Multi-Factor Authentication. For more information, see [Authentication best practices for Teams Android devices](../devices/authentication-best-practices-for-android-devices.md). ## Step 2 - Create a new user account and assign licenses ### Using the Microsoft 365 admin center - > [!NOTE] - > If you're deploying more than one phone at a time, you can use only [PowerShell](../set-up-common-area-phones.md) to create accounts and assign licenses. - > You can use Microsoft 365 admin center to create accounts and assign licenses only if you're deploying one device at a time. +> [!NOTE] +> If you're deploying more than one phone at a time, you can use only [PowerShell](../set-up-common-area-phones.md) to create accounts and assign licenses. +> You can use Microsoft 365 admin center to create accounts and assign licenses only if you're deploying one device at a time. 1. Sign in to [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339), and select **Users > Active Users > Add a user**. 1. Enter a username like **Main** for the first name and **Reception** for the second name. @@ -64,14 +65,14 @@ To purchase the license: 1. Enter a username like **BakeryPhone** or **DutyManager**. 1. Manually set the password for your common area phone. To set the password, clear the **Automatically create a password and require this user to change their password when they first sign in** checkbox. -> [!IMPORTANT] -> Manually setting a password for common area phones is recommended to prevent sign-in issues for your end users. + > [!IMPORTANT] + > Manually setting a password for common area phones is recommended to prevent sign-in issues for your end users. 6. Select the usage location of the device and assign the **Teams Shared Devices** license to the account. If any other licenses are needed, such as **Callings Plans**, assign those licenses too to the account. -> [!NOTE] -> -> When you assign a **Teams Shared Device** license to a device, you don't need to assign an additional Phone System license to get other features. To get inbound and outbound calling minutes with Microsoft Phone System you must add a Calling Plan and set up billing. However, if you are using Operator Connect or Direct Routing, you don't need a Calling Plan. For more information on licenses, see [Microsoft Teams add-on licensing](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md). + > [!NOTE] + > + > When you assign a **Teams Shared Device** license to a device, you don't need to assign an additional Phone System license to get other features. To get inbound and outbound calling minutes with Microsoft Phone System you must add a Calling Plan and set up billing. However, if you are using Operator Connect or Direct Routing, you don't need a Calling Plan. For more information on licenses, see [Microsoft Teams add-on licensing](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md). ### Using PowerShell From 2a2201fdd9f93e65cd6af333dace3bd4fd0aa010 Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:35:27 -0700 Subject: [PATCH 83/87] Correct font weight of table headings Table headings are bold by default on Learn. Having formatting for bold results in having a lighter weight font than is standard on the platform. --- Teams/rooms/supported-ca-and-compliance-policies.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index 07170a762d..e34afe4a82 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -34,7 +34,7 @@ for more information. The following list includes the supported Conditional Access policies for Teams Rooms on Windows and Android, and for policies on Teams panels, phones, and displays. -| **Assignment**|**Teams Rooms on Windows**|**Teams Rooms on Android and panels**|**Teams phones and displays**| +| Assignment | Teams Rooms on Windows | Teams Rooms on Android and panels | Teams phones and displays | |:-----|:-----|:-----|:-----| | User or workload identities | Supported | Supported | Supported | | Cloud apps or actions | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | @@ -79,7 +79,7 @@ Microsoft Teams Rooms on Windows and Teams Rooms on Android support different de Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| **Policy** | **Availability** | **Notes** | +| Policy | Availability | Notes | |--------------|---------------|----------------| | [**Device health**](/mem/intune/protect/compliance-policy-create-windows#device-health) | -- | -- | | Require BitLocker | Supported | Only use if you have enabled BitLocker first on Teams Rooms. | @@ -109,7 +109,7 @@ Below is a table of device compliance settings and recommendations for their use Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| **Policy** | **Availability** | **Notes** | +| Policy | Availability | Notes | |--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | @@ -142,7 +142,7 @@ Below is a table of device compliance settings and recommendations for their use Below is a table of device compliance settings and recommendations for their use with Teams phones and displays. -| **Policy** | **Availability** | **Notes** | +| Policy | Availability | Notes | |--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | @@ -175,7 +175,7 @@ Below is a table of device compliance settings and recommendations for their use Below is a table of device compliance settings and recommendations for their use with Teams panels. -| **Policy** | **Availability** | **Notes** | +| Policy | Availability | Notes | |--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | @@ -204,4 +204,3 @@ Below is a table of device compliance settings and recommendations for their use | [**Android 9 and earlier or Samsung Knox**](/mem/intune/protect/compliance-policy-create-android#android-9-and-earlier-or-samsung-knox) | -- | -- | | Required password type | Not supported | | ---- From 84bfa83742b46064a82ed92cfa9e8e94119f6c9e Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:41:36 -0700 Subject: [PATCH 84/87] Correct indentation of content in list item, correct numbering --- Teams/devices/sip-gateway-configure.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Teams/devices/sip-gateway-configure.md b/Teams/devices/sip-gateway-configure.md index 01e51f8ee8..7b07bba865 100644 --- a/Teams/devices/sip-gateway-configure.md +++ b/Teams/devices/sip-gateway-configure.md @@ -313,7 +313,7 @@ Bulk sign-in is very helpful and can be used in these scenarios. $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC ``` -The `DeviceDetailsFilePath` parameter specifies the location of the CSV you created and saved. The `Region` parameter specifies the SIP gateway provisioning region where the devices are being deployed. The values are: APAC, EMEA, NOAM. + The `DeviceDetailsFilePath` parameter specifies the location of the CSV you created and saved. The `Region` parameter specifies the SIP gateway provisioning region where the devices are being deployed. The values are: APAC, EMEA, NOAM. 4. To check the status of a bulk sign-in batch, run the following: @@ -326,6 +326,7 @@ The `DeviceDetailsFilePath` parameter specifies the location of the CSV you crea ``` ### Bulk sign in error messages + To help you troubleshoot and fix common issues, these are common error messages that you might see and what you should do to fix it. | Error message | Potential solution | From d407a41efaecd92c8a14d8d7845d614d104b7d8d Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:42:15 -0700 Subject: [PATCH 85/87] Correct indentation of alert --- Teams/devices/sip-gateway-dynamic-filters.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/devices/sip-gateway-dynamic-filters.md b/Teams/devices/sip-gateway-dynamic-filters.md index f5ee8d2f56..518848f4a3 100644 --- a/Teams/devices/sip-gateway-dynamic-filters.md +++ b/Teams/devices/sip-gateway-dynamic-filters.md @@ -72,8 +72,8 @@ To add or deactivate custom security attributes definitions, you must have: 7. In the **Description** box, enter an optional description. - > [!TIP] - > A description can be 128 characters long. If necessary, you can later change the description. + > [!TIP] + > A description can be 128 characters long. If necessary, you can later change the description. 8. From the **Data type** list, select the data type for the custom security attribute. - Data type: A description. From 0d84aa280675275251ed85a48edaa9c6c0beea30 Mon Sep 17 00:00:00 2001 From: Gary Moore <5432776+garycentric@users.noreply.github.com> Date: Fri, 18 Oct 2024 14:55:29 -0700 Subject: [PATCH 86/87] Acrolinx: "Teamse" --- Teams/toc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/toc.yml b/Teams/toc.yml index 9d0e990b23..bbba43e39d 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -367,7 +367,7 @@ items: href: using-admin-roles.md - name: Manage teams in Teams admin center href: manage-teams-in-modern-portal.md - - name: Teamse Administrative Units + - name: Teams Administrative Units href: teams-administrative-units.md - name: Manage policies From 1ddbcf646a57ad3ffec3456e657d0fb4badc607a Mon Sep 17 00:00:00 2001 From: "Tony Smith (MSFT)" <153562869+MSTonySmith@users.noreply.github.com> Date: Fri, 18 Oct 2024 15:20:45 -0700 Subject: [PATCH 87/87] Update .openpublishing.redirection.json --- .openpublishing.redirection.json | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index d42392d906..011961df49 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5375,20 +5375,10 @@ "redirect_url": "/microsoftteams/devices/sip-gateway-dynamic-filters", "redirect_document_id": false }, - { - "source_path": "Teams/devices/teams-ip-phones.md", - "redirect_url": "/microsoftteams/devices/certified-devices-overview", - "redirect_document_id": false - }, - { - "source_path": "Teams/rooms/android-app-firmware.md", - "redirect_url": "/microsoftteams/devices/certified-hardware-android", - "redirect_document_id": false - }, { "source_path": "Teams/flw-realwear.md", "redirect_url": "/microsoftteams/devices/usb-devices", "redirect_document_id": false } ] -} \ No newline at end of file +}