Exchange Server 2010 Anti-Spam Update Issue

Hello,
We are not receiving bi-weekly anti-spam updates via Windows Update. The last update that we received was on 1/20/2015 with v3.3.14519.472
Does anyone has the same issue and possibly fix for it?
Sierra

Hi,
Based on my research, the Microsoft Exchange Server Standard Anti-spam Filter Updates v3.3.14519.472 is the latest update for Exchange Standard Edition.
http://catalog.update.microsoft.com/v7/site/Rss.aspx?q=exchange+server+2007+anti-spam&lang=en
If there are any issues related to Anti-Spam setting, I recommenf the following documents:
1. To avoid spoof, I suggest configure SPF record.
http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/
2. Please make sure you didn't configure open relay. Provide a related KB for your reference, even though it applies to SBS.
How to block open SMTP relaying and clean up Exchange Server SMTP queues in Windows Small Business Server
http://support.microsoft.com/kb/324958
3. Share a useful article for your reference to configure the Anti-Spam.
https://technet.microsoft.com/en-us/library/aa997242.aspx?f=255&MSPPError=-2147217396
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]
Lynn-Li
TechNet Community Support

Similar Messages

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013
Detected Problems:
- Access denied for attached mailbox (department mailbox)
- Access denied for delete or move messages on own mailbox
- Can't send new messages with error (Error: [0x80004005-00000000-00000000])
Solution:
- Rollback to Exchange 2010 SP3 - Rollup 7
- You can rollback to Exchange 2010 SP3 - RollUp 7 in 30 min
Algunos de los destinatarios no recibieron su mensaje.
Asunto: Hola
Enviado el: 11/12/2014 8:35
No se puede localizar a los destinatarios siguientes:
'[email protected]' en 11/12/2014 8:35
Este mensaje no se pudo enviar. Inténtelo de nuevo más tarde, o póngase en contacto con el administrador de red.
Error: [0x80004005-00000000-00000000].

See the following forum thread:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8

Exchange Server 2010 Edge Transport Subscription Issue while moving Internal CA Certificate to 3rd Party Certificate

My Client have a Exchange 2010 Organization with Single Domain Single Forest.
They were using Internal CA Certificate and a TLS Cert.
As a POC we are doing a POC for Exchange 2010 Hybrid Office 365 Environment.
For this 3rd Party CA is Mandatory and they have bought a Geo Trust Certificate.
Now when they have installed cert on both HUB as well as EDGE servers, he was prompted to do edge subscription again.
HUB and CAS are combined on the server at both Main and DR Site.
When they try to do edge subscription again they are getting the following error.
SYED WASIL UDDIN Infrastructure Consultant/System Engineer Premier Systems (Pvt.) Ltd.

I was finding out the solution and got this.
1-Certificate will import on both EDGE and HUB Servers.
2-Edge Sync will use Self-Sign Certificate (but I an unable to find how do I configure this)
3-some communication between Edge and Hub will be encrypted via 3rd party Certificate.
Could anyone suggest, which services on HUB must based in this 3rd party cert.
All the external communication must be encrypted via 3rd party CA and communication between HUB-EDGE will set on self-sign Cert. How do I do this.
SYED WASIL UDDIN Infrastructure Consultant/System Engineer Premier Systems (Pvt.) Ltd.
Hi,
Please run Get-ExchangeCertificate | fl to check your Exchange certificate settings. Also confirm if the 5E470560626E313646730C177FCA66728E2BAFF7 certificate is your trusted 3rd party cert.
Please use Enable-ExchangeCertificate cmdlet to assign SMTP service to your self-signed certificate in your Edge server.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 update after Update Rollup 5 for Exchange Server 2010 (KB2407113)

Mine exchange server 2010 standard has Update Rollup 5 for Exchange Server 2010 (KB2407113) as latest update.
Can someone help me which update i can install after this, can i start with
Update Rollup 1 for Exchange Server 2010 SP1.
Many thanks in advance

