Outlook anywhere issue for exchange 2010 users

Hi Guys really hoping some one can help me out here.
I have just introduced 2 new exchange 2013 servers into our existing exchange 2010 environment. 1 CAS server and 1 mailbox server.
The issue i'm having is that any users that are on exchange 2010 mailbox servers can't connect to their profiles in outlook via the exchange 2013 cas box. OWA works fine and users that are on exchange 2013 mailboxes also work fine.
Authentication is set to on exchange 2013 and 2010 cas boxes to
Exchange 2013 cas
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2010 cas
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm}
I was also wondering should I have a reg key on my exchange cas box of HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy\validports_autoconfigure_exchange ???

Thanks for the reply i have changed it to the following
Exchange 2013 cas
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2010 cas
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm}
and reset iis but still no luck authenticating with outlook on existing profiles or a new profile.

Similar Messages

Outlook Client Issues following Exchange 2010 Rollup 8

Update Rollup 8 For Exchange 2010 SP3 (KB2986475) was applied to our Exchange server last night.
All appears to be fine, but users are having all kind of trouble using the Outlook Client to connect to their mailboxes.
Randomly they can't view certain folders (Inbox/Sent Items). Can no longer save to their Calendars. Errors relating to permissions and Outlook notifications?!?!?!?!
This is ONLY when using the Outlook Client - webmail works fine.
There are also no issues when running Outlook in safe mode.
Any advice would be very much appreciated.
Thanks
David

The following has been posted onto the Exchange team site:
http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
Update 12/10/2014:
An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the
new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.
The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish
further updates to this blog post regarding RU8.
This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange OWA does not load OWA for Exchange 2010 users

I have recently installed Exchange 2013 SP1 CU4 in my existing Exchange 2010 SP3 environment but when I use Exchange 2013 OWA to login Exchange 2010 users (it should automatically take the user to Exchange 2010 OWA) but I get this error message "Forbidden
403- Access is denied". However exchange 2010 users can login to their /ecp directory from exchange 2013. Exchange 2010 users can use OWA using their exchange2010/owa URL without any problems. We do not have any http or https redirection enabled
on any of the server. Also I have tried to uncheck the "Required SSL" settings for default web site on both Exchange servers but error is still same. Any help will be highly appreciated.

Hi,
According to your description, your Exchange 2013 cannot proxy OWA request to Exchange 2010 server, but ECP　request　can work properly.
In this case, Ｉ'd like to confirm OWA and ECP settings on Exchange 2013 and 2010 servers before going further:
Get-OWAvituraldirectory |fl identify,*url,*authentication
Get-ECPvituraldirectory |fl identify,*url,*authentication
Thanks,
Angela Shi
TechNet Community Support

No Free/Busy Information for Exchange 2010 users in Outlook 2010 client, 2010 OWA shows this information fine

