Exchange 2010 RBAC issues

I am trying to create an Exchange 2010 RBAC role group for our service desk. I have created a test management role group "Service Desk staff" and assigned the below roles using the Exchange Control Panel:
Distribution Groups
Mail Enabled Public Folders
Mail Recipient Creation
Mail Recipients
Public Folders
Then I access Exchange 2010 via the Exchange Management Console from a client PC with a user account that is in the Management Role Group I created.
I am able to do most tasks such as create/modify distribution groups, create mailboxes and edit the properties of it.
But for some reason I cannot perform the below:
1. Trying to add/remove members from a Distribution group results in an error
Add-DistributionGroupMember
or
Remove-DistributionGroupMember
2. Trying to create a Public folder results in an error:
MailExceptionNoCreateSubfolderRight: Unable to create folder.
(hr=0x80070005 ec=1282)
3. Trying to mail enable/disable a Public folder results in an error:
MapiExceptionNoAcess: Unable to set properties on object.
(hr=0x80070005 ec=2147024891)
4. Changing permission of Public Folders results in an error:
MapiExceptionNoAcess: Unable to modify table.
(hr=0x80070005 ec=2147024891)
Can anyone provide some feedback on how I might resolve this and perform the above tasks using RBAC management group for Exchange 2010? Appreciate any help. Thank you.

Hi,
According to your description, it seems like you failed to assign the permissions.
How did you assign the permissions to the group?
I recommend that you refer to the following article to assign the permissions:
How to give permissions to users to manage Universal Security Distribution
Lists (must use RBAC)
Assign permissions to security group (recommended)
New-managementroleassignment –role “Security group creation and membership” –securitygroup “DL Owners”
or to assign the roles directly to user
New-managementroleassignment –role “Security group creation and membership” –User “username”
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

Exchange 2013 co-existence with Exchange 2010 proxying issue.

Hello,
I am testing Exchange 2010 and Exchange 2013 co-existence in my test lab at the moment, with
a view to migrating our production environment to 2013 later in the year.
The lab is setup, and the problem I'm having is that internal Outlook clients cannot open
their respective mailboxes once the 2013 CAS server is introduced into the mix.
The
setup is listed below:
EXCHANGE 2010 Servers
TESTLABEXCH01 - CAS,HT,MBX - Exchange 2010 SP3
TESTLABEXCH02 - CAS,HT,MBX - Exchange 2010 SP3
Both servers are part of a CAS Array - casarray01.testlab.local
Both servers are part of a DAG - DAG01.testlab.local
RpcClientAccessServer on all 2010 databases set to casarray01.testlab.local
The A record for casarray01.testlab.local points to the IP of the VIP of a load balancer.
The loadbalancer serves
the following ports: 25,80,443,143,993,110,995,135,60200,60201
OutlookAnywhere is enabled on both servers:
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods   : {Basic, Ntlm}
Internal and external mail flow works without issue before the 2013 server is introduced.
Internal and external client access works without issue before the 2013 server is introduced.
Part Two to follow.....
Matt

EXCHANGE 2013 Servers :
TESTLABEXCH03 - CAS,MBX - Exchange 2013 SP1
OutlookAnywhere is enabled on the server:
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods   : {Basic, Ntlm}
RpcClientAccessServer on all 2013 databases set to casarray01.testlab.local
(This an inherited setting I assume from the pre-existing 2010 organization)
Split DNS is in place and all internal/external URL's point to either:
autidiscover.external.com
mail.external.com
The A record for the mail.external.com points to the IP of the load balancer VIP
The CNAME record for autodiscover.external.com points to mail.external.com
When the TESTLABEXCH03 is added to the load balancer config,
and given highest priority this is when the Outlook clients stop working.
Any existing profiles in Outlook 2010/Outlook 2013 can no be opened as there is a persistent
credentials prompt.
Upon trying to create a new profile, the process errors when reaching the "Log onto server"
stage and again prompts for credentials.
Running the test-outlookconnectivity cmdlet from
either of the 2010 servers produces the following results.
[PS] C:\Windows\system32>Test-OutlookConnectivity -Protocol:http
ClientAccessServer   ServiceEndpoint
Scenario                            Result Latency
TESTLABEXCH02 autodiscover.external.com    Autodiscover:
Web service request. Success 343.20
TESTLABEXCH02 casarray01.testlab.local       RpcProxy::VerifyRpcProxy.
Success    0.00
TESTLABEXCH02 casarray01.testlab.local         RFRI::GetReferral.
Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local        NSPI::GetProfileDetails.
Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local
Mailbox::Connect.                   Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local
Mailbox::Logon.                     Skipped   -1.00
If remove the 2013 CAS server from the loadbalancer config and
all connections go directly to the 2010 servers again, all of the above tests pass and Outlook connectivity is also restored.
IIS has been reset on all 3 servers incidentally, following any changes made whilst troubleshooting.
I'm struggling to see what I'm missing here, if anyone can assist in troubleshooting this
matter further, or point out any errors in my setup it would be greatly appreciated.
Regards
Matt
Matt

