Exchange 2010 DL problem.

Hi,
We have exchange 2010 server setup with office 365 in hybrid mode. We moved some users mailboxes from exchange server to office365. Now we have some DL on exchange server that have some users (mailboxes on prem.) and some users (mailboxes on office365).
When we send the mail to that DL, we received error "Your message can't be delivered because delivery to this address is restricted."
How can we resolve this issue? Please help me.
Thanks & Regards,

Hi shrigiriraj
Thank you for your question.
Did you migrate DL to Exchange 2010？In order to make sure correct setting after you migrate, you can refer to the following steps:
1. Click the Distribution Group name as you want to set
2. Click the “Properties“
3. Click the “Mail Flow Settings” Tab
4. Click the “Message Delivery Restrictions” item
5. Click the “Properties…” button
6 .Uncheck the “Require that all senders are authenticated” check-box
7. Click “OK” button
8. Click “OK” button again
If there are any questions, please let me know.
Best Regard,
Jim

Similar Messages

Exchange 2010 synchronisation problem

Hi All
My Exchange mailbox has been updated from 2007 to 2010. Since this has happened my N900 refuses to synch using MfE. Luckily I am still able to check my emails via OWA otherwise my phone would be useless.
I have been trawling through the logs using both my Exchange 2010 account and with a test Exchange 2007 account and what I have found is that the error occurs right after the N900 issues the command HTTP REQUEST: OPTIONS https://"server"/Microsoft-Server-ActiveSync. With Exchange 2007 the certificate is found and downloaded. However with Exchange 2010 the connection is cancelled and no certificate is found or downloaded. An error 901 is recorded in the logs. My Exchange tech contact has confirmed that some changes have been made in how 2010 deals with OPTIONS compared to 2007.
Can anyone advise what if anything can be done so that my MfE client will connect correctly to Exchange 2010? If not will Nokia update the MfE client to work correctly with 2010 like they did with 2003? Should this not be the case then I suppose quite a number of N900 users could find themselves with a useless brick if their mailboxes get updated to 2010.
Many thanks
Chris

Hi Chris,
I am having the same problem after the switch from Exchange 2007 to Exchange 2010 server.
I am really disappointed in the support from Nokia in its own devices, especially the N900. I searched the internet, but no solution yet, and I don't believe it will ever be. I give up and switch phones.
So, I think it was my last Nokia device.
Regards!
Peter

Outlook 2010 to Exchange 2010 connectivity problem

We have a single Exchange 2010 server running DB, CAS, and HT this lives at our Corp HQ. We have 12 offices connected across MPLS and 2 offices connected across a Metro-e 100mb connection. We have had this environment in place for almost 2 years with no
issues.
Today in the office connected across the 100mb metro-e connection had a momentary network hiccup where all uses lost data momentarily.   Connectivity to data and network resources restore immediately, but after that time, none of those users could
connect to Outlook 2010.   When they try to connect outlook times out with an error that it cannot connect to the server.
I can ping the exchange server by name and ip.   Response times are less than 7ms. Utilization on that connection is less than 10%. DNS is resolving.
Users can connect to OWA and get access to email.
The problem is only happening in only the one office. All other remote sites are functioning fine.
Users can access all other network resources with no issues, including OWA and Intranet/Internet sites both HTTP and HTTPS.
I believe that it may be something is blocking the RPC connection.   If I try to run the Connection which also fails to connect.
I have rebooted the Exchange server
I have rebooted the local DC in the remote office with the problem. Also reset DNS.   And on clients tried flush/register DNS.
No server changes have been made on any of the servers involved.
Only changes taken place prior to the network "hiccup" happening was network admins implemented QOS on the routers to give priority to SIP/voice traffic. According to them, this will have no impact on other data.
Any ideas or suggestions on next steps for troubleshooting?

Hi
Did you they not make any routing changes? Can you ask them to check that all ports for exchange are open and also ask them if they made any other changes?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Disabling SSLv2 with Exchange 2010 - potential problems

This question is not about how to disable SSLv2, that's very simple. The question is whether there is anything to consider before doing it. Is it likely to break anything in Exchange 2010 - Outlook Anywhere, CAS communications, OWA?

