Hi
A bit of a new-year challenge for anyone into Exchange server.

We are migrating from a Windows Small Business Server 2011 to Windows 2012R2 + Exchange 2013 on premise. Something I have done successfully for several clients over the past 2 years.

So I had a working WS2012R2 fully Windows updated as of last night, joined to the domain, Exchange prerequisites installed and all ready to install Exchange this morning.

This morning Exchange installed, it seemed happy enough with the install, we could access ECP web page happily and running powershell said that it was 'connected' to our new EX13 server. However when I run 'get-exchangeserver' only the Exchange 2010 server shows in the list, not the Exchange 13. Part of the problem with this is that powershell also didn't recognise the existence of the mailbox database, so trying to eg. move the edb path would fail. I forced it with 'configonly' or similar switch and manually moved the files, but I wasn't happy with the situation. Various attempts to repair and such didn't get very far until a force-delete of the PRogram files\Microsoft\Exchange Server folder

Eventually I ditched the new Exchange 2013 server install, reinstalled WS2012, re-install prerequisites and installed exchange in /m:recoverserver (and by the way /iacceptmicrosoftexchangeserverterms is a ridiculous switch to have to type so many times!). This time, following some advice I saw, I copied the install files to a local disk instead of installing Exchange from UNC. Same result, the server isn't listed and nor is the database in powershell, despite them both being listed and happy in the ECP.

As far as I can tell there are no network issues, AD is syncing and replicating happily between SBS11 and WS2012R2 (separate WS2012 to the Exchange install, obviously). I should also note that the download from the Action Pack site for Exchange SP1 wouldn't complete, so again following advice I found online I simply extracted the EX13 CU11 files and installed from there, IE not from an ISO download.

Anyone think of anything to try next?

Thanks

== Minor Update ==

Running get-exchangeserver -identity <myEx13Server> DOES return information, but still not showing in get-exchangeserver get-mailboxdatabase. I might have found an AD replication issue on one of my DCs but looking in ADSI Edit on that server, the Exchange13 server does show up under the administrative group, and also that server replicates without issue via AD Sites and Services. Thanks.

===== As a wise man once said to me - have a sense of proportion.

Dear all,

I have a exchange 2013 environment that I want to delete, because all the mailboxes are migrated to Exchange Online.

When I try to remove Ex2013, i receive following error

There is one mailbox SystemHealth and that's an arbitration mailbox.
I can't remove this mailbox because I receive the following error

Couldn't disable the arbitrationmailbox because it is associated with existing recipients for whick membership restriction of approval is required or the moderation feature is enabled.

Can somebody help me out with this?

KR

K.

I am the proud new owner of my organizations Exchange environment. We are running 2007 SP3 which I understand there is no direct upgrade path to 2016 for.

My question is should I upgrade us to 2010 so that we can move to 2016, or should I just go straight to 2013? We will be running a Hardware refresh cycle in spring of 2017, and 2007 is already outside of mainstream support. If I push for us to go 2013 now we can easily do that with our existing hardware, but if we move to 2010 then waiting 1.5-2 years for hardware and I may not get approval for 2016 - a tough call.

Obviously fewer upgrades would be easier on me from a time perspective, but I'm not so much worried about that as I am about getting this environment stable (inheritance is a grand thing). So, recommendations? Also, any tools to make it easier that anyone could recommend would totally rock!

Thanks in advance.

Hi, 

Could you please help on the following scenario?

We have an MS Exchange 2010 on-premises server and an Office 365 hybrid environment at the moment.

Now, we need to migrate the MS Exchange server to 2013 or 2016 version. The new server is located in a different location geographically. After this happened we need to remove the 2010 server from the organization.

Unfortunately I didn't find any article what contains exactly this scenario (hybrid migration on different locations).

My questions:

Is the geographically distance make any different compared with a migration what happen on one site?

Is it possible to keep the hybrid server settings during the migration?

If there is any article about the hybrid server migration scenario what I can follow, please let me know.

What do you suggest for this task? Exchange 2013 or 2016?

If I am correct the hybrid connection settings are reset after the new server is added to organization. Could somebody please suggest any solution to back up and restore this settings? I have no really to much information where can I find these settings.

About the current setup: 

There are mailboxes on the Exchange server and on the cloud also. The primary SMTP server is the Exchange 2010 server.

The Office 365 is synchronized on the local domain controllers, users are managed on the local DCs.

Very much appreciated for any help!

Devin Berard I.T Support Renfrew Victoria Hospital, Renfrew ON berardd@renfrewhosp.com

Hello,

We have installed 2 new Exchange 2013 CU10 servers in our Exchange 2010 organization. We are now in coexistence phase. We need to proceed with the change with internal and external namespaces. When we proceed with the change of internal namespace Outlook clients are unable to connect or stay connected. Ultimately, the outlook client will stop responding. I can see that outlook client is trying to establish a connection but fails. It will continue to connect and disconnect for about 500 tries and stops responding. I have the same problem with Outlook 2010, 2013 and 2016.

