Send As Permissions - Exchange 2010 - Outlook 2013

I am currently having an issue with an account. 2 people share an Admin Account inbox, while having their own inbox, Although the Admin mailbox only works in Online
mode or the folders will not update and emails will not come through.
This is not the problem though.
Before today both people were working fine for the last few months. Now User 1 (only user to send as Admin mailbox) can not send as the mailbox, while
in online mode. In cached mode it works fine, however the folders do not work.
When in online mode, i can remove the address from the From: drop down and re-add, however this only works for that email. Sending another email reaches
the same error "you do not have the permission to send as blah blah blah". This is a popup error.
Removing the address and re-adding works every time, however as you can imagine, this is not ideal for the user. In testing I have removed permissions
for send as in EMC but removing the address from the from field and re-adding is still allowing it to send. It seems outlook/exchange is not recognizing the permissions. Does anyone have any ideas on what could be causing this?
Exchange version is 2011
Outlook version is 2013

In testing I have removed permissions for send as in EMC but removing the address from the from field and re-adding is still allowing it to send. It seems outlook/exchange is not recognizing the
permissions. Does anyone have any ideas on what could be causing this?
Hi,
After removing the permissions in EMC, I suspect it still takes some time to take effect. We can verify this by sending as the Admin mailbox on OWA to check the result. Then wait for some time, send the test email in Outlook again.
This issue is actually opposite to these issues I've seen before: Most other issues are that the user is not able to send as another user in Cached mode, but able to send in Online Mode. Your description kind of implies there's something interfering
with the connection between Outlook and Exchange when Outlook is in Online Mode, please disable all suspicious add-ins in Outlook, especially the anti-spam add-ins provided by the anti-virus program. Then disable the anti-virus program and the firewall temporarily
to check the result.
As mentioned in your post, this issue is also related to the Auto-Complete List in Outlook, the list may have been corrupted. We can try clearing the list to check if the problem persists:
In Outlook 2013, click FILE -> Options -> Mail -> Send messages -> Click "Empty Auto-Complete List" button -> Yes -> OK.
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. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

"Resend" option is not working for specific user. "The Operation Failed" Exchange 2010 Outlook 2013

