Re: ActiveSync warning

Thanks for the very complete answer. It is possible that I wasn't very clear
with my original question.
AUTD is working in our enterprise. What is more, I have the same device
(treo 700w with Verizon) and it works perfectly for me.
I know also quite well how it works since I spent 2 weeks readying
information on ActiveSync when we starting using the devices 2 years ago
(with Compaq iPaq)
I did a little more digging and the phone number that it shows is from a
previous device that the user had and it is no longer working ( the screen
is broken)
So, in short the binding is wrong on the exchange server.
Last night I found a tool that is probably what I need (BindingCleanup.exe)
called AUTD Binding Cleanup Tool.
When I said probably is because I get an error when I try to run the tool
Search AUTD Binding Error for: davidh
The remote server returned an error: (403) Forbidden.
DAV Protocol Error: The remote server returned an error: (403) Forbidden.
If I had to take a wild guess I would say that is a problem with
permissions, so this is what I have tried.
Run the tool from my workstation and from the server.
I have run it with my local account and with my domain administrator account
(we don't use administrator account, but instead we have our own account
with the domain administrator rights for auditing pourposes).
I have entered in the account to connect the Domain administrator account,
as well as the user account. Both get the same error.
I also run the exchange best practices analyzer. When I am at the setting to
"Connect to Active Directory" at the domain I have to put our pre-2000
domain name. We migrated from NT4 and Exchange 5.5 in June 2004, and with
the migration came a new domain name (the new one is FQDN, the old one is
not).
Right now I found another road block, but I still want to remove that
binding so I don't see that event log entry anymore.

"chace zhang" <v-chacez@xxxxxxxxxxxxx> wrote in message
news:QpnRyRh1GHA.4280@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

Thank you posting here.

According to your description, I understand you encountered following
error
event in Application log:

Event Type: Warning
Event Source: MSExchangeActiveSyncNotify
Event Category: OMA Push Categorizer
Event ID: 10314
Date: 9/11/2006
Time:
User: N/A
Computer: ATHENS
Description:
The Exchange ActiveSync
user 'email address' has specified an invalid SMTP device address
'0409660990' on their device. The user will not be able to receive
up-to-date notifications on their device until the correct SMTP address is
entered on their device. To fix this problem, tell the user to enter the
correct SMTP address on the device and then synchronize the device with
their Exchange server using ActiveSync.

But you have type the correct SMTP address in the specific mobile device.
Is it correct? If I'm off based, please feel free to let me know.

Technical speaking, Always-up-to-date Notifications is a new feature in
Exchange 2003 that permits an always up-to-date user experience with
Pocket
PC. When an event is generated in a user's Exchange account, i.e. a new
email comes in, a notification is sent to the user's device by SMS. The
warning MSExchangeActiveSyncNotify 10314 indicates that there is an
incorrect SMTP address configured in mobile device, which prevents the
Always-Up-To-Date (AUTD) feature in Exchange server to send message to the
mailbox of your mobile provider. Therefore, if you do use the Server
ActiveSync feature in your Exchange 2003 Server to sync data between your
Exchange mailbox and your mobile device (pocket pc), you may have to
correct the SMTP address in your mobile device.

NOTE: You may need to contact your mobile provider to register the AUTD
feature in their mail server. If your mobile service provider offers such
function, you should input correct Device Email Address in the SmartPhone,
normally, it is phonenumber@MOBILEISP. However, the user typed IP or
public
FQDN (may be the IP address of your Exchange Server) on his device that
resulted the issue. You can check device to confirm my assumption.

If the mobile service provider did not provide Always-up-to-date
Notifications service, you can simply disable such feature on the user
account to remove the warning message:

- Open Active Directory Users and Computers.
- Right click the problematic user account and click properties.
- Click Exchange Features tab.
- Highlight Up-to-date Notifications and then click Disable.

In addition, Always-up-to-date Notifications only sends a message to your
mobile ISP, it does not impact mail flow so you can send/receive emails
without a problem.


Hope this helps, if you have any other questions on this issue, please
feel
free to let me know.

Have a nice day!


Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on Exchange technical issues. If you have
issues regarding other Microsoft products, you'd better post in the
corresponding newsgroups so that they can be resolved in an efficient and
timely manner. You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.


--------------------
| From: <davidhc25@xxxxxxxxxxxxxxxx>
| Subject: ActiveSync warning
| Date: Mon, 11 Sep 2006 12:25:29 -0400
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
| X-RFC2646: Format=Flowed; Original
| X-Antivirus: avast! (VPS 0637-0, 09/11/2006), Outbound message
| X-Antivirus-Status: Clean
| Message-ID: <ut#Zg7b1GHA.2176@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.exchange.clients
| NNTP-Posting-Host: 167.21.225.162
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.clients:97062
| X-Tomcat-NG: microsoft.public.exchange.clients
|
| We have a user that tried to use in his pocket pc "Notify of new email
as
| they arrive" in his schedule. We could never get it to work properly,
and
| even on the few devices that it worked, it was slower than having it to
sync
| every 5 minutes.
| Our problem now is that even we changed the schedule in his device (treo
| 700w) we still get this message logged in the exchange
| App: W 'Mon Sep 11 11:34:37 2006': MSExchangeActiveSyncNotify - " The
| Exchange ActiveSync user (email address removed)
| has specified an invalid SMTP device address '(phone number removed) on
| their device. The user will not be able
| to receive up-to-date notifications on their device until the correct
SMTP
| address is entered on their
| device. To fix this problem, tell the user to enter the correct SMTP
address
| on the device and then synchronize
| the device with their Exchange server using ActiveSync. "
| I removed the email address and tel number, but basically that is the
| message. I look it up, but I cannot change the setting in the ppc since
it
| already has the smtp address entered. I would like to remove Exchange
part
| that is trying to use the up-to-date notification. I could not find any
| setting on the exchange server, not anything usefull while searching the
| Internet
|
|
|



.

Relevant Pages

  • [NT] Vulnerability in Exchange Server Allows Remote Code Execution (MS05-021)
    ... A remote code execution vulnerability exists in Microsoft Exchange Server ... their choice in the security context of the SMTP service. ...
    (Securiteam)
  • Re: NDR delivery delayed errors keep coming, any advice?
    ... I tried to send a note to my home account via the telnet commands ... But that in no way afffects mail delivery, ... All e-mails from my Exchange server to yahoo seem to be ... Telnet to Port 25 to Test SMTP Communication ...
    (microsoft.public.windows.server.sbs)
  • RE: Dave Goldman help: rename AD user creates prob w autocomplete Outl
    ... To rename the account I followed the following steps: ... Then I went to the account properties and made sure that the new Display ... her mailbox name in the Mailbox store in Exchange had not ... I rebuilt the Offline Address Book on the Exchange server and redownloaded ...
    (microsoft.public.exchange.admin)
  • Re: Forwarding from Exchange on SBS 2003
    ... POP3 accounts and from my SMTP Exchange account, ... see if the forwarder works as expected or not. ...
    (microsoft.public.exchange.setup)
  • Re: SBS 2003 PDA Sync Problem - Error 0x85010014
    ... this case is a .local address since we are not using exchange to receive ... ACS Computer Services Inc. ... I have deliver the solution that change the SMTP address as the primary ... |> | looking at his account I saw we had also put in an external SMTP ...
    (microsoft.public.backoffice.smallbiz)