Possible OT: Palm Treo 755 and Active Sync (Exchange 2007 SP1 on SBS2008)

Good evening!

We have a client who just moved from SBS2003 | Exchange 2003 SP2 to SBS2008
| Exchange 2007 SP1.

Lots of Blackberry devices, a sprinkling of Palm devices. BlackBerry
devices are not a problem (already handled the sole issue...). Palm
devices, however, are simply not working. Giving us the SAMStateMachine.c
1913 4628 error.

Lots of looking (google has been my best friend lately) shows me that the
solution is to remove the sole ActiveSync Mailbox Policy using the
remove-ActiveSyncMailboxPolicy cmdlet. Then, everything supposedly works
just swell.

I am hesitant to do this.

Anyone see any issues doing this?

Cary

As of Exchange 2007 SP1, a default policy is *REQUIRED.* The default, out
of the box policy, however, should not be causing device connection issues.
This leads me to believe that a policy is in place with non-standard
settings, and usually if that exists then there is a reason for it. I'd be
reluctant to yank a policy without knowing what I'm yanking.

A little time reviewing the policy settings is in order...

http://technet.microsoft.com/en-us/l.../bb123484.aspx

Since this is a SAM error, I'd guess one or more of the devices/accounts
doesn't conform to security settings in place. Usually better to make the
device or user account conform (complex passwords, etc) than to change
security settings. After all, activesync by definition is exposed to the big
bad world...

-Cliff


"Cary Shultz" <> wrote in message
news:#...
> Good evening!
>
> We have a client who just moved from SBS2003 | Exchange 2003 SP2 to
> SBS2008 | Exchange 2007 SP1.
>
> Lots of Blackberry devices, a sprinkling of Palm devices. BlackBerry
> devices are not a problem (already handled the sole issue...). Palm
> devices, however, are simply not working. Giving us the SAMStateMachine.c
> 1913 4628 error.
>
> Lots of looking (google has been my best friend lately) shows me that the
> solution is to remove the sole ActiveSync Mailbox Policy using the
> remove-ActiveSyncMailboxPolicy cmdlet. Then, everything supposedly works
> just swell.
>
> I am hesitant to do this.
>
> Anyone see any issues doing this?
>
> Cary

Hello Cary,

Thanks for your post and Cliff's input.

I agree that it's better to understand what is the Exchange ActiveSync Mailbox Policies as well as what Exchange ActiveSync Cmdlets will do before trying the suggestions. I
have not ever used the remove-ActiveSyncMailboxPolicy cmdlet, but before you try the power shell command, I think it's easy to do some tests to determine if this is caused
by the Server side or the mobile device side. The following web tool may helps to find the root cause:

Using the Exchange Server Remote Connectivity Analyzer Tool (Part 2)
http://www.msexchange.org/articles_t...ool-part2.html

Here is the tool:
https://www.testexchangeconnectivity.com/Default.aspx


More information:

Managing Exchange ActiveSync Devices
http://technet.microsoft.com/en-us/l.../aa998933.aspx

How to Configure Mobile Devices to Synchronize with Exchange Server
http://technet.microsoft.com/en-us/l.../bb123704.aspx

DEPLOYMENT GUIDE - WINDOWS SBS 2008 with WINDOWS MOBILE 6
http://www.microsoft.com/downloads/d...displaylang=en

Hope this helps.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

================================================== ================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/...i/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/...i/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
================================================== ================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ================
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ================

Good morning, Cliff!

I appreciate your reply. As stated, I am a bit reluctant to yank the sole
EAS policy for exactly the reason that you stated (is required).

The policy is the default...nothing has been added to or removed removed
from the policy. From everything that I have read (please see the below
links) it points to Palm Treo's having issues with EXCH2007 SP1....

http://forums.palm.com/palm/board/me...essage.id=3272
http://ehlotech.blogspot.com/2009/01...lating-to.html
http://technet.microsoft.com/en-us/l.../cc182294.aspx
http://social.technet.microsoft.com/...1-3a3956794225

It seems like lots of people have spent lots of time trying to get this
issue resolved and *nothing* worked short of removing the policy. I really
do not like that "solution".

Anyway, I am going to test using the tools that Robbin so kindly posted.

