Free/Busy data not available - something to setup somewhere ? (Full Version)

All Forums >> [Microsoft Exchange 2007] >> General



Message

michauko -> Free/Busy data not available - something to setup somewhere ? (5.Mar.2008 8:50:57 AM)

Hello,

I have a problem with a MS Exchange 2007 SP1 (from MSDN - I'm validating the solution before buying/deploying).
For my tests, I have both Outlook 2003 & 2007 - I think the client software isn't the reason of my problem.

Excuse me if I'm not using the right words because it's a french version and I don't know exactly the specific terms commonly used in an english version.

=> When I schedule a meeting, I can't see the free/busy data of the attendees (and outlook can't provide me suggestions of common free date and time).
Beside this, if one of the attendees shares his calendar with me, I can access it. So even without this permission, I suppose I should be able to see the free/busy data of someone when I try to invite him.

If I try to refresh the free/busy data from the "options" button when I'm creating the invitation, I have to wait a few seconds (server request I suppose) then  I have the same result : no data available....

Is there anything to do on Exchange's side ? I checked almost every setting in Outlook and did not find something that could explain the problem on the client's side.
Is it a restriction between standard/enterprise version ? is this due to the MSDN version ?


Thank you for your help... this is a basic functionnality, I don't understand it's not working "out of the box".



Sembee -> RE: Free/Busy data not available - something to setup somewhere ? (5.Mar.2008 11:44:46 AM)

There is no restriction for that feature on MSDN, Standard or Enterprise.

When you configured the server, did you choose the option to enable support for older Outlook versions?
With Outlook 2007 the usual cause is autodiscover is not configured correctly.

Simon.



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (10.Mar.2008 12:54:43 PM)

Hi, thank you for your answer.
Excuse me for the delay before I answered, I reinstalled my entire W2K3+exchange 2007 SP1 (among others things ;)because I did a lot of modification on it and I wanted to be sure the conf was clean.

So, I can confirm the compatibilty for previous client version was checked during installation. I'll try to fix my problem for OL 2003 clients later.
Right now I'm trying to fix it for OL 2007.
With your 1st message, I looked for some docs about autodiscover. I read this : http://www.msexchange.org/tutorials/Uncovering-New-Outlook-2007-Discover-Service.html

It can't apply exactly because the windows XP running outlook 2007 are not on the same NT domain. And it won't be for our productive system. I understood the "magical conf" can't happen, but I suppose I still can fix me busy/free problem (I hope so :)
Can you help me on this ?

- On IIS, the autodiscover application is installed (via the CAS role), I didn't change anything in it.
- On my DNS (which is not on this W2K3 server or domain), I've got the right "A" DNS record that makes my name resolution work, hopefully ;)


Many thanks



Sembee -> RE: Free/Busy data not available - something to setup somewhere ? (10.Mar.2008 2:32:02 PM)

Autodiscover is actually designed for use with sites where the server and the clients are on different domains - think hosted Exchange and you will see where its use comes in.

As long as the public folders are there you should be able to see the free/busy information in Outlook 2003. The availability service should provide the interface between the two formats - the availability service makes calls on the /public virtual directory where the free/busy information is stored. Therefore you have to ensure that public folder access works.
http://msexchangeteam.com/archive/2006/10/23/429296.aspx

Simon.



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (10.Mar.2008 3:05:13 PM)

quote:

... think hosted Exchange and you will see where its use comes in ...

oops, of course !

I'm checking the article you mentionned, and some other on the Internet.
Some clients are now seeing free/busy data, some won't. eg : OL 2003 can see a OL2007-user 's information, but this 2007-user can't see a OL2003'user's information.

O_o

Thank you. I hope I'll find the solution soon (and unserstand it ;)



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (12.Mar.2008 10:56:15 AM)

Ok, I found it.

First of all, I forgot to mention an important detail : my DNS server is running under Linux (bind9) and I'm not using the DNS that comes with my W2K3 running my Exchange 2007.

For outlook 2003 & 2007, all the problems were "because" of that (and because outlook doesn't say anything when it can't find a server it needs to operate correctly !! O_o

For outlook 2003 :
- my exchange test server was called testpc.exchange.mycorp.com (runing in a separate domain named "EXCHANGE")
- outlook managed to add my exchange account based on the short name "testpc" and replaced it by "testpc.exchange.mycorp.com". But actually, because of my DNS conf, my PC was unable to resolve that FQDN. Now that I declared it, outlook can access exchange in a "better way" and then access the "public folders" and then read me the free/busy data...

For outlook 2007 :
- same kind of problem. The article you mentionned in a previous message explained me how "autodiscover" is working. Then I sniffed my DNS server and saw outlook 2007 was silently trying to resolve some DNS records : an A record for autodiscover.mycorp.com and a SRV record named _autodiscover.tcp_.mycorp.com
I declared them and the magic happened :)


