SOLVED

Android Enterprise (Device Owner) profile delivery

%3CLINGO-SUB%20id%3D%22lingo-sub-992098%22%20slang%3D%22en-US%22%3EAndroid%20Enterprise%20(Device%20Owner)%20profile%20delivery%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-992098%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20anyone%20else%20experiencing%20issues%20with%20Device%20Owner%20SCEP%20and%20WiFi%20profile%20delivery%3F%20It's%20failing%20for%20newly%20enrolled%20devices%20as%20of%20this%20week%2C%20but%20was%20being%20delivered%20successfully%20previously.%3C%2FP%3E%3CP%3EState%20Details%3A%200%20(No%20error%20code)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-992098%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAndroid%20Enterprise%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDevice%20Owner%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESCEP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-993021%22%20slang%3D%22en-US%22%3ERe%3A%20Android%20Enterprise%20(Device%20Owner)%20profile%20delivery%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-993021%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F254026%22%20target%3D%22_blank%22%3E%40eglockling%3C%2FA%3E%26nbsp%3BWhilst%20I%20don't%20specifically%20have%20that%20issue%2C%20I%20have%202%20customers%20who%20have%20experienced%20delays%20in%20policies%20being%20applied%20this%20week.%20Also%20some%20which%20seem%20to%20error%20on%20device%20registration%2C%20but%20wait%205%20minutes%20and%20it%20works.%20Feels%20like%20a%20slow%20down%20this%20week%20-%20I%20blame%20Ignite%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-993085%22%20slang%3D%22en-US%22%3ERe%3A%20Android%20Enterprise%20(Device%20Owner)%20profile%20delivery%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-993085%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F293080%22%20target%3D%22_blank%22%3E%40PeterEgerton%3C%2FA%3EThanks%20for%20the%20feedback.%20Unfortunately%2C%20it%20seems%20to%20be%20an%20issue%20with%20SCEP%20profile%20delivery%20again.%20We've%20allowed%2024-48%20hours%2C%20but%20the%20delivery%20continues%20to%20fail.%20The%20restrictions%20and%20root%20certificate%20profile%20delivery%20is%20working%20as%20expected.%20Luckily%2C%20Apple%20devices%20are%20receiving%20SCEP%20profiles%20and%20requesting%20SCEP%20certs%20successfully.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1002306%22%20slang%3D%22en-US%22%3ERe%3A%20Android%20Enterprise%20(Device%20Owner)%20profile%20delivery%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1002306%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20everything%20is%20resolved%20now.%20It%20was%20related%20to%20last%20week's%20change%20by%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ERoot%20cause%3A%20A%20recent%20service%20update%2C%20designed%20to%20improve%20the%20overall%20experience%20of%20the%20environment%2C%20caused%20a%20code%20regression.%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

Is anyone else experiencing issues with Device Owner SCEP and WiFi profile delivery? It's failing for newly enrolled devices as of this week, but was being delivered successfully previously.

State Details: 0 (No error code)

3 Replies

@eglockling Whilst I don't specifically have that issue, I have 2 customers who have experienced delays in policies being applied this week. Also some which seem to error on device registration, but wait 5 minutes and it works. Feels like a slow down this week - I blame Ignite :)

@PeterEgertonThanks for the feedback. Unfortunately, it seems to be an issue with SCEP profile delivery again. We've allowed 24-48 hours, but the delivery continues to fail. The restrictions and root certificate profile delivery is working as expected. Luckily, Apple devices are receiving SCEP profiles and requesting SCEP certs successfully.

Best Response confirmed by eglockling (Frequent Contributor)
Solution

Looks like everything is resolved now. It was related to last week's change by Microsoft.

 

Root cause: A recent service update, designed to improve the overall experience of the environment, caused a code regression.