You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -28,6 +24,14 @@ This article describes known issues that can often be resolved by configuration
28
24
29
25
## Known issues
30
26
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
+
31
35
### Autopilot profile not being applied when assigned
32
36
33
37
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
62
66
63
67
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.
64
68
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.
66
72
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.
68
74
69
75
### Virtual machine failing at "Preparing your device for mobile management"
Copy file name to clipboardExpand all lines: memdocs/configmgr/mdt/known-issues.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,44 @@ ms.collection: openauth
16
16
17
17
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.
18
18
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:
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:
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.
34
44
35
-
- More powerful Cloud PCs to run CPU intensive applications.
36
-
- More disk space for file storing.
37
45
38
46
## Requirements
39
47
@@ -55,10 +63,10 @@ Resizing isn’t supported for Cloud PCs provisioned through group-based license
55
63
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.
56
64
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**.
57
65

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.
59
67
4. Select **Resize**.
60
68
- 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.
62
70
- 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.
63
71
- 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.
0 commit comments