Skip to content

Commit bb1dd4d

Browse files
author
Pavel Yurenev
committed
Fixing broken links and pics
1 parent e0218ac commit bb1dd4d

9 files changed

Lines changed: 3 additions & 3 deletions

File tree

support/mem/configmgr/diagnostics/media/failed-devices-client-health-dashboard/client-health-dashboard-scenario-health.png renamed to support/mem/configmgr/console-management/media/failed-devices-client-health-dashboard/client-health-dashboard-scenario-health.png

File renamed without changes.

support/mem/configmgr/diagnostics/media/failed-devices-client-health-dashboard/client-health-dashboard-settings.png renamed to support/mem/configmgr/console-management/media/failed-devices-client-health-dashboard/client-health-dashboard-settings.png

File renamed without changes.

support/mem/configmgr/diagnostics/media/failed-devices-client-health-dashboard/client-status-settings-properties.png renamed to support/mem/configmgr/console-management/media/failed-devices-client-health-dashboard/client-status-settings-properties.png

File renamed without changes.

support/mem/configmgr/diagnostics/media/failed-devices-client-health-dashboard/delete-aged-status-messages.png renamed to support/mem/configmgr/console-management/media/failed-devices-client-health-dashboard/delete-aged-status-messages.png

File renamed without changes.

support/mem/configmgr/diagnostics/media/failed-devices-client-health-dashboard/scenario-health-bar-chart.png renamed to support/mem/configmgr/console-management/media/failed-devices-client-health-dashboard/scenario-health-bar-chart.png

File renamed without changes.
Binary file not shown.

support/mem/configmgr/setup-migrate-backup-recovery/state-message-processing-performance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ To troubleshoot the performance issue, follow these steps:
6464

6565
If your usual processing rate isn't enough to handle the backlog, go to the next step.
6666

67-
3. Change the [internal settings](../update-management/state-messaging-description.md#state_message_system-settings) of the SMS_STATE_SYSTEM component.
67+
3. Change the [internal settings](state-messaging-description.md#state_message_system-settings) of the SMS_STATE_SYSTEM component.
6868

6969
> [!WARNING]
7070
> Serious problems might occur if you change these settings incorrectly. Microsoft can't guarantee that these problems can be solved, and doesn't support this scenario. Modify the settings at your own risk. We recommend that you restore these settings after you resolve the backlog.

support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -358,7 +358,7 @@ Get new Easy Setup Package IDs~~
358358
Found a new available update~~
359359
```
360360
361-
DMPDownloader uses high-priority [state messages](../update-management/state-messaging-description.md) to report progress to the site server. DMPDownloader logs entries that resemble the following example:
361+
DMPDownloader uses high-priority [state messages](state-messaging-description.md) to report progress to the site server. DMPDownloader logs entries that resemble the following example:
362362
363363
```output
364364
Generating state message: 6 for package 3b7d84fa-eccc-4ea0-b8ab-abbda1e88e0e~~

support/mem/configmgr/update-management/track-software-update-deployment-process.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -783,4 +783,4 @@ After the deployment and the deployment policy have been created on the server,
783783
784784
## State message reporting
785785
786-
Throughout the deployment phase, multiple state messages are raised to indicate the current state of the updates and the deployment itself. After these state messages are raised, they're processed in the way that's described in [State messaging data flow](state-messaging-description.md#state-messaging-data-flow).
786+
Throughout the deployment phase, multiple state messages are raised to indicate the current state of the updates and the deployment itself. After these state messages are raised, they're processed in the way that's described in [State messaging data flow](../setup-migrate-backup-recovery/state-messaging-description.md#state-messaging-data-flow).

0 commit comments

Comments
 (0)