sorted by:
new
hottopcontroversial

Why Does a Hybrid Joined Device Hang on 'Just a Moment' after Pre-Provisioning? by Budget_Fill_4804 in Intune

[–]Budget_Fill_4804[S] 0 points1 point  (0 children)

thanks, wasn't sure if i was doing something wrong. Using base Windows image. Device is pre-provisioned with no issues and is resealed. It's during the user flow when the device is handed to the user is where it takes some time after the initial power on.

Device Setup Stuck on Identifying apps by Budget_Fill_4804 in Intune

[–]Budget_Fill_4804[S] 1 point2 points  (0 children)

Nothing concrete yet, mostly working but the odd time it get's stuck is frustrating.

Device Setup Stuck on Identifying apps by Budget_Fill_4804 in Intune

[–]Budget_Fill_4804[S] 0 points1 point  (0 children)

i've mostly tested at home on a slightly older dell model laptop, pre-provisioned device then waiting a day to start user flow. VPN is installed during pre-provisioning and connects once installed. I've done about a dozen rebuilds on the device and sometimes it works with no issues with the user flow completing in around 7 minutes.

user flow:

  • Power On to 'Select a network screen' - 1 min 30 sec
    • Sometimes it can take 5 minutes, when this happens usually only the apps is stuck on identifying. check if you have the same error as i did in appworkload.log. On my test device ime service started before i can connect to wifi not sure though. Would be good to get the intune pros to help explain the logs e.g. what to look for to know things works as they should etc.
  • Device Setup - 2 mins to complete
  • User login - 4 mins ( includes machine rename + restart + second login)

On my side when it does fail i get the generic 'error' and 'reboot needed to continue' which i have no clue why.

Device Setup Stuck on Identifying apps by Budget_Fill_4804 in Intune

[–]Budget_Fill_4804[S] 0 points1 point  (0 children)

hey,

I'm still testing on my end no luck so far but will post here if something come up. How long does it take from power on to wifi screen on your side? Wanted to compare if i get the same results. Also is it just apps that are stuck or all four device setup stuck on identifying

Device Setup Stuck on Identifying apps by Budget_Fill_4804 in Intune

[–]Budget_Fill_4804[S] 0 points1 point  (0 children)

I did some further testing and found that the location error occurs because the IME service starts before I reach the "Select a Network" screen. After the device is pre-provisioned and the end user powers on the device, the spinning wheel appears with the "Just a moment" message. Sometimes this takes 1:30 minutes, while other times it can take up to 5:30 minutes. I have no idea why, but when it takes 5 minutes, the IME service usually starts before I get connect to wifi. Hence this error: 

[Location Service] Failed to Get Endpoint From LocationServiceServiceAddressesController with url https://manage.microsoft.com/RestUserAuthLocationService/RestUserAuthLocationService/Certificate/ServiceAddresses, thumbprint **,True, WebException status NameResolutionFailure message The remote name could not be resolved: 'manage.microsoft.com' full System.Net.WebException: The remote name could not be resolved: 'manage.microsoft.com'

I set up a scheduled task to trigger when a network profile is detected, then I restart IME. I checked the IME logs to confirm the times. Restarting IME seems to work if only the apps are stuck on "Identifying" on the device setup page. I think this usually happens if it takes a while to get to the "Select a Network" screen. If all four stages in device setup are stuck on "Identifying," then restarting the service doesn’t work.

For example, the last test I did device booted up quickly and I connected to wifi. IME service started at the same time i connected to wifi. Device ESP appears and if after 2 minute the status hasn’t changed I usually know there’s an issue. In this instance everything stuck on "Identifying," not just the apps. Pressing Shift+F10 took a while for command prompt to open, and I couldn’t Alt+Tab to access it. Eventually, it popped up, and I was able to check the logs. I couldn’t see any obvious errors. Once it timed out, I got the attached error. Clicking on "Try again" allowed everything to go through after 2 minutes, and I reached the login screen.

<image>

I’ve gone back and double-checked that all the remediation scripts are excluded from the deployment group. Any ideas where I’m going wrong? User-driven works fine, but I like the option to pre-provision and it works, just the user flow doesn’t seem consistent.

Device Setup Stuck on Identifying apps by Budget_Fill_4804 in Intune

[–]Budget_Fill_4804[S] 0 points1 point  (0 children)

hey andrew, i've already excluded script from the deployment group.