Outlook Anywhere Mixed Mode

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?
LVL 1
zequestionerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

chakkoCommented:
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
ash007Commented:
You need to make setting from Outlook client side to make Outlook anywhere work also need to make sure you have proper certificate
zequestionerAuthor Commented:
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.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

chakkoCommented:
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
zequestionerAuthor Commented:
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'.
zequestionerAuthor Commented:
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.
zequestionerAuthor Commented:
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.

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
zequestionerAuthor Commented:
Self resolved
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.