While this is probably something that has not been explicitly tested, chances are that it should not negatively impact Exchange. That said I will ask you to test and validate in your lab!
You are going to have to ensure that all devices, applications and services that connect all support the changed cipher suites. Some old phones may not (I don't have a list to share), so that is why validation with your specific kit is critical.
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 2010 setup problems

I am having some issues and I am need some help please. I tried to setup exchange on a local server yesterday (2010) and 1/2 way through it throught a ton of errors where I could not find some items. So ok I said it would not even uninstall without giving
me grief. I then did a manual uninstall of 2010 since I couldnt get 2010 to even install on the new server without doing so. I then setup a new virtual server today and tried to reinstall it. but am still getting an error and here is the logs.
[04/27/2014 07:48:55.0235] [2] Active Directory session settings for 'initialize-ExchangeUniversalGroups' are: View Entire Forest: 'True', Configuration Domain Controller: '69-64-71-40.ketelaaraccounting.com', Preferred Global Catalog: '69-64-71-40.ketelaaraccounting.com',
Preferred Domain Controllers: '{ 69-64-71-40.ketelaaraccounting.com }'
[04/27/2014 07:48:55.0235] [2] Beginning processing initialize-ExchangeUniversalGroups -DomainController:'69-64-71-40.ketelaaraccounting.com' -ActiveDirectorySplitPermissions:$null
[04/27/2014 07:48:55.0267] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:55.0282] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object CN=Configuration,DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:55.0282] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:56.0031] [2] Used domain controller 69-64-71-40.ketelaaraccounting.com to read object OU=Microsoft Exchange Security Groups,DC=ketelaaraccounting,DC=com.
[04/27/2014 07:48:56.0125] [2] [ERROR] Unexpected Error
[04/27/2014 07:48:56.0125] [2] [ERROR] The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute
in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
[04/27/2014 07:48:56.0156] [2] Ending processing initialize-ExchangeUniversalGroups
[04/27/2014 07:48:56.0156] [1] The following 1 error(s) occurred during task execution:
[04/27/2014 07:48:56.0156] [1] 0. ErrorRecord: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects
attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
[04/27/2014 07:48:56.0156] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted
Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then
rerun the task.
[04/27/2014 07:48:56.0156] [1] [ERROR] The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute in the container
object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.".
[04/27/2014 07:48:56.0156] [1] [ERROR] The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:ed5aa0f9-643b-43d8-bdeb-5e6c0f327703,CN=Deleted Objects,DC=ketelaaraccounting,DC=com on the otherWellKnownObjects attribute
in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ketelaaraccounting,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
[04/27/2014 07:48:56.0156] [1] [ERROR-REFERENCE] Id=443949901 Component=
[04/27/2014 07:48:56.0156] [1] Setup is stopping now because of one or more critical errors.
[04/27/2014 07:48:56.0156] [1] Finished executing component tasks.
[04/27/2014 07:48:56.0187] [1] Ending processing Install-ExchangeOrganization
[04/27/2014 07:48:56.0187] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[04/27/2014 07:48:56.0203] [0] End of Setup
[04/27/2014 07:48:56.0203] [0] **********************************************
Im really lost I can not find the entry it is complaining about no matter how hard I look. I really need help I would rather not scrap all my hard work.
Ted

Hi,
Based on my research, we can try to firstly check the otherWellKnownObjects attribute in order to resolve the issue:
1.) Go to Start -> Run -Type LDP.exe -> click OK
2.) Click Connection -> Connect and then click OK
3.) Click Connection -> Bind and then click OK
4.) Click View -> Tree and for the BaseDN select CN=Configuration,DC=DomainName,DC=local and click OK
5.) In the left-pane expand the Configuration partition -> Services -> Microsoft Exchange
6.) Right-click the object Microsoft Exchange and then click Modify
7.) In the Attribute box type otherWellKnownObjects
8.) In the Values box type B:32:9C5B963F67F14A4B936CB8EFB19C4784:CN=ExchangeLegacyInterop\0ADEL:90d1a283-ed42-4ddf-8402- f0dbef0290b2,CN=Deleted Objects,DC=CAO,DC=local (The invalid DN reference you
want to delete)
9.) Select the Delete radio button
10.) Click the Enter button
11.) The Entry List text box will populate with [Delete] and the selected attribute and its value in steps 7 & 8.
12.) Click on the Run button
And here are some references:
http://blogs.technet.com/b/winde76/archive/2012/06/10/prepare-ad-creates-duplicate-security-groups.aspx
http://social.technet.microsoft.com/Forums/exchange/en-US/2fd295db-f84e-4c7b-a1cb-03fa0433d95f/exchange-2010-install-setup-preparead-fail?forum=exchangesvrdeploylegacy
http://social.technet.microsoft.com/Forums/exchange/en-US/7f0f2ea5-73f0-4a61-8f9f-728f11eea98b/exchange-2010-install-fails-preparead
Thanks,
Angela Shi
TechNet Community Support