All external mailflow and activesync functions correctly.

I have tried redirecting internal clients to both Exchange 2013 servers to eliminate a single server not properly configured.

Can someone help out?

Thanks,

Hi I'm new to PowerShell and I've been attempting to migrate an Exchange 2010 SP3 Public folder to Exchange 2013. I'm following the directions found athttp://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx .

I have gotten to Step 3 .\Export-PublicFolderStatistics.ps1 <Folder to size map path> <FQDN of source server>

It runs the command but when it attempts to write the CSV to the drive I get:

Export-csv : Access to the path '\\servername\sharename' is denied

I am running the Exchange PowerShell in Administrator mode

Within File Manager I have given:

the share Everyone Full permissions

NTFS Full permissions to:

Everyone, Domain Admins, Domain Users, Exchange Servers, Exchange Organization Admins,

PS] C:\Windows\system32>C:\ps_scripts\Export-PublicFolderStatistics.ps1 "\\server\sharename" server.domain.local
[11/21/2013 9:59:42 AM] Enumerating folders under NON_IPM_SUBTREE...
[11/21/2013 9:59:50 AM] Enumerating folders under NON_IPM_SUBTREE completed...25 folders found.
[11/21/2013 9:59:51 AM] Retrieving statistics from server SERVER
[11/21/2013 9:59:52 AM] Retrieving statistics from server SERVER complete...45 folders found.
[11/21/2013 9:59:52 AM] Total unique folders found : 45.
[11/21/2013 9:59:52 AM] Exporting statistics for 45 folders
[11/21/2013 9:59:52 AM] Exporting folders to a CSV file
Export-CSV : Access to the path '\server\sharename' is denied.
At C:\ps_scripts\Export-PublicFolderStatistics.ps1:221 char:70
+ $script:ExportFolders | Sort-Object -Property FolderName | Export-CSV <<<<  -Path $ExportFile -Force -NoTypeInformati
on -Encoding "Unicode";
    + CategoryInfo          : OpenError: (:) [Export-Csv], UnauthorizedAccessException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.ExportCsvCommand

[PS] C:\Windows\system32>

I have introduced an Exchange 2013 CU11 server into an Exchange 2010 environment. Exchange 2010 is updated to the latest Update Rollup of Update Rollup 12 for Exchange Server 2010 SP3.

Installation went just fine with not errors reporting. However, when I run Get-MailboxDatabase from the EMS, it only shows the databases on our Exchange 2010 server. I want to rename and move the default database instead of it being "Mailbox Database 12345678."

When I go into EAC, I can see the database in there just fine with no issues.

Any suggestions?

Thanks,

Eric

exchange is working mail working web mail working no event errors the only thing is that client access did not install 

this is from the log file, have search everywhere and cannot fin the solution

Thank you Christy

Hello I updated my organization from Exchange server 2010 to 2013 , all mailboxes are now on Exchange server 2013 i can send and receive emails from Outlook just fine, however i cannot send from OWA both internally and Externally. It just says following:

"Error: The message can't be sent right now. Please try again later."

I've tested all services are running fine, This is the only Exchange 2013 server we have. Cu11 i am running

Tries to reset OWA virtual directory and Restarted Application pools still no luck, Can anybody assist please?

When trying to install Exchange 2013 SP1, we're prompted with a login screen to input credentials for the O365 setup.
The credentials appear to work however we're unable to get past the hybrid deployment page as we're given the following message:

Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

When attempted to install Exchange 2013 w/o SP1, we're told that "Reading the Exchange online tenant failed with an exception".
I'm unable to see in the logs what this exception is.
I can confirm also that the exchange tenant is above v15 and 'isupgradingorganiztion' field is set at 'false'.

Following this article: http://stackzilla.com/how-to-prepare-ad-for-exchange-2013-server-install-in-hybrid-deployment/

This also fails. I can send through the Exchange Setup logs from the DC that this was run on if required.

Anyone have any ideas on this one? I see it has popped up a bit but not too much concise info as to how or what is causing it.

Hello,

i'm having an issue with a single-server 2013 CU9(it was installed as CU9 directly) when trying to update to CU10 in step 1 i got:

Error:
Se ha generado el siguiente error cuando se ejecutó "$error.Clear();
	install-CannedAddressLists -DomainController $RoleDomainController": "Microsoft.Exchange.Data.DataValidationException: El parámetro ResourceAddressLists no puede tener más de un miembro.
   en Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   en Microsoft.Exchange.Management.Deployment.InstallCannedAddressLists.PostOrganization(ADObjectId resAl)
   en Microsoft.Exchange.Management.Deployment.InstallCannedAddressLists.CreateCannedAddressList(String name, QueryFilter recipientFilter)
   en Microsoft.Exchange.Management.Deployment.InstallCannedAddressLists.InternalProcessRecord()
   en Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   en Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