I have looked for hours and hours on Google and this web site for this type of issue and nothing seems to help.
Problem:
On my new Windows 2008 R2 /Exchange 2010 server with IIS7 installed, I can use Outlook 2010 client to login and send and receive e-mail but when I try to busy search internal Exchange users I get no information (cross-hatch), but the sender of the Meeting Request
can see their own free/busy information fine. And OWA users can see free/busy information fine, as can Outlook 2003 client users against this Exchange 2010 server when logged in.
I don't know if I have a certificate problem with regard to IIS7 or Exchange 2010, I did not create my own certificate , it is just what was installed by default when I installed and configured Win2K8 server, IIS7 and Exchange.
On the Windows 7 workstations with Outlook 2010 client, I am not logging into the Exchange 2010 server DNS domain, if that makes any difference. On these workstations I can ping "autodiscover.my.exchange.server.com" and my.exchange.server.com
with no problem. I even used this Microsoft KB to install a new _autodiscover dns entry, but it did not help :
When I turn on logging on my Outlook 2010 client, I see this in my C:\Users\Administrator\AppData\Local\Temp\1\outlook logging\20131208-135658864-fb.log :
2013/12/08 13:56:58.864: Getting ASURL
2013/12/08 13:56:58.864: URL returned from cached autodiscover: blah blah
2013/12/08 13:56:58.864: Request to URL:
2013/12/08 13:56:58.864: Request action:
2013/12/08 13:56:58.864: Request XML: <?xml version="1.0"?>
2013/12/08 13:56:59.051: Request sent
2013/12/08 13:56:59.051: Response error code: 00000000
2013/12/08 13:56:59.051: HTTP status code: 0
2013/12/08 13:56:59.051: -------------------------------
2013/12/08 13:56:59.051: There is an error in request/response.
2013/12/08 13:56:59.051: XML response:
2013/12/08 13:56:59.051: -------------------------------
2013/12/08 13:56:59.051: Getting ASURL
2013/12/08 13:56:59.644: Failed to get ASURL. Error 8004010F
At an Exchange shell console I enter this command and get these results :
Exchnage Management Shell :
VERBOSE: Connecting to BPExchange2010.my.exchange.server.com
VERBOSE: Connected to BPExchange2010.my.exchange.server.com.
[PS] C:\Windows\system32>Test-OutlookWebServices -id:[email protected] -TargetAddress:[email protected]
ll.com
RunspaceId : c929eacd-d53c-49d7-8532-c4b74e61b8be
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is
Type : Success
Message : [Server] Successfully contacted the UM service at https://bpexchange2010.my.exchange.server.com/ews/exchan
ge.asmx. The elapsed time was 234 milliseconds.
[PS] C:\Windows\system32>
** Also frequently when I log into Outlook 2010 client and start to send a meeting request , I get the Security Alert dialog :
autodiscover.my.exchange.server.com
Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
Green Check Mark : The security cerficate is from a trusted certifying authority
Green Check Mark: The security certificate date is valid
Red X : The name on the security certificate is invalid or does not match the name of the site.
Do you want to proceed ? . I either import the certificate or click YES, but does not help this issue.
NOTE: Each user that shows as NO INFORMATION cross-hatch, these users have appointments and have logged into outlook before.
When I do this autodiscover url from a Windows 7 pc with outlook 2010 I get :
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="14:47:01.5656198" Id="401440650">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Can anyone assist ? What am I missing ?
Thank You
NOTE: When will this go away. I had to strip out a lot of helpful information to post this. "Body text cannot contain images or links until we are able to verify your account."

Hi,
How many users encounter this issue, all users with Outlook 2010 or some specific users?
According to your post, the Error code 600 indicates that your Autodiscover service is working well. as for the certificate mismatch issue, we can also following the KB below to resolve it:
http://support.microsoft.com/kb/940726/en-us
The Free/Busy information in Exchange 2010 is using the Availability service to
retrieve it. Please directly access
https://mail.mydomain.ae/EWS/Exchange.asmx in IE and see whether a proper XML file is returned.
Or we can go to
https://testexchangeconnectivity.com and check MS Exchange Web Services Connectivity Tests.
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 in coexistence with 2010, Outlook keep looking for Exchange 2010 server slow connection

All,
not sure if this topic has already answered, but can't find anything around.
Here's the scenario. Migrating from a single Exchange 2010 to a cluster of 2 + 1 Exchange 2013. Two in a site, One in the other site (DC).
I have migrated successfully a firsat batch of users. Mail flow works perfectly. The only thing is that often the migrated users are experiencing a long time (about 30 minutes) to get their Outlook syncronized. Both OL 2010 and 2013 doesn't make any difference.
They're using OL Anywhere, and I've already tried to rebuild the profile.
From a check on the OL connection status, looks like they're still looking for something on EX2010, but no idea what could be. If I disable the cache mode it works smooth and quick.
My best guess is that is something in cache they're trying to keep updated... but still this doesn't explain the huge delay.
Any help would be highly appreciated!
Thanks!

