Exchange 2013 sp1 move databases

Hello all
I am running Exchange 2013 sp1 in a two node DAG. Originally the DAG had two under powered servers, i built two new more powerful servers added the servers to the DAG, then i moved database copies to the new servers, removed the copies from the original
servers and then removed the original servers from the DAG. The two original servers are multi role (CAS Mailbox) and currently they are still in the org. My confusion is around this. When i run get-mailbox -identity <name>. The output from the command
shows the mailbox is on oldserver. Again oldserver was removed from the DAG and no databases exist on the server. I want to remove the two old servers from the org, but i am hesitant on doing this because all mailboxes seem to think they exist on oldserver
Thanks for any help
Bulls on Parade

You can ignore that:
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-homemta-and-msexchhomeservername-are-not-updated-on-mailboxes.aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist

Hi all,
Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
Why would I get this error? The install itself was problematic so I am concerned something is broke.
Thank you in advance.

Hello,
Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server.
I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online).
I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me).
Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
Issue 1)
After each reboot I get a Kernel-EventTracing 2 error. I cannot find anything on this on the internet so I have no idea what it is.
Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
Issue 2)
I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
https://support.microsoft.com/kb/2870416?wa=wsignin1.0
One of the perf counters fails to register using the script from the link above.
66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
New-PerfCounters : The performance counter definition file is invalid.
At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
+    New-PerfCounters -DefinitionFileName $f
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo
: InvalidData: (:) [New-PerfCounters], TaskException
    + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
   12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