By the way, is there any way to change that hard-coded name ? (from outlook's point of view)
I think it's dangerous : if a vulnerability (or misconfiguration I've done) exists in the autodiscover application in IIS, anyone can easily try to find an autodiscover service : it'll be named autodiscover.somecorp.com running on port 443. Am I wrong ?


Anyway, many many thanks for the information you gave. Now I just have to finish some configuration details.



Sembee -> RE: Free/Busy data not available - something to setup somewhere ? (12.Mar.2008 3:52:45 PM)

You cannot change the autodiscover part. That is a standard that Microsoft have introduced. The idea is that Outlook can be configured using some standard information. If you tried to change the name, how would Outlook know what name to use?

Simon.



t0ta11ed -> RE: Free/Busy data not available - something to setup somewhere ? (12.Mar.2008 6:13:01 PM)

quote:

ORIGINAL: michauko
By the way, is there any way to change that hard-coded name ? (from outlook's point of view)
I think it's dangerous : if a vulnerability (or misconfiguration I've done) exists in the autodiscover application in IIS, anyone can easily try to find an autodiscover service : it'll be named autodiscover.somecorp.com running on port 443. Am I wrong?


You can change the autodiscover URL with the command -autodiscoverserviceinternaluri  on the Exchange server if that's what you mean.



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 8:43:43 AM)

quote:

ORIGINAL: Sembee

... If you tried to change the name, how would Outlook know what name to use?

Simon.


With an automatic configuration, of course, one should not change the hard-coded name so that the OL clients can find it.
I just can't understand you can't change it with manual configuration in OL (the manual conf only asks a few settings). Then we could change it at server's side



t0ta11ed -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 11:51:26 AM)

Um, Outlook 2007 will use whatever you change it to on the server side...



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 12:21:27 PM)

Ok, but how can it find the server if it doesn't know where it is the first time ? (I mean, if I changed all the servernames, not URL, to avoid to have a autodiscover.mycorp.com)



t0ta11ed -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 12:27:58 PM)

You should have DNS configured properly so that Outlook finds both the Exchange server and the autodiscover URL. If you're trying to avoid using autodiscovery.mycorp.com, then how do you expect the service to work? You will never see Free/Busy info in Outlook 2007 clients this way if they don't resolve Autodiscover. 



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 12:32:43 PM)

Ok, taht was my point. As we can't force an alternate URL in the outlook client, you have to have a DNS entry called autodiscover.mycorp.com
It means, in case of a serious security issue with this autodiscover application, then one bad guy can try every autodiscover.something.com he wants and try to have "fun".
I mean, you're just giving the exact way to everyone to knock at your autodiscover's door



t0ta11ed -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 1:13:50 PM)

If you change the URL on the server side, Outlook 2k7 clients will use whatever it is, therefore you ARE changing what the client uses. Your DNS entry can point to whatever you change it to, pretty much mitigating the risk you're talking about.

However, I'm not aware of any exploits against this service, authentication is involved in even finding the service, and if only internal clients are using it there is less of a risk assuming all of your internal employees are too technically retarded to actually cause any harm and they can be trusted. If you are that concerned about trusting internal employees, then your security concerns should be focused elsewhere and not on Autodiscover. 



Sembee -> RE: Free/Busy data not available - something to setup somewhere ? (13.Mar.2008 2:51:00 PM)

If there is an exploit found for autodiscover then Microsoft will move very fast to block it... otherwise autodiscover.microsoft.com will get a lot of activity. MS is a very big prize.

Simon.



michauko -> RE: Free/Busy data not available - something to setup somewhere ? (14.Mar.2008 4:52:32 AM)

Yes, I do agree with both of you.
Don't worry, the server will be in a very restricted DMZ, and all the usual operations will be done.

I just think it's strange to force a specific name when you could choose it and specify it in your email client.

Anyway, thank you again for your help about my first steps in MSExchange's world :)



Sembee -> RE: Free/Busy data not available - something to setup somewhere ? (14.Mar.2008 3:46:00 PM)

Be aware that Exchange is not supported in any kind of DMZ - accept for the Edge role which isn't used for Autodiscover.

Simon.



Page: [1]