Hi Everybody. I have a weird one for you.
I have a user that gets an "operation failed" message whenever trying to use the "resend" option on any email (It's the one right under recall). I had tested up and down on her machine. Exchange 2010 Outlook 2013
Ran in safe mode, recreated her profile, disabled virus scanning, repaired office. (weird, the font just changed sizes on me)
After all of this I tested on other computers, other users seem to be able to "resend" just fine. However her account does not work on any computer I try, internal or external to the network.
It looks more like a profile issue.
She's a very active archivist, so she only has 486MB of space used by her mailbox.
It's well under quota.
It's been really puzzling me.
MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.net

Hi Timssims,
Since there is only one user in the org has this issue, it seems an issue on the Outlook client side.
I suggest asking Outlook Forum for help so that we can get more professional suggestions.
For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
However I also have some suggestions for your reference:
1. If this issue occur on Cached Mode, I suggest turning to Online Mode for testing.
2. Please also paste the detailed error message if "operation failed" is not the
complete information.
3. If still not works after perform operations above (including suggestions from Outlook Forum), I suggest re-creating a new mailbox for the specific user just as Martin suggested.
Thanks
Mavis
Mavis Huang
TechNet Community Support

No calendar connection for Exchange 2010 + Outlook 2013

My environment is this:
Running Outlook 2013 (as part of Office 2013 Suite) connecting to Exchange Server 2010
Both cached and non-cached modes
Connecting using RPC
With both existing profile for last 1yr+ and with a new profile
Outlook v 15.0.4649.1001
The issue I'm having is a room/resource calendar that I was once able to see I can't anymore.
Running Outlook 2010 as the same user from a different computer works fine.
OWA works as well.
Other calendars work
Running Outlook 2013 vs 15.0.4420.1017 also works on a different computer!!!
So this seems to be an issue with my particular version of Outlook, and I did read where a security update seems to have gotten in the way (regression test lately?) but a December patch of 2013 was supposed to fix that. I didn't specifically install the
patch, rather I downloaded from my vendor the latest available version they had.
So is there a patch that will work for me. The only one I've come across tells me it isn't for my machine.
Thanks,
Joe

Hi,
According to your description and test, I understand that the room/resource calendar is invisible in Outlook.
How about changing another user to log on your Outlook?
How about the same version of Outlook on another computer?
Please try to run Outlook under safe mode to avoid some AVs and add-ins.
Please try to re-create profile for testing.
If all method above doesn’t work, please re-install Outlook.
Best Regards,
Allen Wang

Archive Mailbox Duplicated - Exchange 2010/Outlook 2013

Hi,
I have enabled archive mailboxes for a number of users in an Exchange 2010 environment no problem.
There is one user though, that is seeing two online archives:
Online Archive - <Firstname> <Surname>
Online Archive - <email address>
Both are replicas of the other.
Any ideas how to get rid of the duplicate?

I just encountered the same issue. This has been going on for months with my mailbox and no one else's.
I can't tell you how many outlook profiles I created in attempt to fix this.
Originally I was running Outlook 2010 when the issue happened. In my case I had one archived named "Online Archive." The second one was named "Personal Archive." If I expanded either one, I could see the contents in it without issue, but
I couldn't expand the other. I didn't save the error message, but something about being unable to access it.
Once I started using 2013, both archives changed to be called "Online Archive," and were able to be expanded simultaneously. Any changes made in one were immediately reflected in the other. But it still left me with the duplicate archives.
I had reset my password using AD Users and Computers a number of times, but it was always set to the same password. This went on for probably 4 months. Finally I reset my password via ctrl+alt+del. I closed outlook, made sure outlook.exe
wasn't running, opened it back up, and the duplicate archive is GONE!
I even reset the password back to the original one via AD Users and Computers and the duplicate archive has not come back.
Excellent detective skills walshyno_1. But I really want to know why this happens. How is it even possible that creating a different password would remove the duplicate Exchange archive view in Outlook?

Exchange 2010 / Outlook 2013 - Mailflow Issues

Hi everybody,
Some time ago I've configured a SBS2011 server for one of my customers.
The SBS2011 has exchange and sharepoint, these services work fine.
The exchange server is only being used for the calendars, no e-mail flow.
The company uses IMAP through an external hosting-server.
So in Outlook 2013 we configure 2 accounts, one exchange account and one IMAP account.
Configuring the clients isn't a problem, and all seems fine, the calendar works.
But when the e-mail flow starts, users wil receive the same email multiple times and it seems the system is in a loop. E-mail flow will stop or the users get the same e-mails multiple times.
I've checked multiple solution regarding Win8+Outlook 2013 and IMAP, (issue about an update and setting the right root folder), but nothing seems to help.
We installed Outlook 2007 on the clients and configured them with both of the accounts and the system works like a charm! E-mail and the calendar are working like it should.
But the company bought about 20 Office 2013 licenses, so we need to get this to work on the new Outlook.
I don't think there is a problem in the Exchange Server, but in Outlook 2013, possible because both of the accounts share the same OST file.
Does anyone know how to solve this problem? Been running my mind for months.
With kind regards,
Tim Grave

Hi,
This doc may help you a lot.
http://office.microsoft.com/en-in/outlook-help/introduction-to-outlook-data-files-pst-and-ost-HA102749465.aspx
Install Only one Outlook Ex :- Outlook 2007 / 2010 / 2013
And if you want to create a *.pst file you need to go to
1. File > Account Settings > Account Settings.. > Data Files > Add > Create a new PST as you want.
Regards, Koustov Choudhury

Exchange 2010 + Outlook 2013 = Items deleted from inbox, Keep Re-Appearing. (Cached mode outlook only)

Hey Team,
We have a single user who when she deletes items from the Inbox they re-appear (in the inbox), if she is running in cached exchange mode. The items do not re-appear in OWA.
She is not experiencing any network connectivity issues
We have rebuilt her MAPI profile including deleting all existing OST files
We have removed and reinstalled outlook / office 2013
She is the only user with the issue
There are no Sync issues
As soon as we disable cached exchange mode this issue immediately goes away, she is running Office 2013 RTM.
Any Ideas,
Thanks,
Robert
Robert

Hi Robert,
If change another PC to configure her mailbox within outlook 2013, is there the same issue?
In addition, you can try to move her mailbox to another database and check if any helps.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

SBS2011/Exchange 2010 + Outlook 2013 Flow Issues

Hi everybody,
Some time ago I've configured a SBS2011 server for one of my customers.
The SBS2011 has exchange and sharepoint, these services work fine.
The exchange server is only being used for the calendars, no e-mail flow.
The company uses IMAP through an external hosting-server.
So in Outlook 2013 we configure 2 accounts, one exchange account and one IMAP account.
Configuring the clients isn't a problem, and all seems fine, the calendar works.
But when the e-mail flow starts, users wil receive the same email multiple times and it seems the system is in a loop. E-mail flow will stop or the users get the same e-mails multiple times.
I've checked multiple solution regarding Win8+Outlook 2013 and IMAP, (issue about an update and setting the right root folder), but nothing seems to help.
We installed Outlook 2007 on the clients and configured them with both of the accounts and the system works like a charm! E-mail and the calendar are working like it should.
But the company bought about 20 Office 2013 licenses, so we need to get this to work on the new Outlook.
I don't think there is a problem in the Exchange Server, but in Outlook 2013, possible because both of the accounts share the same OST file.
Does anyone know how to solve this problem? Been running my mind for months.
With kind regards,
Tim Grave

Hi,
Based on the description, I understand Outlook uses the calendar via Exchange and email via IMAP, so there are two accounts setup in Outlook 2013, correct? Then how come they share the same .ost file? Please try to configure an individual .ost file
for both accounts, check whether the issue persists.
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.

Can't send or receive internal mail Outlook 2013/Exchange 2013

Working on migrating from Exchange 2010 to 2013 . When I move a mailbox to the 2013 DB I lose the ability to send or receive internal mail. OWA works fine, but no internal. If I move it back to 2010, everything runs perfect. I have
been chasing my tail and seem to be missing something. Any suggestions?
:Updated:
Host record incorrect.

Hi Doc, First of all I would recomend you to take a look to this link:
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AgAEAAAAQAAAAAEAAQAAAAA%7e
It's very helpfull for migrations, take the time to review it, also, in your particulary case, I'd recommend you to redirect all the messaging throught the new Exchange 2013 CAS server, so in that case all the mails from outbound just get authenticated and
then search for each mailbox.
Your issue cames out because your moving the user to an isolate envioroment, maybe the send connectors aren't configured, have you installed the Domain Certificate? or maybe have you exported?
Luis Antonio Navarrete Aranda Consultor Senior Akros Solutions Ecuador

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

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

Manually Move Public Folders from Exchange 2010 to 2013

Hi all,
I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
The final error is the following:
FailureCode                      : -2146233088
FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
FailureSide                      :
Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                   This could be because of one of the following reasons:
                                     Another administrator is currently moving
the mailbox.
                                     The mailbox is locked.
                                     The Microsoft Exchange Mailbox Replication
service (MRS) doesn't have the correct
                                   permissions.
                                     Network errors are preventing MRS from cleanly
closing its session with the
                                   Mailbox server. If this is the case, MRS may continue
to encounter this error for
                                   up to 2 hours - this duration is controlled by the TCP
KeepAlive settings on the
                                   Mailbox server.
                                   Wait for the mailbox to be released before attempting
to move this mailbox again.
So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                   locked. The Microsoft Exchange Mailbox Replication service
will attempt to continue
                                   processing the request after 2/14/2015 12:38:20 PM.
Finally, digging more into reports of migration I found this:
MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
Regards!

What script and process you are running to migrate the Public Folders?
And what do you mean by Manually?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.comTwitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
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 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Exchange 2010 to 2013 Co-Existence Reverse DNS Issue

We are running a Exchange 2010 and 2013 coexistence. Mail Flow is fine on the 2013 side, but for mailboxes still on 2010, some are getting mail delivery failures only for certain external addresses. One of the deliveries says the Sending IP
does not have a valid rDNS. The IP Address it sent back is the main Public IP and not the Public IP assigned to our mail servers. Not understanding why the 2013 mailbox users can send to these external addresses no problem when 2010 mailbox users
are being routed through 2013. Thanks for any help.

Hi,
According to your post, I understand that account in Exchange 2010 deliver message failed for certain external addresses, however the user in Exchange 2013 works fine.
If I misunderstand your concern, please do not hesitate to let me know.
Whether all user in Exchange 2010 or some special account experience this question?
If this issue only occur on some specific external address, please contact its administrator to double confirm the configuration of anti-spam filter.
Besides, I recommend run Message tracking log and Protocol log to check the deliver process. More details about “Analyzing the protocol logs and Message tracking logs in Exchange 2013”:
http://social.technet.microsoft.com/wiki/contents/articles/23182.analyzing-the-protocol-logs-and-message-tracking-logs-in-exchange-2013.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

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 2010 to 2013 users migration

Hi,
I am migrating users from Exchange 2010 to 2013 and facing a lot of migration issues. few of them are as follow.
1. It hung up at "syncing" and end up with a failure.
2. After a long migration i got the following errors
Error: MigrationPermanentExeception: Failed to reset the target mailbox after the move. Error Details:MaipExceptionADUnavailable: Unable to prepopulate the cache for user :: on domain controller xyz.domain.com (hr=0x80004005,ec=2414) Diagnosti Context: Lid:
65256 Lid:1494 ---- Remote Context Beg ---- Lid: 52664 StoreEc: 0x96E Lid: 35973 StoreEc: 0x96E Target Mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible.
Error details: Target mailbox connection was lost.
3. users migration is taking a lot of time although mailbox size is not big and both servers are in same datacenter.
Need urgent help pls....

Hi,
Here are the general steps for troubleshooting mailbox moves:
1. If the move request didn't complete, view the Move Request Statistics.
2. If the move request completed with errors, view the move report.
3. View the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
4. use the Exchange Management Console or the Exchange Management Shell to increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service.
For more detailed information about general steps for troubleshooting mailbox moves, you can refer to the article below:
http://technet.microsoft.com/en-us/library/dd638094(v=exchg.141).aspx
Additionally, in order to narrow down the cause, I’d like to confirm the following information:
1. Are the problematic target mailboxes in the same database?
2. Is there a time boundary? After that, you cannot move mailboxes:
http://social.technet.microsoft.com/Forums/en-US/90403f75-e530-478a-ab68-27823b730f68/exchange-2013-batch-to-migrate-users-from-2010-database-is-hung-at-syncing-after-a-disaster?forum=exchangesvrdeploy
Thanks,
Angela
Angela Shi
TechNet Community Support

Send As Permissions - Exchange 2010 - Outlook 2013

Similar Messages

Maybe you are looking for