Exchange 2013 Installation Issues

Let's document my frustrations with installing and setting up Exchange 2013 on my Server 2012 Standard Edition Server.Steps taken before hitting install:Installed Server 2012 Standard and rebootedCreated a VSS for posterity sake.Downloaded CU2 fromhereInstalled Server Roles in PowerShell: Install-WindowsFeature RSAT-ADDSInstall-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,...
This topic first appeared in the Spiceworks Community

Hi,
As additional, I want to double confirm whether external user cannot receive message send from your environment and contain attachment, or cannot send message with attachment for external mail flow.
If it’s the former, it means mail flow works fine in your environment. You can contact administrator for destination forest to check attachment filter and transport rule.
If it’s the latter, this issue may be caused in your own configuration. We can check anti-spam filter, transport rule and send connector, run message track log and protocol log to find out the node for this issue.
More details about Anti-Spam and Antivirus Mail Flow, for your reference:
https://technet.microsoft.com/en-us/library/aa997242(v=exchg.141).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

Similar Messages

Exchange 2013 installation Problem on Hyper-V

Hello,
I have a very interesting problem Exchange 2013 installation step on Hyper-V.
I have 2 server. I installed on server Server 2012 R2 Standart. And then installed hyper-v role for both server.
I created virtual machine for first server and this virtual machine domain controller.
And then I created virtual machine for second server and this virtual machine Exchange 2013.
I installed all prequisites and exchange 2013 finished successfuly. When I opened https://server/ecp it give me http 500 internal error. I checked almost all forums but any recommendation didn't solve my problem.
And then I removed hyper-v role and installed vmware v11. and installed same applications like above.
Very interesting finished installation and opened ecp console. eveythink seen to good.!
Actualy I find problem.
There is exchange feature installation command on microsoft exchange prequisite. When ruunning this command installing two program on program and feature name is "c++ redistrubutable x64 and x32"
I must uninstall this programs before install unified communication api 4.0.
I cannot see on hyper-v when running this feature.
But I can see on vmware this features on programs and feature.
This is very absurt.
Anybody have an idea for this
Thank you for your clarify.

Hi,
Thanks for your reply.
I run this command before Exchange 2013 installation:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering,
RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell,
Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth,
Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging,
Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,
Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
later run this code on vmware platform , installing 2 program in programs and feature. name is Visual
C++ Redistributable package x64 and x86. I know Unified Communications Managed API 4.0
install same program too. But I must unintall Visual C++ Redistributable package before
install Unified Communications Managed API 4.0. But My problem I cannot see this two program
in programs and feature on hyper-v platform.
I tried it many times.

Exchange 2013 Install Issues

Hi everyone -
I'm having BIG issues with my Exchange setup. First off, I walked into a nightmare of a situation here and it seems everything is completely jacked up in terms of network and servers... I'm actually contemplating starting over 100% with everything,
but when I bring that up to upper management, they say it's not feasible.
We currently have Exchange 2007 SP3 with RU11. I found out that when SP3 was installed, whoever did it never updated AD or the schema. Now I can't do that because i'm on RU11 and it's giving me a version mismatch error. So I've decided
to move on to just upgrade to Exchange 2013.
I am on the beginning steps of doing this and I just ran: setup /PrepareAD /IAcceptExchangeServerLicenseTerms. When doing this I get the following nasty little error:
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
FAILED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
Cannot find the Recipient Update Service responsible for domain 'DC=kuder,DC=local'. New and existing users may not be
properly Exchange-enabled.
     One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installa
tion can't proceed until all Exchange 2000 or Exchange 2003 servers are removed.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
A couple of notes about this error:
1. I swear I've gotten some errors about the Recipient Update Service with Exchange 2007. I'm think that might have lead me to the schema upgrade issue I talked about earlier.
2. We DO NOT have Exchange 2000 or 2003 in our environment!!! Not sure where to even begin to remove the remnants of this!
Any help would be greatly appreciated.
Thanks,
Jeff

