Exchange 2010 calendar(free and busy) cannot work

Hi All
We have a new setup exchange 2010 server.
Everything(Webmail, outlook, autodiscover, out_of_office) is working fine.
When the user check other user calendar, it is not work(no matter in Outlook 2010 or OWA), is there any idea?
Thanks

Hi there
All the user is located in the same site.
The most weird problem is the user using the OWA for checking their own free and busy, it is show no information.
I have tried o use remote connectivity analyzer and the test-outlookwebservice
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1011
Type : Error
Message : When querying Availability for the recipient e-mail address abc@xxx, the following error code and
message were received: ErrorServiceDiscoveryFailed:Unable to find a Client Access server that can serve a
request for an intraforest mailbox <abc>SMTP:abc@xxx.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at https://xxx/EWS/Exchange.asmx. Elapsed time was
12 milliseconds.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1013
Type : Error
Message : When contacting https://xxx/EWS/Exchange.asmx received the error The request failed with a
n empty response.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at https://xxx/EWS/Exchange.asmx. Elapsed time was
249 milliseconds.
But those ews path can be reach when using the browser
Thanks

Similar Messages

Exchange 2010 Out of Office Assistant not working?

New server with a new Exchange 2010 install into an existing domain...
When users on both the internal network and external network try to access the Out of Office Assistant they get an error message of: " Your Out of Office settings cannot be displayed, because the server is currently unavailable".
I have done tons of research on WebServicesVirtualDirectory and AutodiscoverVirtualDirectory and set both internal and external URL's that work if you go to them in IE )internally and externally offsite).
Here are the settings of Autodiscover and Webservices:
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | Format-List
RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
CertificateAuthentication :
InternalNLBBypassUrl : https://MAILSERVER.domain_name.local/ews/exchange.asmx
GzipLevel : High
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
Server : MAILSERVER
InternalUrl : https://MAILSERVER.domain_name.local/EWS/Exchange.asmx
ExternalUrl : https://mail.domain_name.com/owa
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exchange Adm
inistrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=M
icrosoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=local
Identity : MAILSERVER\EWS (Default Web Site)
Guid : 4639e4b9-9cf3-4f92-8940-f7c31e07cd47
ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged : 4/1/2010 2:47:37 PM
WhenCreated : 3/11/2010 11:02:22 AM
WhenChangedUTC : 4/1/2010 8:47:37 PM
WhenCreatedUTC : 3/11/2010 6:02:22 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain_name.local
IsValid : True
[PS] C:\Windows\system32>AutodiscoverVirtualDirectory | Format-List
RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
Server : MAILSERVER
InternalUrl : https://MAILSERVER.domain_name.local/autodiscover/autodiscover.xml
ExternalUrl : https://mail.domain_name.com/autodiscover/autodiscover.xml
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exc
hange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organiza
tion,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=loca
l
Identity : MAILSERVER\Autodiscover (Default Web Site)
Guid : 7a234ea2-20fc-412b-bbf0-3ea5f965d8da
ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 4/1/2010 3:00:49 PM
WhenCreated : 3/11/2010 11:02:07 AM
WhenChangedUTC : 4/1/2010 9:00:49 PM
WhenCreatedUTC : 3/11/2010 6:02:07 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain_name.local
IsValid : True
Test-OutlookWebServices comes up with errors. The Test E-mail AutoConfiguration within Outlook still appears to be looking for Autodiscover at different URLs...
OOF within Outlook Web App functions.
Any suggestions would be helpful!