And, not sure if I mentioned this or not in the original post...when we
"test" from the device it works. However, when we do for real it fails.
Only these two devices (both Palm Treo 755s) are having issues.

Anyway, I will review the settings [yet again! I think that this will be
number 17...not that I am counting! ;-)] and move forward with the testing
per Robbin's suggestion.

Thanks - as always!

Cary

"Cliff Galiher" <> wrote in message
news:...
> As of Exchange 2007 SP1, a default policy is *REQUIRED.* The default,
> out of the box policy, however, should not be causing device connection
> issues. This leads me to believe that a policy is in place with
> non-standard settings, and usually if that exists then there is a reason
> for it. I'd be reluctant to yank a policy without knowing what I'm
> yanking.
>
> A little time reviewing the policy settings is in order...
>
> http://technet.microsoft.com/en-us/l.../bb123484.aspx
>
> Since this is a SAM error, I'd guess one or more of the devices/accounts
> doesn't conform to security settings in place. Usually better to make the
> device or user account conform (complex passwords, etc) than to change
> security settings. After all, activesync by definition is exposed to the
> big bad world...
>
> -Cliff
>
>
> "Cary Shultz" <> wrote in message
> news:#...
>> Good evening!
>>
>> We have a client who just moved from SBS2003 | Exchange 2003 SP2 to
>> SBS2008 | Exchange 2007 SP1.
>>
>> Lots of Blackberry devices, a sprinkling of Palm devices. BlackBerry
>> devices are not a problem (already handled the sole issue...). Palm
>> devices, however, are simply not working. Giving us the
>> SAMStateMachine.c 1913 4628 error.
>>
>> Lots of looking (google has been my best friend lately) shows me that the
>> solution is to remove the sole ActiveSync Mailbox Policy using the
>> remove-ActiveSyncMailboxPolicy cmdlet. Then, everything supposedly works
>> just swell.
>>
>> I am hesitant to do this.
>>
>> Anyone see any issues doing this?
>>
>> Cary
>

I tested with three different user accounts and the EAS and Autodiscover
(shoot...all of them) test out at 100% successful.

""Robbin Meng [MSFT]"" <v-> wrote in message
news:...
>
>
> Hello Cary,
>
> Thanks for your post and Cliff's input.
>
> I agree that it's better to understand what is the Exchange ActiveSync
> Mailbox Policies as well as what Exchange ActiveSync Cmdlets will do
> before trying the suggestions. I
> have not ever used the remove-ActiveSyncMailboxPolicy cmdlet, but before
> you try the power shell command, I think it's easy to do some tests to
> determine if this is caused
> by the Server side or the mobile device side. The following web tool may
> helps to find the root cause:
>
> Using the Exchange Server Remote Connectivity Analyzer Tool (Part 2)
> http://www.msexchange.org/articles_t...ool-part2.html
>
> Here is the tool:
> https://www.testexchangeconnectivity.com/Default.aspx
>
>
> More information:
>
> Managing Exchange ActiveSync Devices
> http://technet.microsoft.com/en-us/l.../aa998933.aspx
>
> How to Configure Mobile Devices to Synchronize with Exchange Server
> http://technet.microsoft.com/en-us/l.../bb123704.aspx
>
> DEPLOYMENT GUIDE - WINDOWS SBS 2008 with WINDOWS MOBILE 6
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Hope this helps.
>
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
> ================================================== ================
> Please post your SBS 2008 related questions to the SBS newsgroup on
> Connect website:
> https://connect.microsoft.com/sbs08/...i/default.aspx
>
> Please post your EBS related questions to the EBS newsgroup on Connect
> website:
> https://connect.microsoft.com/ebs08/...i/default.aspx
>
> If you want to use a newsreader other than a web forum to access these
> newsgroups,
> please refer to the following blog to apply NNTP password and configure a
> newsreader:
> http://msmvps.com/blogs/bradley/arch...ewsgroups.aspx
> ================================================== ================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ================================================== ================
>
>
>

"Cary Shultz" <> wrote in message
news:...
>I tested with three different user accounts and the EAS and Autodiscover
>(shoot...all of them) test out at 100% successful.
>

Cary,

How's it going?

