Merge branch 'public' into patch-1

.github/workflows/BuildValidation.yml

@@ -0,0 +1,21 @@
+name: Build validation
+
+permissions:
+  pull-requests: write
+  statuses: write
+
+on: 
+  issue_comment:
+    types: [created]
+
+jobs:
+
+  build-status:
+    uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-BuildValidation.yml@workflows-test
+    with:
+      PayloadJson: ${{ toJSON(github) }}
+    secrets:
+      AccessToken: ${{ secrets.GITHUB_TOKEN }}
+
+
+

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "Teams/policy-packages-healthcare.md",
+      "redirect_url": "/microsoftteams/manage-policy-packages",
+      "redirect_document_id": true
+    },
     {
       "source_path": "Teams/auto-install-approved-apps.md",
       "redirect_url": "https://admin.microsoft.com/#/MessageCenter/:/messages/MC841224",
@@ -5286,8 +5291,8 @@
 	  "redirect_document_id": false
 	},
 	{
-	  "source_path": "Skype/SfbPartnerCertification/certification/devices-usb-devices.md",
-	  "redirect_url": "/microsoftteams/devices/usb-devices",
+	  "source_path": "Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md",
+	  "redirect_url": "/SkypeForBusiness/certification/devices-usb-devices",
 	  "redirect_document_id": false
 	},
 	{
@@ -5324,16 +5329,96 @@
 	  "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
 	},
-    {
-      "source_path": "Teams/devices/teams-ip-phones.md",
-      "redirect_url": "/microsoftteams/devices/certified-devices-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/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
+  },
+  {
+   "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
+  },
+  {
+    "source_path": "Teams/flw-realwear.md",
+    "redirect_url": "/microsoftteams/devices/usb-devices",
+    "redirect_document_id": false
+  },
+  {
+    "source_path": "Teams/devices/collab-bar-deploy.md",
+    "redirect_url": "/microsoftteams/rooms/rooms-deploy",
+    "redirect_document_id": false
+  },
+  {
+    "source_path": "Teams/devices/teams-android-devices-user-interface.md",
+    "redirect_url": "/microsoftteams/phones/teams-android-devices-user-interface",
+    "redirect_document_id": false
+  },
+  {
+    "source_path": "Teams/rooms/admin-center-license-overview.md",
+    "redirect_url": "/microsoftteams/rooms/rooms-licensing",
+    "redirect_document_id": false
+  },
+  {
+    "source_path": "Teams/manage-sensitive-events.md",
+    "redirect_url": "/microsoftteams/meeting-webinar-town-hall-feature-comparison",
+    "redirect_document_id": false
+  },
+  {
+    "source_path": "Teams/devices/smartvision-admin.md",
+    "redirect_url": "/microsoftteams/devices/multistream-intelliframe",
+    "redirect_document_id": false
+  },
+  {
+"source_path": "Teams/delete-exchange-online-transcripts.md",
+    "redirect_url": "/microsoftteams/tmr-meeting-recording-change",
+    "redirect_document_id": true
+  },
+  {
+    "source_path": "Teams/add-funds-and-manage-communications-credits.md",
+    "redirect_url": "/microsoftteams/turn-off-communication-credits-auto-recharge-mca-customers",
+    "redirect_document_id": true
   }
   ]
 }

Skype/SfBServer2019/control-panel-overview.md

@@ -16,78 +16,15 @@ ms.collection:
 description: "This article provides an overview of the new Control Panel."
 ---
 
-# Control Panel
+# Modern Admin Control Panel
 