Hi Alessandro,
What happens in OWA? I guess it should be good.
Did you have public folders with Exchange 2010? Were they moved over to Exch 2013? Technically you should move the PF to the latest version from the legacy version before moving over the users?
- Moved the PF to OL2013. same behaviour
May be the outlook clients are looking for th OAB? Did you move the OAB to Exchange 2013?
- Did this too.
Try running outlook on safe mode and see what happens? may be one of the outlook add-in's are looking for something on Exchange 2010?
- Will try that....
Can you do a Test Email Auto Configuration in outlook (Hold CNTRL key and right click on outlook icon on status bar) and see if the exchange url's are pointed to Exch 2013?
- Will try that....
Is this happening to all migrated users or specific? Are they BlackBerry users?
- All users and there are no BB users
Do you have any archived emails on those migrated users? May be outlook is looking for some archived stuff on the Exch 2010 side?
- I instructed Exchange to migrate also the archiving database, however There are no archived mailbox on 2010
Could this be because of any calendar entries? May be migrated user mailboxes are having issues with working with non-migrated mailbox calendars?
- This maybe a possibility. I have only 10 users actively using Exchange, while all others have the mailboxes only because they've Lync. I've completed all migrations today, so there shouldn't be anything left on 2010
Let me know how it went - all the best!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

Prepping New Child Domain for Exchange so Users can use it

I have a new Child Domain that needs a "prep" for Exchange 2010 User objects. Instructions don't indicate on which DC this "prep" needs to be made.
Anyone done this before? Thank you!!
Charlie

Hi ,
You can prefer anyone of the domain controller in the child domain for preparing the domain .
Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTermsReference link : http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspxOn that above link please refer the topic "Let me choose which Active Directory domains I want to prepare"RegardsS.Nithyanandham
Thanks & Regards S.Nithyanandham

Exchange Server 2013 Outlook Anywhere issue

I am working on an issue with Outlook Anywhere in Exchange 2013 where external users cannot connect. This is a new server co-existing with an Exchange
2010 server that will soon be decommissioned.
When I run an Outlook Connectivity test on testexchangeconnectivity.com I get the following error. I am not seeing anything in the application or system logs.
I already applied CU 6 (which was released today) and am seeing the same results. Port 443 is exposed directly to the web (no TMG, load balancer, proxy server, or SSL accelerator). Any help would be greatly appreciated!
Attempting to ping RPC proxy <external Exchange URL>.
RPC Proxy can't be pinged.
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: Microsoft.Exchange.Tools.ExRca.Extensions.MapiTransportException
Stack trace:
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
at Microsoft.Exchange.Tools.ExRca.Tests.MapiPingProxyTest.PerformTestReally()
Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at RpcPingLib.RpcPing.PingProxy(String internalServerFqdn, String endpoint)
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
Elapsed Time: 290 ms.