But that one seems unrelated to the ones that still throw errors.
Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Issue 3)
I appear to have some issues related to the healthmailboxes.
I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
I reran setup /prepareAD to try and remedy this but I am still getting some.
Issue 4)
I am getting an MSExchange RBAC 74 error.
(Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
Issue 5)
I am getting MSExchange Assistants 9042 warnings on both databases.
Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server.
If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
Issue 6)
At boot I am getting an MSExchange ActiveSync warning 1033
The setting SupportedIPMTypes in the Web.Config file was missing.
Using default value of System.Collections.Generic.List`1[System.String].
I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

Hi Eric
Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time.
I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”.
If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering.
Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users.
I then applied an address policy to them and gave it the highest priority.
Then I set a default email address policy for the entire organization.
After reinstalling Exchange all of my system mailboxes were created with the internal domain name.
So issue number 3 above has not come up.
For issue number one above I have created a new thread:
https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
For issue number four I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
Issue number Five I have managed to recreate and get rid of in more than one way.
If I create a new database in ECP and set the database and log paths where I want, then this error will appear.
If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear.
The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service.
If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away.
So my off hand guess is that these are caused by orphaned system mailboxes.
For issue number six I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
So for the remainder of this thread we can try and tackle issue number two which is the perf counters.
The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7.
Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five.
Using all of your suggestions so far has not removed these 5 remaining errors either. Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
to make them go away if possible.

What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
How can i do export mailbox to pst file in exchange 2013 SP1?

You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
Follow the steps given below in order to export the mailboxes into PST file
1. Open the Exchange Console and run:
New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
restarted. Now move to the next steps.
2. Assign “Mailbox Import Export” role to it.
3. Add Desired Users to Role Group
4. Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
5. Run PS New-MailboxExportRequest
6. Monitor New-MailboxExportRequest
Verify PST File has been created on the network Share and you are done.
If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

Exchange 2013 SP1 and SCOM 2012 R2

Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
Cheers

FYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 SP1 users not receiving quota warning email message

Hi,
We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013. We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email. Most of the users do not log into OWA but only uses Outlook.
It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
Thanks,
Raman

Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
========================
Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c 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.<SubmitNdrForFailedSubmission>b__0()
at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
Raman

Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 53361   StoreEc: 0x977
    Lid: 51859
    Lid: 33649   StoreEc: 0x977
    Lid: 43315
    Lid: 58225   StoreEc: 0x977
    Lid: 39912   StoreEc: 0x977
    Lid: 54129   StoreEc: 0x977
    Lid: 50519
    Lid: 59735   StoreEc: 0x977
    Lid: 59199
    Lid: 27356   StoreEc: 0x977
    Lid: 65279
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
   0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName        : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!

Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Error when upgrading to exchange 2013 SP1

* First, I install Exchange 2013 SP1 on my server, so step 14 of 18 to 100% then alert error:
=======================
Error:
The following error was generated when "$error.Clear();
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
            trap [Exception]
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
        " was run: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing:
Unable to mount database. (hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x667F9F
    Lid: 57728   dwParam: 0x668155
    Lid: 46144   dwParam: 0x66851E
    Lid: 34880   dwParam: 0x66851E
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
    Lid: 35200   dwParam: 0x548
    Lid: 46144   dwParam: 0x66885A
    Lid: 34880   dwParam: 0x66885A
    Lid: 56264   StoreEc: 0x1388
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".
========================
* After I run install Exchange 2013 SP1 again, so go to step 5 of 9 then alert error.
* Now, my Exchange 2013 not run. So bad. Please help me fix it! Thank you so much!

* Thank you, Amit Tank, i passed step 4 of 9, but to step 5 of 9 then alert error:
Error:
The following error was generated when "$error.Clear();
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
            trap [Exception]
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
        " was run: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing:
Unable to mount database. (hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x35AF49
    Lid: 57728   dwParam: 0x35B062
    Lid: 46144   dwParam: 0x35B3EC
    Lid: 34880   dwParam: 0x35B3EC
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
    Lid: 35200   dwParam: 0x1BA0
    Lid: 46144   dwParam: 0x35B757
    Lid: 34880   dwParam: 0x35B757
    Lid: 56264   StoreEc: 0x1388
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".
* Please can you help me?! Thank you so much.

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

Coexistence & Upgrade Exchange 2010 SP3 Unified Messaging to Exchange 2013 SP1 UM

Hello Experts,
We're doing Exchange 2010 SP3 to Exchange 2013 SP1 upgrade.
This upgrade also include Unified Messaging component which is currently working with Exchange 2010 SP3 and Lync 2013.
We have one dial plan and its SIP URI and Secured.
Looking for high level steps to plan coexistence and upgrade of Unified Messaging from Exchange 2010 SP3 to Exchange 2013 SP1 integrated with Lync 2013. I'll also appreciate tips on what kind of certificate and its Subject name(s).
Microsoft documentation is not very clear and I found it confusing for my scenario. Since I we don't want any downtime for UM users, looking for some help.
Thanks in advance for help.
-DK

Hello Hinte,
Thanks for the information. I have been to this article which explains fresh deployment but doesn't address coexistence and migration scenario.
I'm looking for high level steps only. Can anyone validate and suggest if I'm missing something!
1) Install new CAS+MBX Server
2) Move system mailbox as per MS documentation to Exchange 2013 MBX
3) On CAS+MBX Server Enabled internal CA trusted Cert for UM Services.Internal
CA certs contain only CAS+MBX server's FQDN only.UM services Startup Mode is set to "Dual".
4) Assigned existing SIP URI Based Exchange 2010 Dial plan to New Exchange 2013 Servers.
5) Run Exchucutil.ps1
in Exchange 2013 and OcsUMUtil in Lync 2013 (Again?)
Will this be enough or Do I need to create New Auto attendant or
Haunt Group etc?
Thanks for all the help!

Exchange 2013 SP1 - The attempt to search the administrator audit log failed.

During migration process from Exchange 2010 to 2013, after moving Arbitration mailbox from Exchange 2010 database to Exchange 2013 SP1 database, cmdlet Search-AdminAuditLog fails with following error.
The attempt to search the administrator audit log failed. Please try again later.
+ CategoryInfo : NotSpecified: (:) [Search-AdminAuditLog], AdminAuditLogSearchException
+ FullyQualifiedErrorId : [Server=EX2013,RequestId=517873e3-a623-4363-bfdc-e5aa23595c33,TimeStamp=29. 4. 2014
8:38:37] [FailureCategory=Cmdlet-AdminAuditLogSearchException] 2774D0CF,Microsoft.Exchange.Management.SystemConfig
urationTasks.SearchAdminAuditLog
+ PSComputerName : ex2013.domainname.local

Hi,
First, please make sure the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller service are running and please run the get-mailbox -arbitration cmdlet to check the result.
Besides, please check the properties of the DiscoverySearchMailbox and verify that the homeMDB attribute is set to a mounted database.
If the steps above don't work, please try to re-create a new Discovery System Mailbox to check the result. You can refer to the following article.
Re-Create the Discovery System Mailbox
http://technet.microsoft.com/en-gb/library/gg588318(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

New DAG - 2012R2 & Exchange 2013 SP1

Hi there,
Setting up a test platform running on 2012R2 with Exchange 2013SP1, and whilst all looks ok I simply cannot add any server to a new DAG, I can create the dag without any issues and tried using DAG with an IP, and a simplified DAG without IP however simply
cannot add any of my 2 member servers with the following error;
Exchange 2013 SP1 A server-side administrative operation has failed. 'GetNetworkConfig' failed on the server. Error: The NEtworkManager has not yet initialized.
LAN - 10.21.129.111 & 112 / 24
REPLICATION - 192.168.129.111 & 112 / 24
I've checked everything! All sits on vCloud, removed ALL NICs and replaced, removed Symantec, no loss between REPL NICs, all seems fine. Not a lot in the logs other than these last results;
[2014-03-05T12:51:10] Updating 'MDB001'.MasterServerOrAvailabilityGroup to 'DAG001.
[2014-03-05T12:51:10] database[ 0 ] (MBDB01)'s MsOrDag=DAG001.
[2014-03-05T12:51:10] database[ 1 ] (MDB001)'s MsOrDag=DAG001.
[2014-03-05T12:51:10] Updated Progress 'Successfully updated the membership of server 'SRV111' in Active Directory group 'DAG001'.' 18%.
[2014-03-05T12:51:10] Working
I'm at the end of the road and cannot find anything to help me ;(

HI Jared,
I agree, have a feeling it's that bit but not sure how to check if working or re-install perhaps.
Copy status is ALL ok;
CopyQueueLength - 0
ReplayQueueLEnght - 0
ContentIndexState - Healthy
This is without DAG. For replication Health fails on last 2 points on both VMs, could it be missed failover cluster bit or didn't install correctly?
DatabaseRedundancy
DatabaseAvailability
RunspaceId       : d4597641-ae09-4687-8e66-cfbef67bc31f
Server           : SRV111
Check            : DatabaseRedundancy
CheckDescription : Verifies that databases have sufficient redundancy. If this check fails, it means that some
                   databases are at risk of losing data.
Result           : *FAILED*
Error            : Failures:
                       There were database redundancy check failures for database 'MBDB01' that may be lowering its
                   redundancy and putting the database at risk of data loss. Redundancy Count: 1. Expected Redundancy
                   Count: 2. Detailed error(s):
                           SRV111:
                           Database 'MBDB01' does not have enough copies configured to meet the validation criteria.
                       There were database redundancy check failures for database 'MDB001' that may be
                   lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1.
                   Expected Redundancy Count: 2. Detailed error(s):
                           SRV111:
                           Database 'MDB001' does not have enough copies configured to meet the validation
                   criteria.
Identity         :
IsValid          : True
ObjectState      : New
RunspaceId       : d4597641-ae09-4687-8e66-cfbef67bc31f
Server           : SRV111
Check            : DatabaseAvailability
CheckDescription : Verifies that databases have sufficient availability. If this check fails, it means that some
                   databases are at risk of losing service.
Result           : *FAILED*
Error            : Failures:
                       There were database availability check failures for database 'MBDB01' that may be lowering its
                   availability. Availability Count: 0. Expected Availability Count: 2. Detailed error(s):
                           SRV111:
                           Couldn't read the database availability group for server
                   'SRV111.ad.totalitycloud.com' from Active Directory. Error: Could not find the database
                   availability group object for server SRV111 in Active Directory.
                       There were database availability check failures for database 'MDB001' that may be
                   lowering its availability. Availability Count: 0. Expected Availability Count: 2. Detailed
                   error(s):
                           SRV111:
                           Couldn't read the database availability group for server
                   'SRV111.ad.totalitycloud.com' from Active Directory. Error: Could not find the database
                   availability group object for server SRV111 in Active Directory.
Identity         :
IsValid          : True
ObjectState      : New

Error while adding member to the dag in exchange 2013 sp1

I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
Senior Technical Consultant, MDS Computers

When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
[PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
+ CategoryInfo : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
+ FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
mConfigurationTasks.SetDatabaseAvailabilityGroup
+ PSComputerName : <server>
Also, this is logged in the eventlog:
Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
ErrorReportingEnabled: True
Definitely looks like a problem creating the filewitness share.
Frank.

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
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.

Exchange 2013 sp1 move databases

Similar Messages

Maybe you are looking for