From your previous post, I understand that OOF doesn't work for both internal and external clients. Error message "Your Out of Office settings cannot be displayed, because the server is currently unavailable" was received from Outlook client side. Please correct me if I have any misunderstanding.
Before we go any further, I would appreciate your help in clarifying the following questions:
1. When did this issue begin to occur, since the installation of Exchange 2010?
2. Can we access and configure OOF from OWA?
As internal & external clients are using different methods/URL to access Autodiscover and EWS, which provided OOF service, I recommend we focus on the internal users first.
To troubleshoot this issue, please install the hotfix mentioned in the following KB on the Exchange Client Access Server first:
Outlook 2007 crashes or you cannot access OOF settings after you install a package that contains the .NET Framework 3.5 with SP1 and the .NET Framework 2.0 with SP2 on an Exchange 2007 Client Access server or on an Exchange 2010 Client Access server
http://support.microsoft.com/kb/958934
After that, check if the issue remains. If there is still problem, please help me collect:
1. Test E-mail AutoConfiguration from Outlook client
1. Launch Outlook 2007 using a correct configured profile.
2. Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area.
3. In the menu that appears, click Test E-mail AutoConfiguration.
4. Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes.
5. Choose the desired auto configuration methods with Use Autodiscover, clear other selection.
6. Click Test.
7. Please send me the screenshot of the result tab and log tab.
2. Result files after running the following command on the Exchange 2007 server
Get-ExchangeCertificate | FL >C:\cert.txt
Get-WebServicesVirtualDirectory –Server ServerName | FL >C:\EWS.txt
Get-AutodiscoverVirtualDirectory –Server ServerName | FL >C:\Audis.txt
Get-ClientAccessServer | FL >C:\cas.txt
Email them to me at [email protected]
With the title as
"Exchange 2010 Out of Office Assistant not working?"
Regards
Fazal M khan

Exchange 2010, UCC SSL, and the "new" CA/BROWSER Forum not issuing for .local

I don't know how many people have run into this yet, but the CA/BROSWER Forum, the "standards" authority for SSL issuing, has mandated that CA's can no longer issue a certificate using a FQDN "intranet" name for new or renewal SSL certificates effective
Nov 1, 2012. i.e. the Microsoft standard of mydomain.local will no longer be accepted as a SAN on a UCC for Exchange 2010. I've looked thru the KBs and Social forums, but haven't really found any guidance on how to solve this. I'm presuming
that the certs will have to be split and the "external" domain name of server.mydomain.net will just become a single server SSL, and the internal name of server.mydomain.local will become a Self-Signed certificate. With the increasing prevalence of OA
and ActiveSync devices, is there any baseline guidance yet on how to make this happen without completely fouling up production servers and killing access to the user community?

On the same topic, though likely different environment...
Against recommended deployment, I have a number of clients running all their services on one box. Windows Server 2008, Active Directoy, DNS, Exchange 2010 ...and so on. These servers all have .local addresses, which means of course that the SAN
certificates have .local addresses as one of the SANs.
I've read alot online about this issue, and am trying to find the most cost effective solution to switch numerous production servers running this configuration.
The best solution I've come up with so far is...
1. Virtual AD with new external domain, 2. Migrate Exchange CAS to this domain, 3. Reconfigure network through the box.
Obviously these steps will contain alot more details, but this is just the outline atm. At best, I see me having to take a second box with me to each location to perform these steps, and I can't see it happening without disruption to the work flow
of employees.
Thankfully, all of these businesses are relatively smal...under 25 employees. Still, I'd like to find the smoothest transition solution possible.
Any suggestions would be greatly appreciated!
Regards

Exchange 2010 management tools and others

Win2k8 domain, Exchange 2010 servers
We want to move to Win8.1 but we, the admins, are preventing it because our tools like the Exchange 2010 Management tool doesn't work with Win8.0 so we're stuck with Win7.
I've googled around and most suggestion never worked.
Does Microsoft have any plans at all to have Exchange 2010 management tools and other tools we use to manage our domain work with Win8.1?

Hi Rino,
Thanks for your sharing and efforts put on this issue.
This will benefit others who encounter the similar scenario as yours.
Happy holiday~
Kate Li
TechNet Community Support

Exchange 2010 calendar not showing on outlook 11 Mac

Exchange 2010 calendar not showing on Outlook 11 Mac on my iMac. It shows fine on iPhone and OWA.

Since this question is about a Microsoft product, you might have more luck getting suggestions if you ask in Microsoft's own forums.
Regards.

Real-world experience with Exchange 2010 SP3 RU5+ and Powershell 4?

