Skip to content

Commit 90d8fba

Browse files
committed
switching to include file
1 parent feb5a0e commit 90d8fba

5 files changed

Lines changed: 35 additions & 29 deletions

File tree

windows-365/business/restore-overview.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -40,18 +40,11 @@ In addition to these short-term restore points, there are also four long-term re
4040

4141
As time passes and a new short-term or long-term restore point is added, the oldest short-term/long-term (respectively) restore point is removed.
4242

43-
## Risks and results of restoring a Cloud PC
43+
[!INCLUDE [Restore risks and best practices](../includes/restore-risks-best-practices.md)]
4444

45-
Cloud PCs have same risks as all Windows PCs when performing a full disk restore. These risks and results include:
45+
## End user interface
4646

47-
- All changes made to the Cloud PC between the saved restore point and when the restore is started will be lost. This lost information includes all data, documents, installed applications, configurations, downloads, and other changes. External data stored in cloud services, like OneDrive, won't be lost.
48-
- Various applications, agents and tools also use rolling passwords, secrets, certificates, and keys. If any of these credentials are updated between the current time and the restore point, the associated service or application will be impacted.
49-
- The chances of data loss and [automated machine account password updates](known-issues.md#restore-and-automatic-rolling-credentials) increase with longer time gaps between the selected restore point and the current time.
50-
51-
## Best practices
52-
53-
- To minimize data loss and the risk of a rolling password conflict, choose a restore point that is as close as possible to the current time.
54-
- After a restoration is complete, the user should immediately sign into their Cloud PC to verify that they can successfully connect. If a user can't connect, or experiences unexpected behavior, try a second restoration to a different restore point that is more recent. On rare occasions you may need to reprovision/reset a Cloud PC if all restore points have obsolete rolling credentials.
47+
To restore their Cloud PC, an end user must sign in to http://windows365.microsoft.com, select the gear icon, select **Restore (preview)**, and follow the onscreen prompts.
5548

5649
<!-- ########################## -->
5750
## Next steps

windows-365/enterprise/known-issues-enterprise.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -38,14 +38,6 @@ The following items are known issues for Windows 365 Enterprise.
3838

3939
A [resize](resize-cloud-pc.md) of a Cloud PC eliminates all existing [restore](restore-overview.md) points for that Cloud PC. New restore points will be captured at the intervals defined in the user setting.
4040

41-
## Restore and automatic rolling credentials
42-
43-
Many devices registered with Active Directory might have a machine account password that is automatically updated. By default, these passwords are updated every 30 days. This automation applies to hybrid joined PCs but not Azure Active Directory Native PCs.
44-
45-
The machine account password is maintained on the Cloud PC. If the Cloud PC is restored to a point that has a previous password stored, the Cloud PC won't be able to sign onto the domain.
46-
47-
For more information, see [Machine Account Password Process](https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/machine-account-password-process/ba-p/396026).
48-
4941
## Next steps
5042

5143
[Troubleshoot Windows 365 Enterprise Cloud PC](troubleshooting.md)

windows-365/enterprise/restore-overview.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -40,17 +40,7 @@ In addition to these configurable short-term restore points, there are also four
4040

4141
As time passes and a new restore point is added, the oldest restore point is removed.
4242

43-
## Risks and results of restoring a Cloud PC
44-
45-
Cloud PCs have same risks as all Windows PCs when performing a full disk restore. These risks and results include:
46-
47-
- All changes made to the Cloud PC between the saved restore point and when the restore is started will be lost. This lost information includes all data, documents, installed applications, configurations, downloads, and other changes. External data stored in cloud services, like OneDrive, won't be lost.
48-
- Various applications, agents and tools also use rolling passwords, secrets, certificates, and keys. If any of these credentials are updated between the current time and the restore point, the associated service or application will be impacted.
49-
50-
## Best practices
51-
52-
- To minimize data loss and the risk of a rolling password conflict, choose a restore point that is as close as possible to the current time.
53-
- After a restoration is complete, the user should immediately sign into their Cloud PC to verify that they can successfully connect. If a user can't connect, or experiences unexpected behavior, try a second restoration to a different restore point that is more recent. On rare occasions you may need to reprovision/reset a Cloud PC if all restore points have obsolete rolling credentials.
43+
[!INCLUDE [Restore risks and best practices](../includes/restore-risks-best-practices.md)]
5444

5545
<!-- ########################## -->
5646
## Next steps

windows-365/includes/known-issues.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,3 +15,11 @@ When non-local admin users sign in to a Cloud PC by uinsg an iPad and the Micros
1515

1616
**Troubleshooting steps**: Make sure that you have the latest version of Remote Desktop Client as found [here](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients).
1717
In addition, you can also sign in to the Cloud PC by using [windows365.microsoft.com](https://windows365.microsoft.com).
18+
19+
## Restore and automatic rolling credentials
20+
21+
Many devices registered with Active Directory might have a machine account password that is automatically updated. By default, these passwords are updated every 30 days. This automation applies to hybrid joined PCs but not Azure Active Directory Native PCs.
22+
23+
The machine account password is maintained on the Cloud PC. If the Cloud PC is restored to a point that has a previous password stored, the Cloud PC won't be able to sign onto the domain.
24+
25+
For more information, see [Machine Account Password Process](https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/machine-account-password-process/ba-p/396026).
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: include file
3+
description: include file
4+
author: ErikjeMS
5+
ms.service: cloudpc
6+
ms.topic: include
7+
ms.date: 03/03/2022
8+
ms.author: erikje
9+
ms.custom: include file
10+
---
11+
12+
## Risks and results of restoring a Cloud PC
13+
14+
Cloud PCs have same risks as all Windows PCs when performing a full disk restore. These risks and results include:
15+
16+
- All changes made to the Cloud PC between the saved restore point and when the restore is started will be lost. This lost information includes all data, documents, installed applications, configurations, downloads, and other changes. External data stored in cloud services, like OneDrive, won't be lost.
17+
- Various applications, agents and tools also use rolling passwords, secrets, certificates, and keys. If any of these credentials are updated between the current time and the restore point, the associated service or application will be impacted.
18+
- The chances of data loss and [automated machine account password updates](known-issues.md#restore-and-automatic-rolling-credentials) increase with longer time gaps between the selected restore point and the current time.
19+
20+
## Best practices
21+
22+
- To minimize data loss and the risk of a rolling password conflict, choose a restore point that is as close as possible to the current time.
23+
- After a restoration is complete, the user should immediately sign into their Cloud PC to verify that they can successfully connect. If a user can't connect, or experiences unexpected behavior, try a second restoration to a different restore point that is more recent. On rare occasions you may need to reprovision/reset a Cloud PC if all restore points have obsolete rolling credentials.

0 commit comments

Comments
 (0)