Passcode issue with Windows phones

Hello John,

Thanks for getting in touch.

Could you please let us know what Windows Mobile versions are affected, the version of the OS they're running, what updates are applied, what Sophos Mobile versions are installed, does the issue no return after wiping and re-enrolling? What about new devices that are fully updated then setup, do they suffer the same issue?

Hi Toby

The devices are Lumia 650s and Lumia 640s

The firmware versions are

WM 10.0.15063.674
WM 10.0.15063.540
WM 10.0.15063.483
WM 10.0.15063.608
WM 10.0.15063.297
WM 10.0.15254.1
WM 10.0.15063.414

The Control apps are

7.0.30.0
6.1.1160

The first date detected was 06/10/2017

If a device is wiped and re-enrolled they seem OK

Un-enrolling a device and re-enrolling does not seem to work 

Devices that are compliant do not have the option to remove the pin but ones that have become non-compliant do have the option to remove the pin

When built the policy accepts a simple pin ie 1234 but once they go non-compliant this type of pin is now not acceptable

Not all devices have gone non-compliant, however more are failing each day.

Hope this helps

John

Hi,

phone that I wiped and re-added yesterday has just failed again, only thing I did was accept "Windows Hello" though the phone does say it does not support it.

It did ask for the pin at this point.

John

Hi everyone,

this issue should be solved following this knowledgebase article.

Best regards
Stefan

Stefan,

applied the patch and changed the password profile and synced as recommended, the volume of non compliant phones dropped from 286 down to 112 but they are beginning to go non compliant again now up to 187 Any ideas?

John

Hi John,

is the compliance violation again stating that the device has no passcode configured?

Best regards

Stefan

Stefan,

Yes correct it is stating that no passcode is present. I am just wiping one phone and re-enrolling it to see if it stays OK but with 188 now reporting in as non-compliant I would prefer not to have to do this for all devices

Update, the wiped and re-enrolled device is at the moment all OK, just have to wait now to see if it stays OK

John

Hi John,

have you changed anything within your policies in the meantime which could have lead to that behavior?

Can you please raise a support case referencing to this communication thread and get the case escalated for further analysis?

Best regards

Stefan

To keep everyone updated this is the current position from support

"I'm happy announce this problem has been addressed in Sophos Mobile 7.1.6 - this is currently being tested for global availability, I'll let you know the moment this becomes available to you."

John

To keep everyone updated this is the current position from support

"I'm happy announce this problem has been addressed in Sophos Mobile 7.1.6 - this is currently being tested for global availability, I'll let you know the moment this becomes available to you."

John