Exchange 2010 - Database issues

Good morning everyone!
I have an exchange database problem. It was first caught when implementing exchange backups with Acronis backup software.
(EXCHANGE 2010 v 14.01.0218.013)
So the backups fail one night and succeed the next. But each time it fails we get 4 errors (Consistency related). Also the database size is growing rapidly. Here are the errors:
Then a couple more:
EVENT ID 9782
Exchange VSS Writer (instance b1bfbf43-9594-4cee-980f-50d84b0ee4eb:76) has completed the backup of database 'xxxxxxxxx' with errors. The backup did not complete successfully, and no log files were truncated for this database.
Then finally:
EVENT ID 2007
Information Store (2136) Shadow copy instance 76 aborted.
For more information, click http://www.microsoft.com/contentredirect.asp.
EDIT:
SO my DB is not growing because the issue...I had forgotten that we enabled LEGAL HOLD. But my backups fail / succeed / fail / succeed.
Any ideas on this?
Kevin

Hi,
Please use Windows Server backup to backup the Exchange database to check result.
If Windows Server backup works well, I recommend you contact the third party support to confirm this issue.
If the issue persists, please check whether your database is dirty shutdown. If it's dirty, please bring to clean state and backup agian to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 RPC issue, "The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process"

Hi All,
this is the first time iv had to post on here on a forum since ive been doing IT but here goes.
Server background:
SBS 2011
Exchange 2010 SP3 RU6
Installed 2 years ago and has run relatively smooth since installation
Possible Cause: a recent application that had created a virtual directory in IIS.
Issue:
A user recently reported an issue with Outlook Anywhere, i did an exchange connection test and reported the following error
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3834 ms.
Fixes Tried so far
- Reg fix for ports 6001,6002,6004
- Telnet 127.0.0.1 6001 all returns expected results
- Disable RPC then Re-enable via the management console
-Ran fix my network wizard which has shown an error in compenent 3 which it fixed
Component ID #3
If the Fix My network wizard shows that component ID #3 is broken, this means that within IIS the RPC virtual directory settings are incorrect.
Continuing to fix this error within the wizard will correct the RPC virtual directory to support both Basic and NTLM authentication to this virtual directory.
Any suggestions would be great as im running out of ideas, i have thought about rebuilding outlook anywhere but unsure of the implications on an SBS

Hi,
In order to check whether it is an RPC Virtual Directory issue, you can open IE and input:
Https://mail.domain.com/RPC/RPCProxy.dll
After inputting the credential, the expected result is a blank page. If not, I means the issue resides on the RPC VD. You can try rebuilding the RPC VD for the first try.
Thanks,
Simon Wu
TechNet Community Support

CUC 8.5.(1) with Exchange 2010 TTS issue

Hi,
I'm configuring CUC 8.5(1) ( 2 servers in HA ) with MS Exchange 2010 ( one server in a MS domain ).
Single inbox works well, so voice recognition.
I'm now trying TTS but i'm encountering some problems.
Feature is licensed, so i enabled it in the class of service and flagged the allow user to access voice mail
using imap client and\or single inbox. Also at user level the proper configuration is done.
I followed the official guides about it and all recall to a 8.0 with exchange 2007 way to enable imap access
using external services and external services accounts.
My issue is that i don't have these voices in my system settings of my CUC.
Where should i point my attention to get it work? The environment is only internal so exchange is not configured
for TSL, is it mandatory to have it enabled? How should i access emails in TTS mode by phone? I tried the
voice mail interface but it doesn't speak about emails, only voicemail.
Is there any step by step guide correct\update for exchange 2010?
Thanks to all for your help, i'm at a stuck and i need this feature working in a few days.
Michele

Thanks a lot Brad,
All is working, just a couple of question, i'm also using voice recognition, it works but it doens't has the
play external messages option, is there any specific i have to set or say?
The touchtone command in my classic conversation is not 7 but i have to execute a little procedure following the
menu, somenthing like 0 --> 9 --> 1 ---> 7 ( external message option ) --> 1
Is there any way to change or abbreviate this ?
Thanks again
Michele

Case of the Missing User Exchange 2003 - Exchange 2010 Migration issue

Hey All,
I am in the middle migrating from Exchange 2003 to Exchange 2013 by way of Exchange 2010 and going through the final parts of my Exchange 2010 portion of the migration I found that one of the users on Exchange 2003 is not showing up in the EMC to migrate.
In EPS I can find the user with Get-User username but I cannot get the mailbox or kick off the mailbox move from EPS giving me the error of "Object could not be found" It is a valid user with a valid user mailbox and I can log into the
mailbox in OWA for Exchange 2003. Any thoughts as to why the user's mailbox is not showing in EMC or that I can't get it to move via PS?
Thanks,
Joe

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Exchange 2010 upgrade issue