Thanks for the reply Cara... After further investigation last night it is clear to me that whoever upgraded us from Exchange 2003 to Exchange 2007, definitely didn't decommission the 2003 box correctly. (this was all done WELL before I came around).
I've checked into a few things that you asked about:
1. In ADSI Edit, I have 2 Administrative groups.  the first one (Exchange Administrative Group (FYDIBOHF23SPDLT)) shows the correct 2007 server in the CN=Servers, the other one (first administrative group) shows the old 2003 box
under CN=Servers.
2. I did get the schema update for 2007 SP3 to finally go. so when I looked in ADSI Edit, the Exchange Schema version is 14625 which according to that article is Exchange Server 2007 SP3, which is correct. Last time I looked, it was 14622,
which was for SP2. So we should be good there now.
3. The error with the RUS, was in Exchange 2007 BPA. After investigating this further last night, this is again because of failure to properly decommission the old 2003 box. Looks like I maybe need to remove any entries for Recipient Update
Service under ADSI Edit: CN=Configuration,DC=domainname -> CN=Services -> CN=Microsoft Exchange -> CN=First Organization -> CN=Address List Container -> CN=Recipient Update Services. There are two items in that location now, CN=Recipient
Update Service (domain) and CN=Recipient Update Service (Enterprise Configuration). From what I've read I can delete both of these since 2007 no longer uses this service.
4. No errors in the Application Log currently.
Other Notes:
1. Everything with 2007 appears to be working fine. No major issues.. I just want to upgrade us to Exchange 2013.
2. From the 2007 EMS, I ran: exchangeserver | ft name,admindisplayversion,exchangeversion. This showed me the following:
Name                       AdminDisplayVersion        ExchangeVersion
ADELSB01                   Version 6.5 (Build 7638... 0.0 (6.5.6500.0)
K01SIT003                  Version 8.3 (Build 83.6)   0.1 (8.0.535.0)
Definitely still showing the old 2003 Exchange box in there.
Thanks!

Exchange 2013 installation error

i have a server running server standard 2012 r2 recently upgraded from server standard 2003
it is a dc,dchp,dns.
i am trying to install exchange server 2013 standard during the installation i get the following error message.
and am unable to continue.
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")
" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\Administrator.example\AppData\Local\Temp\ldif.err'".

Hi,
Agree with Amit. And I also find some information for your reference:
Error 8224 is easily resolved by checking the Windows Firewall Profile and either.
A. Disable Domain Profile firewall as well as Private and Public Profles.
B. Disable or turn off Windows Firewall and change the state of the service to Manual.
More details in the following thread:
Exchange 2013 Error 8224
http://social.technet.microsoft.com/forums/exchange/en-US/318ef90d-59be-49b2-9202-688f80074418/exchange-2013-error-8224
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 installation fails

We're in the process of migrating from Exchange 2007 to Exchange 2013. I've followed the prerequisites, and have the necessary account permissions, but when I start the installation it fails at step 1 of 5 (mailbox role:mailbox service).
This warning shows up in the application log:
Event ID 2397
Process ExSetupUI.exe (PID=9844). Object [CN=Mailbox Database 1783948598,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<domain>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=local]. Property [Server] is set to value [<Exchange 2013 server name>
DEL:492ae292-f89f-4a29-b009-22a60973a4bf], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
This error shows up in the Exchange install console, as well as the application log:
Event ID 1002
Exchange Server component Mailbox role: Mailbox service failed.
Error: Error:
The following error was generated when "$error.Clear();
if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
else
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
" was run: "The Exchange server for the database object "Mailbox Database 1783948598" wasn't found in Active Directory Domain Services. The object may be corrupted.".
I should also mention that this installation was attempted once before by an ex-coworker, and it failed. I've spent hours searching Google but haven't come up with a solution. Does anyone have any ideas?

Check it at Exchange 2007 side, Get-MailboxDatabase -Server E2007ServerName or via EMC to confirm but if msExchOwningServer/msExchMasterServer
points to the server which is stale 2013 server then it shouldn't be connected to E2007 by any way and you are good to remove those...
But I wouldn't touch another DB which has just server name and not servername\0ADEL:guid
as it is not giving error (at least yet...) in the setup
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 backscatter issue - recipient validation without Edge

Hello all,
It looks like there is a flaw by design in Exchange 2013 recipient validation, which in turn causes backscatter issues. I failed to find a way around it, maybe someone could help.
The Design: 2 x Exchange 2013 CAS + MBX servers (hardware NLB & DAG)
Version: Exchange Server 2013 Cumulative Update 3 (CU3) (Version
15.0 (Build 775.38) )
The issue:
Recipient validation has a flaw, which is documented (probably that should make it a "feature", but it doesn't):
In short - Recipient validation on Mailbox servers blocks message to all recipients, if at least one of them is non-existent.
http://social.technet.microsoft.com/Forums/office/en-US/12181f43-7173-44dd-998a-9307f92ffc5d/exchange-2013-casmbx-recipient-validation-rejects-entire-message-if-any-of-recipients-are-invalid
As there is no way to explain the logic of blocking e-mails to valid recipients if at least one of them is invalid to a customer, the Recipient validation on Mailbox servers becomes unusable and is disabled.
But if the recipient validation is disabled, the Exchange design without Edge servers or other perimeter SMTP servers that could block e-mails to non-existent recipients, becomes vulnerable to backscatter SPAM attacks, since Exchange will always send out
NDR to the FROM address.
According to the answer in the thread mentioned above, other antispam features should prevent it, but as always with antispam - it's not even close to 100% effective, as recipient validation would be. The result - an entry in backscatterer.org.
Question: How to prevent backscatter in Exchange 2013 without Edge servers, and without loosing valid e-mails due to recipient validation bug ("feature")?
Thank You for Your help.
Sincerely,
Vince

Hello,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migrating public folders to exchange 2013 hebrew issue

I am migrating public folders to exchange 2013. half of them a named in hebrew.
The migration fails, the error is character related.
Is it possible at all to migrate hebrew named public folders?

Hi,
Did you got the error message mentioned in the following thread?
http://social.technet.microsoft.com/Forums/exchange/en-US/8b383a46-b710-4fc0-aa0b-e52f288cf93d/e2010-to-e2013-public-folders-migration-failed?forum=exchangesvrdeploy
If so, please check if they are mail-enabled public folders. If they are mail-enabled public folders, please make sure there are no invalid characters in alias.
Based on the description, you couldn't migrate public folders named in Hebrew, other public folders could be moved successfully. If I misunderstood your concern, please let me know.
If the issue persists, I'm afraid you need to rename these public folders in English.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Q10 on Exchange 2013 AS issues

Hello Gents,
So we have moved over to exchange 2013 and we are having issues with the Q10 using active sync. When the phone is setup initially it works perfect, everythings syncs and updates as it should. After a day or so, there is alot of intermittent connectivity.
For instance, calendar appointments updated on outlook will not reflect on the phone and vice versa. Yesterday it just stopped receiving emails as a whole for a while. It is not the users account because he also has a Galaxy note 3 using active sync and everything works just fine both ways.
Is there a known issue on the Q10's with active sync?
Any work arounds?
Please advise,

Hi I have the same problem and I can't understand why.....

Exchange 2013 mailflow issues & transport latency

Hi,
we have more then 50 Exchange Server 2013 deployed and every single Exchange has transport issues.
-the transport Service do not respond for 30 min or more.
-RAM consumption
-the e-mail are stock in outlook for long time
-we have Exchaneg 2013 with all CUs / SP1 version installed and i cannot see any improvement.
I m disappointed and i hope that someone can help me to understand the Exchange 2013 Mailflow
Best regard

@ 1 i want to say thanks all of you for the Replays and for helpful information.
Yes i have a Transport Agent on the Computer for Archiving S.Nithyanandham
I fix the Problem with the Microsoft Script and now i will wait to see any improvement.
After i set the eventlog to high i can see
event id 12028
The process with process ID 11596 is holding the performance counter connections current Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 11596 StartupTime: 130566455797932178 from instance _total(CFBEE918) RefCount=0 SpinLock=0 Offset=32 and category MSExchangeTransport
SmtpSend while running processes are: Processes running are:
5908 w3wp
8468 msdtc
13736 powershell
1964 sftracing
20864 UMWorkerProcess
4128 MSExchangeDagMgmt
3468 Microsoft.Exchange.Diagnostics.Service
1368 mqsvc
4912 w3wp
12988 RuntimeBroker
2152 Microsoft.Exchange.Directory.TopologyService
388 svchost
6876 MSExchangeMailboxReplication
3132 MSExchangeSubmission
2540 MSExchangeMigrationWorkflow
19284 iexplore
2932 noderunner
10416 w3wp
16136 conhost
564 svchost
20352 conhost
1144 Internal.Exchange.CADNArchivingService
2132 WMSvc
12828 ParserServer
4296 scanningprocess
4688 GXHSMService
19244 conhost
17096 Microsoft.Exchange.Imap4Service
22020 vmtoolsd
4092 Microsoft.Exchange.UM.CallRouter
3696 MSExchangeThrottling
5664 Microsoft.Exchange.EdgeSyncSvc
344 csrss
736 svchost
14328 ParserServer
1128 svchost
19660 WmiPrvSE
5904 Microsoft.Exchange.Imap4
2108 svchost
21412 mmc
3464 w3wp
1316 cvd
6040 MSExchangeFrontendTransport
15560 iexplore
916 svchost
1504 hostcontrollerservice
16672 taskhostex
16868 explorer
9972 w3wp
712 svchost
4060 umservice
6620 svchost
6616 w3wp
13116 svchost
704 dwm
7204 Microsoft.Exchange.Store.Worker
15900 iexplore
108 winlogon
24732 conhost
500 lsass
696 Microsoft.Exchange.Store.Service
5816 Microsoft.Exchange.Search.Service
1480 svchost
1280 fms
7976 dllhost
1080 spoolsv
684 LogonUI
22248 mmc
20040 rundll32
10924 w3wp
13612 conhost
6588 MSExchangeMailboxAssistants
21952 conhost
1464 SMSvcHost
23816 mmc
16828 mmc
2640 noderunner
2836 noderunner
4608 EvMgrC
16700 Microsoft.Exchange.SharedCache
5196 w3wp
15636 MSExchangeHMWorker
6396 mmc
9044 Microsoft.Exchange.Imap4Service
4400 SMSvcHost
1836 nsclient++
3016 Microsoft.Exchange.RpcClientAccess.Service
1636 inetinfo
15424 csrss
1436 vmtoolsd
1828 ForefrontActiveDirectoryConnector
9384 w3wp
24148 MSExchangeTransport
6552 w3wp
4384 scanningprocess
4972 Microsoft.Exchange.AntispamUpdateSvc
3788 MSExchangeTransportLogSearch
14644 rundll32
19348 Microsoft.Exchange.Imap4
432 winlogon
22692 conhost
23676 rdpclip
2792 noderunner
4564 scanningprocess
228 smss
5152 MSExchangeDelivery
620 Microsoft.Exchange.ServiceHost
9484 w3wp
22216 ParserServer
5736 MSExchangeHMHost
1992 updateservice
21296 iexplore
21004 dwm
8292 WUDFHost
608 svchost
16768 conhost
396 csrss
5136 Microsoft.Exchange.Store.Worker
800 svchost
11240 w3wp
404 wininit
7692 svchost
9716 w3wp
492 services
4 System
24748 ParserServer
2760 msexchangerepl
0 Idle
event 2006
Send connector Inbound Proxy Internal Send Connector: the connection to xxx.xxx.xxx.x:2525 was disconnected by the remote server.
event 2128
Process w3wp.exe (ECP) (PID=10924). Object CN=HealthMailbox526969de2c35417c8a01222265520c3e,CN=Monitoring Mailboxes,CN=Microsoft Exchange System Objects,DC=domain,DC=dc was not found on the Domain Controller %hostname%. This may indicate a replication or
permission issue.
event 1012
The store driver failed to submit event 18522569 mailbox d57dd45b-f3e9-492d-b23c-0fea92c8dd85 MDB 7b71f84c-1bd3-4b16-a8a9-dca18f50fbb5 and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException
   at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase submissionItem, TransportMailItem message)
   at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem()
   at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<FailedSubmissionNdrWorker>b__0()
   at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
event id 1023
Windows cannot load the extensible counter DLL ASP.NET_2.0.50727. The first four bytes (DWORD) of the Data section contains the Windows error code.

Exchange 2013 SPAM issues

I have a new install of Exchange 2013, I enabled the anti-spam features. From day one, my server has been sending out NDR spam from "Sender" <> (no sender just the two "<>") to user.ru, user.ro, user.gr, etc.
This issues is driving me crazy and there is almost zero info on the net with this issue. I find it hard to believe a clean install does this right out of the box. In Exchange 2007/10, I just have to tic a box in the transport agent.
Can someone help me please, I'm lost. Hell I even installed GFI this morning just to see if that would make a difference and even GFI is letting the SPAM <> mail through without any issues. It's just a matter of time before my server is
blacklisted...
Thanks you,
TCMagic

Well that did not fix the problem. My server is still sending spam. Here's what one of the messages look like (I removed my actual domain):
Identity: mail\71\627065225217
Subject: Undeliverable: Never lose a food storage container again
Internet Message ID: <[email protected]>
From Address: <>
Status: Ready
Size (KB): 212
Message Source Name: DSN
Source IP: 255.255.255.255
SCL: -1
Date Received: 4/13/2013 1:00:13 PM
Expiration Time: 4/15/2013 1:00:13 PM
Last Error:
Queue ID: mail\71
Recipients: [email protected];2;2;;0;CN=InternetConnector,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group
As I look at this the SCL rating is -1 so the server thinks is good mail. Can someone help me here?
Thank you

Exchange 2013 Search Issues

We are having many issues with users being able to search old emails since migrating to Exchange 2013. We have renamed the search index files and rebuilt multiple times and they all state healthy at this time but users are still having issues finding
old emails. Trying to see if this is a product issue or a server issue and if so what needs to be done. Using Standard edition with 5 databases at this time.

Hi,
Thank you for your question.
Is there any error when we search email in outlook or OWA? I suggest we could post error to
[email protected] for our troubleshooting.
Did user search email within a week? Because we want to know if those emails were deleted by Retention Policy.
Are there relevant event id or application log?
We could make sure the service of “Microsoft Exchange Search” is running on all Exchange mailbox server. if the service of “Microsoft Exchange Search” is running on all Exchange mailbox server. we could restart it to check if the issue persist.
If OWA could search email, we could rebuild the outlook profile to check if the issue persist.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Tricky Exchange 2013 send issue - im stumped...

Hi everyone,
I ran into an issue this morning in my Exchange 2013 SP1 environment today that has me stumped. Like most issues, it just happens. No changes, patches or updates to the system were applied and the system was normal until now. Here is my problem –
My Outlook users have their own mailboxes, and my company has a Help Desk email box that has its own user account. My users are set up via Exchange / Outlook to have their own mailboxes and full access to Help Desk mailbox in their Outlook .
Each Outlook client in configured with the users account, and the Help Desk account because users want to be able to hit the FROM button in Outlook and chose whether a reply comes from them personally or the Help Desk mailbox. This has worked great,
up until now.
All of a sudden, you cannot send from the Help Desk account anymore. The mailbox opens up, a user can see and access all the mail and it is receiving email fine. But if a user wants to reply or create NEW email, choses FROM and uses the Help Desk account
they get this error on sending
Sending reported error (0x8004010F) Outlook data file cannot be accessed.
The users regular account works fine.
I recreated the mail profile, didn’t help the issue. I checked on OWA and if you access the Help Desk account on its own it sends fine.
If you create an email from your own email account and CC the Help Desk, it sends fine.
All users have Full Access permission and Send As permission on the server.
Nothing has changed that I know of and this worked totally fine for almost a year until today, it just stops working.
Any ideas, I’m totally stumped… I have to apply CU7 still this weekend, maybe that will do something. But as of now I cant even see any real errors as to whats going on here.
Ric

Hi,
In your case, please check the autodiscover and OAB by using "Test E-mail AutoConfiguration".
If autodiscover fails, please troubleshoot the autodiscover by directly accessing the autodiscover url via IE and let me know the error code. If autodiscover works, you need to troubleshoot the OAB generation, publishing and downloading issues.
For OAB generation and publishing issues, you can check the application logs on the CAS and Mailbox servers. For the OAB downloading issue, you can manually access the OAB url via IE and see if there is any error code.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Introducing Active Directory sites AFTER exchange 2013 installation

Hi
We have multiple physical sites and only 1 active directory site. Email environment is pure on-premises exchange 2013. Each physical site has CAS/Mailbox servers. There are not IP restrictions between these physical sites. Everything
is outlook anywhere obviously.
I would like to introduce NEW AD sites for each of these physical locations.
Do you see any major issues that I need to be aware of?
Can this be done in the middle of the day?
Will there be pop ups in outlooks and disconnects?
I appreciate your help.

I haven't had to do this before, but I would probably schedule this at night as there are some changes that will need to be made on the Exchange side of things.
Once you have the new AD Sites configured (Make sure you have at a minimum one Global Catalog, although I would recommend at least 2 in each AD site). You should cycle the AD Topology Service on each Exchange Server (this is going to cause all services
to restart so do it one at a time).
You should also use Set-ClientAccessServer and set the proper site scopes that you want Autodiscover to respond to.
I'm sure there's more, but that's what I can think of at the moment.
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

Move Exchange 2013 installation to new virtual machine

Currently have: 1 virtual server - Server 2012 (DC, Global Catalog), Exchange 2013 CU1 installation (yes I know- dont install Exchange on DC etc etc ... ). Server2012/Exchange2013 is installed on one VMDK, EDB and logs are saved on another VMDK.
Want to do: Create second virtual machine and install Server 2012 (different name), add it as a member to the same domain (also in the same network), install Exchange 2013, move all mailboxes to the new server, uninstall the old Exchange 2013.
Question is- is it possible to somehow unmount the existing database (I am only using one database for mailboxes and public folders) and mount it to the new server or do I have to create a new database on the new server and move the mailboxes there? I've
heard that the Exchange EDB databases were supposed to be portable between same versions of Exchange.
Any advice is appreciated.

Hi,
Agree with Andy, to avoid down time, we can depend on database portability.
And here are the steps you can refer to:
1. Install new Exchange server on the member server.
2. Move Mailbox Database using Database Portability:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
3. Move the public folders (if any), re-home the offline address book, and move your SMTP connectors
http://support.microsoft.com/kb/822931
4. Remove the old Exchange server.
Thanks,
Angela Shi
TechNet Community Support
Thanks for the reply.
I'm a bit confused on the instructions from
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx- does step 4 instruct me to overwrite the newly created database (on the new server) with the old database and then mount it on the new server? Also, as the public folders are now in
a mailbox on the same database- aren't they moved with the database without extra hassle?
Also the link you gave me in Step 3 in your post refers to Exchange 2003.
Thanks in advance.

Exchange 2013 Installation

I am installing Office 365 online for my network. The present setup is that I have pop 3 mailboxes with my ISP - I don't have any exchange installation.
My question is should I install Microsoft exchange 2013 locally and then move online OR should I simply install online -- when I look at the Exchange Server Deployment Assistant it seems to work with upgrading installations as opposed to clean installs.
Apols if this Q has an obvious answer.
Rgds
O

Hi
As per the information and details provided by you, I think you should install Exchange 2013 on a member server.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

Exchange 2013 Installation Issues

Similar Messages

Maybe you are looking for