search

tabs-not-spaces / Intune.USB.Creator

A module containing tools to assist with the creation of a bootable WinPE USB used to provision devices for enrollment to Intune.
GNU General Public License v3.0
131 stars 43 forks source link

device not provisioning #19

Closed belacs closed 4 years ago

belacs commented 4 years ago

Hello, im hoping you can help me. I ran the tool and chose a autopilot profile when the system boots up and i sign in it says wait while we configure then it sits there for a long time and then gets error "something went wrong. confirm you are using the correct sign-in information and that your organization uses this feature. you can try to do this again or contact your sys admin with error code 80070002. we have A5 licenses, and i can see the device in enrolment manager. when i look at hte event log on the device this is one of the few errors. I have been talking to MS but they have not helped with any actual troubleshooting yet, just listened to them complain for about an hour that using a usb is unusual.

Log Name: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin Source: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider Date: 8/24/2020 1:57:51 PM Event ID: 404 Task Category: None Level: Error Keywords:
User: SYSTEM Computer: DESKTOP-E43PIMM Description: MDM ConfigurationManager: Command failure status. Configuration Source ID: (196EB1CE-94DC-4FA0-9D15-EFEB3A15B8AD), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Receiver/Properties/Policy/FakePolicy/Version), Result: (The system cannot find the file specified.). Event Xml:

404 0 2 0 0 0x8000000000000000 510 Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin DESKTOP-E43PIMM 196EB1CE-94DC-4FA0-9D15-EFEB3A15B8AD MDMDeviceWithAAD Policy 1 ./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Receiver/Properties/Policy/FakePolicy/Version 0x80070002
belacs commented 4 years ago

the other weird thing is i have run the process a few times and it actually adds a new device each time, i did not think that was possible.

belacs commented 4 years ago

i think there is just some thing simple i am missing. tried the whiteglove option and it says "Deployment profile: no profile found" but i chose the profile when i made the usb.

tabs-not-spaces commented 4 years ago

Hey belacs,

Doesn't sound like an issue with the code base, so I'm going to have to close this issue out.

As far as troubleshooting the experience you are having, I'd start by just trying the process of capturing the hardware hash manually first.

Make sure there are no device objects in AAD or Intune with the serial number of your device (it's entirely normal for duplicate objects to appear in Intune - each time you reimage the device it's seen as a new one in the Intune space).

Without knowing how your environment is configured, there's little more I can suggest, as there could be multiple things blocking you from using this "offline autopilot" method.

If you want to discuss further, hit me up on twitter @powers_hell.

On Wed, 26 Aug 2020, 7:19 am belacs, notifications@github.com wrote:

i think there is just some thing simple i am missing. tried the whiteglove option and it says "Deployment profile: no profile found" but i chose the profile when i made the usb.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/Intune.USB.Creator/issues/19#issuecomment-680275525, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LIH7KQ2T6MKWWZYE2DSCQTHHANCNFSM4QK73ORA .

belacs commented 4 years ago

i understand. thanks for the info and this tool! :)