dear
we are in the process to upgrade our exchange 2003 to exchange 2010, our domains are 2003 and the functional level is 2003.
every time i run the pre deployment analyzer i get this massage
Active Directory site 'SITENAME' does not contain any global catalog servers running Windows Server 2003 Service Pack 1 or later. This will prevent Exchange 2010 servers from
being installed into site 'SITENAME'.
can any one help me

Hi,
Based on my research, Exchange Best Practices Analyzer v2.8 should not be used to scan Exchange Server 2007 and Exchange Server 2010. In Exchange Server 2007 and Exchange Server 2010, the Best Practices Analyzer is installed during Exchange Setup and can
be run from the Exchange Management Console Toolbox. Thus, I’d like to confirm your BPA version:
http://social.technet.microsoft.com/Forums/exchange/en-US/158f4eca-917b-455c-9a99-5294f601e75b/exchange-bpa-28?forum=exchangesvrdeploylegacy
And here is a more similar thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/83798a09-51ca-4c7c-9cc2-63f8ccd2f181/migration-to-exchange-2010?forum=exchange2010
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 OAB issue on clients

Hey guys,
Need some assistance fixing a OAB issue.
All workstations are getting an error when trying to download OAB through outlook 2010 "Server reported error (0x80190194): The operation failed". Also please note I unchecked the box "download changes since last send/receive" or just left
it checked for new setups.
I checked Exchange both MBX and both CAS servers and no error messages in logs appear.
Have done some research on the issue and found some posts telling me to manually update the OAB through EMC under the mailbox section. Have done that but still nothing.
Also checked permissions on both MBX servers under path: C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB. Now from what I read, these need to be replicated to the CAS server under C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB. I
checked permissions for this folder too and they are OK.
How can I rectify this? Its happening on all workstations within network, cached mode and also using RPC over HTTP.
Also within the network, they use a proxy but when at home using RPC over HTTP, it does not use proxy and I still get same error message and its a new outlook profile setup.
I'm running SP3. Thanks guys,

follow this Exchange Team article.
http://blogs.technet.com/b/exchange/archive/2012/04/27/how-large-is-my-exchange-offline-address-book-oab.aspx
Where Technology Meets Talent
Hi ExchangeITPro,
So the size of my -data-<sequence>.lzx file is 1.89 MB. I found this by running the exchange command to find out the mailbox server generating the OAB files and then going to the path C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB\<GUID>
and then finding the -data-<sequence>.lzx file.
Now how do I delete and re-create the OAB?

CSS 11501 Exchange 2010 ActiveSync issue

When performing an ActiveSync test from Microsoft's Connectivity test tool (https://www.testexchangeconnectivity.com/) all the steps for the ActiveSync test pass except the last one which fails with this error:
Attempting FolderSync command on ActiveSync session
FolderSync command test failed
Additional Details
Exception Details:
Message: The request was aborted: The request was canceled.
Type: System.Net.WebException
Stack Trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Tools.ExRca.Tests.ActiveSync.ActiveSyncFolderSyncTest.PerformTestReally()
When we test directly to the node, bypassing the contenet services switch, the test finshes properly, and ActiveSync works on mobile devices.
Any ideas?

Hi,
We can create allow lists, block lists, and quarantine lists specifying which mobile devices are allowed to access Exchange mailboxes. A mobile device that's blocked because of a device access setting won't be allowed to connect to the Exchange
server and will receive HTTP 403 Forbidden errors. For more information about how to manage mobile device, please refer to the following article.
http://technet.microsoft.com/en-us/library/ff959225(v=exchg.141).aspx
Best Regards.

Exchange 2010\Outlook Mail issues

Hi,
I am having some issues with mail disappearing and outlook not updating. The issues are:
When sending an email from Outlook it appears in the sent items for 30 seconds in Outlook and then disappears. It never shows up in OWA The email does send though. If an email is sent via OWA the email appears and stays in both OWA and Outlook. This is
happening in Outlook 2010\Exchange 2010
Updating issues on random folders in Outlook. This is happening on both Outlook 2013 and Outlook 2010 different users with the same Exchange 2010 back end.
Both users have cached email forced. I have tried rebuilding the mailbox locally.
Cheers,
Zac Avramides

Hi,
Thanks for your detailed information about the symptom.
It seems the issue is more related to the Outlook client since OWA works fine. I suggest we can follow the checkpoints below:
1. Rebuild Outlook profile.
2. Disable any third-party firewall or AV programs.
3. Run Windows in Clean Boot.
4. Run Outlook in safe mode by “Outlook /safe”.
What’s the result now?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Issue with SLA reports of Exchange 2010 MP in SCOM 2007 R2 !!

