Skip to content

Commit f2e12a8

Browse files
committed
Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into erikre-2210ID-15477561
2 parents 6910023 + b664f7e commit f2e12a8

5 files changed

Lines changed: 76 additions & 17 deletions

File tree

memdocs/autopilot/known-issues.md

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,14 @@
11
---
22
title: Windows Autopilot known issues
33
description: Inform yourself about known issues that may occur during Windows Autopilot deployment.
4-
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
5-
ms.prod: w10
6-
ms.mktglfcycl: deploy
4+
ms.prod: windows-client
5+
ms.technology: itpro-deploy
76
ms.localizationpriority: medium
8-
ms.sitesec: library
9-
ms.pagetype: deploy
10-
audience: itpro
117
author: aczechowski
128
ms.author: aaroncz
139
ms.reviewer: jubaptis
1410
manager: dougeby
15-
ms.date: 05/18/2022
11+
ms.date: 09/21/2022
1612
ms.collection: M365-modern-desktop
1713
ms.topic: troubleshooting
1814
---
@@ -28,6 +24,14 @@ This article describes known issues that can often be resolved by configuration
2824

2925
## Known issues
3026

27+
### Autopilot deployment report shows "failure" status on a successful deployment
28+
29+
The Autopilot deployment report (preview) will show a failed status for any device that experiences an initial deployment failure. For subsequent deployment attempts, using the **Try again** or **Continue to desktop** options, it won't update the deployment state in the report. If the user resets the device, it will show as a new deployment row in the report with the previous attempt remaining as failed.
30+
31+
### Autopilot deployment report doesn't show deployed device
32+
33+
Autopilot deployments that take longer than one hour may display an incomplete deployment status in the deployment report. If the device successfully enrolls but doesn't complete provisioning after more than one hour, the device status may not be updated in the report.
34+
3135
### Autopilot profile not being applied when assigned
3236

3337
In Windows 10 April and some May update releases, there is an issue where the Autopilot profile may fail to apply to the device and the hardware hash may not be harvested. As a result, any settings made in the profile may not be configured for the user such as device renaming. To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device.
@@ -62,9 +66,11 @@ When you attempt an Autopilot reset, you see the following message: _Autopilot r
6266

6367
When a device is registered in Autopilot and no profile is assigned, it will take the default Autopilot profile. This behavior is by design. It makes sure that all devices that you register with Autopilot go through the Autopilot experience. If you don't want the device to go through an Autopilot deployment, remove the Autopilot registration.
6468

65-
### White screen during HAADJ deployment
69+
### White screen during hybrid Azure AD joined deployment
70+
71+
There's a UI bug on Autopilot hybrid Azure AD joined deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
6672

67-
There's a UI bug on Autopilot HAADJ deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
73+
This issue was resolved in September 2022.
6874

6975
### Virtual machine failing at "Preparing your device for mobile management"
7076

memdocs/configmgr/mdt/known-issues.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,44 @@ ms.collection: openauth
1616

1717
This article provides details of any current known issues and limitations with the Microsoft Deployment Toolkit (MDT). It assumes familiarity with MDT version concepts, features, and capabilities.
1818

19+
## HTA applications report Script error after upgrading to ADK for Windows 11, version 22H2
20+
After you updated your MDT boot image to [ADK for Windows 11, version 22H2](/windows-hardware/get-started/adk-install), HTA applications stop working and a message box is displayed: Script Error - An error has occurred in the script on this page.
21+
22+
HTA applications rely on MSHTML and starting with Windows 11, version 22H2, the default legacy scripting engine was changed.
23+
24+
To work around this issue you need to add the following registry value in WinPE:
25+
```
26+
reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f
27+
```
28+
To enable this change in MDT, we recommend that you back up the following file: `C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x64.xml` and to modify it as follows:
29+
``` <?xml version="1.0" encoding="utf-8"?>
30+
<unattend xmlns="urn:schemas-microsoft-com:unattend">
31+
<settings pass="windowsPE">
32+
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
33+
<Display>
34+
<ColorDepth>32</ColorDepth>
35+
<HorizontalResolution>1024</HorizontalResolution>
36+
<RefreshRate>60</RefreshRate>
37+
<VerticalResolution>768</VerticalResolution>
38+
</Display>
39+
<RunSynchronous>
40+
<RunSynchronousCommand wcm:action="add">
41+
<Description>Lite Touch PE</Description>
42+
<Order>1</Order>
43+
<Path>reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f</Path>
44+
</RunSynchronousCommand>
45+
<RunSynchronousCommand wcm:action="add">
46+
<Description>Lite Touch PE</Description>
47+
<Order>2</Order>
48+
<Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
49+
</RunSynchronousCommand>
50+
</RunSynchronous>
51+
</component>
52+
</settings>
53+
</unattend>
54+
```
55+
After saving the changes, you will need to completely regenerate the boot images.
56+
1957
## Windows Deployment Services (WDS) multicast stops working after upgrading to ADK for Windows 11
2058