Outlook 2010, Exchange 2010 - Searching Problems

Anyone out there able to help with some searching problems some of our users have been seeing?
Searching in OWA works fine but some people have problems when searching for older emails in Outlook. We've rebuilt Outlook profiles, rebuilt the windows index's (which seems to work but only temporarily). If there's a way to schedule the Windows index to
rebuild every night or once week, I'd be very happy to test that out but haven't been able to figure out how to do that.
Anyone have any other ideas?

Hi,
It seems something keeps corrupting the index... Run Anti-virus program and Malicious Software Removal Tool to scan your system, check if there's any virus or malware that may cause the index issue.
If this issue persists, please also go to File tab ->
Options -> Search -> Indexing Options
-> Advanced -> Click Troubleshoot search and indexing, to do some troubleshooting steps to find the possible cause.
I hope this helps.
Regards,
Melon Chen
TechNet Community Support

Surface + Outlook 2013 + Exchange 2010 + VPN Problem

Ok so the Surface with Outlook 2013 works fine with our Exchange setup when the machine is attached to the network directly. Once it is on an external network and attached via a VPN connection it ceases to operate, and attempting to run Outlook simply results
in a box asking for credentials, which even when typed in correctly are not accepted.
We use many other laptops that are running Windows 7, and a couple that are running Windows 8.1 in the exact same manner, and they operate without issue.
Any ideas?

Hi,
May I first know your Surface version?
If you are not using Surface RT, I suggest you try this:
In Outlook, go to FILE -> Account Settings -> Account Settings -> Double click on the account name -> More Settings -> Connection -> Exchange Proxy Settings -> We can find under "Proxy authentication settings", there are "Basic
Authentication", "NTLM Authentication" and "Negotiate Authentication", I suggest you try "Basic Authentication", then click "OK". Other two authentications can also be tried if the "Basic Authentication"
doesn't work.
I hope the information is helpful.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Problems with a shared calendar using Outlook 2007 and Exchange 2010

Hello all,
We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
I realize this is a big mess, and your help would be greatly appreciated.

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

TS3899 I have upgrade my to iOS7 and my company recently upgrade to Exchange 2010. My emails are not synching to my inbox. I can see all of my sent items. I have already deleted the account 3 times but this did not fix the inbox problem.

I have upgrade my phone to iOS7 and my company recently upgraded to Exchange 2010. My emails are not synching to my inbox. I can only see my Sent items. I have already deleted the account 3 times but this did not fix the inbox problem.

You need to have a different Apple ID for each of the other devices.

Exchange 2010 : Doubt with recipient type and problem with disappearance of the original recipient in the mail relay

Hello. First of all, thank you very much for your attention.
After that, I will expose the problem:
I have a user domain called "comercial" with a corresponding mailbox "[email protected]"
. This user
has assigned multiple emails such as "[email protected]", "[email protected]", "[email protected]" , having as default email "[email protected] ".
On
the other hand,
another domain user
called
"menganito" with it's mailbox "[email protected]" account, also has a few mail accounts "[email protected]", "[email protected]", " [email protected]"
...having
as default email "[email protected]
The user "Comercial" is forwarding
all of it's mails to the user "menganito".
The problem is that "menganito" is not receiving the exact
"comercial"
sender email, but the email which appears by default ("[email protected]").
"Menganito" would like to know
from which email exactly the mails he is receiving have been sent ("[email protected]",
or "[email protected]"
or "[email protected]").
Also, he would like to knowthe email of the original sender (from the outside of the domain) whom the user "Comercial"
have received the email from.
In another type of email servers (Kerio,...)
this is not a problem, because forwarding by
defaultis always showing
the original sender and original receiver.
Maybe the problem comes from the recipient type I'm using.
Should I use another type of recipient? should I use a transport rule?
Any idea ? Thanks again in advance.

Hi Simon. First of all thanks for your answer.
This happens with all accounts. I tried with news accounts and different browsers for OWA and Outlook anywhere and happens the same. Is not a cache problem
The problem is
when "[email protected]"(default
and set as default answer
account by
exchange)
receives
a message in "[email protected]" when
forwards to "Menganito"
this message will appear from"[email protected]"
instead of "[email protected]".
This happens with all accounts.
I can understand that i can't avoid
default reply address on the same
domain, but also with different domains happens
the same?
The platform is only one clean and updated server 2012 as dc and another clean and updated server 2012 with exchange 2010 sp3 directly and after rollup 4 for exchange SP3, no previous versions and servicepacks of exchange 2010 was installed before. Before
install exchange 2010 sp3, i installed all the filterpacks (3) and .net 3.5 and all updates that i finded for 2012 server (i tried for 2 days): No more updates for sure. After, in powershell, i put this:
Add-WindowsFeature NET-Framework-Core,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,Web-Mgmt-Tools,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy
-Restart
The machine and exchange works good (i3 with 4gb ram, and raid 1 1tb of HD) and the organization only has 15 mailboxes. No problems with even viewer and all is correct.
Thanks again.

