From 4f76cf0cd04da4bfb3e2fdaa55563245c950d4c4 Mon Sep 17 00:00:00 2001 From: David Strome <21028455+dstrome@users.noreply.github.com> Date: Mon, 30 Sep 2024 14:55:40 -0700 Subject: [PATCH 1/6] Adding Stale Workflow --- .github/workflows/Stale.yml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 .github/workflows/Stale.yml diff --git a/.github/workflows/Stale.yml b/.github/workflows/Stale.yml new file mode 100644 index 0000000000..dec280f776 --- /dev/null +++ b/.github/workflows/Stale.yml @@ -0,0 +1,19 @@ +name: (Scheduled) Mark stale pull requests + +permissions: + issues: write + pull-requests: write + +on: + schedule: + - cron: "0 */6 * * *" + workflow_dispatch: + +jobs: + stale: + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-Stale.yml@workflows-prod + with: + RunDebug: false + RepoVisibility: ${{ github.repository_visibility }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file From 6e728ac69ab19787bfad6e398f2ff10d5c239429 Mon Sep 17 00:00:00 2001 From: Alicia Weixelman Date: Tue, 1 Oct 2024 09:32:42 -0500 Subject: [PATCH 2/6] Update fix-upload-manager-hierarchy-warnings.md Edits for corrected error text to match what users see in Glint --- .../fix-upload-manager-hierarchy-warnings.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md index 6c862be94a..355821f730 100644 --- a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md +++ b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md @@ -16,13 +16,14 @@ ms.custom: When you upload employee attribute data to Microsoft Viva Glint, you may receive one of the following warning messages. Select the warning that you experience from the list at the top of the article, and follow the appropriate resolution to fix the warning. -## MANAGER_HIERARCHY_UPDATE_WARNING +## MANAGER_HIERARCHY_UPDATE_WARNING (no manager ID assigned) Warning message: > MANAGER_HIERARCHY_UPDATE_WARNING: There are \ employee records without a manager. The CEO/top of hierarchy shouldn't have a Manager ID. Employees without a Manager won't be reported in Manager reports, their scores/response won't roll up into any manager. The first 20 records: user1@contoso.com, user2@contoso.com... -**Note**: Results for employees without a Manager ID won't appear in the manager hierarchy results but will still be aggregated to other attributes and the overall organization score. +> [!NOTE] +> Results for employees without a Manager ID won't appear in the manager hierarchy results but will still be aggregated to other attributes and the overall organization score. This issue occurs if employees other than the CEO or top-level person aren't assigned a **Manager ID** value. Only the CEO or top-level person should have a blank Manager ID field. @@ -33,14 +34,16 @@ To fix the issue, follow these steps: 1. In the employee attribute data file, review all employees whose **Manager ID** field is blank, except the CEO or top-level person. 1. Enter their Manager ID values. - **Note**: If there are employees whose manager role has to be entered, use the Manager ID of their skip-level manager. + > [!NOTE] + > If there are employees whose manager role has to be entered, use the Manager ID of their skip-level manager. + 1. Upload the file again to Viva Glint. -## INVALID_MANAGER_HIERARCHY +## MANAGER_HIERARCHY_UPDATE_WARNING (missing manager record) Warning message: -> INVALID_MANAGER_HIERARCHY: User id \ has a nonexistent Manager ID \. This will cause your manager's hierarchy to be incomplete. +> MANAGER_HIERARCHY_UPDATE_WARNING: external user id is mapped to manager reference which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. This issue occurs if the uploaded file contains employees who are shown to report to a manager whose Manager ID doesn't have a corresponding employee record. @@ -53,5 +56,7 @@ To fix the issue, follow these steps: 1. In the errors file, identify the Manager IDs that are listed as nonexistent. 1. For each Manager ID that's identified in step 3, add corresponding employee records in the original employee attribute data. - **Note**: If there are managers (non-CEO level) who aren't part of the regular employee upload (for example, they are on leave or are contractors), set their **Status** value to **INACTIVE** in the employee attribute data file to complete your manager hierarchy. + > [!NOTE] + > If there are managers (non-CEO level) who aren't part of the regular employee upload (for example, they are on leave or are contractors), set their **Status** value to **INACTIVE** in the employee attribute data file to complete your manager hierarchy. + 1. Upload the file again to Viva Glint. From c055386be31486b3e49ac2e6885cef64e32c5056 Mon Sep 17 00:00:00 2001 From: Alicia Weixelman Date: Tue, 1 Oct 2024 09:40:20 -0500 Subject: [PATCH 3/6] Update fix-upload-manager-hierarchy-warnings.md --- .../data-file-upload/fix-upload-manager-hierarchy-warnings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md index 355821f730..26d305ddc1 100644 --- a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md +++ b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md @@ -43,7 +43,7 @@ To fix the issue, follow these steps: Warning message: -> MANAGER_HIERARCHY_UPDATE_WARNING: external user id is mapped to manager reference which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. +> MANAGER_HIERARCHY_UPDATE_WARNING: external user id \ is mapped to manager reference \ which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. This issue occurs if the uploaded file contains employees who are shown to report to a manager whose Manager ID doesn't have a corresponding employee record. From 74a9f1af0bbcca861e39c2b0cf774051ed0cd1d2 Mon Sep 17 00:00:00 2001 From: Meera Krishna Date: Tue, 1 Oct 2024 11:31:27 -0700 Subject: [PATCH 4/6] Update fix-upload-manager-hierarchy-warnings.md --- .../data-file-upload/fix-upload-manager-hierarchy-warnings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md index 26d305ddc1..4bc01d04c5 100644 --- a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md +++ b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md @@ -43,7 +43,7 @@ To fix the issue, follow these steps: Warning message: -> MANAGER_HIERARCHY_UPDATE_WARNING: external user id \ is mapped to manager reference \ which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. +> MANAGER_HIERARCHY_UPDATE_WARNING: external user id \<`x`\> is mapped to manager reference \<`y`\> which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. This issue occurs if the uploaded file contains employees who are shown to report to a manager whose Manager ID doesn't have a corresponding employee record. From 2b697b721d288e30c4e4976840ca6ebd9882287a Mon Sep 17 00:00:00 2001 From: Meera Krishna Date: Tue, 1 Oct 2024 11:38:28 -0700 Subject: [PATCH 5/6] Update fix-upload-manager-hierarchy-warnings.md --- .../data-file-upload/fix-upload-manager-hierarchy-warnings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md index 4bc01d04c5..26d305ddc1 100644 --- a/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md +++ b/Viva/Glint/data-file-upload/fix-upload-manager-hierarchy-warnings.md @@ -43,7 +43,7 @@ To fix the issue, follow these steps: Warning message: -> MANAGER_HIERARCHY_UPDATE_WARNING: external user id \<`x`\> is mapped to manager reference \<`y`\> which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. +> MANAGER_HIERARCHY_UPDATE_WARNING: external user id \ is mapped to manager reference \ which is not on file or system. This will cause your manager's hierarchy to be incomplete and employee results don't roll into Manager Hierarchy views in reporting. This issue occurs if the uploaded file contains employees who are shown to report to a manager whose Manager ID doesn't have a corresponding employee record. From b05876c25d210d41ac5eda1a24c6d9f4f34f004b Mon Sep 17 00:00:00 2001 From: Meera Krishna Date: Wed, 2 Oct 2024 15:11:00 -0700 Subject: [PATCH 6/6] Updated 2 MTRW known issues --- .../teams-rooms-known-issues-windows.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md b/Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md index e5d80c3fcf..4bfa9900ea 100644 --- a/Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md +++ b/Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md @@ -22,7 +22,7 @@ appliesto: - Microsoft Teams search.appverid: - MET150 -ms.date: 09/23/2024 +ms.date: 10/02/2024 --- # Known issues with Teams Rooms on Windows @@ -45,8 +45,8 @@ ms.date: 09/23/2024 |QR code to join meetings reappears after being disabled.|You have disabled the QR code that is displayed on the device console and in Front of Room displays to join Teams meetings.

However, the QR code reappears when the device restarts, or after a user either joins or leaves a meeting on the device.|Restart the device so that it picks up a new configuration that fixes the issue.| |Volume change indicator not working|When you change the volume of a Teams Rooms device by using the volume controls that are on the device or on an external audio device, the change isn't displayed in the volume setting of the Teams Rooms device.

The change to the volume settings takes effect but the visual display doesn't reflect the change.|No workaround is required because the functionality is working.| |Teams Rooms app window doesn't fill the screen on the device console.|The window of the Teams Rooms app takes up only a part of the device console or Front of Room display and doesn't resize to fill the screen.

This issue usually occurs in displays that are disconnected in their Sleep or Wake states.|To fix the issue, update to version 5.1.24.0 of the Teams Rooms app.| -|Chat panel in Gallery view is blank.|You restart a Teams Rooms on Windows device and join a meeting. However you see that the chat panel in Gallery view is empty.

This issue occurs only with the first meeting that you join after restarting your device. Subsequent meetings are not affected.|To work around the issue for the first meeting that's impacted, use the following steps:
  1. Select the **Chat** button on the device console to hide the chat panel.
  2. Select the **Chat** button again to reopen the chat panel. Now you can see incoming messages.
| -|The onscreen keyboard on a touch console device is missing or not responsive.|The onscreen keyboard on the touch console in a Teams Rooms for Windows device either doesn't work or doesn't appear.

Because of this issue, you're unable to perform the following actions:
  • Enter text to call another user.
  • Add a user to a meeting.
  • Enter a username and password to access the Settings menu.
|Use the following steps to work around the issue:
  1. In the Teams Rooms device console, select **More** > **Settings**.
  2. Select **Windows Settings**.
  3. Sign in as an administrator.
  4. Search for and select the Registry Editor.
  5. Select the **HKEY_USERS** folder from the list of machine user SIDs.
  6. Select **File** > **Load Hive**.
  7. Browse to the C:\Users\Skype folder, type `NTUSER.dat` in the **File name** field, and then select **Open**.
  8. When prompted for a key name for the newly loaded hive, type `Skype`.
    You will see the registry settings for the user named Skype.
  9. Browse to the **HKEY_USERS\Skype\SOFTWARE\Microsoft\TabletTip\1.7** folder in the registry.
  10. Right click (or tap and hold) the **1.7** folder, select **New** > **DWORD (32-bit) Value**.
  11. Type `EnableDesktopModeAutoInvoke` as the name of the registry entry.
  12. Double-click the **EnableDesktopModeAutoInvoke** registry entry, type `1` in the **Value data** field, and then tap **OK**.>/li>
  13. Restart the Teams Rooms device.
| +|Chat panel in Gallery view is blank.|You restart a Teams Rooms on Windows device and join a meeting. However you see that the chat panel in Gallery view is empty.

This issue occurs only with the first meeting that you join after restarting your device. Subsequent meetings are not affected.|To fix the issue, update to version 5.2.115.0 of the Teams Rooms app.| +|The onscreen keyboard on a touch console device is missing or not responsive.|The onscreen keyboard on the touch console in a Teams Rooms for Windows device either doesn't work or doesn't appear.

Because of this issue, you're unable to perform the following actions:
  • Enter text to call another user.
  • Add a user to a meeting.
  • Enter a username and password to access the Settings menu.
|To fix the issue, update to version 5.2.115.0 of the Teams Rooms app.| ## Hardware issues