Exchange 2010 and Outlook

[zeta_immersion]

I have SBS 2011 with Exchange 2010.

I am able to send/receive e-mails and login through OWA however I am unable to setup Outlook to access the Exchange server.

I have tried some tutorials but I think I am missing some crucial Exchange setup (maybe a few lines in console or management)

I have attached the MS autodiscover test for Outlook

				Autodiscover Account Settings
				XML response:
				<?xml version="1.0"?>
				<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
				<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
				<User>
				<DisplayName>test user</DisplayName>
				<LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=some name</LegacyDN>
				<DeploymentId>2fa542bd-30dc-4c27-a568-aab4d0df9b13</DeploymentId>
				</User>
				<Account>
				<AccountType>email</AccountType>
				<Action>settings</Action>
				<Protocol>
				<Type>EXCH</Type>
				<Server>SERVER.name.local</Server>
				<ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVER</ServerDN>
				<ServerVersion>738180DA</ServerVersion>
				<MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVER/cn=Microsoft Private MDB</MdbDN>
				<ASUrl>https://remote.domain.com/EWS/Exchange.asmx</ASUrl>
				<OOFUrl>https://remote.domain.com/EWS/Exchange.asmx</OOFUrl>
				<OABUrl>https://remote.domain.com/OAB/42212ace-9471-4743-94e3-ec6eb00d7de2/</OABUrl>
				<UMUrl>https://remote.domain.com/EWS/UM2007Legacy.asmx</UMUrl>
				<Port>0</Port>
				<DirectoryPort>0</DirectoryPort>
				<ReferralPort>0</ReferralPort>
				<PublicFolderServer>SERVER.name.local</PublicFolderServer>
				<AD>SERVER.name.local</AD>
				<EwsUrl>https://remote.domain.com/EWS/Exchange.asmx</EwsUrl>
				<EcpUrl>https://remote.domain.com/ecp/</EcpUrl>
				<EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
				<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr>
				<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt>
				<EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
				<EcpUrl-sms>?p=sms/textmessaging.slab&exsvurl=1</EcpUrl-sms>
				</Protocol>
				<Protocol>
				<Type>EXPR</Type>
				<Server>remote.domain.com</Server>
				<ASUrl>https://mail.domain.com/ews/exchange.asmx</ASUrl>
				<OOFUrl>https://mail.domain.com/ews/exchange.asmx</OOFUrl>
				<OABUrl>https://mail.domain.com/OAB/42212ace-9471-4743-94e3-ec6eb00d7de2/</OABUrl>
				<UMUrl>https://mail.domain.com/ews/UM2007Legacy.asmx</UMUrl>
				<Port>0</Port>
				<DirectoryPort>0</DirectoryPort>
				<ReferralPort>0</ReferralPort>
				<SSL>On</SSL>
				<AuthPackage>Basic</AuthPackage>
				<EwsUrl>https://mail.domain.com/ews/exchange.asmx</EwsUrl>
				<EcpUrl>https://mail.domain.com/ecp/</EcpUrl>
				<EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
				<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr>
				<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt>
				<EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
				<EcpUrl-sms>?p=sms/textmessaging.slab&exsvurl=1</EcpUrl-sms>
				</Protocol>
				<Protocol>
				<Type>WEB</Type>
				<Port>0</Port>
				<DirectoryPort>0</DirectoryPort>
				<ReferralPort>0</ReferralPort>
				<Internal>
				<OWAUrl AuthenticationMethod="Basic, Fba">https://remote.domain.com/owa/</OWAUrl>
				<Protocol>
				<Type>EXCH</Type>
				<ASUrl>https://remote.domain.com/EWS/Exchange.asmx</ASUrl>
				</Protocol>
				</Internal>
				<External>
				<OWAUrl AuthenticationMethod="Fba">https://mail.domain.com/owa/</OWAUrl>
				<Protocol>
				<Type>EXPR</Type>
				<ASUrl>https://mail.domain.com/ews/exchange.asmx</ASUrl>
				</Protocol>
				</External>
				</Protocol>
				</Account>
				</Response>
				</Autodiscover>
				[/CODE]

Is there anything I am missing? Thank you.

[sc302 Veteran]

sbs..so this should be easy. if it works with owa it should work with outlook.

Do a manual setup for exchange, don't do the automatic. Let me know if that works. There is nothing that you have to do with an outlook client to get it to connect to an exchange server. If the automatic is failing it is due to dns issues on your domain.

[zeta_immersion]

there seems to be an issue between website panel and the default website thus the autodiscovery was not being detected at all ...

setting this up properly is a pain in the ass

[sc302 Veteran]

autodiscovery is a pain in the ass. good luck with that...I would just use manual,

http://technet.microsoft.com/en-us/library/bb201695.aspx - if you didn't read through yet.

[Dashel]

Careful with Exchange shell commands on SBS, can get tricky. Sounds more like you never setup your autodiscover DNS SRV entry if using a single SSL cert.

Have you run this? https://www.testexchangeconnectivity.com/

[zeta_immersion]

Ok, so I was able to eliminate all problems except one (al test check fine except RPC/HTTP)

Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server server.local.

The attempt to ping the endpoint failed.

Additional Details

The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

As such I have made sure in registry the FQDN is pointing to the right ports (using the program forget the name atm)

Also, EchangeIS (AS) or something like that within the registry have been done proper.

6001 is open can be pinged (firewall also has a rule for 6002 & 4)

now ... i have read i need the netbios/fqdn in nosts ... did that and almost broke it ... anyone know anything about this? as an example or any other input?

[zeta_immersion]

I realised I started off my old thread, well ... ignore the date, the issue is current :)

OWA and everything else works fine

[sc302 Veteran]

it would be much easier to have rpc over https and have a valid certificate. I have a little bit of time today, I can remote in and look at it if you want.

It should be as simple as turning on the service and enabling outlook anywhere. There is no rocket science behind it after that. if you are having issues you have some serious config issues going on and there should be something in the event logs.

All that needs to be opened to the exchange server is 25, 80, and 443. There should be no other ports unless you have totally screwed with the config.

[sc302 Veteran]

Server.server.local is an invalid internet domain name. That is your issue with the test. You will never get the test to succeed with that. You need a good domain name accessible through the internet with a good cert.

I would like to help you out, but I need good information. This is a garbage in garbage out scenerio. You want quality help give me something to woek with.

[olger901]

First of all: SBS is a pain in the ass if you're trying to do anything outside of the box of pre-configured wizards. If you'd like to do basically anything outside of this scope, you're better of with 2x a Microsoft WIndows Server 2008 R2 (Standard or Enterprise) with one running as PDC (with any other supported roles on DC's) and one as Exchange Server

Secondly there a few things you should do first:

- Make sure DNS resolution is working and configured properly (it doesn't seem like it);

- Make sure the RPC connection isn't being firewalled by the Microsoft Windows Firewall;

- Buy a 3rd party certificate to remove the bloody annoying SSL certificate errors, or generate and distribute your own using the Microsoft Windows Certificate Services (Google for howto's)