Exchange 2010/Outlook 2010 Security Alert (...there is a problem with the site's security certificate.)

I've been looking to resolve this issue for a while now and was hoping someone could help me understand my options.
We have Exchange 2010 & Outlook 2010 in our environment. I've created a SSL cert for our ActiveSync from a reputable CA and unfortunately, as you may not be surprised, we are seeing an alert each time we open Outlook that states:
"Security Alert; Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
The name on the security certificate is invalid or does not match the name of the site."
Of course my internal server name does not match my external server name. So the SSL I had created for use with OWA and ActiveSync is rejected by my internal Outlook clients.
After doing some research I believe this is related to the Autodiscover service being configured with my internal server name and not my external name.
I've found some info about adding New-AutodiscoverVirtualDirectory and Set-ClientAccessServer commands and then found this article that might help. (Configure
Outlook Anywhere to Use Multiple SSL Certificates) but nothing is specific to my configuration and I'm concerned about what will happen to my existing configuration if this fails.
What happens when you run Set-ClientAccessServer? Does it retain and keep the old server config in place and add a new one or does it wipe it out? Will all of my devices need to be reconfigured?
Same with New-AutodiscoverVirtualDirectory. Does this simply add another virtual directory or is it going to overwrite my existing config?
Then there is the question of whether or not any of this will actually address my issue at all.
absolutezero273c

Sorry.
"[PS] C:\Windows\system32>Set-ClientAccessServer -Identity MailExt -AutoDiscoverServiceInternalUri "https://MailExt
.contoso.com/autodiscover/autodiscover.xml"
The operation couldn't be performed because object 'MailExt' couldn't be found on 'DomainController2.contoso.local'.
+ CategoryInfo : NotSpecified: (0:Int32) [Set-ClientAccessServer], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : 4D980455,Microsoft.Exchange.Management.SystemConfigurationTasks.SetClientAccessServer"...is the error I get.
I've created the split zones and populated the Forward Lookup Zones as follows:
CONTOSO.COM
MailExt(CNAME)MailInt.contoso.local
_tcp _autodiscover(SRV)MailExt.contoso.com
CONTOSO.LOCAL
MailInt(A)192.168.1.10
MailExt(CNAME)MailInt.contoso.com
One thing I did notice is that there isn't a _tcp _autodiscover entry for MailInt in my Forward Lookup Zones. It was recommended that I make that entry for _tcp _autodiscover(SRV)MailExt.contoso.com in another post I read somewhere.
I believe what I am trying to do is create a new autodiscover object as is shown here:
I see there is a Get-ClientAccessServer & Set-ClientAccessServer command but I need to add a CAS. Does the Set-ClientAccessServer add or simply modify?
Or would that require the New-AutodiscoverVirtualDirectory command? I read
this page that discussed creating new virtual directories but that seemed a little risky without knowing all the ins and outs of how this service functions and to what degree this would affect the existing configuration.
I was able to use the Set-ClientAccessServer command and change the actual internal autodiscoverUri to https://MailExt.contoso.com/autodiscover/autodiscover.xml but the name still says MailInt and I continue to get the SSL cert warnings because it is looking
at MailInt.contoso.local.
absolutezero273c

Exchange 2013 & 2010 coexist problem. Authentication Credentials Prompt in Outlook

Hello Forum
We have two Exchange servers coexisting together. A new 2013 and a old 2010.
Everything was setup with the help of the Exchange Deployment Assistant.
I have had alot of trouble with Outlook 2013 Prompting for credentials on Exchange 2013 Mailboxes. None of the 2010 Mailboxes expericence this popup.
I solved most of the popup issues with this by changing the ExternalClientAuthenticationMethod to ntlm.(from negotiate)
http://blog.gothamtg.com/2013/10/15/users-constantly-prompted-for-credentials-after-being-migrated-to-exchange-2013/
and installing this update for Outlook:
http://support2.microsoft.com/kb/2899504/en-us
Now 2013 Mailboxes Work without any anoying popups. Except when they try to open another users mailbox that is located on the old 2010 server or a shared 2010 calander.
The connection to Exchange 2010 is working if I input the users password, but should it not work without this popup too?
This connections name acording to Outlook is called: Exchange-Mail RPC/HTTP (remote [NTLM])
We use the same domain for external and internal autodiscover connections.
Test Exchange Connectivity Analyzer shows everything ok.
If i run
get-outlookanywhere | fl *external*
(2013 server)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl          : True
(2010 server)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True
Only one thing I am wondering here is. If I change my old 2010 Auth Method to NTLM if that will break anything i OWA and so on.
What do you Guys have setup in your environments and can you point me towards any troubleshooting?
Thanks!

