Connecting to Exchange 2010 via Outlook

Hi,

I'm attempting to migrate from Exchange 2003 to Exchange 2010. I have the client access, hub, mailbox roles all setup on one new box. I've moved a test user to the new box and am attempting to connect via Outlook. I've made sure that all the services are running, the stores are mounted, DNS is correct, etc, but I can't connect. I get an error message saying "Cannot open your default e-mail folders. The attempt to log on to Microsoft Exchange has failed." If I uncheck encypt data in the account setup in Mail settings I then get "cannot open your default email folders the information store cannot be opened". Any ideas? This is driving me crazy as everything looks correct and I'm set to go live in a few days.

Thanks,
arwen1201Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

Please try to start Outlook as -> Outlook.exe /resetnavpane

Next please check if outlook is not in compatabillity mode:
C:\Program Files x86\Microsoft Office\Office 14\Outlook.exe (right click properties ->Compatibility tab)

If any boxes are checked, uncheck them and apply. Please try again.
0
AmitIT ArchitectCommented:
What is your outlook client version? Also what is the service pack level on your Exchange server?
0
Paul MacDonaldDirector, Information SystemsCommented:
What version of Outlook are you using?  You need at least 2010 to connect to Exchange 2010...


Can you connect to OWA?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Patrick BogersDatacenter platform engineer LindowsCommented:
Rubbish, you can still use Outlook 2003 to connect with exchange 2010.
0
fabric8Commented:
I've had the same error when trying to connect to my exchange 2013 server, these settings solved my problem, so maybe it will help you..

In outlook, while you add the user, where you have to fill in server address and username
- Click 'more settings'
- On the connection tab check 'connect with http ...', then click exchange proxy settings.
- In the first field where you can enter an URL, enter your mail.domain.org name
- uncheck al boxes below
- choose basic verification in the proxy settings.

note: i do not have an english pc in front of me, so naming is not accurate ; )

So see if it helps with these settings..
0
MarkMichaelCommented:
Did you use the manual way of setting up an account or did it automatically set up the account when you created the profile?

I would suggest re-creating the profile and going through the wizard to create your account.

If that fails, try to manually put the details in and hit 'check names' to see if you're account is being found.
0
arwen1201Author Commented:
I'm running Outlook 2010.I'm running Exchange 2010 build 639.21. It's not running in compatibility mode; I've tried putting it in compatibility and unchecking it to see if that helped.
Nothing helps.
0
arwen1201Author Commented:
OWA does work from this workstation and as this user...
0
AmitIT ArchitectCommented:
You need to upgrade to SP3 with RU2 and issue with be resolved. Currently you are running RTM version.
0
arwen1201Author Commented:
Downloading the SP right now and will upgrade. I will post and let you know how it goes....
0
AmitIT ArchitectCommented:
In case you need steps follow this:

Steps Upgrading Exchange 2010 SP1 or SP2 to SP3:


My Lab Setup: 2 node Multi-role server with DAG.

1) Upgrade the schema for Exchange 2010 SP3. If you have Enterprise and Schema Admin rights, setup will do it automatically, however if not, then AD team is required to perform this task.

Purpose of this Schema Update:
===================

In Order to have the Exchange 2010 SP3 deployed across the environment, it is a prerequisite to have the Active Directory Schema to be extended for supporting Exchange 2010 SP3. During this upgrade, the Active Directory Schema will be extended to support Exchange 2010 SP3.

Steps to be performed for this upgrade:
================================

Reference Article –
http://technet.microsoft.com/en-in/library/bb629560(v=exchg.141).aspx

Prerequisites: AD account need to be member of following groups
Member of: Domain Admin, Enterprise Admin, Schema Admin

Install Active Directory Management Tools (Run this Command, if Required)
ServerManagerCmd -i RSAT-ADDS

Software Location Exchange 2010 SP3
http://www.microsoft.com/en-us/download/details.aspx?id=36768

Download it and extracting it run below command for preparing the schema.

 setup /PrepareLegacyExchangePermissions (Optional):
 Check C:\ExchangeSetupLogs\ExchangeSetup.log for successful completion
 Setup /PrepareSchema
 Check C:\ExchangeSetupLogs\ExchangeSetup.log for successful completion
 Setup /PrepareAD /OrganizationName:"Your Org Name"
 Check C:\ExchangeSetupLogs\ExchangeSetup.log for successful completion

How to verify schema version?
http://technet.microsoft.com/en-in/library/bb125224%28v=exchg.141%29.aspx

2) Steps for Upgrading Exchange 2010 to SP3

Software Location:
1) Exchange 2010 SP3: http://www.microsoft.com/en-in/download/details.aspx?id=36768

