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

Similar Messages

  • 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

  • ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

    Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
    users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
    I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
    As you can see from the error above  ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
    virtual folders?!
    What I’m missing here?! Please help.

    Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
    To check whether inheritance is disabled on the user:
    1.Open Active Directory Users and Computers.
    2.On the menu at the top of the console, click View > Advanced Features.
    3.Locate and right-click the mailbox account in the console, and then click Properties.
    4.Click the Security tab.
    5.Click Advanced.
    6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
    Ref:
    http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
    Also check the Virtual directory authentication
    Microsoft-Server-ActiveSync
     •Basic authentication
     •SSL required
     •Requires 128-bit encryption
    Ref:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    Check the IIS log if you are able to find any error message on it
    Exchange Queries

  • 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

  • Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

    Hi Everybody,
    For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
    When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
    This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
    So i did the traditional cmdlet
    Get-SendConnector
    Set-SendConnector -Indentity "connector name" -Port 551
    Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
    When i type Get-ExCommand
    Any reference to SendConnector and ReceiveConnector are not on the list.
    Am I missing somethings?  This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
    I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
    The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials.  However, i very much doubt the on-premise installation add-on to SBS would cause any issues
    to missing cmdlets.
    I searched all over the internet and found nothing.
    Now my biggest fear is to re-install Exchange and import the mailboxes manually.
    Any help is greatly appreciated.
    MattLok

    Hello
    check role asigment for your user:
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
    sorry my english

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    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.

  • BSOD after upgrading to exchange 2013 SP1

    Hi,
    I Have 4 servers, x2 Mailbox and x2 CAS, all with 2008 r2 OS, Mailboxes with DAG. Problem started after I upgraded all servers from Exchange 2013 CU3 to Ex13 SP1. All Servers are in Vmware, same hardware.
    All servers getting BSOD, error is same as some other posts in Internet about:
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8007ab4890, Terminating object
    Arg3: fffffa8007ab4b70, Process image file name
    Arg4: fffff800019de7b0, Explanatory message (ascii)
    Debugging Details:
    PROCESS_OBJECT: fffffa8007ab4890
    IMAGE_NAME:  wininit.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME:  MSExchangeHMWo
    BUGCHECK_STR:  0xF4_MSExchangeHMWo
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff80001a67ab2 to fffff800016d9bc0
    LOGS:
    RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityServerReboot: Throttling rejected the operation
    RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityConfigDCServerReboot: Throttling
    rejected the operation
    Recovery Action Failed. (ActionId=RestartService, ResourceName=ServerName.contoso.com, Requester=ActiveDirectoryConnectivityRestart,
    InstanceId=140408.062707.65292.001, ActualStartTime=2014-04-08T15:27:07.6529270Z, ActualEndTime=2014-04-08T15:27:07.7777262Z, ErrorMessage=Service ServerName.contoso.com was not found on computer '.'.)
    when Server restarts, logs show 
    Bugcheck action reported by server 'ServerName' initiated by responder 'ActiveDirectoryConnectivityServerReboot'
    Recovery Action Started. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ExpectedToFinishAt=2014-04-08T15:38:07.9326175Z
    Recovery Action Succeeded. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ActualStartTime=2014-04-08T15:33:07.9326175Z, ActualEndTime=2014-04-08T15:35:07.0828500Z)
    I found that it could restart like many times in a day, but
    Throttling does not let it, just one restart per day.
    I already spent four days trying to find problem but no luck.
    Try'ed to add override
    Add-GlobalMonitoringOverride
    -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    but
    after 
    (Get-WinEvent
    -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled
    still shows propertyValue 1, and servers are restarting no matter what, I just dont want to disable HealtManager
    Service.
    Try'ed to recreate all performance counters, did'nt worked
    Try'ed to create prefered domain controller, did'nt worked
    Try'ed to play with healthSet 'AD', but there is almost no information about it in TechNet, so I just looked which services are unhealthy, sometimes it shows ActiveDirectoryConnectivityServer
    or ActiveDirectoryConnectivityConfigDCServer as unhealthy, but after few minutes it goes to
    healthy, problem that Exchange could already restart the server
    mainly reason I think is: 
    The AD Health Set has detected a problem with Server.contoso.com at 2014.04.09 06:33:11. The Health Manager is reporting that ActiveDirectoryConnectivityProbe/Server.contoso.com
    Failed with Error message:  Search took 1518 ms. Threshold 800 ms. Attempts to auto-recover from this condition have failed and requires Administrator attention. Exception Details: System.Exception:  Search took 1518 ms. Threshold 800 ms
    I really need some new ideas...
    EDIT: Exchange 2013 sp1 works perfectly in test lab, there are  cloned machines from production, the only difference is DomainController, there is just one (server), no replications, and no subdomains (production domain have subdomain). 
    Running DCDiag shows no errors

    Hello Everyone,
    We have 2 CAS and 4 Mailbox server that were installed from SP1 and seeing the same issue.  This is a clean install still with no mailboxes migrated over as of yet.  Opened a case with MS.  also ran:
    Add-GlobalMonitoringOverride
    -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    Waiting
    for MS to get back and to see how this workaround does.  Seems like the original issue was not resolved completely?
    Will
    post back when we get an update.  Changing the DirectoryActiveMonitoringContext.xml and the above workaround do not seem suitable for us.  We would like to see a complete resolution for this.
    Good
    luck!

  • ADFS-WAP-Exchange 2013 SP1

    Hello guys,
    i will setup a new infrastructure with exchange 2013 account forest.In this new forest, users will authenticate by WAP and ADFS.
    The accounts user are in other with a exchange 2003 that i'll migrate.
    My question is how adfs will authenticate owa's user and do i need to setup a adfs server in account forest ?
    Concerning my adfs certificate, do i need to put the UPN from the exchange forest or to put also the account forest
    Thanks for you advice
    Jérôme

    Hi,
    I find 2 related blog for your reference, hope they are what you want:
    Setting up Windows Application Proxy for Exchange 2013
    http://blogs.technet.com/b/jrosen/archive/2013/12/28/setting-up-windows-application-proxy-for-exchange-2013.aspx
    Configuring Exchange 2013 SP1 to Accept AD FS Claims
    http://blogs.technet.com/b/platformspfe/archive/2014/03/12/configuring-exchange-2013-sp1-to-accept-ad-fs-claims.aspx
    Thanks
    Mavis Huang
    TechNet Community Support

  • 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.

  • 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.

  • Outlook 2013 can't connect to Exchange 2013 SP1

    Hello,
    I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
    The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain)  with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
    ...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
    In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
    Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
    Thank you in advance,
    Michael

    Hi,
    When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
    "Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Exchange 2013 SP1 CU8 installation stuck

    Good Morning,
    I'm just installing CU8 for Exchange 2013 on a DAG Member (only mailbox role installed), and setup is stuck at 49% of "Mailbox Role: Client Access service" for more than 2 hours now.
    The ExchangeSetup logfile says:
    [04/15/2015 06:44:20.0582] [2] Active Directory session settings for 'New-PerfCounters' are: View Entire Forest: 'True', Configuration Domain Controller: 'srv-dc02.oostvogels.com', Preferred Global Catalog: 'dc02.contoso.com', Preferred Domain Controllers: '{ dc02.contoso.com }'
    [04/15/2015 06:44:20.0582] [2] User specified parameters: -DefinitionFileName:'ServiceProxyPoolCounters.xml'
    [04/15/2015 06:44:20.0582] [2] Beginning processing new-PerfCounters
    [04/15/2015 06:44:20.0582] [2] Processing file: C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\ServiceProxyPoolCounters.xml
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Proxy Instance Count, type is NumberOfItems32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Current Outstanding Calls, type is NumberOfItems32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Total Number of Calls, type is NumberOfItems32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Calls/sec, type is RateOfCountsPerSecond32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Average Latency, type is AverageCount64.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Base for Average Latency, type is AverageBase.
    [04/15/2015 06:44:20.0582] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
    [04/15/2015 06:44:20.0738] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
    [04/15/2015 06:44:22.0255] [2] Ending processing new-PerfCounters
    Does anyone have any suggestions or did you experience a similar issue?
    I also can see some events like this:
    Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName "ADDriverCachePerformanceCounters.xml".
    Thanks and best regards,
    Sebastian

    Hi,
    According to your post, I understand that install Exchange 2013 SP1 CU8 in a DAG with MBX role failed with error “Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName ‘ADDriverCachePerformanceCounters.xml’”.
    If I misunderstand your concern, please do not hesitate to let me know.
    I want to double confirm whether you deploy clean install or implement upgrade an existing Exchange Server 2013 installation to Cumulative Update 8.
    To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command:
    1. Rebuilding the counters:
        cd c:\windows\system32
        lodctr /R
    2. Resyncing the counters with Windows Management Instrumentation (WMI):
        WINMGMT.EXE /RESYNCPERF
    3. Stop and restart the Performance Logs and Alerts service.
    4. Stop and restart the Windows Management Instrumentation service.
    If the issue persists, please run to reload all the perf counters. For your reference:
    http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.aspx
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Allen Wang
    TechNet Community Support

  • Exchange 2013 SP1 - Edge Tranport Role

    Hi.
    When Exchange 2013 was released only CAS & Mailbox roles where available. Hub & Edge Transport server roles were discontinued.
    Now with Exchange 2013 SP1, the edge transport role has came back.
    Question:
    1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
    I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
    2. will there any be problems without an Edge Transport ?
    Thanks,
    Paul

    Hi ,
    Please find the below mentioned points .
    1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
    I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
    Answer :
    Just ensure that the product is having all the features as you need on your side .There is not necessary to have a an edge server in all the exchange environment's. Moreover Gateway and anti spam products will differ as per the company requirements.
    2. will there any be problems without an Edge Transport ?
    Answer :
    If you are having any one the anti spamming solution to have all the emails scanned before it reaches the exchange server then it will be good .
    Just ensure that the anti spamming product what you are going to use is mainly doing the reverse dns lookup
     and spf look up .With the help of that we can able to avoid large no of forged emails.
    Regards
    S.Nithyanandham

  • HTTP 500 ERROR AFTER EXCHANGE 2013 SP1 INSTALL

    Help after exchange 2013 sp1 new install unable to get to the ECP or OWA page with HTTP 500 error in IE the install went ok but not sure what can be causing the error any  help would be appriciated.
    EXCHANGE 2013--SP1 on WIN2K12--R2 Standard
    TY
    M4326

    See the following:
    http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
    CK

Maybe you are looking for