Hi there,

this question has been asked a couple times here but no one seems to have my kind of issue.

I tried to export my public folders from Ex2010 to Ex2016. Soon after start my migration fails. After examining the logs and the public folders it seems that every mail with a size larger than about 1 MB (!) is marked as "too large" and therefore skipped.

How can that be? I thought the size limit was a lot larger than that. Is there any way to determine WHAT influences this kind of odd behaviour?

Thanks
groddjur42

From logfile:

[ex10] Großes Element erkannt: Element (IPM.Note) Betreff: "Programm", Größe: 1.489 MB (1,561,482 bytes), Ordner: "TdM"

We have Exchange 2013 servers installed in a parent domain and a number of child domains. We want to limit the ability of the child domain Exchange Administrators (Mail Recipient Roles) to a particular OU when adding new user objects or mail enabling existing ones. Limiting the creation to a particular OU was easy enough. When adding an existing user, how can the view of the existing users be limited to one OU?

My apologies if this has been asked before. Googling didn't nail the exact answer. Any pointers greatly appreciated.

T

Exchange 2013 CU21. When creating a new user we receive an error message stating the operation failed when it actually did not fail. We have a parent Exchange Server and a number of child domain servers. When the user object gets created on a child domain, the child domain DC picks it up instantly. The error message indicates that the system is trying to read back the new object from the parent domain DC and it fails (which is understandable due to replication times).

If the system tried to verify the creation of the user object on the site DC where it just created the object I believe he error would be resolved.

How to force the child domain Exchange server to verify the creation of a new user object on the DC it just created it on and not the parent DC?

Many thanks for any assistance.

T

When I try to install CU20, setup.exe crashes with the error CLR20r3.

I currently have CU18 installed. If I run that update, the setup program for CU18 runs fine.

I have followed the instructions for the prerequisites listed below:

• .NET Framework 4.7.1  (Left at .Net 4.6.2 per the instructions below:)

  Important

  Exchange 2013 CU21 require .NET Framework 4.7.1. Upgrade your servers to .NET Framework 4.7.1 before you install Exchange 2013 CU21 or you'll receive an error. If .NET Framework 4.6.2 is installed on your Exchange servers, upgrade your servers to Exchange 2013 CU20 before installing .NET Framework 4.7.1.

• Windows Management Framework 4.0 (included with Windows Server 2012 R2)

• Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

• Visual C++ Redistributable Packages for Visual Studio 2013

Need help to determine why setup.exe is crashing.

Can't test CU19 as the download is no longer available.

Since I have .Net 4.6.2 installed, I have to update to CU20 before installing .Net 4.7.1 and installing CU21 which is the latest.

Incidentally, CU21 also crashes in the same way.

Thanks for your help.

Hi everyone,

I have a trouble with adding a exchange mailbox from another forest domain.

I have old exchange server with many mailboxes, now i create a new domain and join a computer in it.

In my new domain with my joined computer, is it possible to connect the old exchange mailbox with my old domain account in the outlook?

Thank you very much!

We had a major crash of our server and backups were corrupt, did a recoverSetup of exchange.  mail.edb file was recoverable and mounted in new server setup.  Reissued ssl cert and installed.  None of my clients are able to connect to the exchange server. 

Creating an outlook profile has ssl errors and wants to import an old cert, I manually imported the new cert, but outlook still wants to import the old?  If I try and connect manually I get the following error:  "Outlook cannot log on. Verify you are connected and using the proper server and mailbox name..."

My cert is a multi site with the doamin.com and add-ons for exchange.domaiin.com and autodiscover.domain.com

Hi,

I have two users (user1/user2) and a resource mailbox (office).

Exchange 2013/Office 2016

User1/user2 should only work with the office mailbox and therefore the users where not email activated.

If I try to configure the Outlook profile in the client I got the message "The name cannot be matched to a name in the address list". When I email activate the mailbox user1, autodiscover works well for the profile user1. Also when I create a new profile office I can enter the contact details and it is fine.

Why it does not work with user2, without an email mailbox?

Thanks

Christian

I'm in the process of migrating from E2013 to E2016. I've tried to start my mailbox moves, but any user I migrate just stays in a "syncing" state. I've left batches running for days and it never changes. The users are only test accounts, so there really is almost no data. I am also only doing 1 user at a time until it is successful.

On the E2016 event log, it shows the migration cmdlet was started successfully. No other events after that. On the E2013, no messages there either.

Running the Get-MoveRequest -BatchName "Pilot" | Get-MoveRequestStatistics cmdlet yields nothing. It just returns to a prompt with no output.

I've had to kill the batches forcefully as deleting them also just hangs in a state of deleting.