-The current Control Panel is a new version of the legacy Control Panel, with which it exists in tandem. The new Control Panel came into existence from the Cumulative Update of July 2019. It helps manage the configuration of servers, users, clients, and devices in the environment of an organization.
+Modern Admin Control Panel (MACP) is a new version of the legacy Control Panel, with which it exists in tandem. MACP came into existence from the Cumulative Update of July 2019, and it has undergone further enhancements in the Cumulative Update of November 2024. It helps manage the configuration of servers, users, clients, and devices in the environment of an organization. It has all the menu items that were present in the legacy Control Panel.
 
 The legacy Control Panel might not work as Silverlight technology reached the "end-of-support" stage on October 12, 2021. For more information, see [Silverlight End of Support](https://support.microsoft.com/windows/silverlight-end-of-support-0a3be3c7-bead-e203-2dfd-74f0a64f1788).
 
 > [!NOTE]
-> For information on the legacy Control Panel, see [Control Panel](../SfbServer/management-tools/install-and-open-administrative-tools.md), and navigate to the section **Skype for Business Server Control Panel**.
+> We recommend you don't use the legacy Control Panel anymore, and disable it. For information on how to disable the legacy Control Panel, see [Disable Legacy Control Panel (CSCP)](/SkypeForBusiness/plan/disable-legacy-control-panel).
 
-## Access Control Panel
+## Access Modern Admin Control Panel
 
-To launch the new Control Panel in the browser, enter https://<pool-FQDN>/macp or a configured simple URL.
-
-The new Control Panel includes commonly used menu items that cover most of the needs of the organization. There are a few menu items from the legacy Control Panel that are unavailable in the new Control Panel. However, there's an option for the user to avail the functionalities in those menu items through PowerShell cmdlets. For more information, see the following table.
-
-> [!NOTE]
-> The documentation for other menus items will be made available subsequently in a phased manner.
-
-## Client
-
-|Sub-menu  |Source of Information for cmdlet  |
-|---------|---------|
-|Client Version Policy         |    [Client Version Policy](use-powershell-client-menu.md#client-version-policy)     |
-|Client Version Configuration      |  [Client Version Configuration](use-powershell-client-menu.md#client-version-configuration)       |
-|Device Update    | [Device Update](use-powershell-client-menu.md#device-update)        |
-|Test Device     | [Test Device](use-powershell-client-menu.md#test-device)        |
-|Device Log Configuration         |    [Device Log Configuration](use-powershell-client-menu.md#device-log-configuration)     |
-|Device Configuration         |    [Device Configuration](use-powershell-client-menu.md#device-configuration)     |
-|Mobility Policy         |    [Mobility Policy](use-powershell-client-menu.md#mobility-policy)     |
-|Push Notification Configuration         |    [Push Notification Configuration](use-powershell-client-menu.md#push-notification-configuration)     |
-
-## Security
-
-|Sub-menu  |Source of Information for cmdlet  |
-|---------|---------|
-|Registrar         |    [Registrar](use-powershell-security-menu.md#registrar)     |
-|Web Service      |  [Web Service](use-powershell-security-menu.md#web-service)       |
-|PIN Policy    | [PIN Policy](use-powershell-security-menu.md#pin-policy)        |
-
-## IM and Presence
-
-|Sub-menu  |Source of Information for cmdlet  |
-|---------|---------|
-|File Filter         |    [File Filter](use-powershell-im-and-presence-menu.md#file-filter)     |
-|URL Filter      |  [URL Filter](use-powershell-im-and-presence-menu.md#url-filter)       |
-
-## Monitoring and Archiving
-
-|Sub-menu  |Source of Information for cmdlet  |
-|---------|---------|
-|Call Detail Recording       |    [Call Detail Recording](use-powershell-monitoring-and-archiving-menu.md#call-detail-recording)     |
-|Quality of Experience Data      |  [Quality of Experience Data](use-powershell-monitoring-and-archiving-menu.md#quality-of-experience-data)       |
-|Archiving Policy       |    [Archiving Policy](use-powershell-monitoring-and-archiving-menu.md#archiving-policy)     |
-|Archiving Configuration      |  [Archiving Configuration](use-powershell-monitoring-and-archiving-menu.md#archiving-configuration)       |
-
-## Network Configuration
-
-|Sub-menu  |Source of Information for cmdlet  |
-|---------|---------|
-|Location Policy       |    [Location Policy](use-powershell-network-configuration-menu.md#location-policy)     |
-|Bandwidth Policy      |  [Bandwidth Policy](use-powershell-network-configuration-menu.md#bandwidth-policy)       |
-|Region       |    [Region](use-powershell-network-configuration-menu.md#region)     |
-|Site      |  [Site](use-powershell-network-configuration-menu.md#site)       |
-|Subnet      |  [Subnet](use-powershell-network-configuration-menu.md#subnet)       |
-|Region Link       |    [Region Link](use-powershell-network-configuration-menu.md#region-link)     |
-|Region Route      |  [Region Route](use-powershell-network-configuration-menu.md#region-route)       |
-
-## Topology
-
-|Sub-menu  |Source of Information for cmdlet  |
-|---------|---------|
-|Status       |    [Status](use-powershell-topology-menu.md#status)     |
-|Server Application      |  [Server Application](use-powershell-topology-menu.md#server-application)       |
-|Simple URL       |    [Simple URL](use-powershell-topology-menu.md#simple-url)     |
-|Trusted Application       |    [Trusted Application](use-powershell-topology-menu.md#trusted-application)     |
+To launch Modern Admin Control Panel in the browser, enter https://<pool-FQDN>/macp or a configured simple URL.

Skype/SfBServer2019/deprecated.md

@@ -29,12 +29,6 @@ The following features and functionality have been deprecated in Skype for Busin
 
 Skype for Business Server 2015 and its predecessors allowed you to configure an Extensible Messaging and Presence Protocol (XMPP) proxy on the Edge Server and an XMPP Gateway on the Front End Server or Front End pool. This functionality is no longer available in Skype for Business Server 2019.
 
-### Persistent Chat for 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. Persistent chat can't be deployed with Skype for Business Server 2019. This server role is removed from Topology Builder and from the code. 
-
-The same functionality is available in Teams. For more information, see [Getting started with your Microsoft Teams upgrade](/microsoftteams/upgrade-start-here).
-
 ### SQL Mirroring for Skype for Business Server
 
 SQL Mirroring can't be deployed with Skype for Business Server 2019. Other options for providing High Availability and Disaster Recovery are still supported and you should choose from among them. See [Plan for high availability and disaster recovery in Skype for Business Server](../SfbServer/plan-your-deployment/high-availability-and-disaster-recovery/high-availability-and-disaster-recovery.md) to review the options.

Skype/SfBServer2019/migration/migrate-persistent-chat-pool.md

@@ -0,0 +1,75 @@
+---
+ms.date: 11/21/2024
+title: "Migrate Persistent Chat pool"
+ms.reviewer: 
+ms.author: serdars
+author: serdarsoysal
+manager: serdars
+audience: ITPro
+ms.topic: quickstart
+ms.service: skype-for-business-server
+f1.keywords:
+- NOCSH
+ms.localizationpriority: medium
+description: "Migrate Persistent Chat pool from Skype for Business Server 2015 to Skype for Business Server 2019."
+---
+
+# Migrate Persistent Chat pool
+
+If you are migrating from Skype for Business Server 2015 (with Persistent Chat enabled) to Skype for Business Server 2019 and you want to migrate your Persistent Chat data, follow these steps:  
+
+Ensure that admin has the `RTCUniversalServerAdmins` permission assigned.
+
+1. **Export Persistent Chat data from Skype for Business Server 2015:**<br> 
+Run the following cmdlet on the Skype for Business 2015 front-end server to export Persistent Chat data (categories, rooms, chats etc.):
+
+   ```powershell
+   Export-CsPersistentChatData -DBInstance "<backend-FQDN\instance-name>" -FileName "C:\PersistentChatData.zip"
+   ```
+
+2. **Import Persistent Chat data into Skype for Business Server 2019:**<br> 
+Bring in the exported Persistent Chat data (zip file) from Skype for Business 2015 front-end server to Skype for Business 2019 front-end server (at C:\PersistentChatData.zip). Run the following cmdlet on the Skype for Business 2019 front-end server to import Persistent Chat data:
+
+   ```powershell
+   Import-CsPersistentChatData -DBInstance "<backend-FQDN\instance-name>" -FileName "C:\PersistentChatData.zip"
+   ```
+
+3. **Update default Persistent Chat pool URL in Skype for Business Server 2019:** 
+
+   1. Open the Topology Builder of Skype for Business Server 2019 and right-click the site-name. 
+   2. Select **Edit Properties** and go to **Persistent Chat setting**. 
+
+      :::image type="content" source="../media/migration/right-click.png" alt-text="Screenshot of Topology builder." lightbox="../media/migration/right-click.png":::
+
+   1. You'll notice that **Default Persistent Chat pool** has Skype for Business Server 2015 value selected in the dropdown. Change that to select Skype for Business 2019 Server pool value, and select **OK**. 
+
+      :::image type="content" source="../media/migration/default-pool.png" alt-text="Screenshot of Edit Properties.":::
+
+   1. To publish the topology, in the Topology Builder, select **Topology** and select **Publish**. 
+
+      :::image type="content" source="../media/migration/topo-1.png" alt-text="Screenshot of publishing topology.":::  
+
+
+4. **Verify duplicate categories in Skype for Business Server 2019:**
+After importing the database, ensure that duplicate categories from Skype for Business Server 2015 are created in Skype for Business Server 2019. This can be checked in the Modern Admin Control Panel (MACP). 
+
+    :::image type="content" source="../media/migration/duplicate-1.png" alt-text="Screenshot of MACP." lightbox="../media/migration/duplicate-1.png":::
+
+5. **Move users from Skype for Business Server 2015 to Skype for Business Server 2019:** <br> 
+Move users from Skype for Business Server 2015 to Skype for Business Server 2019 using the **Users** section in Modern Admin Control Panel (MACP). 
+
+    :::image type="content" source="../media/migration/bulk-action.png" alt-text="Screenshot of MACP users." lightbox="../media/migration/bulk-action.png":::
+
+6. **Add users as Creators:**<br> 
+Add users in the imported categories as creators. This step is necessary because the import process might not include this information.
+
+    :::image type="content" source="../media/migration/creator.png" alt-text="Screenshot of adding users as creators." lightbox="../media/migration/creator.png":::
+
+7. **Create Persistent Chat rooms:**<br> 
+You should now be able to create Persistent Chat rooms with Skype for Business 2019 users in the Skype for Business 2019 Persistent Chat pool.
+
+Additionally, if you have multiple Skype for Business 2015 Persistent Chat server pools, you need to export every database in a similar manner. Then import into Skype for Business 2019 Server and follow the steps as given above.
+
+## Related articles
+
+- For more information about backing up and restoring Persistent Chat databases in Skype for Business, see [Back up and restore Persistent Chat databases in Skype for Business Server.](../../SfbServer/manage/persistent-chat/back-up-and-restore-databases.md)    

Skype/SfBServer2019/migration/migration-phases.md

@@ -33,10 +33,12 @@ The following phases describe the process of a pool migration to Skype for Busin
 5. [Phase 5: Add Skype for Business Server 2019 Edge Server to pilot pool](phase-5-add-edge-server-to-pilot-pool.md)
 
 6. [Phase 6: Move from pilot deployment into production](phase-6-move-from-pilot-deployment-into-production.md)
+
+1. [Phase 7: Migrate Persistent Chat pool](migrate-persistent-chat-pool.md) 
 
-7. [Phase 7: Complete post-migration tasks](phase-7-complete-post-migration-tasks.md)
+7. [Phase 8: Complete post-migration tasks](phase-7-complete-post-migration-tasks.md)
 
-8. [Phase 8: Decommission legacy pools](phase-8-decommission-legacy-pools.md)
+8. [Phase 9: Decommission legacy pools](phase-8-decommission-legacy-pools.md)
 
 
 

Skype/SfBServer2019/migration/migration-to-skype-for-business-server-2019.md

@@ -51,10 +51,12 @@ This article defines terms as specified in the following list.
 - [Phase 5: Add Edge Server to pilot pool](phase-5-add-edge-server-to-pilot-pool.md)
 
 - [Phase 6: Move from pilot deployment into production](phase-6-move-from-pilot-deployment-into-production.md)
+
+- [Phase 7: Migrate Persistent Chat pool](migrate-persistent-chat-pool.md)  
+
+- [Phase 8: Complete post-migration tasks](phase-7-complete-post-migration-tasks.md)
 
-- [Phase 7: Complete post-migration tasks](phase-7-complete-post-migration-tasks.md)
-
-- [Phase 8: Decommission legacy pools](phase-8-decommission-legacy-pools.md)
+- [Phase 9: Decommission legacy pools](phase-8-decommission-legacy-pools.md)