• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 664
  • Last Modified:

Autodiscover configuration

Hi Experts,
I have Exchange 2010 CAS server that is visible from internet and internal network also.

From internet, that is working well, but internal clients (domain joined computers) using SCP method and they are configured to use RPC over HTTP, which is EXPR provider settings.

Maybe Im misunderstanding something? How I can enforce the internal clients to use EXCH provider that is without RPC over HTTP?
0
Jan Vojtech Vanicek
Asked:
Jan Vojtech Vanicek
  • 10
  • 3
  • 3
  • +1
2 Solutions
 
Sushil SonawaneCommented:
If you configure e-mail user outlook to use RPC over HTTP then outlook not use the SCP method.

If you want to use SCP method then you have to configure another profile for user.

1) Internal : Use SCP method.

2) External : RPC Over HTTP

If user work in home network that time he/shel will use internal profile and outside network that time use external profile.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
Thats not problem. Problem is that SCP method is configuring outlook to use RPC over HTTP.
I dont see the way I can change it.
0
 
Sushil SonawaneCommented:
create a one host record host autodiscover or RPC over http url point to your exchange server in internal dns.

Example

rpc over http FQDN : autodiscover.aa.com
exchage server fqdn : exchange.aa.com

Create a host entry autodiscover.aa.com pointing to your exchange.aa.com in your local dns server.
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

 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
I dont understand what it will solve.

We have internally the scp that is pointing to fdqn of exchnage CAS. It is working, but it is configuring outlook to use RPC over HTTP. I want use only RPC here.

Externally there is SRV record in external DNS that is pointing to the same fdqn. It is working well - as required.

You are describing only to create another path to autodiscover service. But it is not needed.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
Maybe it will be better if I reconfigure the question:
it is possible to setup autodiscover service that way?:
-Internal network - connect to CAS by RPC only
-External network (from internet) - connect to CAS by RPC over HTTP

I cant found anything on that topic.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
I has read that post, Im missing one thing:

in the EMC, I can setup internal and external urls for the CAS,
in autodiscover, there is EXCH section for internal clients and EXPR for external.

How outlook knows if it is connected locally or remotely? Is there any article that can clarify that?
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
May be it isnt possible to setup rpc without proxy by autodiscover with Outlook Anywhere  enabled... By any supported way.
0
 
ExchangePanditCommented:
May be you might want to apply this to your internal clients:

http://www.christitus.com/blog/2011/03/23/disable-outlook-anywhere-in-group-policy-object-gpo/
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
but if I set that by gpo, my notebook users, that are part of domain will be unable to connect from outside of company network...
0
 
ExchangePanditCommented:
Create new OU, move all computers to that and then apply GPO to that new OU, and keep notebook users in the same OU or vice versa.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
yes, but goal of this thread is to set internal outlooks automaticaly to not use proxy and externals to use proxy.
0
 
Simon Butler (Sembee)ConsultantCommented:
If you have Outlook Anywhere enabled, then all Outlook clients will be configured to use Outlook Anywhere. That cannot be stopped.

However that does NOT mean they will use OutlooAnywherere.
Outlook will initially attempt to make a TCP/IP connection and will only use HTTPS if that is not available.

To see what Outlook is using, hold down CTRL and right click on the Outlook icon in the system tray and chConnectionction Status. Look at the protocols. It should say internally TCP.

Nothing else to worry about.

Simon.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
OK, I have experience that setup will slow down the start of outlook if you are on external network - it is trying to connect by tcp and http it tries after timeout, so outlook completely freeze for couple of seconds. That is why I searching for clear solution of this.

So if I need to connect clients internally without outlook anywhere I need a separate CAS server for internal network and for internet access?
0
 
Simon Butler (Sembee)ConsultantCommented:
The delay is because the internal name must resolve externally.
Check your DNS doesn't have a wildcard in it so the names resolve when they shouldn't do.

Simon.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
wildcard domain name *.domain.com is not present i my domain, there is only domain.com A record that is directed to our web server.
0
 
Simon Butler (Sembee)ConsultantCommented:
From an external client, if you ping the server name, do you get a reply or timeout? If things are setup correctly then you should get unknown host or similar error.

Simon.
0
 
Jan Vojtech VanicekIT SpecialistAuthor Commented:
Its propably my completely misunderstanding of autodiscover service. Thank you for advice.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

  • 10
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now