Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

Lotus Domino to Exchange 2019 Migration

$
0
0

Our customer wants to migrate emails from Lotus Dominos to Exchange/Office 365.

Normally the tool from Quest is needed for sync of address book and other features during the migration.

If we skip that took and do the migration without that, what would be the downsides?

This is because tool cost of per user.


Shahid Roofi


Office365 and blocking of free versions: hotmail/outlook/live

$
0
0

 Out customer is migrating from Dominos/Lotus to Exchange. They have currently blocked all free emails web access like outlook.com, gmail.com.

 In order to use Office365 they need to connect to office365.outlook.com so what would be our option

 How to continue to block all hotmail.com, outlook.com and even live.com or infact there free emails web access and just allow office365 emails.


Shahid Roofi

Adding Exchange servers, getting certificate errors

$
0
0

Hi,

My client had a single Exchange 2013 server with ~400 mailboxes. Recently we added two more Exchange 2013 servers and created a DAG. When we move a test mailbox to the new database, Outlook (connected internally) throws a certificate error (but if you click past it, it works). I have done the following to remediate:

1. Made sure that the Outlook Anywhere internal and external URL are the same on all three servers (mail.xxx.com.au). 

2. Exported the GoDaddy cert from the original Exchange server that has mail.xxx.com.au as one of it's names in the SAN list. Imported it on the two new servers, and bound it to IIS and SMTP (as it was on the original server).

3. Tried configuring A records in the internal DNS server for all three servers (all named mail.xxx.com.au), this caused certificate errors for users who's mailboxes had not yet been moved to the new servers. So deleted these two new records and left the original A record for mail.xxx.com.au. 

4. Tried configuring another A record for one of the Exchange servers that with a different DNS name that was also listed on the SAN cert - the test mailbox still got the certificate error in Outlook. 

Certificate error:

I have looked at the official documentation and other blog posts but not found any information on how to configure DNS so that the certificate error doesn't appear. 

Any help will be most appreciated. 


Paul Schnackenburg MCSA, MCSA, MCTS, MCITP, MCT

How to Renew the default Microsoft Exchange Server Auth Certificate

$
0
0

Hello,

Good Day!!!

We have 2 Exchange 2013 CU23 member of the DAG, Which the default Microsoft Exchange Server Auth Certificate is about to expire in 2 weeks, Do we have to Renew this Certificate?? What will happen to our Exchange servers if this Certificate is expired??

If we have to renew, Please i am looking on a detailed STEPS  on how to do it on our2 Exchange servers 2013.

Note:The other certificate which we configured in our internal CA will expire in 6 months.

Your HELP and Support will be very much appreciated.

Thanks very much.


Unable to login to Exchange Admin Console after failed Ex2013 CU23 update

$
0
0

Hi All

Getting error while login to Exch2013 ECP:

Server Error in '/ecp' Application.
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS1702: Warning as Error: Assuming assembly reference 'Microsoft.Exchange.Data.Common, Version=15.0.1397.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' matches 'Microsoft.Exchange.Data.Common, Version=15.0.1374.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35', you may need to supply runtime policy

Source Error:
[No relevant source lines]

Source File:    Line: 0
Show Detailed Compiler Output:

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3535.0

no ecp after renewing godadday certificate

$
0
0

This one is very strange. We have an Exchange 2016. It works good. The certificate we used was almost expired. So we created a new one at the site of Godaddy. We created a .req file, added it in our account of godaddy, and we received a pem and a crt. We imported it in Exchange and we linked the protocols like iis, pop, impa and smtp. Everything 's fine.

Working: https://fqdn/owa, outlook, mail on mobile, activesync, ....

Not working: https://fqdn/ecp

But after that we couldn't logon anymore into ECp, so https://our-url-domain/ecp shows the logonpage, we filled out our credentials with the correct password and....... it never logs on; It reshow us the logonpage.