I've tried restarting a Mailbox Replication as others have suggested and that doesn't do anything either.

Any ideas?

HI,

We have a Hybrid setup with 99% users hosted on O365 and very few app mailboxes on Exchange 2010 OnPrem

We are in process of Migrating DC from existing vendor. We are setting up parallel Exchange 2010 setup in new DC and will do side by side migration.

MX record pointing to EOP.

I have query on Edge server setup in DMZ with single NIC. Can we use single private IP in DMZ subnet and NAT it for mail communication with EOP IPs. The same private IP can be used for Internal communication with HUB server. Is this supported?

Or should I go with 2 NIC card, one for External communication with O365 and other NIC card for internal communication with HUB server for mail flow and edge sync.

Thanks

We migrated all mailboxes from on-premise Exchange 2013 to O365 in October, with final cut-over migration occurring on October 19th, 2018. All was fine for approximately 2 weeks. We have a mixture of Outlook client versions in use: 2010, 2013 & 2016.  After the approximate 2 weeks,  we had 2 users whose Outlook 2010 reverted back to old Exchange profile and showed mail up until 10/19/18. We deleted their old profile and new profile and started over- then it happened again for one of the same users. Could not figure out how Outlook 2010 could just be showing mail up to that 10/19/18 date??, and since no one was having this issue with Outlook 2013 or 2016, we decided to upgrade users to O365/outlook2016. One user's PC was upgraded and the other user got a brand new PC with no previous Outlook profiles or installs except fresh O365. Since that time these users get the attached temporary mailbox error periodically and we have to delete their Outlook profile and add again. We also had a 3rd user with a new PC and new O365 install that has received the same "temporary mailbox" error.

 Other information:

- Exchange 2013 has not been uninstalled or disabled  --could this be a problem?  If so, we thought Exchange could run in a hybrid state even if we are no longer using it for external  mail.  We do plan to eventually uninstall but wanted to make sure migration was complete and no questions arose concerning where are mail was. Would like to temporarily disable it?

- We have not had this error, or had profile revert to 10/19/18 mail, with anyone using Outlook 2013

- This error seems common with Outlook 2016 and O365  --but we want to rule out Exchange 2013 still running as culprit --is there a way to temporarily disable Exchange instead of uninstalling it to rule it out? It is installed on a Domain Controller so it s difficult to time up uninstalling and not affect production.

Thank you!

Dear All,

Last year, we migrated Exchange 2010 to Zimbra and found it was difficult to handle.

So we want to move back to Exchange 2013. Exchange 2013 and Zimbra may co-exist in our organization.

We will deploy two Exchange Server,CAS+Mailbox.

We are considering if put Exchange as the smarthost.

Anyone has idea?

Besides, is there any wonderful migration tool?

Xiu

Hey, I am back

I have got ransomware attack on my active directory server. Now I newly setup a domain controller with same configurations. 

I have an exchange 2010 server running on same network. How do i re create all the exchange entries in AD ? How can i bring live my exchange again ? 

Regds

DxbTexh

I recently migrated our 2007 Exchange Server to 2013.  This is a single server setup.  Everything seemed to go fairly well.  I've been through many Exchange migrations in the past, but this is the first one that has been 2007 to 2013.  This environment has also been migrated from 2003 to 2007 in the past (not me) and the Exchange 2003 server was never decommissioned properly.  So...  I've removed the 'first administrative group' from ADSI Edit which enabled me to install Exchange 2013 without it thinking there was a legacy 2003 server installed.

Once I got everything setup I moved all mailboxes have been moved to the new 2013 server, set all URLs to the respective domain names, installed the new cert.  Pretty much followed a guide i found online for an Exchange 2007 to 2013 migration.  Everything with 2013 seems to be functioning correctly.  I have mailflow between 2007 and 2013, i have mailflow to external addresses, mailflow in from external.  OWA functions properly, ActiveSync for all of my mobile devices seems to be working just fine.

Here's my one (major) issue:

My Outlook Clients are now asking for credentials upon launch and then about every 10 mins or so thereafter.  At first i was testing with my account and Outlook Client (2013).  Then decided to test with Outlook 2010.  Same issue on both clients. After a lot of searching on this particular issue, I found a possible cause of the issue, but cannot for the life of me seem to fix it...

I've found multiple posts stating that this issue is related to the OAB connection.  This was confirmed by noticing Outlook was trying to download the OAB everytime the authentication box would pop up under the Local Mailbox tab on the Connection Status option using the ctrl+rightclicking the outlook icon in the notification area.