Hi,
Does the issue only happen to your Exchange 2013 external users? How about Exchange 2010 users?
Please make sure the external host name in your external Exchange URL is pointed to your Exchange 2013 in public DNS. For your coexistence environment, please make sure the Outlook Anywhere configurations are correct in both Exchange 2010 and Exchange 2013.
We can run the following command to check it:
Get-OutlookAnywhere | FL
If the configuration is not correct, we can run the following command to set it(supposing the mail.domain.com is your External host name):
For Exchange 2010:
Set-OutlookAnywhere -Identity “E14-01\Rpc (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods NTLM, Basic
For Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalHostname mail.domain.com -ExternalHostname mail.domain.com -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl
$True -InternalClientsRequireSsl $true
After all settings, please recycle MS Exchange RPCProxy AppPools and Default AppPools on both Exchange 2013 and Exchange 2010. Then restart IIS service by running IISReset /noforce from a command prompt window.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2007 Clients Cannot Access Free/Busy Calendar info. for Exchange 2010 Mailbox

Hi:
I have Outlook 2007 clients that cannot access Free/Busy Calendar info. for Exchange 2010 mailboxes. They receive error like "...you do not have appropriate permissions..."
If those same users logon to a machine running Outlook 2010 then they can view the free/busy info. of the other user's mailbox, so I believe the permissions are set correctly on the mailbox to allow the viewing.
Any insights are greatly appreciated!
Thank you!
Bob Herman IT Tropolis

Hi Herman,
As you said, it seems users have proper permissions on mailbox.
Please make sure users has Reviewer permission on Outlook 2007.
Please try to run Outlook 2007 under safe mode or re-create profile.
Also try to turn Outlook 2007 to Exchange Online mode from Cached mode.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 2007 co-existence Outlook Anywhere issues

Sorted out all other issues (apart from a SSO issue- another thread) . Activesync, autodiscover etc all working- but Outlook Anywhere does not work for Exchange 2007 external mailboxes. It does work for 2013 mailboxes internally and externally-
and 2007 mailboxes internally.
Exchange 2013 SP1. Exchange 2007 Sp3 RU10. Legacy namespace is in use and on certificate. Outlook Anywhere IIS Authentication is set to Basic and NTLM on both 2007 and 2013 servers. Outlook Anywhere external client authentication is set to Basic.
Any sugestions what to look at next?

Tony,
I apologize for the stupid question, but was Outlook Anywhere working on Exchange 2007 before you started the upgrade?
When you open command prompt on Exchange 2007 and ping the Exchange 2007 internal FQDN or NetBIOS name, do you get an IPv4 address or you get the IPv6 one?
Step by Step Screencasts and Video Tutorials

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Outlook anywhere not workinhg , exchange 2013

i have exchange 2013 environment everything is working fine except outlook anywhere iam using TMG 2010 for publishing rule (OWA , Active sync and OA ) all are working fine except OA
when i try to configure outlook user his computer not in domain it keep asking for username and password during configuration and after 2 times asking the password it shows the attached screen with no success
can you advice why this happening ?

this happen to all users , no one can use OA but others services like OWA and active sync working fine with all , they all configured in same TMG sever with same listener
get-outlookanywhee | fl output as below
RunspaceId                         : 8153f39f-76d2-4b02-8b4b-fdd8fa9f4977
ServerName                         : severname
SSLOffloading                      : True
ExternalHostname                   : webmail.xxxx.com
InternalHostname                   : webmail.xxxx.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://servename.xxxxx.local/W3SVC/1
                                     T/Rpc
Path                               : C:\Program Files\Microsoft\Exchange
                                     Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 847.32)
Server                             : servername
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=P
                                     cols,CN=servername,CN=Servers,CN=Exchan
                                     Administrative Group
                                     (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=xxxxxx
                                     Co,CN=Microsoft Exchange,CN=Services,C
                                     nfiguration,DC=xxxxx,DC=local
Identity                           : servername\Rpc (Default Web Site)
Guid                               : b667bc75-2280-4b1b-99cd-9991b2300f6e
ObjectCategory                     : xxxxxx.local/Configuration/Schema/ms
                                     h-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory,
                                     msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/18/2014 6:07:17 PM
WhenCreated                        : 11/4/2014 9:07:48 AM
WhenChangedUTC                     : 12/18/2014 2:07:17 PM
WhenCreatedUTC                     : 11/4/2014 5:07:48 AM
OrganizationId                     :
OriginatingServer                  : DC.xxxxx.local
IsValid                            : True
ObjectState                        : Changed
note
my domian xxxxxxx.local and my extrenal url webmail.xxxxxx.com

Rollup 6 for Exchange 2010 SP3

Does anyone know when Microsoft is going to release either Rollup 6 or a patch for Exchange 2010 SP3? Rollup 3 for SP3 introduced the following issues:
“Some users (not all of them) report that they don't see new emails in their Outlook 2010 box on Shared folders, even though they got the new email message envelope. When they change folder and back to the Inbox the new mail is suddenly visible. Same sort
of "delay" happens when users mark a message for follow-up or try to change a message from unread to read.”
We have installed Rollup 5 but it did not address the issue.
Thanks
Dave

Hi,
Currently, there is no official document about the release of RU6 for Exchange 2010 SP3. If the RU6 for Exchange 2010 SP3 will be coming, you can find this information in the Exchange Team Blog.
http://blogs.technet.com/b/exchange/
Thanks for your understanding.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Weird issue with Exchange 2010 Room Mailboxes - allows multiple booking of the created meeting rooms

Hi,
we are facing weird issue with Exchange 2010 Room Mailboxes
it allows multiple booking of the created meeting rooms.Sometime we are not getting acceptance or declined mail but and we could see our meetings has been booked at slot.
for e.g.
User A booked room1 with weekly recurrence for time 4pm to 5pm., and User B made his booking other day,without realizing that user A meeting is exists.
Neither of user A nor user B got declined/rejected emails.
please sahre guidelines if anyone known to this issue.
Note - Allow Conflict booking is disabled already :) but still have issue
Thanks,
NPratik