My recommendation will be:
Remove update roll-up 5
Install SP1 check that everything is working
Install SP2 check that everything is working
Install SP3 check that everything is working
I think it will be risky for you to go straight to SP3.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Exchange 2010 Mailbox automapping issues after updated to Rollup 5 for Exchange Server 2010 SP3

Hi,
i have problem with Outlook Uses who have Full Access on other mailbox.
An authentication window pop up very time a user start Outlook.
If i remove the access everything is ok.
if i insert manual the mailbox everything is ok
The System was for 3 days ago updated to Rollup 5 for Exchange Server 2010 SP3
Before the update, was no issue.
i will appreciated any help
Thanks

Same issue here. 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.

Any known issue reported for "Rollup 8 for Exchange Server 2010 Service Pack 2"

Hello,
Currently our servers are running with "Exchange 2010 SP2 RU7", we are planning to update the Rollup version to RU8 for SP2.
Is there any knows issues reported for "Rollup 8 for Exchange Server 2010 Service Pack 2" till now ? is it safe to update the RU8 ?
http://www.microsoft.com/en-us/download/details.aspx?id=41394

(1) I had to roll it back:
The rollup released Tuesday the 9th caused random problems with systems ranging from general slow down to operation failed errors. It didn’t impact everyone at once and seemed to take 48hrs for everyone to have a problem. Rolling
back the update and rebooting the server seemed to resolve the issue.
Issues reported before the general mailflow stopping for everyone:
Nothing major … an occasional operation failed when I hit send but, it will go thru after I hit the send button a couple of times.
A MICROSOFT OUTLOOK BOX APPEARS WITH A TRIANGLE WITH A ! INSIDE IT. THE MESSAGE SAYS THE OPERATION FAILED.
(2)
ANOTHER CODE APPEARED WHEN I TRIED TO SEND THIS E-MAIL SO I CLOSED OUTLOOK AND RE-STARTED OUTLOOK. THE MESSAGE READ, CANNOT CREATE THE E-MAIL MESSAGE BECAUSE A DATA FILE TO SEND AND RECEIVE MESSAGE CANNOT BE FOUND. CHECK YOUR SETTINGS IN THIS MICROSOFT
OUTLOOK PROFILE. IN MICROSOFT WINDOWS, CLICK CONTROL PANEL.CLICK USER ACCOUNTS AND THEN CLICK MAIL. CLICK SHOW PROFILE, AND THEN CLICK PROPERTIES.
When he tries to open an e-mail, he gets an error message.
If he tries to mark an e-mail unread, he gets a different message.
Thanks Ben

Installing Update Rollup 7 for Exchange Server 2010 SP3

Hi,
I have 4 Exchange servers. Two CAS and two DAG. I am currently on Rollup 2 for Exchange Server 3010 SP 3. Can I install Update Rollup 7 for Exchange Server 2010 SP3 or do I need to install a previous one first?
Thannks!
Wave~Chaser

Hi,
When I try to install Exchange 2010 SP3 roll up 7, am getting the below error:
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may
be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
and please find below event log:
Product: Microsoft Exchange Server - Update '{A93DA06F-A5B8-4DF8-8B3F-B285E014C659}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions
on turning on logging support.
Can you please help me with this error.
Thanks

Exchange Powershell issue while loading the snapin on command prompt, in Exchange server 2010.

Hi,
When we launch the Exchange powershell via command prompt.. with below command:
PowerShell.exe -PSConsoleFile "D:\Program Files\Microsoft\Exchange Server\V14\Bin\ExShell.psc1"
it throws the following error:-
Following errors occured when loading the console
D:\Program Files\Microsoft\Exchange Server\V14\Bin\ExShell.psc1:
can not load windows powershell snap-in microsoft.exchange.management.powershell.e2010 because of the following error:
no snap-ins have been registered for windows powershell version 2
We are using Exchange server 2010 SP3 rollup 5 and EXCHANGE Server 2010 SP01.We see the issue on both the servers
Can you please provide the steps to reslove the issue.
Thanks & Regards,
Sanjeev Gupta