Also, i've noticed if i hit 'cancel' to the authentication request, Outlook functions just fine.  All folders are updated, however the request does come back.  It also shows 'need password' in the bottom right of Outlook.  It also doesn't matter how many times i enter the correct user and password it doesn't take it.  (yes, password is correct and yes, i've entered user name as domain\username, just username and username@domain).

So, I started investigating the OAB issue.

The first thing i did was verify i have an OAB.. I did... There was the default one with 2007 and there was a new one for 2013.  I did try and do a move-offlineaddressbook request during the migration process and it failed stating I couldn't move an old OAB to Exchange 2013 i had to create a new one.  So i removed the (already new) exchange 2013 OAB, and created my own and made it default.  Still no change in behavior.  I verified the internal and external URLs for the virtual directory they are correct (https://mail.domain.com/oab) and the virtual directory is linked to the OAB. 

One thing i did notice that was odd was when i do a get-offlineaddressbook | fl, on my new OAB i notice that there is a property called OriginatingServer and it was pointed to my old 2007 server FQDN, not the new 2013 one.  I found that odd that it wouldn't originate from 2013 especially when I created the OAB from the 2013 server....

My next step was to just kill all services to the 2007 box...  Essentially shutting down the old 2007 exchange server.  Everything was moved so i should be able to use it solely off 2013.  Once i did this, my Outlook 2010 clients seemed to function just fine, no long requiring username and password.  Score!  I then i tried Outlook 2013 thinking the issue would be remedied once i uninstall and decommission 2007....  WRONG.  Outlook 2013 is now broken.. I get the following error when starting Outlook 2013:

Cannot Start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened.  The attempt to login to Microsoft Exchange has failed.

I started all 2007 services up again and Outlook 2013 is still jacked up.  Outlook 2010 is back to asking for credentials.  My worry is this:  SOMETHING is still tied to Exchange 2007.  I'm guessing it's with OAB, but no clue if that's it.

Oh  I also looked for the arbitration mailboxes for OAB, they are on the new server and i have none on the old 2007 server.  I'm at such a loss at this point.  Can anyone help me??

Thanks!

-Jeff

Hi all,

Due to the POODLE vulnerability and TLS 1.0 showing as enabled on one of our external scans, we were informed that we would need to disable SSL 3.0 and TLS 1.0 on our Exchange server.

Apparently, this wouldn't even be possible until Update Rollup 9 was released on 3/16/15:

Rollup resolves:

KB 3029667 SMTP is not transported over TLS 1.1 or TLS 1.2 protocol in an Exchange Server 2010 environment

After installing this update, SSL 3.0 and TLS 1.0 were disabled and the servers rebooted (cross site, same domain, two Exchange servers).  After resolving some issues with certificates that apparently broke as a result of the changes, we found that EWS was not working - the log full of these errors:

Dear All,

I added new exchnage server in my exsting exchnage 

(2Mailbox and 2 cas), after deployment i couldnt able to see my new server in ecp also server tab it is showing none

please find the below

please suggest me for fixing this

After a recent reboot of an Exchange 2013 server, I can no longer get into OWA or ECP. 

When rebooting, the server gave me the option to 'Update and Reboot' which I did.  It appears that CU9 was installed according to recent updates however I did not manually apply the update.

After reboot, all Exchange services and a few other services were set to Disabled.  Using another Exchange server I was able to determine what the startup type should be, set it accordingly and was able to get mail working however I still have some problems.

OWA will display logon screen but says 'bad request' after entering credentials.  ECP gives the following

=============================================================
Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Stack Trace:

[FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) +0
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) +153
   System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +63
   System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +124
   System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +76

[ConfigurationErrorsException: Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +12425356
   System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement) +69
   System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) +62
   System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +299
   System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1262
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +133
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Could not load file or assembly 'Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12618692
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12458309
=====================================================================

I tried to uninstall CU9 but after reboot all services were disabled again.  Now that mail flow is working, I wanted to get some other ideas before experimenting and making things worse.  This appears to be an IIS issue but I welcome ideas, or better yet, solution, on how to get things working again.

Thank you.

Hello,

I run into a problem with replacing a exchange 2013 server and I wanted to ask you if you could help me.

I installed a new exchange 2013 (same build like the old one) and included it into the same oranization and domain. After I copied/changed the certificates, mailboxed and send connector, the clients connected well everthing looked good.

To test everything, I paused the main Exchange Server (VM). When the main Exchange Server is not accessible, I can't open ecp or owa (html error 500) anymore on the new Exchange Server. When I start the first Exchange Server again everything works like it should. 

Strange is, that owa and the clients however (outlook) works fine with or without the first Exchange server.

Do you have an idea?

Thank you

Frenz