Hi,
Just add more in this issue, following testing is done.
referring results and conclusion, you will get better view on issue
====================
Test Case - 1
User OnCloud/O365 - Pratik Nimbalkar
Email ID - [email protected]
( same as UPN)
Room Booking Scenario - Book Room for 6.30pm to 7.30pm slot
Results - Accepted
Room Booking Scenario for same slot- ReBook Room for 6.30pm to 7.30pm slot
Results - Declined
Conclusion = working fine
==================
Test Case - 2
User OnCloud/O365 - Testsm
Email ID - [email protected]
( different from UPN)
Room Booking Scenario - Rebook Room for 6.30pm to 7.30pm slot
Results - No Response from Room Mailbox neither Accepted nor Declined
But we can see as booked as "Tentative"
Room Booking Scenario for same slot- Rebook Room for 6.30pm to 7.30pm slot
Results -No Response from Room Mailbox neither Accepted nor Declined
But we can see as booked as "Tentative"
=========================
Conclusion = There is issue with booking room and not getting response while user is
@abc.my id.
======================
Note = for all other on premise users those are having @abc.co.in
and @abc.my it is working fine. Users are getting respective correct reply from room mailboxes.
This issue seems with only on cloud
@abc.my users

Exchange 2003 users are unable to send attachments larger then 8 MB to Exchange 2010 users on the same LAN

I am migrating from Exchange 2003 to Exchange 2010.
Users who are still on Exchange 2003 cannot send attachments any larger than around 8MB to Exchange 2010 users on the same LAN.
Users on Exchange 2010 can send large attachments to fellow Exchange 2010 users without issue.
I do not have any quota restrictions on Exchange 2010.
Had a look at the Exchange 2003 Connector but could not see any reference to attachement restrictions.
Has anyone come across this?

Here is a note of the NDR:-
Your message did not reach some or all of the intended recipients.
Subject:
The following recipient(s) cannot be reached:
Tracey xxxxxx on 01/12/2014 13:27
This message is larger than the current system limit or the recipient's mailbox is full.
Create a shorter message body or remove attachments and try sending it again.
<mail.xxxxxxxxx.com #5.2.3 smtp;450 5.2.3 Msg Size greater than allowed by Remote Host>

Uninstall Forefront for Exchange 2010

I have acquired another spam filter appliance that will used instead of Forefront for Exchange 2010.
How do I uninstall Forefront for Exchange 2010 without any issues while still using Exchange 2010.
Basically the email will go through the email appliance filter then to Exchange. I want to deactivate or uninstall Forefront for Exchange with impacting my email services. Is it as simple as just uninstalling it?

Hi,
About uninstalling Forefront for Exchange 2010, you could check the following article.
If spam filtering was enabled, the configurations in the corresponding antispam settings in Microsoft Exchange that were leveraged by FPE will be retained by their Exchange antispam counterparts after FPE is uninstalled. These settings include: Connection
Filtering, Sender ID Filtering, Sender Filtering, and Reciepient Filtering. To change these configuration settings you will need to modify them through the Exchange management console.
Uninstalling Forefront Protection 2010 for Exchange Server
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Outlook anywhere issue for exchange 2010 users

Similar Messages

Maybe you are looking for