I have got the resolution of the problem. In my environment, the Powershell.exe which was being launched from command prompt, was 32 bit exe, while it was needed 64 bit exe.
It was occuring because in system path there was 32 bit powershell.exe was present. So, after replacing the exe with 64 bit exe, the problem was solved.
Thanks for the help provided above..
Regards,
Sanjeev

Microsoft Exchange Server 2010 SP3 update to Update Rollup 8-v2 for Exchange Server 2010 SP3

i have Microsoft Exchange Server 2010 SP3 and i would like to update to Update Rollup 8-v2 for Exchange Server 2010 SP3.
what is the best way to do so?
my current env:
Name : xxxxxxxx
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, HubTransport
Site : domain/Configuration/Sites/xxx
Name : yyyyyyyy
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/yyy
Name : cccccccc
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/ccc
Name : dddddddd
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : ClientAccess
Site : domain/Configuration/Sites/ddd
Name : iiiiiiii
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/iii
thanks
Mayson

Consider referring to the articles below and that explains it all.
Install the Latest Update Rollup for Exchange 2010 - https://technet.microsoft.com/en-us/library/ff637981.aspx
Applying Service Pack and Rollup Updates on Exchange Server 2010 (Part 1) - http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/applying-service-pack-and-rollup-updates-exchange-server-2010-part1.html
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Update Rollup 6/7 for Exchange Server 2010 SP2

Our config :
Version 14.2 (Build 247.5)
2 Mailbox servers (DAG), 2 CAS/HUB Servers using a NLB, 2 edge
my question is the following:
can i go directly to rullp 7 without installing 2,4, 5, 6 or I have to install all rollup ?
and what's the bests practices for installing rollup ?

Hello,
You can install rollup 7 directly without installing rollup 2,4, 5, 6.
You should install rollup 7 on your Exchange 2010 server roles in the following order: Client Access/ Hub Transport ,Mailbox and Edge Transport.
Please refer to the following article to install rollup 7 on CAS Array Members. (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does
not guarantee the accuracy of this information.)
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-cas-arrays/
Please refer to the following steps to install rollup 7 on Database Availability Group Members.
=============================================================
1. Run the StartDagServerMaintenance.ps1 script on the server being updated.
2. Install the update rollup .
3. Run the StopDagServerMaintenance.ps1 script .
4. Re-balance the DAG, as needed .
Here is the article for your reference.
http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

My exchange server 2010 always receive spam mail

Hi.
My exchange server always receive spam mail. All the mail account receive junk mail. I have tried to setup the Anti Spam Content Filtering and set it to '2'. But still receive spam mail. Is there another way to prevent my exchange server receive the spam
mail?
Thank You

Nearly everyone subscribes to a cloud message hygiene service or have on-premises appliances nowadays.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange server 2010 sp2 slow issue

My Exchange server 2010 sp2 performance very slow in morning time 9 to 10 AM and evening time 4 to 5 pm only and other time working fine

Hello,
Forums for Exchange versions prior to Exchange 2013 are over here:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserverlegacy&filter=alltypes&sort=lastpostdesc
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Exchange Server 2010: Incoming mail not delivered

