Can't Connect To New Exchange 2010 Installation

It appears this has solved my error 500 issue when using remote outlook access:

http://blogs.technet.com/b/sbs/archive/2011/03/23/error-500-attempting-to-access-owa-on-sbs-2011-standard.aspx

However, I still can not connect to exchange using outlook. Any help would be greatly appreciated.

Presumably you have run the connect to the internet and set up your internet address wizards to properly configure Exchnage?

When prompted for your user name try using the format:    Domain\UserName

Thanks for the suggestion. I have been using DOMAIN\User Name and I have ran the connect to internet wizard and also the internet address wizard.

As an additional step I turned off the windows firewall. Still no go.

I did notice that the login box says "welcome back to remote.domain_name.com", is this normal?

Perhaps similar to this ?
https://www.experts-exchange.com/questions/26944705/Login-dialog-box-pops-up-when-I-launch-Outlook-2007-against-Exchange-2007-on-SBS-2008.html

I was using outlook 2007 but I just tried outlook 2003. In 2003 I don't get the login dialog box but it still says it can't synchronize my profile and ends up closing outlook.

What's the best way in SBS 2011 to check the service pack I am using for exchange? Thanks.

I was just poking around and saw that the offline address book was still using my old server name. I changed this and updated the OAB. Unfortunately I still have this problem but is there a chance there are still some other references to my old server tha should not be there? Any way to check for that?

When I go to run BPA for exchange my old administrative group is still there.

Thanks.

You should be able to tell under Programs and Features | View Installed Updates

However if it won't sync it sounds like a corrupt profile, yet you chnaged to 2003.  Did you use the same local profile, or allow it to create another?  
If OWA is working then it sounds like a local issue, not server.

To be honest I am not sure how you would verify and clean that up.  I would recommend clicking the "Request attention" link and ask that an Exchange Expert be contacted, or post a new question with those specifics.

This is all using a brand new profile in outlook. First I tried a computer with outlook 2007 that was never configured with a profile. Then I tried another computer with outlook 2003 which was also never configured with a profile. Both times I can't connect.

I don't see any exchange updates under programs and features.

I will click the request attention link now. Thanks.

I am at a loss at this point. I have a feeling this has something to do with public folders since it is trying to login to remote.domain.com but not 100% sure. Digging through the BPA report I found this:

The default public folder database for mailbox database 'Mailbox Database 2011112613' on server SERVERNAME isn't local. Public folder database: CN=Public Folder Database 0337598525,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=SDV,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local.

I am not sure how to change this.

One more thing. When I go to the public folder management console and right click "Public folders = Servername.domain.local" and select update I get this error:

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Action 'Update Hierarchy' couldn't be performed.

Update Hierarchy
Failed
Error:
Cannot start hierarchy replication on public folder database 'Public Folder Database 0337598525'.

MapiExceptionNoReplicaAvailable: StartHierachyReplication failed. (hr=0x80004005, ec=1129)
Diagnostic context:
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 18084   StoreEc: 0xFFFFF9BF
    Lid: 33819   StoreEc: 0x469    
    Lid: 27225   StoreEc: 0x469    
    Lid: 1750    ---- Remote Context End ----
    Lid: 26322   StoreEc: 0x469    




--------------------------------------------------------
OK
--------------------------------------------------------

Not sure if this is normal.

Server needed reboot.