The support-ability matrix for Exchange (http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx) says Exchange
2010 SP3 RU5+ and Powershell 4 are compatible. But, there is very little actual discussion about how well that works.
I use Powershell extensively for mission critical and somewhat complex processes, with Exchange 2010 on 2008 R2 and AD access/reads/updates.
Can I get a summary of the caveats and benefits from someone who has actually done this in a
real-world/production scenario (more than one server, managing from a separate non-Exchange server), and who has scripting experience with this configuration?
Also, how has this affected EMC operations?
As always thank you in advance!

I believe the matrix states that its supported to install Exchange into an environment where __ version of WMF is present. Exchange 2010, launched from a Win 2012 server, reports version 2.0 when you call $host. For example, calling the ActiveDirectory
module from EMS on an Win 2012 server (ps 3.0) fails.
I'll double check the extent of this scenario and get back to you.
Mike Crowley | MVP
My Blog --
Planet Technologies

My MBP mid 2010 display blackout and froze while working but my keyboard light will still light up. Won't be able to retrieve it and have to hard shutdown. Sometimes it happens a lot. Wether it connected to power or not, it will blackout on and off. Pleas

My MBP mid 2010 display blackout and froze while working but my keyboard light will still light up. Won't be able to retrieve it and have to hard shutdown. Sometimes it happens a lot. Wether it connected to power or not, it will blackout on and off. Please advice what shall I do.

Do you have a 15" mid-2010? If so then your problem is surely...
Mid-2010 15" MacBook Pros - the bad NVIDIA GPU
If you're having frequent kernel panics with your 15" mid-2010, or intermittent screen problems, the problem is, more than likely, the faulty NVIDIA GPU found in a number of those machines.
Here's just a sample of a kernel panic log that points to the faulty NVIDIA card:
Kernel Extensions in backtrace (with dependencies):
         com.apple.GeForce(6.4.0)@0x82ac4000->0x82b7afff
            dependency: com.apple.NVDAResman(6.4.0)@0x834a0000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x82fd3000
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a802000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x8301b000
         com.apple.nvidia.nv50hal(6.4.0)@0x83c05000->0x84019fff
            dependency: com.apple.NVDAResman(6.4.0)@0x834a0000
         com.apple.NVDAResman(6.4.0)@0x834a0000->0x8378dfff
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a802000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x82fd3000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x8301b000
Here's the "official" Apple take on the issue - but the very real kernel panics need not be preceded by 'Intermittent black screen or loss of video'... in fact, you might not experience any video problems at all. Although video problems can certainly be a portent of things to come…
So what can you do? Print out a copy of your kernel panic and a copy of the Knowledge Base article and take them, along with your machine, to your local Apple Store or an Apple Authorized Service Provider. The unfortunate thing is that many people have passed the “three years from date of purchase” now and Apple is not honoring the free logic board replacement for many users. Some dealers seem to be making some exceptions for those past the three year mark, but don’t count on it…
Good luck,
Clinton

Hello! I have a printer,Canon MP250 and I bought a new MacBookPro with Maverick and I cannot work this printer

Hello! I have a printer,Canon MP250 and I bought a new MacBookPro with Maverick and I cannot work this printer with the driver that came with the printer and I've tried to find an update but with no success, can you help me?
Thanks!!

you can try resetting the network settings in settings or you can try doing a reset - hold down the home/power button together until you see the apple logo and then release. Then wait for the phone to boot back up. You won't lose any data.

CUP 8 Support for Exchange 2010 Calendaring

Will Unified Presence 8.5 support Exchange 2010 calendaring?
Thanks!
Jeff

That's the plan. Nothing is guaranteed until it reaches FCS though.

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

Exchange 2010 Rollup 2 SP3 update cannot find installation package exchangeserver.msi file on SBS 2011... NEED HELP!!!

Hello,
I am running a windows SBS 2011 standard system and there was currently an update for Exchange 2010 Rollup 2 Service Pack 3 and it keeps failing. It says that it cannot find the installation package (exchangeserver.msi) and it is looking for it
in E:\Software\Exchange2010-SP3-x64\ folder but there never was this folder. There is only an Exchange2010-SP3-x64.exe file.
The only exchangeserver.msi file that I find on the server any where is in C:\ProgramFiles\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1 but it won't accept it (says not authorized for this update or something alike).
Please help. It is currently causing issues with email. Some of the features are not working because it says exchange is currently under maintenance.
Any suggestions would be greatly appreciated. Thank you.

