Exchange 2003 legacy server

Hi
We have 2010 exch currently and would like to upgrade to 2013.
before proceeding I have a question about exch 2003.
when exch 2003 was removed and decommissioned its not entirely gone yet we still see exch 2003 exists in organisation and we want to total remove this now.
can you please assist or suggest something please. thank you.
p.s. we currently decommissioning exch 2007 as well.
regards
KB

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Similar Messages

  • Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

    Hi,
    I'm trying to resolve an issue.  We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010.  We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
    off this server and onto the Exchange 2010 environment.
    The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
    for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010).  The TO address is in the format of [email protected]  Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
    email, because one of our send connectors has, as address space, *.domain.corp.  However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
    also is an SMTP server.  I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
    the mail, processes it and then saves it to a file somewhere.
    We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server.  Any help troubleshooting this issue is appreciated.

    The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server.  You
    should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 MBX with a Exchange 2003 Frontend server. Coexist?

    We currently have a exchange 2003 environment with 5 mailbox server and 1 front end server. We would like to introduce a 2010 Exchange MBX server. Is that possible? Do we just install the MBX role with CAS/HT? 
    Thnaks, 

    Hi 
    You need to have MBX,CAS and HUB all the three in Exchange 2010 else they wont be functioning without any one of them.
    You can introduce Exchange 2010 server in Exchange 2003 server environment 
    Ensure you have at-least Exchange server 2003 SP2 else the it wont allow you to install Exchange 2010 
    You can only deploy Exchange 2010 in an Exchange 2003 organization that operates in native mode
    Below article for your reference 
    http://technet.microsoft.com/en-us/library/aa998604(v=exchg.141).aspx
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
    Regards,
    Sathish

  • SAP to Exchange 2003 Mail Server

    Hi,
    We have upgraded our exchange servers to 2003 but when  I point SCOT at the new SMTP node I am getting an error message on a couple of lines inthe trace:
    <b>[email protected] 806
    806=501 5.5.4 Invalid Address</b>when I look in SOST.
    I can telnet onto the exchange server from I-series without problem.
    Is there any difference in set up for an Exchange 2003 server from SAP ? We can use SMTP to this server from non-SAP.
    Many Thanks
    David

    Hi David,
    We configured SMTP on WAS 6.40 based on Note 455140 long time ago. When the exchanged server was upgraded to 2003, we simply changed the hostname in SCOT, just like what you did, and it worked.
    Note 751332 says that kernel upgrade is needed to a similar message, but it was very low patch level.
    One time I reconfigured the whole thing to fix an issue I don't remember now... Or make the new node look like original one by keeping same hostname/IP address?
    Good luck,
    Victor

  • Exchange 2003, SBS Server, Outlook 2010, User Over Limit, 2 GIgs

    I have a user's who's account is over limit. I have recently done a clean install of Windows 7 Professional and Office 2010. I keep trying to have his computer archive old emails but in the process the machine keeps hanging. I try to crash out Outlook
    but the outlook.exe process will not let me shut it down telling me access denied. The only way to recover is to completely shut down the computer (which I cannot do VIA the regular shutdown option because of outlook hanging). What do I have to do to resolve
    this problem? Kind of urgent as it's affecting his receiving emails.
    Vern

    Hello,
    According to your description, the issue seems to be related to outlook profile or your PC. I recommend you check if the issue occurs when other users use the PC. If the issue doesn't occurs, it means your outlook profile should be problem.
    If the issue persists, please check if there is related error in application log.
    If there is any update, please free let me know.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Legacy integration between Exchange 2003 and Exchange 2010

    Dear Team,
    we are using Microsoft Exchange 2003 & 2010 Server for Emails, now we have both servers are connected, we want to raise new Single incident request for doing this activity, we want disconnect 2003 server from 2010 server so accordingly need support,
    we are ready to pay for this incident, 
    pls do the needful,
    Thanks & regards
    Anteshwar Bhosale

    Hi Anteshwar,
    If you want to remove Exchange 2003 from your coexistence environment, please perform the following procedure:
    1. Move all mailboxes to an Exchange 2010 server in the organization.
    2. Move all content from the public folder database on the legacy Exchange 2003 server to a public folder database on an Exchange 2010 server in the organization.
    3. On Exchange 2003 servers, for each offline address book (OAB), move the generation process to an Exchange 2010 server.
    4. Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers.
    5. Verify that all inbound protocol services (Microsoft Exchange ActiveSync, Microsoft Office Outlook Web App, Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange Web service) are configured for Exchange 2010.
    If all above steps have been prepared, we can remove the last Exchange 2003 server from the Exchange 2010 organization from ADSIEdit. For detailed steps about this, please refer to:
    https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Removing dead Exchange 2003 and Exchange 2000 Server from the domain

    Hi Team,
    I have come across a client who wants to migrate to O365 from existing Exchange 2003 environment through the Hybrid Model. I am trying to introduce 2010 Sp3 to the environment. While checking the environment using Exchange pre-deployment found 2 servers
    in the environment which is not present on the network now. Client has no clue what they are.
    One is Exchange 2003 and the other is Exchange 2000. The problem here is i cannot introduce Exchange 2010 Sp3 unless all the Exchange servers are running minimum Exchange 2003 Sp2. 
    At present i find only 2 exchange 2003 Sp2 server which are in production. Need kind assistance to move forward.

    Hi,
    I recommend you follow the steps below:
    1. Please upgrade Exchange 2000 and Exchange 2003 to Exchange 2003 SP2 at first.
    2. Deploy Exchange 2010 servers in this order: CAS, Hub, UM and Mailbox. For more information, here is an article for your reference:
    Exchange 2003 - Planning Roadmap for Upgrade and Coexistence
    http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
    3. Install Exchange 2010 SP3.
    Here is an article for your reference.
    Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
    http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
    About a hybrid deployment with Microsoft Office 365 using Microsoft Exchange Server 2010 servers, here is an article for your reference. 
    Understanding Upgrading Office 365 Tenants for Exchange 2010-based Hybrid Deployments
    http://technet.microsoft.com/en-us/library/jj945383(v=exchg.141).aspx
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Disable link state updates Exchange 2003 server

    Good Day ,
    Current Environment:  Exchange 2003 SP2 server and one Exchange Front-End Server
    What I will have:  Two Exchange 2010 servers with DAG
    After running the Exchange Pre-Deployment Analyzer I see the message :Before introducing Exchange Server 2010 into this topology, the 'SuppressStateChanges' configuration parameter should be set to '1' on server
    server.com. This parameter is essential if you plan to create multiple connectors to the dedicated Exchange 2010 routing group.
    So I must do it ?if yes is safe for my exchange 2003
    Many Thanks
    Regards
    e

    After doing the Pre_Deployement Analyzer :
      Found 1 Active Directory domain(s) containing Exchange servers: companydomaine :  
      Found 1 Active Directory domain(s) in the forest. :  
      Found 1 Active Directory site(s) containing Exchange servers: Terminal. :  
      Found 1 Active Directory site(s) in the forest. :  
      Found 1 Active Directory tree(s) in the forest. :  
      Found 1 administrative group(s) in the organization. :  
      Found 1 DNS domain(s) containing Exchange servers: companydomaine.com. :  
      Found 1 routing group(s) in the organization. :  
      Found 148 pre-Exchange 2010 mailboxes in the organization. :  
      Found 2 Active Directory server(s) running Windows Server 2003 Service Pack 2. :  
      Found 2 Active Directory server(s) running Windows Server 2008 R2. :  
      Found 3 server(s) running Exchange Server 2003.
    so that I understand I have just one routing group ?
    Regards
    e

  • Exchange 2003 with Windows Server 2012 DC's only. Migrate to Exchange 2010.

    I have the following situation:
    An Exchange 2003 SP2 server in an 2003 FFL and DFL domain with 2 Windows Server 2012 DC's. There are no Windows Server 2003 DC's anymore. Exchange 2003 is still functioning properly, but the eventlog is showing me some errors about LDAP which is unable to
    find an old 2003 DC.
    I know this is not supported, so we want to migrate to Exchange 2010 as soon as possible.
    What is the best way to do this? Will coexsitence still work? Do I have to add an 2003 DC's again?
    Please advice. Thank's in advance!

    Oh thank GOD I found this thread!
    I am facing a similar situation:
    http://social.technet.microsoft.com/Forums/exchange/en-US/9a8bc14b-1a45-4b8b-ac3a-38d63e66a7da/exchange-predeployment-analyzer-exchange-2010-compatibility-check-does-not-recognize-windows?forum=exchangesvrdeploylegacy
    And this is the first post I have seen marked as an answer by a Microsoft Contingent Staff affiliated person.
    Thanks Steve and Simon, you have saved me a bunch of grey hairs.
    C.
    "Time is an illusion, Lunchtime, doubly so..." - Ford Prefect

  • Exchange 2003 and Exchange 2010 Coexistence Activesync Issue

    Hello,
    I am currently on the progress of migrating mails from Exchange 2003 SP2 to Exchange 2010 SP3. Before I can do actual migration, I need to make sure that OWA and Activesync works when Exchange 2010 becomes Internet facing.
    Right now Exchange 2003 is Internet facing while Exchange 2010 is internal LAN only. OWA login from Exchange 2010 to a mailbox in Exchange 2003 works fine. However, trying to open a mailbox in Exchange 2003 from Exchange 2010 Activesync fails.
    Activesync login from Exchange 2010 to a mailbox in Exchange 2010 works fine, as well as logging in from Exchange 2003 to mailbox in Exchange 2003.
    Tests using AccessMyLAN ActiveSync Tester using Exchange 2010 as entry point are inconclusive. The test shows the app successfully contacting ActiveSync version 6.5 which is Exchange 2003, but results in "Activesync detected, but not correctly configured."
    Tests using Test-ActiveSyncConnectivity from Exchange 2010 reveals Error HTTP 400 when contacting Exchange 2003. The cmdlet also shows it successfully contacting Activesync version 6.5 (Exchange 2003).
    I have searched around, installed hotfix KB937031, enabled Integrated Windows Authentication on Exchange 2003 Microsoft-Server-Activesync, disabled Require SSL for Microsoft-Server-Activesync and exchange-oma, yet I still can't connect to a mailbox inside
    Exchange 2003 through ActiveSync 2010. Website Multiple Identities for port 80 has been set correctly. Exchange 2003 has Forms-Based Authentication Enabled and is the one thing we haven't tried disabling yet.
    We want to make sure everything works first, then make Exchange 2010 Internet facing, and finally do the mail migration. We do not want to migrate everyone in a single sitting. Please if anyone have ideas any help is welcomed!

    Exchange 2010 will proxy ActiveSync for Exchange 2003.  For OWA, it will redirect, so you need a legacy redirect URL.  You can test all of this internally without changing your Internet connection.  For ActiveSync you can use a WiFi connection.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Connector help ( Coexistence Exchange 2003 and Exchange 2010)

    Dear all,
    we are in a Coexistence state where all the mailboxes are not yet migrated to Exchange Sever 2010.
    On Exchange server 2003 we have two connectors 1) Internal 3) External
    1) Internal connector is used to have mail flow between postfix mail and Exchange server.
    2) External Connector is used for sending/receiving emails from External domains (like gmail,yahoo etc...)
    3) when we added first Exchange 2010 that time it created one RGC used for sending/receving emails between Legacy and new server.
    What I want to achieve is created new two more connectors on Exchange server which will act as Internal & External connector.
    if these works then delete connectors on legacy server and go ahead with for rest migration
    is it possible if not then how do it ? 
    TheAtulA

    Hi AtulA,
    Thank you for your question.
    Internal:
    To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange
    2003 as Exchange Routing Group within Exchange Administrative Group.
    During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, we must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead
    server located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all
    Exchange 2010 servers, regardless of the Active Directory site in which they reside.
    Notice: Don't move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and don't rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use
    this routing group for communication with Exchange 2003.
    External:
    We could create send connector and receive connector to send/receive email from Internet, we should modify the firewall setting to point to Exchange 2010.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • IOS 4 / Exchange 2003 No longer works

    I just upgraded my iPhone 3G to iOS 4.0. We did not have any problems with connectivity with an Exchange 2003 mail server. Now my Inbox no longer works. My calendar and contacts work just fine. I make an update on my phone and it is pushed to Exchange. We are running Exchange 2003 and ISA Server 2004. I checked the firewall logs and everything is clean. My other external emails are just fine. Any ideas?

    I had 3 users show up with iPhone 4s. 2 of the 3 synced fine against Exchange 2003. The third would attempt to sync but eventually time out and get a server connection failed error after adding the account. All three users were previously syncing fine with iPhone 3GS phones against the same Exchange 2003 setup.
    Upon further inspection I noticed that the account was successfully connecting and retrieving the mailbox subfolders that the user had created and that the user was able to send mail from his phone. This led me to believe that there was nothing wrong with the account but rather the phone was having trouble enumerating all of the mail in the user's mailbox.
    Turns out the user had around 40,744 items in his main inbox folder. Upon creating subfolders for 2004/2005/2006/2007/2008 and moving all older mail into these subfolders, the user was left with approximately 13,000 items in his main inbox from 2009-2010. Immediately after archiving the older mail, the phone began successfully syncing again.
    Hope this helps

  • Exchange 2003 to GroupWise 7

    We are not able to successfully complete a migration of all users from
    Exchange 2003 to GroupWise 7 on Netware. Issues below:
    ** NOT Necessarily in exact order of sequence **
    System config:
    Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
    GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
    existing server.
    Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
    special or unusual about this setup for Exchange, pretty generic.
    1. Issue attempting to install Migration utility. Utility unable to run
    after installation on any workstation. Various errors from "unable to
    create GroupWise account" to "unable to login to Exchange mailbox" and a
    few others. We also got "fatal errors when trying to extract .csv file".
    This was resolved later by running fixmapi.
    2. After nearly 18 hours attempting to get the utility to work, we were
    able to successfully load it onto 2 workstations. It appeared that it
    would work on both.
    3. We tried many things to install and run the utility on 15 additional
    workstations with no success.
    4. Found that the only 2 workstations that appeared to run the utility
    were fairly new, less than 2 months old. We then tried fresh installations
    of WINXP and WIN2000 on 2 workstations with no success. One of the 2
    workstations that did work, later no longer would run the utility. After
    running fixmapi.exe on that workstation, it did again work.
    5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
    have corrected 4 of the 10 workstations on which we tried it.
    6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
    the migration utility did not work. We found this by logging in as
    "Workstation Only" which connected the workstation to the domain, then a
    login to eDirectory. The utility did work. So, again we tried to login on
    startup to eDirectory and again were not able to run the utility. So, the
    fact that some workstations here use DLU may be an issue for this utility.
    7. Found that on other workstations, the utility would run ONLY if
    "Workstation Only" was selected, then login to eDirectory. We were able to
    repeat this sequence multiple times. This is on a workstation not running
    ZEN DLU.
    8. Of the 6 workstations we were able to run the utility, 1 failed in the
    first 5 minutes and would no longer work. So, we split the .csv file from
    the Exchange server into 5 parts and started the migration on the 5
    available operating workstations. Of the 5, only 2 completed the utility.
    Of those 2, only 7 of the 45 users to be migrated completed on 1
    workstation and 15 of 45 completed on another.
    9. On the 2 workstations that completed, all user accounts were created
    but the utility was unable to access the GroupWise account. Login to
    GroupWise account failed.
    10. Migration utility rules creation issue. There are 2 issues here.
    10a. The utility suggests to create a rule using a sub-domain and a
    forward rule in Exchange to the new GroupWise system. We are migrating
    from: royalmouldings.com to ggc.com. So, the sub-domain is
    marexch.ggc.com. The rule would read "forward all mail to
    [email protected]. However, Exchange cannot forward to an external
    domain at the client level. The only means to do so is to create a contact
    in AD with an SMTP email address of the domain to be forwarded to. Then,
    in the users account a rule may be created to forward to that newly
    created contact. The fact that we are forwarding to an external internet
    domain, as in NOT the same one currently used in Exchange, is not
    indicated in the documentation. Additionally, if anyone is to do this, a
    lot of manual work must be done to accomplish this task. Not too practical
    to do for hundreds or thousands of users. This has been a big problem as a
    result of the large amount of users in the system and the time it takes to
    create each of these contacts.
    10b. The second issue is the fact that the rule was created for 1 user,
    then no other users had the rule created. So, even if the rule were to
    work or we were migrating from and to the same domain name, we'd still
    have the rule issue as it was never again created by the utility after the
    first user was migrated.
    Any help would be greatly appreciated.
    Thanks

    Bill, you're understandably frustrated. I have a couple of comments.
    1. The network authentication system used by Microsoft Exchange requires that you log in to your workstation with the same user ID and password as your account on Exchange. If they don't match, Exchange returns errors that are not always understandable. That might explain why Zen DLU has problems.
    2. It seems that every application that deals with e-mail has its own version of MAPI, and they're not always compatible with each other. Outlook, GroupWise, and the migration utility all use MAPI. The fixmapi utility will restore the MAPI DLLs that Outlook expects, which is usually the version that works best.
    3. The migration utility should be improved to detect potential errors like these.
    >>> Bill Long<[email protected]> 5/19/07 11:59 AM >>>
    We are not able to successfully complete a migration of all users from
    Exchange 2003 to GroupWise 7 on Netware. Issues below:
    ** NOT Necessarily in exact order of sequence **
    System config:
    Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
    GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
    existing server.
    Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
    special or unusual about this setup for Exchange, pretty generic.
    1. Issue attempting to install Migration utility. Utility unable to run
    after installation on any workstation. Various errors from "unable to
    create GroupWise account" to "unable to login to Exchange mailbox" and a
    few others. We also got "fatal errors when trying to extract .csv file".
    This was resolved later by running fixmapi.
    2. After nearly 18 hours attempting to get the utility to work, we were
    able to successfully load it onto 2 workstations. It appeared that it
    would work on both.
    3. We tried many things to install and run the utility on 15 additional
    workstations with no success.
    4. Found that the only 2 workstations that appeared to run the utility
    were fairly new, less than 2 months old. We then tried fresh installations
    of WINXP and WIN2000 on 2 workstations with no success. One of the 2
    workstations that did work, later no longer would run the utility. After
    running fixmapi.exe on that workstation, it did again work.
    5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
    have corrected 4 of the 10 workstations on which we tried it.
    6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
    the migration utility did not work. We found this by logging in as
    "Workstation Only" which connected the workstation to the domain, then a
    login to eDirectory. The utility did work. So, again we tried to login on
    startup to eDirectory and again were not able to run the utility. So, the
    fact that some workstations here use DLU may be an issue for this utility.
    7. Found that on other workstations, the utility would run ONLY if
    "Workstation Only" was selected, then login to eDirectory. We were able to
    repeat this sequence multiple times. This is on a workstation not running
    ZEN DLU.
    8. Of the 6 workstations we were able to run the utility, 1 failed in the
    first 5 minutes and would no longer work. So, we split the .csv file from
    the Exchange server into 5 parts and started the migration on the 5
    available operating workstations. Of the 5, only 2 completed the utility.
    Of those 2, only 7 of the 45 users to be migrated completed on 1
    workstation and 15 of 45 completed on another.
    9. On the 2 workstations that completed, all user accounts were created
    but the utility was unable to access the GroupWise account. Login to
    GroupWise account failed.
    10. Migration utility rules creation issue. There are 2 issues here.
    10a. The utility suggests to create a rule using a sub-domain and a
    forward rule in Exchange to the new GroupWise system. We are migrating
    from: royalmouldings.com to ggc.com. So, the sub-domain is
    marexch.ggc.com. The rule would read "forward all mail to
    [email protected]. However, Exchange cannot forward to an external
    domain at the client level. The only means to do so is to create a contact
    in AD with an SMTP email address of the domain to be forwarded to. Then,
    in the users account a rule may be created to forward to that newly
    created contact. The fact that we are forwarding to an external internet
    domain, as in NOT the same one currently used in Exchange, is not
    indicated in the documentation. Additionally, if anyone is to do this, a
    lot of manual work must be done to accomplish this task. Not too practical
    to do for hundreds or thousands of users. This has been a big problem as a
    result of the large amount of users in the system and the time it takes to
    create each of these contacts.
    10b. The second issue is the fact that the rule was created for 1 user,
    then no other users had the rule created. So, even if the rule were to
    work or we were migrating from and to the same domain name, we'd still
    have the rule issue as it was never again created by the utility after the
    first user was migrated.
    Any help would be greatly appreciated.
    Thanks

  • Exchange 2003 - Continous password prompts in Outlook 2010

    Hi. 
    A customer is experiencing continous password prompts in Outlook 2010. Outlook is configured against the Exchange 2003 BE server (FQDN) and Outlook Anywhere is configured to sync.customer.com with a valid 3rd party certificate. 
    Outlook is configured with Negotitate as Logon network security, setting this to basic/NTLM does not help. Connect to Microsoft Exchange using HTTP is set and configured with sync.customer.com, and msstd:sync.customer.com. All points checked except "On
    fast networks, connect using HTTP first, then connect using TCP/IP", authentication is set to Basic. Changing authentication from Basic to NTLM seem to make the problem vanish. 
    Outlook Anywhere is functioning correctly and only prompting once for password when connecting from an external network. ISA is not configured for NTLM/Kerberos.
    Exchange 2003 is located in main site in a resource domain. The prompts occur more often in two remote sites than the main site. 
    When opening Outlook RPCDiag shows established connection to BE and Active Directory, sometimes with prompt and sometimes without. After about 5 minutes the prompt may reappear, entering password does not remove the prompt, clicking cancel puts Outlook in
    the "Need password" state, clicking this usually successfully connect Outlook to Exchange. Other times this just cause the prompt to reappear. 
    I´ve tried adding the internal and/or external IP address of the ISA server as sync.customer.com in the host-file on a client and forcing RPC/HTTPS through the DisableRpcTcpFallback, still getting the password prompts. 
    We have also been through the KB975363, changing the MaxConcurrentAPI on all domain controllers. 
    Finally, we know Exchange 2003 is in a unsupported state so there is no need to comment this. 

    Hi,
    Firstly, I'd like to explian, basic authentication requires the user to enter domain, user name, and password. Thus, it's an expected behavior that the credential prompts once when the authentication is set to basic and it disappears when it's NTLM authentication:
    http://technet.microsoft.com/en-us/library/aa996225(v=exchg.65).aspx
    For the issue that the credential keeps prompting, I'd like to confirm if Outlook 2003 works well. If yes, you can refer to the following article:
    http://support.microsoft.com/kb/927612/en-us
    If all outlook clients prompt credential, you can check the RPC over HTTP connectivity by ExRCA:
    https://testconnectivity.microsoft.com/
    http://support.microsoft.com/kb/820281/en-us
    Thanks,
    Angela Shi
    TechNet Community Support

  • Can't connect to Exchange 2007 SP2 server

    When I try and set up a new Exchange account to our internal Exchange 2007 server I get the following error message:
    "The Exchange Server '<server name>' doesn't have the minimum required version installed. To use Mail with Exchange, the server must be running Update Rollup 4 for Exchange Server 2007 Service Pack 1 or later. Contact your server administrator.'
    in spite of Service Pack 2 being installed on the server.
    Exchange Web Services are running as expected at the URL '/EWS/Exchange.asmx'.
    If anyone has suggestion on how to diagnose the exact problem I would very much appreciate the assistance.
    N.

    Hello,
    I don't have any ideas yet but can chime in with "me too".
    A customer has an Exchange 2003 SP2 server (MS Server 2003 for SBS). It has a self-signed SSL certificate that does not expire until June 2011.
    One user has some species of Blackberry that can pick up his email (but not contacts or calendar) via OWA. I can see his accesses in the IIS log and they are coming from IP addresses resolving to (stuff).bise.na.blackberry.com and are not getting 404's.
    Another user is trying to set up his new Blackberry via BIS. His accesses in the IIS log are coming from different IP addresses that resolve to (stuff).bis.ap.blackberry.com and these are getting 404's.
    An ExpertsExchange.com article - http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_22806090.html - suggested putting the full email address into the OWA URL. This works fine in a browser but not in BIS. I still get the same error message from BIS and 404's in the IIS log.

Maybe you are looking for