Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 558
  • Last Modified:

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?
0
zequestioner
Asked:
zequestioner
  • 5
  • 2
1 Solution
 
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
0
 
ash007Commented:
You need to make setting from Outlook client side to make Outlook anywhere work also need to make sure you have proper certificate
0
 
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.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now