For us, the changes made in IIS are permanent, there quite possibly is a powershell way of doing it but I am still getting to grips with PS myself so I don't know.
I wont plagiarise others work but these two links here give a good explanation between Basic and NTLM. personally, I have always used basic because I always seem to get problems with NTLM, though one time it did work as expected but I forgot what I did to
get it working now.
https://social.technet.microsoft.com/Forums/exchange/en-US/92178beb-3310-4363-8848-d022a6e2a77f/basic-vs-ntlm-authentication-outlook-anywhere
http://www.sysadminlab.net/exchange/outlook-anywhere-basic-vs-ntlm-authentication-explained

Problems with archive mailbox in Outlook, with exchange 2010+2013 co-existence

Hi!
We have an Exchange 2010 environment plus one Exchange 2013 MBX server meant for archive mailbox purpose. (We are going to upgrade to 2013 but with over 20.000 mailboxes it will take som time. Therefore we need to co-exist with primary mbx on 2010 and archive
mbx on 2013 for some time.)
My primary mailbox is on a 2010 MBX server, and I have today given myself an archive mbx on 2013 MBX server.
When I use OWA, both my primary mailbox and my archive shows up and everything works 100% fine!
But when I try Outlook 2010 or Outlook 2013, only my primary mailbox works. The archive mailbox shows up, but generates an error when accessing it:
"The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance"
Anyone who knows about this issue? Would we nice to know why it works in OWA but not in Outlook.
Thanks!
Trond Jenssen

Hi，
Please try to recreate a profile to access archieve mailbox.
If it doesn't make sense, also try Uncheck “Download shared folders” and check it again.
If you have any feedback on our support, please click
here
Wendy Liu
TechNet Community Support

Problem with Assigning Policy button in Outlook 2010 and Exchange 2010

First of all, I'm posting here because I'm not sure how to post in the previous version of Exchange forums.
Secondly, I'm re-posting this from the Outlook forums as I'm not getting any responses there despite of views.
Hi,
I'm having an issue in Outlook 2010 where I can't assign personal policies to folders. I have setup personal tags and added the mailbox to the right policy. I have also ran Start-MangedFolderAssistant in Exchange 2010 Shell against the mailboxes.
When I go into OWA, everything shows up perfectly, I can right-click and assign policies at will, but when I open Outlook 2010 then the Assign Policy button never appears. I force added it to the ribbon and I can see from there that the button stays grayed
out irregardless of where I click in the folder structure. I have even assigned the mailbox user Owner rights to all the folders to see if it will make a difference.
If anyone can help me solve this problem I will very grateful, I'm pulling my hair out here and I'm certain I could just be missing something very obvious somewhere,
It might be worth mentioning that the company has been using .prf files to configure Outlook thus far, I'm
looking to eliminate that. I'm not sure if that will have any effect on my current problem.
Thanks for your time.
Nico

Thanks for the reply Max, that's a pretty good link.
Like is I said though, I have the policies all set up in the Exchange configuration side of things, when I use OWA all the options for applying tags appear. It's just in Outlook 2010 Standard that the Assign Policy button stays grayed out.
Thanks.
EDIT:
This has been solved, looks like version problem with Outlook.
http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx

Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

I currently have an Exchange 2010 server with all the roles installed. Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error. When I installed Exchange 2013, I got an error saying I
had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left. There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group. This deletion caused my access
to my public folders to get messed up. I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA. I also get this error when
trying to access either Default or System Public Folders. "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
-server 'ExchangeServer' "
My Public Folder Database exists and is mounted. Any help is appreciated.

Hi Belinda,
Thank you for responding. Yes you do understand my problem correctly. One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA. I followed these steps in the below article:
http://blog.bruteforcetech.com/archives/766
After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
Here are the results to your requests:
et-PublicFolder -Recurse | Format-List Name
Name : IPM_SUBTREE
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
[PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
Name : NON_IPM_SUBTREE
Name : EFORMS REGISTRY
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

Exchange 2010 DL problem.

Similar Messages

Maybe you are looking for