What kind of cert is on the machine? Is Forms enabled? For one customer on a
2003 box with Forms, and a single name SSL cert, I had to create a separate
ActiveSync (Exchange_OMA) sub web to make it work for the ActiveSync device.
Not sure if this is related, but thought I would throw something else in
your bag of stuff to look at. I know, I know, it's for 2003, but just wanted
to bring it to your attention.

Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or
forms-based authentication is required for Exchange Server 2003
http://support.microsoft.com/kb/817379

On another note, I had a similar issue with a friend's 2007 SP2 system and
some off the wall phone that he bought because he said it looked nice.
(Bah!) I think it was an LG or Sanyo phone, can't remember now since it has
been a few months. The phone was supposed to (according to their site, docs,
etc), be able to pull Exchange mail using OWA functions. Boy was that a PITA
to work on. I followed some of the folks' responses that did get it to work
messing with various Forms and other settings, but finally gave up after an
hour+ telling him I do not feel comfortable making all of these changes,
especially when your current Windows Mobile ActiveSync and Blackberry phones
(set to use OWA method) worked fine. It told him to dump the phone and get a
real Windows phone. He didn't like that!

Back to the Palm, I had a bunch of old Palms (Palm softward - 700s I think?)
working two years ago at another company with Ex2003, but since you are on
2007, it's different. If the Exchange test site comes back clean, then it
tells me it's something in the Palms.

If you need to get the phones to work by removing the policy, then you're
going to neeed to remove it. Just take notes on the policy so when you
replace it with a new one, it will be easier to set up again.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Good afternoon, Ace!

Really do not want to remove the policy. All of the other phones are
working just swell...just not these two.

I have spent more like four hours on this (I like to be thorough so that
when it is time to throw in the towel I know that I put the kitchen sink in
beforehand). Looks like the client is going to get new phones....these are
rather old (whatever that means, right?).

And, good call on the OMA|FBA thing.....but I already thought of that! No
joy there! But, good call!

We just moved (SBS2003 to SBS2008 in Migration Mode...that works S W E E E E
E E T!) from SBS2003 to SBS2008...there were no issues before the move.

UCC/SAN Cert with all of the names (and then some) with mail.mydomain.com as
the CN. And, done the proper way (considering that this is SBS2008...I do
not want any of the SBS MVPs cursing me for doing it the "normal" Windows
way...would that even work?).....created the csr via the "wizard" and
imported | installed via the "wizard. Funny how things just work when you
do it the right way!

Well, this is not working. Not yet. Pretty sure that the client will get
two new phones...

Will keep you all updated....

Thanks all from beautiful Roanoke, VA (SW Virginia)


"Ace Fekay [MCT]" <> wrote in message
news:%...
> "Cary Shultz" <> wrote in message
> news:...
>>I tested with three different user accounts and the EAS and Autodiscover
>>(shoot...all of them) test out at 100% successful.
>>
>
> Cary,
>
> How's it going?
>
> What kind of cert is on the machine? Is Forms enabled? For one customer on
> a 2003 box with Forms, and a single name SSL cert, I had to create a
> separate ActiveSync (Exchange_OMA) sub web to make it work for the
> ActiveSync device. Not sure if this is related, but thought I would throw
> something else in your bag of stuff to look at. I know, I know, it's for
> 2003, but just wanted to bring it to your attention.
>
> Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or
> forms-based authentication is required for Exchange Server 2003
> http://support.microsoft.com/kb/817379
>
> On another note, I had a similar issue with a friend's 2007 SP2 system and
> some off the wall phone that he bought because he said it looked nice.
> (Bah!) I think it was an LG or Sanyo phone, can't remember now since it
> has been a few months. The phone was supposed to (according to their site,
> docs, etc), be able to pull Exchange mail using OWA functions. Boy was
> that a PITA to work on. I followed some of the folks' responses that did
> get it to work messing with various Forms and other settings, but finally
> gave up after an hour+ telling him I do not feel comfortable making all of
> these changes, especially when your current Windows Mobile ActiveSync and
> Blackberry phones (set to use OWA method) worked fine. It told him to dump
> the phone and get a real Windows phone. He didn't like that!
>
> Back to the Palm, I had a bunch of old Palms (Palm softward - 700s I
> think?) working two years ago at another company with Ex2003, but since
> you are on 2007, it's different. If the Exchange test site comes back
> clean, then it tells me it's something in the Palms.
>
> If you need to get the phones to work by removing the policy, then you're
> going to neeed to remove it. Just take notes on the policy so when you
> replace it with a new one, it will be easier to set up again.
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>