We already search the internet for this issue and it seems that more people have this issue. So we have indeed execute some possibilities. I cannot sum up all of them but these are some of them:

  • Remove-EcpVirtualDirectory -Identity “server\ecp (Default Web Site)”

    New-EcpVirtualDirectory  -InternalUrl “https://fqdn/ecp” -ExternalUrl  “https://fqdn/ecp”
  • Also the owa default web site (remove and recreate)
  • certificate = Microsoft RSA SChannel Cryptographic Provider
  • certificate in iis ecp bindings = microsoft Exchange and for owa = our renewed certificate
  • remove-WebApplication -Site "Exchange Back End" -Name ecp
  • New-WebApplication -Site "Exchange Back End" -Name ecp -PhysicalPath "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp" -ApplicationPool MSExchangeECPAppPool
  • we restarted the exchange server more than once, also the iisreset was executed after every change.
  • .... a lot more

But the problem resists.

BUT we now found that if we want to change the ecp authentication it does not give an error but it does not change the settings like we inserted.

Example:

set-owavirtualdirectory -identity "server\owa (Exchange Back End)" -WindowsAuthentication $True -BasicAuthentication $False. It executes, but the parameter Windowsauthentication is still showing WindowsAuthentication False. We did an iisreset!

Same with the ECP.......

I hope someone can give another solution because after 16 hours of searching it makes a man tired.

Thank you for your feedback.

