Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Outlook Anywhere Mixed Mode

Posted on 2012-04-09
8
Medium Priority
?
549 Views
Last Modified: 2012-07-01
In Exchange 2010 I would like to enable Outlook Anywhere. (RPC over HTTPS)

Since this is an existing environment, i want to make certain that when this is enabled on the CAS it will not 'break' all of the existing clients. Will enabling this feature in the existing environment require reconfiguration of existing users or simply allow new users to be configured as Outlook Anywhere?
 
What are the other 'gotchas' of enabling the Outlook Anywhere feature?
0
Comment
Question by:zequestioner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
8 Comments
 
LVL 22

Expert Comment

by:chakko
ID: 37824257
I have not actually ever tried to enable outlook anywhere with other clients already connected.  But, I cannot think of anything that would cause a problem as far as disconnecting existing outlook clients.

Some gotchas could be:  SSL certificate if you are using the self-signed type of certificate.  A commercial UCC/SAN SSL will make things easier and smoother.
Also, having the correct DNS record for autodiscover feature should be already created, check that you already have it
0
 
LVL 9

Expert Comment

by:ash007
ID: 37826398
You need to make setting from Outlook client side to make Outlook anywhere work also need to make sure you have proper certificate
0
 
LVL 1

Author Comment

by:zequestioner
ID: 37828548
After enabling this feature, i received the following messages in the Application Logs on the Exchange server: (See below)

I think it's important to note this is a full version Exch. 2010 server that was migrated from a SBS 2003 Exch. server.

It seems like there is a reference to the old server somewhere.

Any thoughts on how to remove the old server completely from the config?

The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 SBS.MyDomainlocal in Routing Group CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local in routing tables with the timestamp 4/10/2012 4:00:34 PM.

Cannot find route to Mailbox Server CN=SBS,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local for store CN=Public Folder Store (SBS),CN=First Storage Group,CN=InformationStore,CN=SBS,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local in routing tables with timestamp 4/10/2012 4:00:34 PM. Recipients will not be routed to this store.

Cannot find route to Mailbox Server CN=SBS,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local for store CN=Mailbox Store (SBS),CN=First Storage Group,CN=InformationStore,CN=SBS,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local in routing tables with timestamp 4/10/2012 4:00:34 PM. Recipients will not be routed to this store.


Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=SBS,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local for connector CN=SmallBusiness SMTP connector,CN=Connections,CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local in routing tables with timestamp 4/10/2012 4:00:34 PM. Microsoft Exchange is ignoring the source transport server.


The Active Directory topology service could not discover any route to connector CN=SmallBusiness SMTP connector,CN=Connections,CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=MYDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local in the routing tables with the timestamp 4/10/2012 4:00:34 PM. This connector will not be used.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
LVL 22

Expert Comment

by:chakko
ID: 37828614
have you removed the 2003 server already?
In the EMS I would try get-routinggroupconnector and see if they are still there.  You may need to delete them with remove-routinggroupconnector cmdlet
0
 
LVL 1

Author Comment

by:zequestioner
ID: 37828665
Where do I check for this in the EMC? I've check all the configuration and I do not see any references to the server.

When use the Exchange Shell (powershell) I tried the command get-routinggroupconnector but it did not display anything. It simply dropped down back to the prompt > as if it took the command but there was nothing to display.

Also, i noticed that all the existing users Outlooks were automatically configured for Outlook anywhere once this was 'enabled'.
0
 
LVL 1

Author Comment

by:zequestioner
ID: 37839307
Hello, this worked great but now the problems is that external users have an issue connecting. it keeps popping up asking for a password. but password is correct as I can successfully log into owa, however outlook is not accepting it.
0
 
LVL 1

Accepted Solution

by:
zequestioner earned 0 total points
ID: 37839810
The issue turned out to be the fact that i was using the external hostname on the initial exchange setup wizard instead of the internal hostname. Configuring an external client, I thought that was weird, but Google showed some posts that told me to use the internal name and only use the external hostname via the exchange proxy settings. This proxies the connection to the internal exchange hostname,  so apparently the internal hostname is still a requirement.
0
 
LVL 1

Author Closing Comment

by:zequestioner
ID: 38142499
Self resolved
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…
Suggested Courses

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question