Hi,
I have issues with Exchange 2010 MP SLA reporting. Whenever report is run it fails on some or the other dataset(Outage**,SLAbyDAte etc.) When I digged in, I found that it is connecting to DW Exchange 2010 Availability tables + Planned maintainance +
outage table. The tables were not available in the DW, not sure how it got removed. Initially I tried by uninstalling and installing MP(Exchange 2010 & Exchange 2010 reports both) if relevant tables get created automatically but it did
not help and I was still facing the same issue. Then I tried to create the tables manually and check if it could resolve the issue. There was unique ID associated(different in different computer) with the name of most of the tables. I tool it from Exchange
report data source which exists in reporting server. But I could see that table remain empty with no records there and SLA report start giving different issues stating table instances do not exist.
Could anyone help me to restore the SLA report of Exchange 2010 MP ? How should I ensure that data start populating the tables ? I am also helpless here because we do not have correct DW dump to restore back to earlier when it was working fine.
//BR

Hi,
Based on my research, to correctly install the Correlation Engine, consider the following when you install the Exchange 2010 Monitoring Management Pack:
Determine which server will host the Correlation Engine. While not strictly required, it's strongly recommended that the Correlation Engine be installed on the Root Management Server computer.
Make sure that you download and install the Exchange 2010 Management Pack that matches the operating system for the selected server. You can install the 32-bit or 64-bit version.
Make sure that you run the Microsoft Installer (.msi) package on the server where you want the Exchange 2010 Management Pack and the Correlation Engine to be installed.
After the installation is complete, the Correlation Engine service will have been installed on the server, and the Management Pack files will have been copied to the
System Center Management Packs folder. By default, the installation directory is C:\Program Files\System Center Management Pack.
Quote from:
http://technet.microsoft.com/en-us/library/ee758051(v=exchg.140).aspx
In addition, here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/e75e84d9-0c9e-4d83-b3da-45a143757f85/exchange-2010-monitoring-with-scom-2012-correlation-service-issue
Regads,
Yan Li
Regards, Yan Li

Just updated to my macbook pro to 10.8.2. ical not synching with my Exchange 2010 server. Worked flawlessly prior to the upgrade. Settings set to auto discover. I matched settings of a partner in my who is still using 10.7.1 without issues. Help!

Just updated to my macbook pro to 10.8.2. ical not synching with my Exchange 2010 server. Worked flawlessly prior to the upgrade. Settings set to auto discover. I matched settings of a partner in my who is still using 10.7.1 without issues. Help!

Also - my battery has been telling me "service battery" for a LONG time and then it switched to "replace soon" som time ago. Can't really see what this has to do with anything but whatever.
That could conceivably explain all the problems you're describing. Replacing a Mac's battery should not be postponed since a failed battery will cause other problems to occur. It is also possible that its hard disk has failed, which means the information on it may soon become unrecoverable.
... my latest TM back up was from April 2014, can I just run this when I have rescued everthing and then it might not be as slow?
If that Time Machine backup remains intact, it may be the only viable means of recovering that Mac's information. I suggest you do not attempt to restore its contents to your ailing Mac.
Given that you are having trouble creating a newer Time Machine backup you should stop using that Mac immediately and have it serviced as soon as you are able. Do not take it to anyone other than Apple or a service facility authorized by Apple, for the very reasons you explained. If there are no Apple Stores in your vicinity search for an Authorized Apple Service Provider using the Contact Us link below. Use one of the options that appear under Contact Apple Support. The language on that page will be different for your location.

Issue with Update Rollup 5 for Exchange 2010 SP3 - Mailboxes that were auto mapped not working

Below is my response in another thread but creating a new one in the hopes that someone has the same issue and a solution besides mine below.
Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

Not sure why it was suggested to use the auto mapping feature to grant permissions because that is the component that is causing the issue. Also, there is nothing wrong with the auto configuration because the user can access their own mailbox just fine and
also select mailboxes in their Outlook that were NOT auto mapped.
With that said, here is how I fixed them all.
Remove the permissions using the Exchange Console. Don't forget Send As
Wait about 15 minutes. The mailbox should disappear from the users Outlook
Open an Exchange PowerShell window and run the following command:
.\add-mailboxpermissionsnoautomap.ps1 -Identity mailbox -User user -AccessRights FullAccess
Have the user add the mailbox to their Outlook using the manual process.
All is well....
If you don't have the PS script add-mailboxpermissionsnoautomap.ps1, you can download it. I stumbled across it a few years ago and use it all the time. If you can't find it, just use the Exchange built in command for adding mailbox folder permissions but
specify automap $false.
The idea here is to grant the user access without auto mapping.

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 RBAC issues

Similar Messages

Maybe you are looking for