Susan you are correct: After I installed Exchange 2010 SP3, I deleted the msi just to "clean up' my hard disk... While trying to install Rollup 2 for SP3, the installer is trying to find it. I downloaded the installer, used 7-zip to get
the msi and I pointed the installer to it when asked.
The installation failed 3 times...
NOTE: I was using WSUS to install the Rollup: I downloaded the Rollup installer and I executed: I could see where the installer was hanging up! First it asked me to stop an SBS service and something else (sorry I do not remember), I stopped
the services and installation continued. Then it asked me for more files from the SP3 installation which I found on the installation folder that I created with 7-zip. I copied to the path that the installer was looking and installation finished
(finally!)...
NOTE 2: If you have any firewall appliance that denies Internet access to un-authenticated requests, you better turn that rule off because the installer accesses the internet (not sure why - probably for Dot Net assemblies)...
Susan THANKS for all your help to the community! You have helped so much!
All the Best
Constantine

Exchange 2010 accepted domain and email address policy

So I need some help as to which accepted domain is right for us. We are a single forest single domain that is subbed to a parent domain.
sub.domain.com
We run our own exchange 2010 separate from domain.com. We want all mail to show up as @domain.com for our users. The @domain.com will be configured to forward to @sub.domain.com. This is free Linux mail server that is separate from us.
In order to configure an email address policy for @domain.com I need to pick from the 3 types. I am pretty sure we are not authoritative for @domain.com (they are the parent). So it is either an internal relay or external relay. We all
use the same networking, and our DNS servers point to domain.com as forwarders and they host a secondary copy of our DNS.
It is a little unclear as to which to use. I have gone to each account individually to test, and that works perfectly, but I would like to set this Globally.
Thanks
Tim

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010 Certificates, IPs, and Domain Names...

I'm setting up a new Exchange 2010 server, migrating from an old Exchange 2003.
I'm at the point now where I'm stuck and cannot move the mailboxes of the users to the new server until I get the new server setup with certificates, reconfigure the firewall, and more Aname records. ... reason, I'd like to take advantage of the autodiscover,
sync, outlook anywhere, etc.
I've been tossing ideas around but I think I'm over thinking this entire thing on domain names, anames, certificates, etc.
Can someone tell me what the best practice would be for creating the CSR? And I'm a bit curious as to IPs.
While the examples in the New Exchange Certificate wizard all show 'mail.contoso.com' I wanted to be more specific on the functions of each but maybe I'm causing myself a lot of extra work. Each full aname needs pointed to a different public IP from my understanding
of the certificates. Can anyone tell me if this approach(below) is best practice or far from it?
I'm very intrigued with the capabilities but dont' understand why MS would use as an example the same domain name, mail.contoso.com for each function. But it may be because they'd just have to point to one IP address whereas I'll have to point several IPs
public to a single IP internal.
I'm just asking for suggestions... and ideas... and how you setup your exchange 2010
I was going to create:
Outlook Web App:
webmail.domainname.com,domainname.com
Sync:
sync.domainname.com,domainname.com
Autodiscover:
domainname.com
Outlook Anywhere:
outlook.domainname.com, domainname.com

Not sure I understand - but why do you want to map each individual service to an individual public IP ? Usually the trend is to keep as little public IPs as possible (you can get away with 1 public IP for the CAS role). For autodiscover, I've usually seen
the autodiscover.domainname.com being used, due to the domainname.com reserved (public site) - this actually keeps inside the logic used by Outlook clients to autodetect the servers (see
this link).
As for the Subject Alternate Names (SANs) on the certificate itself - it all depends whether you're publishing the server directly (in this case you'll want to get away with as little SANs as possible) or you'll use a reverse proxy (TMG/WAP) to publish the
internal box (in this case the certificate on the reverse proxy can contain little SANs, but the internal server can have SANs map to each service if you want).
Also - Allen's link is a definitely must read.