excuse the spanish, it essentially says that ResourceAddressLists can't have more than 1 member.

after this Exchange stopped working, mail flow stopped completely, smtp gave service not ready, etc etc, i had to re-reun the setup and then it started working( a reboot wouldn't fix it).

what's going on?, am i better off with running the CU10 adprepare and the domainprepare manually before launching the CU10 setup itself?

Upgraded Lotus Notes version into newer 8.5 it has complex functionalities. These functions are not easily graspable and it takes long time to understand, I decide to export my data into another (MS Outlook) platform, is it possible, I want new updates about conversion in cost-effective manner. And if yes then suggests me the way?

Hello I updated my organization from Exchange server 2010 to 2013 , all mailboxes are now on Exchange server 2013 i can send and receive emails from Outlook just fine, however i cannot send from OWA both internally and Externally. It just says following:

"Error: The message can't be sent right now. Please try again later."

I've tested all services are running fine, This is the only Exchange 2013 server we have.

Please help.

Migrating from 2007 to 2013. Last night we attempted to migrate 1000 small mailboxes totalling something like 5Gb total.

Estimated this at around 7 hours. BUT its 20 hours and still going.

We've based our estimate on mailbox sizes which I dont think is correct. (i.e. 1000 mailboxes total 10Gb same as 1 mailbox 10Gb). Looks like number of mailboxes adds a large overhead.

Questions:-

1. Is there a procedure/tool to allow some sort of estimates of mailbox migrations to be produced?

2. Are there any recommendations/tuning suggestions for migrations? (i.e. max number of mailboxes migrated in parallel etc).

Hi,

I upgraded two separate test forests from CU10 to CU11. The versions before the upgrade are Exchange 2010 Sp3 RU11 and Exchange 2013 CU10. In both forest I see the same behavior;

The accounts used worked and still work fine in CU10 and have not been altered. Accounts I tested with are member of Domain Admins and Organization Management. I should be able to virtually anything.

With account 1, I connect to the CU11 server I cannot see the Exchange 2013 servers anymore. I also cannot see any databases or other resources on the other Exchange 2013 servers. If I connect to the Exchange 2013 CU10 server I can see all the other Exchange 2013 servers including the CU11 server.

With account 2, I connect to the CU11 server and I can see everything. Connecting to a CU 10 server still works fine

The only workaround that I could find is to create a new account and that works flawlessly. Moving the failing account to an Exchange 2013 CU11 database did not make a difference.

Using the account that fails using CU11 I also cannot perform a get-mailboxdatabase.When I try to do a new-moverequest for instance and I get an accessdenied exception...

The operation couldn't be performed because object 'mbxdb13100' couldn't be found on 'dc001.testdomain.com'.

below some examples using a simple get-exchangeserver cmdlet.

--------------------Situation 1------------------

Working, CU10, administrator@testdomain.com

 VERBOSE: Connected to Exchange201302.testdomain.com

[PS] C:\Windows\system32>Get-ExchangeServer | select name,edition, admin*

 Name                                                                    Edition AdminDisplayVersion

----                                                                    ------- -------------------

EXCHANGE201001                                               StandardEvaluation Version 14.3 (Build 123.4)

EXCHANGE201302                                               StandardEvaluation Version 15.0 (Build 1130.7)

EXCHANGE201303                                               StandardEvaluation Version 15.0 (Build 1156.6)

____________Situation 2___________________

Fault -  CU11 administrator@testdomain.com

 VERBOSE: Connected to exchange201303.testdomain.com

[PS] C:\Windows\system32>Get-ExchangeServer | select name,edition, admin*

 Name                                    Edition                                AdminDisplayVersion

----                                    -------                                 -------------------

EXCHANGE201001                          StandardEvaluation                      Version 14.3 (Build 123.4)

 --------------Situation 3, another account who appearently kept its permissions--------------

Correct, CU11 admin2@testdomain.com

 VERBOSE: Connected to Exchange201303.testdomain.com

[PS] C:\Windows\system32>Get-ExchangeServer | select name,edition, admin*

 Name                                                                    Edition AdminDisplayVersion

----                                                                    ------- -------------------

EXCHANGE201001                                               StandardEvaluation Version 14.3 (Build 123.4)

EXCHANGE201302                                               StandardEvaluation Version 15.0 (Build 1130.7)

EXCHANGE201303                                               StandardEvaluation Version 15.0 (Build 1156.6)

__________________

Regards,

Thorwald

Thorwald van Elburg

I have an Exchange 2007 environment (Edge - Hub/CAS) that I will upgrade to Exchange 2013 in the near future (on-premises). I am using the Exchange Server Deployment Assistant (https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e) and checking out the various steps in the checklist. Presently, my MX record points to a cloud-based spam filter (MXGuarddog) which forwards all non-spam email to my edge server.

How will this affect the mail flow during the transition steps mentioned in the checklist, mainly the existence of legacy and new servers?

Thanks for the input!

Dave