Exchange Server - Exchange 2007 Cannot directly book meetings

Asked By sawyer
08-Feb-10 01:46 PM
Hello all

I am running Exchange 2007 sp2, the mbx and cas\ht are on separate servers,
I have configured all the exchange web services correctly, all users are
running outlook 2007. Autodiscover, availability,oof, and OAB all work
correctly. Currently I still have a public folder store (left over from a
transition from exchange 2003) I no longer need the public folder store and
I am trying to get rid of it, but I cant. When I dismount the public folder
store, users can no longer book meetings, the error message users get is
dismounted, all users can still download the oab, oof works and free\busy
works, so this tells me that the exchange web services are setup correctly,
the only thing that does not works is directly booking meetings.

All resource (room) mailboxes are setup for "autoaccept" and when the public
folder store is mounted and I use outlook to log into one of the room
mailboxes and click the resource scheduling tab, all the boxes are
unchecked, and this is how it should, this is the correct setting for a
exchange 2007 resource mailbox. Now if I dismount the public folder store,
then go back into the resource mailbox, I can no longer click on the
resource scheduling tab, I get a "not implemented" error, (not sure what
that means) so again, I do not know if I am getting this error because the
mailbox databases are still associated with the public folder store, or if
there is something wrong with the resource booking attendant feature? I cant
remove the public fodler store until I understand what is causing this issue
to occure.

Thanks very much for any assistance with this
Database
(1)
Autodiscover
(1)
Autoaccept
(1)
Attributes
(1)
Mailboxes
(1)
Meetings
(1)
Adsiedit
(1)
Outlook
(1)
  sawyer replied to sawyer
10-Feb-10 04:13 PM
So, I was able to fix this issue.

Used adsiedit and deleted the public folder store from the exchange 2003
administrative group, after doing this the public folder database on the
exchange 2007 server would not mount, but I no longer had the issue with
users not being able to book meetings in resource calendars (so this was a
step in the correct direction) I could not remove the public folder store on
the 2007 server, because it was looking for attributes that got removed when
I deleted the 2003 public folder DB  out of AD using adsiedit. I then went
back into adsiedit and then deleted the 2007 public folder database, and
after this when I launched ESM, I no longer saw public folder database it
was gone, however the mailbox databases were now pointing to an object that
was deleted. This whole time free\busy worked and I could directly book
appointments. I then created a new 2007 public folder database and
associated all the mailbox databases with the new public folder database.
After this I followed this KB to remove the system and default public
folders http://technet.microsoft.com/en-us/library/bb201664.aspx once this
was done I removed the public folder database and this removed it from all
the mailbox databases. NO MORE PUBLIC FOLDERS!!!!

thanks for all the help mvp's
Create New Account
help
directly book meetings. The error they get is resource mailbox for automateprocessing is set to autoaccept. Once I mount the public folder database users can directly book again. when the public folder store is dismounted users can download very strange. Thanks for any suggestions Exchange Admin Discussions Exchange Server (1) Outlook 2007 (1) Database (1) Chong (1) Autodiscover (1) Autoaccept (1) Mailboxes (1) Meetings (1) Outlook 2007 does not use PF for freebusy, OAB etc So if you had read the post you would have known that I was using autodiscover , availability and exchange web services, and that all outlook clients were 2007. In fact I logging into them using outlook, and I also made sure that "automateprocessing" was set for "autoaccept" So I am still way confused as to why when the public folder store is are talking about here. And again all the other exchange web services are working correctly, autodiscover, availability, OOF, and OAB, they all function when the public folder store has been dismounted
Try again later On searching the internet this it seems this may be because the autodiscover service is failing. Testing the autodiscover service with outlook 2007 gives the following error but I can't find a successful solution to this problem. Attempting URL https: / / servername.domain.local / Autodiscover / Autodiscover.xml found though SCP Autodiscover to https: / / servername.domain.local / Autodiscover / Autodiscover.xml starting Autodiscover to https: / / servername.domain.local / Autodiscover / Autodiscover.xml FAILED (0x800C8203) Autodiscover to https: / / domainname.com
Autodiscover Service Exchange Server Hi, I need help on configuring the Autodiscover Service for OAB downloading from Outlook 2007 (Domain Jointed) After 2 weeks research the technical document about configuring the Autodiscover service, SSL, OAB. I still have problem download the OAB from the CAS server. The 06 / 18 / 07 14:54:22 Attempting URL https: / / dvn-hk-mail2007.hk.dvngroup.com / autodiscover / autodiscover.xml found through SCP 3160 20701941 06 / 18 / 07 14:54:22 Autodiscover to https: / / dvn-hk-mail2007.hk.dvngroup.com / autodiscover / autodiscover.xml starting 3160 20702175 06 / 18 / 07 14:54:22 Autodiscover to https: / / dvn-hk
Autodiscover service and related issues Exchange Server We are having some problems with autodiscover. We have a NLB Exchange 2007 CAS server. Clients accessing it via OWA are able are unavailable. New user settings ARE automatically detected and basic connection settings are fine. The autodiscover DNS A record points to the IP address of our NLB cluster. When we test the settings from Outlook we get the following: Attempting URL https: / / <nlb> .<my domain> / Autodiscover Autodiscover.xml found through SCP Autodiscover to https: / / <nlb> .<my domain> / Autodiscover / Autodiscover.xml starting Autodiscover request completed with http status code 404 Autodiscover to https: / / <nlb> .<my