Note: Any Interim Updates for Exchange Server 2010 must be uninstalled prior to installing this update.

As I have all roles in one server in a 2 node DAG. Kindly perform the below steps.

Phase 1: Upgrading Database Availability Groups to Exchange 2010 SP3 (Start with Passive)

Note: Make sure to take full Exchange backup, including system state or any custom setting related to CAS role. Do save the OWA folder under bin path too. During SP3 installation, Exchange setup removes all SP2 related folders; in case you have any proxying it might fail, so make sure to upgrade all servers, however one by one.

1) Open Exchange Management Shell, browse to script folder and run below command
     
.\StartDagServerMaintenance.ps1 -serverName servername

Note: This script move all Exchange related component including database to another server.
           
2) Disable the Forefront by using below command (It might ask you to stop few Exchange services)

fscutility /disable

3) Stop the OS Antivirus services and Monitoring Agent for Microsoft Exchange Server

4) Verify Backups are completed.

5) Run the SP3 setup files using GUI or goto run setup /m:upgrade. If you are getting IIS component error goto run setup /mode:upgrade /installwindowscomponents

Note: If you are getting this error "A Restart from a Previous Installation is Pending"

Open regedit and delete the HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations key and Rerun Setup.

Ref: http://technet.microsoft.com/en-us/library/cc164360(v=exchg.80).aspx

6) Reboot the server

7) After reboot verify below logs for any error:
     
Event Logs
 
Setup Logs (C:\ExchangeSetupLogs)

Services - All Exchange related services are running.
     
Check IIS Settings are not changed.
     
Check Authentication settings from EMC for OWA/OMA/ESW. If you find any change revert back to old.
     
8) Enable Forefront Protection for Exchange. Command fscutility /enable (It might ask you to stop few Exchange services)

9) Start OS Antivirus and Exchange Monitoring Agent Services
     
10) .\StopDagServerMaintenance.ps1 -serverName servername

11) Now use same steps on another server in DAG.

-------------------------------------------------------------------------------------------------

Phase 2: Upgrade Management Tools

If you have installed management tools in any other machine make sure to upgrade those also.
-------------------------------------------------------------------------------------------------
Finally: - how to verify the upgrade.

Goto Powershell and type below command.

GCM exsetup |%{$_.Fileversioninfo}
0
Paul MacDonaldDirector, Information SystemsCommented:
[Patricksr1972] is right.  I meant Outlook 2002/Outlook XP.  Sorry!
0
arwen1201Author Commented:
Upgrade went fine. Have new error message when attempting to open via Outlook if cached mode is off "Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance". If cached mode is on "you must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)". I've tried disabling cached mode, deleting the .ost files, no luck.
0
Patrick BogersDatacenter platform engineer LindowsCommented:
Assumeable your Information Store services are running and OWA works like a charm i would delete the profile in controle panel- email and start outlook, what server does autodiscovery find?
0
AmitIT ArchitectCommented:
check from another machine.
0
arwen1201Author Commented:
Stores are mounted, info store service is running, web access works, auto discovery does the same thing. Everything looks like it "should" work, but it's not.
0
AmitIT ArchitectCommented:
delete this profile restart you pc and create new one.
0
Patrick BogersDatacenter platform engineer LindowsCommented:
Not sure why i am saying this but could you temporarely kill any kind of AV/SPAMfilter software if applicable or even the Windows Firewall (if turned on of course)
0
arwen1201Author Commented:
It's not connecting from any machines and Outlook.
0
AmitIT ArchitectCommented:
then goto exrca.com click on client tab, download the tool and start troubleshooting.
0
arwen1201Author Commented:
Deleted the profile, restarted, not working.
Disabled the AV/firewall, not working.

What is going on?? I don't understand....
0
Patrick BogersDatacenter platform engineer LindowsCommented:
Dont give up, it will be something easy to miss.

Please have a shot with the MS Exchange Analysers
0
Paul MacDonaldDirector, Information SystemsCommented:
What host name are you using to connect to your Exchange server?  Can you ping that exact same name from a command prompt?  It may be that you're literally not able to connect because Outlook can't find the server...
0
arwen1201Author Commented:
I can ping the name from the machine I'm trying to connect from. I'm going to contact support. Thanks for the help everyone.
0
arwen1201Author Commented:
Update, during the move from Exchange 2003 to Exchange 2010, users attributes were not updated completely. In ASDI Edit, I had to modify the LegencyExchange setting and that solved the problem. Thanks for your help, everyone!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
arwen1201Author Commented:
This was the only thing that worked for me. I tried all the other solutions first, but in the end the LegencyExchange attribute needed to be updated.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.