"Cary Shultz" <> wrote in message
news:...
> Good afternoon, Ace!
>
> Really do not want to remove the policy. All of the other phones are
> working just swell...just not these two.
>
> I have spent more like four hours on this (I like to be thorough so that
> when it is time to throw in the towel I know that I put the kitchen sink
> in beforehand). Looks like the client is going to get new phones....these
> are rather old (whatever that means, right?).
>
> And, good call on the OMA|FBA thing.....but I already thought of that! No
> joy there! But, good call!
>
> We just moved (SBS2003 to SBS2008 in Migration Mode...that works S W E E E
> E E E T!) from SBS2003 to SBS2008...there were no issues before the move.
>
> UCC/SAN Cert with all of the names (and then some) with mail.mydomain.com
> as the CN. And, done the proper way (considering that this is SBS2008...I
> do not want any of the SBS MVPs cursing me for doing it the "normal"
> Windows way...would that even work?).....created the csr via the "wizard"
> and imported | installed via the "wizard. Funny how things just work when
> you do it the right way!
>
> Well, this is not working. Not yet. Pretty sure that the client will
> get two new phones...
>
> Will keep you all updated....
>
> Thanks all from beautiful Roanoke, VA (SW Virginia)

Good choice not to recreate the policy, especially if it's only for these
two phones that don't work. Sounds like you've did a lot of research. I'd
give up too, especially if the other phones are working. Time for new
phones!!

Ace

Boss man there decided to get new phones. The owner of the company (read:
client) is a true pleasure to "work for" and I really try to go the extra
mile for him. I have thrown in the towel at this point...but you betcha
that I threw in the kitchen sink before doing that! ;-)

I probably spent way too much time on this issue but wanted to make sure
that there was no stone left unturned.

Anyway, new phones are on order....Case closed (well, I still hate not
"fixing it"). But, not everything can be fixed.

Yak with you later....

Cary

"Ace Fekay [MCT]" <> wrote in message
news:%...
> "Cary Shultz" <> wrote in message
> news:...
>> Good afternoon, Ace!
>>
>> Really do not want to remove the policy. All of the other phones are
>> working just swell...just not these two.
>>
>> I have spent more like four hours on this (I like to be thorough so that
>> when it is time to throw in the towel I know that I put the kitchen sink
>> in beforehand). Looks like the client is going to get new
>> phones....these are rather old (whatever that means, right?).
>>
>> And, good call on the OMA|FBA thing.....but I already thought of that!
>> No joy there! But, good call!
>>
>> We just moved (SBS2003 to SBS2008 in Migration Mode...that works S W E E
>> E E E E T!) from SBS2003 to SBS2008...there were no issues before the
>> move.
>>
>> UCC/SAN Cert with all of the names (and then some) with mail.mydomain.com
>> as the CN. And, done the proper way (considering that this is
>> SBS2008...I do not want any of the SBS MVPs cursing me for doing it the
>> "normal" Windows way...would that even work?).....created the csr via the
>> "wizard" and imported | installed via the "wizard. Funny how things just
>> work when you do it the right way!
>>
>> Well, this is not working. Not yet. Pretty sure that the client will
>> get two new phones...
>>
>> Will keep you all updated....
>>
>> Thanks all from beautiful Roanoke, VA (SW Virginia)
>
> Good choice not to recreate the policy, especially if it's only for these
> two phones that don't work. Sounds like you've did a lot of research. I'd
> give up too, especially if the other phones are working. Time for new
> phones!!
>
> Ace
>
>
>

"Cary Shultz" <> wrote in message
news:...
> Boss man there decided to get new phones. The owner of the company (read:
> client) is a true pleasure to "work for" and I really try to go the extra
> mile for him. I have thrown in the towel at this point...but you betcha
> that I threw in the kitchen sink before doing that! ;-)
>
> I probably spent way too much time on this issue but wanted to make sure
> that there was no stone left unturned.
>
> Anyway, new phones are on order....Case closed (well, I still hate not
> "fixing it"). But, not everything can be fixed.
>
> Yak with you later....
>
> Cary

That's true, not everything can be fixed! At least you gave it your all!!

Ace