Exchange 2010+Outlook Anywhere+Windows XP not working together

Hello,
We have Exchange 2010 installed on Server 2008 R2. CAS/Hub/mailbox roles on same server. Outlook Anywhere is enabled and using a Go Daddy signed certificate for OWA. Now my problem is that Windows XP (w SP3) PC's that are not located inside domain and
shoud use Outlook Anywhere cannot connect to that service. Outlook version is 2007 SP2. On the other hand, that same user can connect from a Windows 7 pc what is also located outside domain without problems. On XP pc windows keeps asking for password repeatedly,
on W7 pc it asks it and accepts and logs the user in and connects it to his mailbox. I have read numerous posts about this kind of issue, put so far none of them helped me. The certificate is issued to mail.domainname.ee and autodiscover.domainname.ee. The
internal name of the server is excha.domainname.ee, external name is mail.domainname.ee. Also I used the Set-OutlookProvider cmdlet to set EXPR to msstd:mail.domainname.ee and also tried msstd:excha.domainname.ee this change did not have any effect on XP pc.
What is wrong in XP and Outlook 2007 combination not being able to connect to Echange 2010?

I was suffering from a very similar issue. The one major difference for me is that I was using a wildcard ssl certificate for "*.contoso.com" which was not matching with the server name of owa.contoso.com.
Behaviour definitely seemed to only manifest with Windows XP on the open internet (not domain joined or internal) trying to use either Outlook 2007 or 2010 to connect to our internal Exchange 2010 server via RPC over HTTPS. Autodiscover was successful
but user would be repeatedly prompted for their credentials but they would never match.
The key changes that seemed to fix this for us were to make these updates -
Set-OutlookProvider EXPR -CertPrincipalName msstd:*.contoso.com
alternatively if you dont care whether the proxy server name exactly matches your ssl cert you can do this (not recommended) -
Set-OutlookProvider EXPR -CertPrincipalName none
These commands manipulate the Microsoft Exchange Proxy Settings under the Outlook Anywhere options under the connection tab of your mail profile. In particular the field labeled "Only connect to proxy servers that have this principal name in their
certificate"
Also, to force RPC over HTTPS and never try and timeout on TCP/IP connection (which cannot work through the firewall) -
Set-OutlookProvider EXPR -OutlookProviderFlags:ServerExclusiveConnect
This should click the checkbox for "On fast networks, connect using HTTP first, then connect using TCP/IP"
This should then allow autoconfigure to work fine when setting up your mail profile. If you want to check the settings page you should have something that looks like this -
Finally, please note that Autodiscover settings are updated periodically not instantly. I believe it is something like every 15m or so. As such, make the changes above and then wait for at least 15-30mins before making any other changes.
I ended up chasing my tail and then some complete red-herring *seemed* to fix the problem. It was actually something that I had changed 20mins before!

Exchange 2010 calendar meetings - allows meeting to be sent then sends decline message

We updated from Exchange 2003 to 2010 last year and are still trying to figure out how to make the resource rooms work properly. In 2003, if you tried to schedule a meeting and the room was not available, it would not let you send the request.
2010 does and then sends back a decline message. Can this be changed to be like 2003?

Is there not a way to have Outlook reject the meeting before sending it (like exchange 2003 did)? I know you can see this in scheduling assistant but not all users use that unfortunately....they just type in the names and send. Before
in Exchange 2003, it would check availability before sending and NOT send the meeting at all if the room was not available. That is what I would like to get back to.
Nope. Not possible in Exchange 2010 or 2013 using the built-in Exchange Calendar Asst features. Direct-booking is not recommended and Outlook 2010 and above do not allow it by default.
That is by design, allowing the server to manage and handle the meeting request logic.
The reason being is that there is now built-in delegate moderation, in-policy and out of policy requirements etc... The resource mailbox has no way of knowing if the meeting request meets or fails the requirements without receiving it first.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 calendar(free and busy) cannot work

Similar Messages

Maybe you are looking for