Removing the Default Activsync Policy
We are Running Exchange 2007 SP1 w/rollup9 on a Win2008 Enterprise OS.
Having an issue with several users running Palm 755P mobile devices. The Palm device with VersaMail fails with the error: AirSAMStateMachine.c 1913 4628. All other mobile devices working without issue.
Google searches suggest the removal of the DEFAULT ActiveSyncMailboxPolicy via PowerShell command:
Remove-ActiveSyncMailboxPolicy - idenity "Default".
Some searches state that remote wipe ability will be lost if the default policy is removed.
Can the "Default" ActiveSyncMailboxPolicy policy be safely removed and for that matter restored without affecting other mobile device users? Is there a any corrective actions that can be done from the server side? The only solution suggested by the mobile vendor is to remove the default policy.
Reference: http://episteme.arstechnica.com/eve/forums/a/tpc/f/579009962631/m/417009683931
Thanks,
Joe
Answers
The steps in my last post is the typical procedure to test the ActiveSync function on the exchange server, since you have passed all the test, and the issue only happens to Palm Smartphone. I would suggest you to contact Palm Support, which would be the most efficient way to seek the resolution
- Proposed As Answer byJames-LuoMSFT, ModeratorFriday, October 09, 2009 1:27 AM
- Marked As Answer byJames-LuoMSFT, ModeratorMonday, October 12, 2009 12:59 AM
All Replies
Please check the HTTP compression of static content and dynamic content on the “Microsoft-Server-ActiveSync” virtual directory, and check the issue after disable them
- Any update on this issue?
- sorry, we just asked the user with the Tre to sync and it still fails.
Thank you for the suggestion James.
Any other ideas?
Joe Please verify the functionality of ActiveSync:
1. Please check “Microsoft-Server-ActiveSync” virtual directory
a. Launch IIS
b. “Microsoft-Server-ActiveSync”>Directory Security> Authentication and access control
c. Please make sure “Basic authentication” is checked and “enable anonymous access” is unchecked
d. Then right-click the virtual directory and select Browse, the expected behavior should be “ 501/505” error
2. Please test the configuration of Microsoft Exchange ActiveSync
a. Launch EMS
b. Test-ActiveSyncConnectivity -MailboxCredential (Get-Credential domain\username)
c. Enter the user name and password in the jumped window
d. Check the output
3. Please to test Remote Connectivity Analyzer the ActiveSync with problematic user account
Please also run ExBPA for a health check on exchange
- Proposed As Answer byJames-LuoMSFT, ModeratorThursday, October 08, 2009 1:00 AM
- Any update?
Sorry for the slow response as I was out of town for the past week.
All tests pass for activesync.
Activesync works on all other smartphone devices except for the Palms running versamail 3.5
Since the original issue we have found one other user with the same Palm device and same error.
This problem only happens on devices using versamail 3.5
JoeThe steps in my last post is the typical procedure to test the ActiveSync function on the exchange server, since you have passed all the test, and the issue only happens to Palm Smartphone. I would suggest you to contact Palm Support, which would be the most efficient way to seek the resolution
- Proposed As Answer byJames-LuoMSFT, ModeratorFriday, October 09, 2009 1:27 AM
- Marked As Answer byJames-LuoMSFT, ModeratorMonday, October 12, 2009 12:59 AM
We are Running Exchange 2007 SP1 w/rollup9 on a Win2008 Enterprise OS.
Having an issue with several users running Palm 755P mobile devices. The Palm device with VersaMail fails with the error: AirSAMStateMachine.c 1913 4628. All other mobile devices working without issue.
Google searches suggest the removal of the DEFAULT ActiveSyncMailboxPolicy via PowerShell command:
Remove-ActiveSyncMailboxPolicy - idenity "Default".
Some searches state that remote wipe ability will be lost if the default policy is removed.
Can the "Default" ActiveSyncMailboxPolicy policy be safely removed and for that matter restored without affecting other mobile device users? Is there a any corrective actions that can be done from the server side? The only solution suggested by the mobile vendor is to remove the default policy.
Reference: http://episteme.arstechnica.com/eve/forums/a/tpc/f/579009962631/m/417009683931
Thanks,
Joe
I can confirm that running the remove-activesyncmailboxpolicy cmd will allow treo's and older win mobile devices to work.
JP
