run the powershell command "get-outlookprovider" and report the results...
Main Topics
Browse All TopicsHi All,
I have recently set up a SBS 2008 running Exchange 2007 with the intention of getting Outlook Anywhere to work, something which I have very quickly found out is easier said than done...
Setup: Single server domain, SBS 2008, Exchange 2007, IIS7, Clients - Outlook 2007 SP2, Windows XP SP3, not joined to the domain, Firewall - ports 443, 80 and 25 open
Installed SBS 2008 clean install, installed Exchange, enabled Outlook Anywhere with basic authentication and hostname remote.domain.co.uk, installed self signed certificate*, checked and set permissions for virtual directories in IIS, pointed remote.domain.co.uk and autodiscover.domain.co.uk to the external static IP address
*I have read that self signed certificates will not work, or at least the default self signed will not work, I have requested a SAN certificate using Exchange PowerShell and issued with my server so that it contains; hostname, hostname.local; domain.co.uk, remote.domain.co.uk, autodiscover.domain.co.uk,
I do think the problem may lie with the certificate, however until I know it will solve the issue I am unable to spend the £250 required for a SAN certificate. I also believe there may be another problem as OWA accepts the certificate without a problem when browsing to https://remote.domain.co.u
Here is how far I can get:
OWA works without a problem, as long as the certificate is installed on the client (cert error if not)
Autodiscover passes a test (the one which ignores SSL authentication) on testexchangeconnectivity.c
When setting up a profile on an external client and entering the email address and password, it brings back the internal name of the server but says 'you must be connected/online to complete this operation'
When setting up a profile on an internal client (not joined to the domain, just in the same switch) it comes back with the correct information, connects and shows emails, but when send/receive is pressed it crashes on receiving when trying to download either the OAB or public folders.
Here is what I have tried from various forums (including this one):
Disabling IPv6
Editing hosts file to hash out #;;1 and add hostname, hostname.local to internal IP
Browsing directly to https://remote.domain.co.u
Switching between NTLM and Basic authentication in Outlook Anywhere
Inserting registry entries to manually assign ports 6001-6004 (which may be redundant but it was worth a shot)
rpcping from client computer (passes tests on ports 6001-6004)
Using a free trial certificate for remote.domain.co.uk from Comodo (unable to find trial SAN certificate)
Manually setting the clients to use https://remote.domain.co.u
Removing and reinstalling RPC over HTTP
Disabling and re-enabling Outlook Anywhere
Breaking a keyboard (not much good to the server but relieved a little stress)
I apologise if this seems a little scrambled, I have spent the last few days on this same problem so it is possible I have missed a few steps out..! Any suggestions would be greatly appreciated
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Get-OutlookProvider
name server certprincipalname TTL
EXCH hostname 1
EXPR hostname 1
WEB hostname 1
Outlook Anywhere With AutoDiscover test:
Attempting to Resolve the host name autodiscover.domain.co.uk in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: [correct IP]
Testing TCP Port 443 on host autodiscover.domain.co.uk to ensure it is listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname autodiscover.domain.co.uk in Certificate Subject Alternative Name entry
Validating certificate trust
Certificate trust validation failed
Additional Details
Certificate chain could not be built. You may be missing required intermediate certificates.
Outlook Provider AutoDiscover (Ignore Trust For SSL)
Attempting to test potential AutoDiscover URL https://autodiscover.domai
Testing AutoDiscover URL succeeded
Test Steps
Attempting to Resolve the host name autodiscover.domain.co.uk in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: [correct IP]
Testing TCP Port 443 on host autodiscover.domain.co.uk to ensure it is listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The certificate passed all validation requirements.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname autodiscover.domain.co.uk in Certificate Subject Alternative Name entry
Testing certificate date to ensure validity
Date Validation passed. The certificate is not expired.
Additional Details
Certificate is valid: NotBefore = 8/5/2009 8:09:00 AM, NotAfter = 8/5/2011 8:09:00 AM
Attempting to Retrieve XML AutoDiscover Response from url https://autodiscover.domai
Successfully Retrieved AutoDiscover XML Response
Additional Details
AutoDiscover Account Settings - XML Response:<?xml version="1.0"?>
<Autodiscover xmlns:xsi="http://www.w3.o
<Response xmlns="http://schemas.micr
<User>
<DisplayName>User Account</DisplayName>
<LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip
<DeploymentId>c19e45e1-ed14-
</User>
<Account>
<AccountType>email</AccountTy
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>hostname.local</Serve
<ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
<ServerVersion>720180F0</Serv
<MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
<ASUrl>https://remote.domain
<OOFUrl>https://remote.domai
<OABUrl>https://remote.domai
<UMUrl>https://remote.domain
<Port>0</Port>
<DirectoryPort>0</DirectoryPo
<ReferralPort>0</ReferralPort
<PublicFolderServer>hostname
<AD>hostname.local</AD>
<EwsUrl>https://remote.domai
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>hostname</Server>
<ASUrl>https://remote.domain
<OOFUrl>https://remote.domai
<OABUrl>https://remote.domai
<UMUrl>https://remote.domain
<Port>0</Port>
<DirectoryPort>0</DirectoryPo
<ReferralPort>0</ReferralPort
<EwsUrl>https://remote.domai
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPo
<ReferralPort>0</ReferralPort
<External>
<OWAUrl AuthenticationMethod="Fba"
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://remote.domain
</Protocol>
</External>
<Internal>
<OWAUrl AuthenticationMethod="Basi
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://remote.domain
</Protocol>
</Internal>
</Protocol>
</Account>
</Response>
</Autodiscover>
Outlook 2003 RPC/HTTP (manual entry of server name etc)
Testing RPC/HTTP connectivity
RPC/HTTP test failed
Test Steps
Attempting to Resolve the host name remote.domain.co.uk in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: [correct IP]
Testing TCP Port 443 on host remote.domain.co.uk to ensure it is listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname remote.domain.co.uk in Certificate Subject Common name
Validating certificate trust
Certificate trust validation failed
Additional Details
Certificate chain could not be built. You may be missing required intermediate certificates.
I believe you might need to recreate the certificate using the SBS wizards.
Another thing I might mention...we had a SBS 2008 implementation not too long ago where one of the first things we tried doing (just because of issues when we had Exchange 2007 on Server 2008 boxes) was to disable IPv6. This ended up causing all sorts of wierd issues with non-Exchange services on the SBS 2008 box, so we ended up turning it back on.
lastlostlast: I will re-enable IPv6, the internal certificate was not installed on the computer I ran the test from, would this make a difference?
esmith69: What would be the best way to create the certificate via SBS? The current certificate I have I requested via Exchange PowerShell, I also tried via IIS but I have not used an SBS certificate wizard before
Thank you both for your assistance in this
Try Network->Connectivity->Fix My Network. From what I've read, this is supposed to recreate the certs.
http://sbs.editme.com/sbs2
Running Fix My Network found and fixed a few errors, the new log I receive from exchangeconnectivity is:
Attempting to Resolve the host name autodiscover.domain.co.uk in DNS.
Host successfully Resolved
Additional Details
IP(s) returned: [Correct IP]
Testing TCP Port 443 on host autodiscover.domain.co.uk to ensure it is listening/open.
The port was opened successfully.
Testing SSL Certificate for validity.
The SSL Certificate failed one or more certificate validation checks.
Test Steps
Validating certificate name
Certificate name validation failed
Tell me more about this issue and how to resolve it
Additional Details
Host name autodiscover.cobaltenergy.
I have tested it with clients anyway, installing the certificate using the install package in Public\downloads and I get the following results:
Creating a profile whilst on the same network allows me in but (after giving a certificate error, autodiscover.domain.co.uk is not valid on this certificate) it uses TCP/IP rather than HTTPS (even when selected on fast networks). Also, in the field "use this url to connect to my proxy" it has the local hostname rather than the external, if i attempt to change this it changes it back...
When I re-open this profile it seems to attempt to connect to HTTPS (i get the certificate error again) but quickly gives up and uses TCP/IP
Creating a profile manually whilst not on the network results in the "this server must be online / connected" error message.
The only way which seems to half work is if the client is on the same network using TCP/IP, but even then if you send/receive it sticks on receiving and you have to click cancel all
Is there another wizard I am missing?
sorry, I re-read your last post and think I answered my own question.
Check out the following link for some more information about how this whole process works with SBS: http://blogs.technet.com/s
I've run the wizard as suggested: I already have a domain > I want to manage the domain name myself > [domain.co.uk]. The Remote Web Workplace Site (https://remote.domain.co.
Still no joy though I'm afraid, I read through the link provided and the only thing I'm not sure about is the SRV record so I have sent an email to our DNS guy
Update: Since running the internet connection wizard (and possibly the import certificate wizard) the 'rpc' and 'rpcwithcert' virtual directories within IIS have moved from 'SBS Web Applications' to 'Default Website'. OWA, OAB, Exchange etc. are all still in 'SBS Web Applications'.
Now if i browse to https://remote.domain.co.u
I realise I could change this back in IIS but am unwilling due to so many reports of 'use the wizards, only the wizards, and nothing but the wizards...!'
I think you can export a directory to a backup file, then restore it into the location that you desire in IIS. I know this is how it was done in 2003 but I'm not 100% sure the process is identical in 2007. I'd imagine you could at least copy the OWA, OAB, Exchange, etc. directories into the default website though and maybe that would do the trick?
i too am having similiar problems. I noticed on my setup that the /Rpc and /RpcwithCert folders are under Default Website and not SBS Web Applications. I beleive this is a result of installing TS Gateway on the SBS 2008 Server which set a binding on port 443 on the Default Website. Given that two websites cannot listen on port 443, the default website does not start.
Finally managed to get this working!! Just as I was about to open a support call to Microsoft I stumbled across this forum:
http://social.technet.micr
The part that worked for me was the following:
On our exchange server:
- We added another registry key: HKEY_LOCAL_MACHINE\SYSTEM\
Value Name: MaxWorkItems
Data Type: REG_DWORD
Value data: 8192 (decimal)
- Ran IISRESET and restarted the System Attendant service.
- Now, the username resolves while configuring a profile and Outlook connects on HTTPS without errors.
This is the only place i have even seen this key mentioned, and I have no idea why it works but am very happy it does. Hopefully this will help with anybody else having this problem.
hottips: please see the below link for how I managed to move my /rpc and /rpcwithcert virtual directories;
http://www.experts-exchang
Thanks everyone for the suggestions
I had a similar error I followed the link below it may help
http://sbs.editme.com/sbs2
Business Accounts
Answer for Membership
by: lastlostlastPosted on 2009-08-11 at 11:23:53ID: 25071842
run a test for Outlook RPC over HTTPS at https://testexchangeconnec tivity.com and let us know the results...