2159
<!-- 12891430 -->

memdocs/intune/remote-actions/remote-help.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The Remote help app supports the following capabilities:
7777
> [!NOTE]
7878
> Remote help has the following limitations:
7979
>
80-
> - Remote help is not supported on GCC, GCC High or DoD Tenants.
80+
> - Remote help is not supported on GCC High or DoD Tenants.
8181
> - You cannot establish a remote help session from one tenant to a different tenant.
8282
> - May not be available in all markets or localizations.
8383
@@ -376,4 +376,4 @@ Version 4.0.0.0 - GA release
376376
## Next steps
377377

378378
[Get support in Microsoft Endpoint Manager admin center](../../get-support.md)
379-
379+

windows-365/enterprise/resize-cloud-pc.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,18 @@ ms.collection: M365-identity-device-management
3030

3131
# Resize a Cloud PC (preview)
3232

33-
The **Resize** remote action lets you upgrade a Windows 365 Enterprise Cloud PC’s RAM, CPU, and storage size to meet the user’s needs. Resizing is important for users that need:
33+
The **Resize** remote action lets you upgrade a Windows 365 Enterprise Cloud PC’s RAM, CPU, and storage size to meet the user’s needs. Resizing is important for users that need to:
34+
35+
- Upgrade a Windows 365 Enterprise Cloud PC’s RAM, CPU, and storage size to meet the user’s needs.
36+
- Downgrade the RAM and CPU of a Cloud PC.
37+
38+
Resizing gives admins the flexibility to upgrade/downgrade the following specifications without having to provision Cloud PCs from scratch:
39+
- Increase the RAM and vCPU cores when a user requires CPU intensive applications.
40+
- Increase the disk space for file storing.
41+
- Decrease the RAM and vCPU cores when a user doesn't need to run CPU intensive applications.
42+
43+
Resizing doesn't you let downsize disk space.
3444

35-
- More powerful Cloud PCs to run CPU intensive applications.
36-
- More disk space for file storing.
3745

3846
## Requirements
3947

@@ -55,10 +63,10 @@ Resizing isn’t supported for Cloud PCs provisioned through group-based license
5563
1. Contact your end users and have them save their work and sign out. Resizing automatically disconnects the user from their session and any unsaved work might be lost. Therefore, it's best to coordinate any resizing with the user before you begin.
5664
2. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **All Devices** > choose a device > **Resize**.
5765
![Screenshot of resize a Cloud PC](./media/resize-cloud-pc/resize.png)
58-
3. You’ll see a list with all the possible SKUs that you can upgrade to. You can only increase a Cloud PC’s storage and specifications. Options with lower storage or specifications are grayed out. Select one of the available options.
66+
3. You’ll see a list with all the possible SKUs that you can upgrade to. You increase and decrease a Cloud PC’s specs (RAM/vCPU). You can only increase the OS disk storage. You can't decrease the OS disk storage. If you are downsizing a user’s Cloud PC, options with lower storage will be grayed out. Select one of the available options.
5967
4. Select **Resize**.
6068
- When triggering a resize, the Cloud PC will be rebooted and the user will be immediately disconnected from their current session. Make sure the user saves all their work to avoid any potential data loss.
61-
- If there are available licenses, the upgrade will take place.
69+
- If there are available licenses, the upgrade/downgrade will take place.
6270
- If you have a combination of paid and trial licenses, the resize feature will use your paid licenses first. After these licenses run out, the resize operation will use your trial licenses.
6371
- If there are no licenses in your inventory, the resizing will fail. You can contact your procurement admin to request more licenses. After the license has been purchased and added to the inventory in the Microsoft Admin Center, you can retry the resize operation.
6472

windows-365/enterprise/whats-new.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: ErikjeMS
88
ms.author: erikje
99
manager: dougeby
10-
ms.date: 09/20/2022
10+
ms.date: 09/22/2022
1111
ms.topic: reference
1212
ms.service: cloudpc
1313
ms.subservice:
@@ -51,6 +51,13 @@ Learn what new features are available in Windows 365 Enterprise.
5151
<!-- ########################## -->
5252
## Week of September 19, 2022
5353

54+
<!-- ***********************************************-->
55+
### Device management
56+
57+
#### Downsize Cloud PCs (Preview)<!--41076858 -->
58+
59+
You can now downsize a Cloud PC's RAM and specifications (except disk size). For more information, see [Resize a Cloud PC](resize-cloud-pc.md).
60+
5461
<!-- ***********************************************-->
5562
### Device provisioning
5663

0 commit comments

Comments
 (0)