I have an Exchange Server 2010 Standard with all recent patches and updates.
-It has been in service for 3 years without any issues.
-There is plenty of hard drive space for the logs and the data (over 100GB in each)
-The current size of the mail database is 150GB
-There is no registry entry in place limiting the size of the database ([url="http://technet.microsoft.com/en-us/library/bb232092.aspx"]Database Size Limit in GB as outlined here[/url]
Starting a few days ago, incoming mail is reaching the server but not being delivered to user mailboxes. Internal mail works fine when this happens. Looking at the Queue Viewer doesn't show anything abnormal. The Submission Queue shows nothing.
It is only after I reboot the Exchange Server that the Submission queue will show all the messages waiting to be delivered and they will all be delivered successfully after the reboot. The event logs do not show any error messages.
The server will continue to run fine for a few hours and then the problem starts all over again.
What could be causing this?

Any 3rd party antivirus/anti-spam software installed on the server? If so, disable and test.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

Send As, Send on Behalf and Full Access for Exchange server 2010/2013

[This FAQ contains 2 parts]
Testing and watching the behavior of Send As, Send On Behalf and Full Access permission.
Common issue and Troubleshooting on the three permission.
[Testing and Watching]
Based on following blog, I decide to test on my lab:
Full Mailbox Access Rights + Send On Behalf = Send As ?
http://blogs.technet.com/b/ehlro/archive/2012/04/06/full-mailbox-access-rights-send-on-behalf-send-as.aspx
Description on my lab and test:
Exchange 2010 + Outlook 2010
Exchange 2013 + Outlook 2013
Senders: A01, A02, … , A07, A08
Recipient: A09
A01 grand permission to other senders.
Two methods:
a. Use A0x’s credential configure A01’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
b. Use A0x’s credential configure A0x’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
Result as following forms:
1. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A01’s mailbox, then send From both A01 and A0x
To A09.
2. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A0x’s mailbox, then send From both A01 and A0x
To A09.
[Common Issue]
1. [Issue]
Exchange 2010 + Outlook 2010. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
You can’t send a message on behalf of this user unless you have permission to do so. Please make sure you’re sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Details as following pic:
[Troubleshooting]
1) Based on the NDR, it seems a permission issue. Check Send As permission, however the Send As permission configured correctly. Pic as below:
2) ince the Send As permission configured correctly, it seems the permission hasn’t been replicated. Try to restart Microsoft Exchange Information Store service. It works.
Note: The Send As permission isn’t granted until after replication has occurred. Replication times depend on your Exchange and network configuration. To grant the permission immediately, stop and then restart the Microsoft Exchange Information
Store service.
2. [Issue]
Exchange 2013 + Outlook 2013. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
Your message did not reach some or all of the intended recipients.
Subject: xxx
Sent: xx/xx/2014 8:20 AM
The following recipient(s) cannot be reached: A09
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Details as below:
[Troubleshooting]
1) Also check the Send As permission configuration first.
2) Then try to use A03 send as A01 to A09 via OWA. If OWA works well, it seems and issue on the Outlook client side.
3) This behavior may occur if the OAB in Outlook isn’t updated. Try to download OAB manually.
4) If doesn’t work, please close Outlook and try to delete all the OAB folder on your computer. The path of OAB folder in Win7, Win8 as below:
\Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books
5) Restart Outlook.
Note: Be aware that you cannot send e-mail messages on behalf of a mailbox if the mailbox is hidden from address list. When sending a message, Exchange requires that e-mail address is resolved in the
From field.
3. [Issue]
Exchange 2010. A01 grant A0x “Send As” or “Send on Behalf” permission. A0x send as/ send on behalf of A01. The message is only copied to the Sent Items folder in A0x’s mailbox (same as the result of my test). Also cannot configure Exchange 2010 so that the
message is copied to the Sent Items folder of both A01 and A0x.
[Troubleshooting]
This issue occurs because Exchange server 2010 was designed to copy message to the Sent Items folder of the sender only. This issue can be solved by installing Exchange 2010 SP2 UR4. More details in the following KB:
Messages that are sent by using the "Send As" and "Send on behalf" permissions are copied only to the Sent Items folder of the sender in an Exchange Server 2010 environment
http://support.microsoft.com/kb/2632409/en-us
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Nice guide Mavis, I recently explored the same topic. Few things you might want to add is the type of connectivity (Cached vs Online will produce different results) and to expand further on the methods of adding the other mailbox in Outlook (additional mailbox
vs additional account defaults to different methods). Check the screenshot:
And please post this somewhere more visible, like blog/wiki page.

Exchange Server 2010 Anti-Spam Update Issue

Similar Messages

Maybe you are looking for