Let me start by saying I used to carry 3 phones around all the time. 1 personal, and 2 are for work. I have gotten rid of 1 work phone, mostly, thanks to Google Voice. The other work phone i could not ditch because the Sprint Hero doesnt support EAS (or so i thought). Here's the weird part ....
My companies EAS policy is as follows,
1) The phone must be password protected. That password must be a strong password which would include, atleast 8 digits long, must contain uppercase, must contain lowercase, must contain a number, must contain 1 symbol/character.
- The Hero does not have a password setting (that im aware of). It has a pattern setting ...
2) The phone must time itsself out after a maximum of 30 minutes of not being used and require the strong password to be entered.
- Again because the Hero uses a pattern and not a password, it does not meet this rule
3)Phone must support remote wipe (kill pill) in the event of company termination or lost phone.
- Hero does not support this function.
Because of all the stuff listed above, my company has avoided Android devices until proper EAS support is included. With that in mind, I never tried setting it up on on my companys server. Just for S's and G's i decided to give it a go the other day just to see what would happen and wouldn't you know it .... IT WORKS!!!!!
I am able to; get mail (all folders), Delete mail, accept meeting requests (cant send response), sync calendar, sync contacts, and access the company directory. The major downfall is I cannot send emails which is apparently a known issue thats addressed in 2.x
I called one of my friends in Windows Server Engineering just to see if the policy had been changed and it hadn't. When i showed him my device was android, not password protected, and he couldn't remotely wipe it (yes, we tried lol) he was baffled. Luckly he's my boy and he's not going to say a word but we has stunned and the only thing he could figure was the Hero was somehow spoofing these functions which allowed it to communicate with the server.
Anyway if you've been avoiding setting your Sprint Hero up on EAS I say give it a try, you might be surprised!!
My companies EAS policy is as follows,
1) The phone must be password protected. That password must be a strong password which would include, atleast 8 digits long, must contain uppercase, must contain lowercase, must contain a number, must contain 1 symbol/character.
- The Hero does not have a password setting (that im aware of). It has a pattern setting ...
2) The phone must time itsself out after a maximum of 30 minutes of not being used and require the strong password to be entered.
- Again because the Hero uses a pattern and not a password, it does not meet this rule
3)Phone must support remote wipe (kill pill) in the event of company termination or lost phone.
- Hero does not support this function.
Because of all the stuff listed above, my company has avoided Android devices until proper EAS support is included. With that in mind, I never tried setting it up on on my companys server. Just for S's and G's i decided to give it a go the other day just to see what would happen and wouldn't you know it .... IT WORKS!!!!!
I am able to; get mail (all folders), Delete mail, accept meeting requests (cant send response), sync calendar, sync contacts, and access the company directory. The major downfall is I cannot send emails which is apparently a known issue thats addressed in 2.x
I called one of my friends in Windows Server Engineering just to see if the policy had been changed and it hadn't. When i showed him my device was android, not password protected, and he couldn't remotely wipe it (yes, we tried lol) he was baffled. Luckly he's my boy and he's not going to say a word but we has stunned and the only thing he could figure was the Hero was somehow spoofing these functions which allowed it to communicate with the server.
Anyway if you've been avoiding setting your Sprint Hero up on EAS I say give it a try, you might be surprised!!
Facebook
Twitter
Instagram