Forum Widgets
Latest Discussions
Display language choice on HP and Dell are skipped in OOBE when network cable are connected
I have been involved in many Intune Autopilot deployments where we have technicians who complete the pre-deploy on computers from HP and Dell before delivery. This has worked well for many years, but lately, we have received complaints from users because the computer arrives with the wrong OS/Display language. I am aware of the settings for region and keyboard I deployment profiles. I also know how to change the language with LIP in Win10 and PowerShell in Win11. What we have discovered now but not yet verified is the following: A computer from, for example, HP is shipped from the factory with multiple languages of the OS, which comes up as a question BEFORE the normal first screen in OOBE for region and keyboard, and if you choose Swedish in our case, the computer's language becomes Swedish after pre-deploy. What we have noticed now is that if you connect a network cable before starting the computer, the language choice in the OS never shows up; it instead jumps directly to region and keyboard and has chosen English as the OS language. It doesn't matter if you run pre-deploy or user driven deploy the display language choice are skipped and defaults to English. To get the language choice back, you must run restore with F11, i.e., the manufacturer's image, and then restart pre-deploy without the network cable connected until you have pressed Win 5 times. Yes,i know it is possible to change it afterwards with PowerShell in this case for Windows 11, but it takes time. Has anyone else noticed the same effect with multi-language, pre-deploy, and network cable? Or have i missed a major change in Intune or Windows?
Unable to enroll in MDM
Hi all. I am trialing Intune now so am new to it. I initially was able to enroll my Windows test machine. Showed up under devices in Intune. It stopped working in the last couple days. If i turn off the MDM under Automatic Enrollment i can sign it into EntraID and sign in with my account there. Once i enable the MDM again for that user, i get a spinning circle of dots immediately after signing in. I have deleted all the policies i created to get it back to 0, but still just spinning. Does not move onto to setting up account. User has Intune license covered under M365 E3. Can anyone help? Thanks AshIntune Re-Enrollment Registry Key "MmpcEnrollmentFlag"
Hey there, In the last few weeks, we encountered issues with clients (Entra Hybrid Joined) losing their Intune connection after setting an incorrect group policy. Although the group policy change was quickly reverted, about 10 clients were removed from Intune. I attempted to re-enroll these clients using various methods (MEMC Co-management, GPO, Scheduled Task, and even using psexec to directly start auto-enrollment), but the enrollment process consistently failed with the following error under Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider\Enrollment: Auto MDM Enroll: Device Credential (0x1), Failed (Bad request (400).) and/or following in CoManagementHandler.log Failed to get management URL with error 0x80070002 Eventually, I discovered a registry key that was not present on the working clients: Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments Value: MmpcEnrollmentFlag Data: 0x00000002 After deleting this key and restarting the enrollment, everything worked immediately. I am curious about how and why this registry key is created and what its function is. Looking forward to your input.
Developer Options on Android Device
Hi all, I have an Android device enrolled in InTune and I'm trying to enable developer options. This would normally be done by tapping on the build number 7 times, however, when I try it on this device, nothing happens. There's no pop-up or error message, just nothing. I've tested on other identical devices and it works. It's got developer options enabled in the configuration policy, compliant in InTune, and was freshly reset/set-up, any ideas why it's not working?Unable to create Win32 apps in Intune
I am unable to create a very basic Win32 application in Intune. I get green check marks across the board but when I try to create the application I get an error message saying "Save Application Failed. TypeError: Cannot read properties of null (reading 'id')". Any suggestions?
Deploying Script as Win32 App
Hi all, I created a script that is supposed to check if a certain app was installed from a managed installer, then create a file in the C:\Temp folder if it was installed from a managed installer. I would deploy this as a Win32 app so that I could use the detection rules in the Win32 App deployment to check which device was installed via a managed installer. However, it doesn't seem to work. I created a transcript log as well to check if I would get an output from the variables, but it seems to only run the else block in the If Statement. We use a Business Premium license, so I don't access to Enterprise license capabilities like proactive remediation scripts. It is run using the System credentials, I've tested the script locally which works. Thank you, I've included some images of the script and transcript log. Script: Transcript Log Output:Allow non-admins to install apps from Company Portal
How to allow users without local administrator permissions to install Microsoft Remote Help ? The Microsoft Remote Help application is featured on Company Portal (app & Web). Users can click "Install", but then they get a UAC credential prompt, asking them for an admin username & password. This is not what is expected from InTune: Another important layer is security. Normally, installing apps would require installation rights, for example, local administrator permissions on your Windows 10 Enterprise endpoint. Delivering your app via Microsoft Endpoint Manager allows you to assign and install apps – in a modular fashion – without the need to make the user a local administrator. [Application delivery via Microsoft Endpoint Manager | Mastering Microsoft Endpoint Manager (packtpub.com)]
