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
Copy file name to clipboardExpand all lines: memdocs/autopilot/known-issues.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,18 @@ This article describes known issues that can often be resolved by configuration
28
28
29
29
## Known issues
30
30
31
+
### White screen during HAADJ deployment
32
+
33
+
There is 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 should not impact the deployment process.
34
+
35
+
### Virtual machine failing at “Preparing your device for mobile management”
36
+
37
+
This error can be resolved by configuring your virtual machine with a minimum of 2 processers and 4GB of memory.
38
+
39
+
### ODJConnectorSvc.exe leaks memory
40
+
41
+
When using a proxy server with the ODJConnector service, the memory file can get too large when processing requests resulting in impacts to performance. The current workaround for this issue is to restart the ODJConnectSvc.exe service.
42
+
31
43
### Reset button causes pre-provisioning to fail on retry
32
44
33
45
When ESP fails during the pre-provisioning flow and the user selects the reset button, TPM attestation may fail during the retry.
| Device experience | Make Microsoft Launcher the default launcher | Not configured | Organizations may choose to implement Microsoft Launcher to ensure a consistent home screen experience on Fully managed devices. For more information, see [How to Setup Microsoft Launcher on Android Enterprise Fully Managed Devices with Intune](https://techcommunity.microsoft.com/t5/intune-customer-success/how-to-setup-microsoft-launcher-on-android-enterprise-fully/ba-p/1482134)|
@@ -150,6 +150,7 @@ The policy settings enforced in level 3 include all the policy settings recommen
150
150
| General | Date and Time changes | Block ||
151
151
| General | Tethering and access to hotspots | Block ||
152
152
| General | Beam data using NFC | Block ||
153
+
| General | Search work contacts and display work contact caller-id in personal profile | Block ||
| Applications | App auto-updates | Always | Organizations should adjust this setting as necessary as data plan charges may occur if app updates occur over the cellular network. |
155
156
| Work profile password | Number of sign-in failures before wiping device | 5 | Organizations may need to update this setting to match their password policy. |
0 commit comments