Kurt

    Exchange 2013 Hybrid - Autodiscover behaviour

    $
    0
    0

    Hi

    Setup:

    Exchange 2007 On Prem. Exchange 2013 CU2 Hybrid server (both CAS and Mailbox roles on 1 server). Office 365 setup ok. Dirsync and ADFS working ok. Few users migrated from on-prem to O365. Mail flow working OK.

    The problem is this - as soon as an on prem user is migrated to O365, their autodiscover stops working against the 2013 Hybrid server. It now comes up with an HTTP Error 500. Running the testexchangeconnectivity tool returns a status of "OrganizationMailboxNotFound"

    However - autodiscover for the same user against the 2013 Server on Port 444 (ie the Mailbox role) works perfectly. Copying the contents of the autodiscover folder from the MBX Clientaccess folder to the CAS Httpproxy folder then results in testexchangeconnectivity working perfectly again.

    It is almost as if the 2013 CAS is not proxying the requests correctly for users with Office 365 mailboxes. On prem users work ok.

    Any thoughts or ideas much appreciated.

    Thanks for looking

    I can't migrate mailbox from exchange to office 365.

    $
    0
    0

    Hi

    I am trying to migrate mailboxes on-premise to O365, however it does not apply since as a status in the execution of the migration task, it remains in synchronization throwing the following error.

    Error: MigrationTransientException: MapiExceptionNoAccess: Unable to open message store. ‎(hr=0x80070005, ec=-2147024891)‎ Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=184] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=216][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x80070005 Lid: 26937 Lid: 21921 StoreEc: 0x80070005 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 45112 StoreEc: 0x80070005 Lid: 56872 dwParam: 0xFE Lid: 42712 StoreEc: 0x80070005 Lid: 10786 dwParam: 0x0 Msg: 15.00.1497.000:Dysis Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80070005 Lid: 26297 Lid: 16585 StoreEc: 0x80070005 Lid: 32441 Lid: 1706 StoreEc: 0x80070005 Lid: 24761 Lid: 20665 StoreEc: 0x80070005 Lid: 25785 Lid: 29881 StoreEc: 0x80070005 --> MapiExceptionNoAccess: Unable to open message store. ‎(hr=0x80070005, ec=-2147024891)‎ Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=184] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=216][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x80070005 Lid: 26937 Lid: 21921 StoreEc: 0x80070005 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 45112 StoreEc: 0x80070005 Lid: 56872 dwParam: 0xFE Lid: 42712 StoreEc: 0x80070005 Lid: 10786 dwParam: 0x0 Msg: 15.00.1497.000:Dysis Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80070005 Lid: 26297 Lid: 16585 StoreEc: 0x80070005 Lid: 32441 Lid: 1706 StoreEc: 0x80070005 Lid: 24761 Lid: 20665 StoreEc: 0x80070005 Lid: 25785 Lid: 29881 StoreEc: 0x80070005



    Check the migration log, verifying all necessary permissions on the administrator account, any other suggestions? since checking on the internet I can not find any possible cause or solution to my problem.


    Recover Exchange 2010 server

    $
    0
    0

    where i can download Microsoft Unified Communications Managed API 2.0 SDK

    Thanks

    Microsoft.Exchange.Clients.Security.MailboxNotFoundException

    $
    0
    0

    Hi,

    I cannot login into a new account. The error below comes up. This is an outlook.com address

    X-ClientId: 5F5B7577D7844E15B84D1603BDABC5F8
    X-Auth-Error Microsoft.Exchange.Clients.Security.MailboxNotFoundException
    X-FEServer ME2PR01CA0066
    X-BEServer HKAPR01MB3572
    Date:28/06/2020 03:37:31
    InnerException: Microsoft.Exchange.Data.Directory.CannotResolveTenantNameException

    Thanks

    Error upgrading Exchange 2013 CU22 to CU23

    Exchange 2013 Hybrid setup questions

    $
    0
    0

    My organization is migrating to Microsoft 365. We have decided that Full Hybrid (classic) offers us the highest level of flexibility and the smoothest end user transition. While running through he Hybrid Configuration Wizard I have encountered the following topics that have given me pause to reconsider our approach.

    Environmental Info:

    • Exchange 2013 CU 23
    • 2 server DAG
    • IB proxy via Proofpoint

    Questions

    1. Local Admin account for HCW:  Roughly 50% through the HCW, the wizard asks for a local admin account that will manage the on-prem resources. I have not been able to locate ANY documentation explaining what specific permissions are required for this account. I'd prefer not to grant any more permissions than required.
    2. Moving off on-prem exchange eventually: Our desired end-state is to have an on-prem AD environment, with AADconnect syncing on-prem user accounts to MS365 and Exchange Online being the sole repository for email. I have seen a lot of mixed information about being able move away from the Hybrid configuration. There is MS documentation that states you "cannot manage mailboxes in this scenario" which is so generic of a statement, I have to imagine there is more nuance here. I have a hard time believing that with the ferocity that MS pushes Hybrid as the gateway to Exchange Online, that there is no way to leave legacy Exchange behind. Has anyone moved into the desired end-state that I describe above


    Exchange 2013 Cu6 fails to install

    $
    0
    0

    When I attempt to install CU6 on Exchange 2013 I get this error message and cannot continue, occurs after reboot as well and trying to re-run setup.  Any ideas how to fix?

    Thanks,

    Setup Error 2nd time 5 of 9 after restart

    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: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "Domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.

       at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
       at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
       at System.Security.Principal.NTAccount.Translate(Type targetType)
       at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
       at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
       at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    How can update Exchange 2013 from RTM to CU23 ?

    $
    0
    0

    Dear all,

    Now, my exchange 2013 is version RTM (first), I want update to version CU 23.

    Can I update directly from version RTM to version CU23 ? or have to update via the intermediate version. Currently, MS does not allow downloads of versions older than version 21. Please help me update the version.

    Thanks you so much.

    Exchange Powershell Commands Missing from EMS

    $
    0
    0

    I just performed a fresh install of Exchange 2013 w/ SP1 on Windows 2012 Standard R2 which is also a domain controller in an organization that already has an Exchange 2010 server (on a separate server). When I launch the Exchange Management Shell and attempt to run "Get-ExchangeServer" I get the error "The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program..." I see that \\HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.SnapIn is loading the module name "D:\Program Files\Microsoft\Exchange\bin\Microsoft.Exchange.PowerShell.Configuration.dll" (which is the correct path to that file).

    I've restarted the server twice and have the same issue. Also tried doing an unattended install of just the Managment Tools since using the setup GUI didn't give me the option of uninstalling and reinstalling the Management Tools since the checkbox is greyed out. I searched the ExchangeSetup log for errors and didn't find any.

    How do I get the Exchange Management Shell to register the Exchange Powershell commands? Do I need to uninstall Exchange and Re-Install?


    Exchange 2013 CU 23 failed

    $
    0
    0

    HI, I am upgrading my exchange 2013 to CU 23 and its getting failed with below error, i have also followed below mentioned link...

    Error:

    The following error was generated when "$error.Clear(); 
              $BEVdirIdentity = $RoleNetBIOSName + "\OAB (Exchange Back End)";
              $be = get-OabVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              {
              new-OabVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;
              }
              set-OabVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeOABAppPool" -Version:"v4.0";
            " was run: "System.Runtime.InteropServices.COMException (0x80070003): The system cannot find the path specified.

       at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
       at System.DirectoryServices.DirectoryEntry.Bind()
       at System.DirectoryServices.DirectoryEntry.get_AdsObject()
       at System.DirectoryServices.PropertyValueCollection.PopulateList()
       at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
       at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
       at Microsoft.Exchange.Management.Metabase.IisUtility.CheckForAuthenticationMethod(DirectoryEntry virtualDirectory, AuthenticationMethodFlags method, Boolean ignoreAnonymousOnCert)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOabVirtualDirectory.StampChangesOn(IConfigurable dataObject)
       at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.SetVirtualDirectory`1.PrepareDataObject()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.PrepareDataObject()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOabVirtualDirectory.PrepareDataObject()
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.InternalValidate()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOabVirtualDirectory.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage taskStage, Action initFunc, Action mainFunc, Action completeFunc)
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()".

    Note: 

    I have already followed to recreate the OWA ECP Virtual directory and setting the permission, but still same issues

    https://www.reddit.com/r/exchangeserver/comments/bu8c60/exchange_2016_complete_uninstall/

    https://support.microsoft.com/en-us/help/2778897/cannot-access-outlook-on-the-web-or-the-eac-after-you-re-create-the-ow

    Any help would be highlight appreciated

    Regards

    Muz


    Steps to shut down all exchange servers in DAG and then bring them back without losing the quorum

    $
    0
    0

    We are going to migrate Data Center. Hence need to shut down all exchange servers in DAG.

    What are the steps to perform to shut down 2 exchange server DAG and then bring them back without losing the quorum

    Cannot Migrate Orphaned Exchange Mailboxes to Exchange 2013

    $
    0
    0

    Hi. Half way through migrating exchange 2010 to exchange 2013.

    Have migrated all users mailboxes to new servers and are left with 3 mailboxes in Exchange 2010 EMC that show as "legacy Mailbox" but do not have an associated mail database.

    On further inspection of the affected objects (which include the Domain administrator account) I can see in AD Users and computers Attribute editor that the user objects have the attribute msExchHomeSever referencing a long gone Exchange 5.5 Server (i.e. they were not correctly migrated to exchange 2010 from 5.5).

    Can I get some advice on either adding a new database on the exchange 2010 server for each object and then migrating object to 2013 or how to remove the old exchange attributes in order that I can then create a mailbox for each and then migrate these over to 2013

    Thanks

    [Announcement] ‘Exchange Server 2013 - Setup, Deployment, Updates, and Migration’ forum will be migrating to a new home on Microsoft Q&A !

    $
    0
    0

    This “Exchange Server 2013 - Setup, Deployment, Updates, and Migration” Forum will be migrating to a new home on Microsoft Q&A!

    We’ve listened to your feedback on how we can enhance the forum experience. Microsoft Q&A allows us to add new functionality and enables easier access to all the technical resources most useful to you, like Microsoft Docs and Microsoft Learn.  

    Now until July 26, 2020:

    From July 27, 2019 until August 10, 2020:

    • New posts – We invite you to post new questions in the “Exchange Server 2013 - Setup, Deployment, Updates, and Migration” forum’s new home on Microsoft Q&A. The current forum will not allow any new questions.
    • Existing posts – Interact here with existing content, answer questions, provide comments, etc.
      August 10, 2020 onward:

    This forum will be closed to all new and existing posts and all interactions will be in Microsoft Q&A.

    We are excited about moving to Microsoft Q&A and seeing you there. Learn More.


    Configuring Exchange 2010 and Exchange 2013 virtual directories for coexistence.

    $
    0
    0

    I'm testing Exchange 2010/Exchange 2013 coexistence in a lab environment.  Below is the set-up:

    Exchange 2010 has 2 Exchange servers.  Each server houses the CAS, mailbox and hub transport roles.  There is a DAG configured and they are installed on 2008R2 servers.

    Exchange 2013 also has 2 servers.  Each server has the CAS and mailbox roles installed and there is also a DAG configured.  These Exchange servers are installed on 2012R2.

    Since installing 2013, I'm struggling getting the virtual directories configured correctly for EWS, OWA etc.  Basically, I'm just looking for straight forward documentation on how the particular virtual directories should be configured for a 2010/2013 coexistence scenario.  Any help in pointing me in the right direction is appreciated.  Thanks.

    Viewing all 7008 articles
    Browse latest View live


    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>