Hi Folks,

 We are facing 2 issues the issues are with our Newly Deployed  DR site Exchange Server.,We have 3 Exchange Server 2016 CU6  DAG in Primary site plus 2 DC's and we are going to make a DR site.. In the DR site we have Deployed to ADC's .After the successful installation of ADC's we installed our first Exchange Servers (it will be total 3 in the DR site after Deployment) but after installation when we tried to access that Exchange Server ecp it's redirecting from https://localhost/ecp to https://mail.abc.com which is our external url for accessing our Exchange Server.if we give the local Exchange Server IP address in that Server host file against mail.abc.com  it works fine but if we remove it, it again start redirecting to that external url when we put the credential in the first page.

The 2nd thing is after we access  that Exchange Server by putting the ip against the mail.abc.com in that Server.We can't edit anything in the console (Ecp).While the Exchange Management shell is working fine .

Thank You!

Hello,

I need to upgrade our standalone Exchange 2013 CU16 (Windows 2012 R2 + .NET 4.6.2) to latest CU21.

Issue is that CU21 requires .NET 4.7.1 and VC++ 2013 run-time library.

MS stance on this is:

When upgrading Exchange from an unsupported CU to the current CU and no intermediate CUs are available, you should upgrade to the latest version of .NET that's supported by Exchange first and then immediately upgrade to the current CU. This method doesn't replace the need to keep your Exchange servers up to date and on the latest, supported, CU. Microsoft makes no claim that an upgrade failure will not occur using this method, which may result in the need to contact Microsoft Support Services.

Based on this and to execute steps in order in which they are most supported by MS, this means we need to:

• Upgrade from CU16 to CU20 to gain support for .NET 4.71
• Install .NET 4.71
• Upgrade from CU20 to CU21
• Install VC++ 2013 run-time library

Would this be the best route since in our case intermediate CUs are available?

Going from CU16 (installing .NET 4.7.1 and VC2013 run-time) to CU21 directly would not be supported since intermediate CUs are available?

It is unclear from the MS Exchange blog weather VC++ 2013 needs to be installed before or after installing CU21 - does anyone know?

Thanks

I am working in the VMware virtual machine...I am installing Exchange Server 2013 and receive the following error on Step 8 out of 15: Mailbox Role: Transport Service.....I have installed all prerequisites, I have already disabled IPV6 through Regedit...Not sure why I am receiving this error. What is the fix for this error?

Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "Unable to set shared config DC.".

Can someone tell me the fix for this? I am installing Exchange Server 2013 in a Virtual Machine and keep getting the error message below on Step 8 of 15 of the Exchange 2013 installation. All prerequisites are installed. 

Error:

The following error was generated when "$error.Clear();

       if ($RoleStartTransportService)

       {

          start-SetupService -ServiceNameFMS

        }

        "was run: "Service 'FMS' failed to reach status 'Running' on this server.".

I am working in the VMware virtual machine on Windows Server 2012 R2...I am installing Exchange Server 2013 and receive the following error below on Step 8 out of 15: Mailbox Role: Transport Service.....I have installed all prerequisites, I have already disabled IPV6 through Regedit...Please Help

Error:
The following error was generated when "$error.Clear(); 
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "Unable to set shared config DC.".

Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

I need to migrate an Exchange server to a different DC, so it will require a different IP.   It's a Hybrid server, the only piece of Exchange-related kit still on site. Is there any guidance online anywhere on how to do this?  Everything I've found so far relates to a straight on-prem to 365 migration, or from on-prem to hybrid.

I'm aware that at a minimum I'll need to inform Office 365 somehow of the change of public IP address, and ensure firewall rules are transferred of course.  fw rules are not a problem but how to inform Office 365 about the IP change?

What else is there to consider?  I'm a nix admin not windowsy at all so highly nervous about migrating it.

Thanks in advance.

Hi!

I tried updating Exchange Server 2013 Standard CU20 to CU21 on Windows Server 2012 R2.

This is the first error that occured:

-----

Error:
The following error was generated when "$error.Clear(); 
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'hostcontrollerservice' failed to reach status 'Stopped' on this server.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(ServiceController serviceController, Boolean ignoreServiceStopTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StopService(String serviceName, Boolean ignoreServiceStopTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime)
   at Microsoft.Exchange.Management.Tasks.StopSetupService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

-----

First, I retried the setup. Then this error occured:

-----

Error:
The following error was generated when "$error.Clear(); 
Start-SetupProcess -Name "iisreset" -Args "/noforce /timeout:120"

" was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 1053.
   at Microsoft.Exchange.Management.Tasks.RunProcessBase.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

-----

Next time this one:

And now I'm again stuck on this one:

-----

I've been using the following scripts to disable/re-enable the Exchange services to do a restart of the System after the failed installation without actually starting Exchange:

http://www.oakeley.com.au/Ex2013-Disable.txt
http://www.oakeley.com.au/Ex2013-Enable.txt

Can anyone help?

Cheers,

Wolfram

Hi,

We are planning to upgrade our exchange 2013 server from CU 18 to CU 21. Please let us know the recommendation or any best practice need to follow during the upgrade.

We have total 4 MBX server and 4 CAS including main site and DR site.

Please let me know in which order do we need to perform the upgrade.

Does it affect anything to windows 7 client after upgrade as TLS 1.2 is disabled in windows 7 client.

Regards,
Hakim. B

Hakim.B Sr.System Administrator

I have to change my internal/external web urls including OWA/ActiveSync/Autodiscover. My current setup has multiple smtp domain and the primary smtp domain to which all the urls are configured with is migrating to Office 365 and there will be total cut off of this primary smtp from the current Exchange Infra. I will be changing the urls to point to one of the main remaining SMTP domains and setup the new SSL certificate on the servers and LB. I would like to know if there would be any re-configuration required on all the Smartphone devices using Active Sync as the AS url is currently configured on all the devices with old smtp domain url.

Thanks

Please help, i'm somewhat of a newb to certificates.

I have an expired CA certificate on my exchange server which i believe is causing problems when i try set up new iphones to connect to our exchange account.

How can I create a new certificate while keeping all the same settings of the original certificate.  I do not have the option to renew cert in EMC.

I can view the expired cert, but when starting the new echange certificate wizard i'm unsure what to select from outlook web app, exch active sync, web services, pop,etc.... 

I dont know what was selected in the expired cert so i dont know what to put in the new cert.  

I hope this all makes sense. Please help

I recently hired into my organization and found that it is currently on Exchange 2013 CU14 and .NET Framework 4.7.2.  According to the supportability matrix this is an unsupported combination of .NET and CU.  

My question is can I make the jump from CU14 directly to CU21 based on the fact that .NET Framework is already at the newest version.

Hi All

After running the Hybrid Configuration Wizard on one node of an Exchange 2013 DAG the Outlook clients are unable to connect and access via OWA is also not working. Only when moving the active databases over to the node which I did not run the wizard on, are the clients able to connect.

What could be the cause of this? And how can I fix it?

Any feedback / suggestions will be greatly appreciated.

Kind regards

Hi Everyone

I am trying to move a mailbox between DAGs and it fails repeatedly. What is strange can be seen below:

[PS] C:\Windows\System32\WindowsPowerShell\v1.0>Get-Mailbox -Identity "9ee7ab4d-ad1a-49f2-b6b6-672394ea7a5a"

Name                      Alias                ServerName       ProhibitSendQuota
----                      -----                ----------       -----------------
 *mailboxowner*       *mailboxowner*   *servername*     Unlimited


[PS] C:\Windows\System32\WindowsPowerShell\v1.0>Get-Mailbox -Identity "9ee7ab4d-ad1a-49f2-b6b6-672394ea7a5a" | New-MoveRequest -TargetDatabase *targetdb* -BadItemLimit 1000
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to
 the destination mailbox. At move completion, these corrupted items will not be available at the destination mailbox.
Cannot find a recipient that has mailbox GUID '02df50ff-a778-4911-a925-893269fb2592'.
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemotePermanentException
    + FullyQualifiedErrorId : [Server=*server,RequestId=11e2e0f8-9f7d-4f24-9bc3-836f0bc064c5,TimeStamp=09/01/2019
    13:43:27] [FailureCategory=Cmdlet-RemotePermanentException] 95CA0EB5,Microsoft.Exchange.Management.RecipientTasks
  .NewMoveRequest
    + PSComputerName        : *server*

The environment is currently running in hybrid mode and the corresponding mail user object can be located on exchange online shell, seen below:

PS C:\Users\huntab-admin> Get-MailUser -Identity 02df50ff-a778-4911-a925-893269fb2592

Name                                     RecipientType
----                                     -------------
*mailboxowner*                      MailUser

Since the same guid was used, it can be assumed that it's not because of o365 missing the mailbox guid, as it would have been the only solution that I could find on google.

The mailbox was recently disconnected from its original AD account and connected to another account in another forest. Is it possible that it has something to do with this issue?

Thanks for the help

Boda

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

Hello,

I am trying to configure ADFS 3.0 on Windows Server 2012 R2 for Single Sign on with Exchange 2013. There seems to be very little information regarding configuring ADFS in an Exchange resources forest deployment, so I am hoping someone has come across this and has a solution :)

The environment:

There are four forests in the environment, consisting of:

• User forest 1 - user1.local
• User forest 2 - user2.local
• User forest 3 - user3.local
• Resource forest 1 - resource.local

The resource forest contains all of the Exchange infrastructure.

The user forests contain all the corporate users who have have linked mailboxes in the resource forest.

Each user only has one account, which will exist in one of the 3 users forest, and use their employee ID numbers (e.g. ID12345) to sign in 

There is a one-way outgoing trust between the resource.local forest and each of the user forests. There are no trust between the user forests.

The problem:

I would like to configure ADFS for OWA to allow the corporate users in the users domain to access their mailbox . Please keep in mind that these users only have accounts the their respective users domain, and their account\"place-holder"AD object in the resource forest is disabled.

The ADFS farm will be deployed in the resource forest

Environmental Restrictions:

• A two-way trust between the user forests and resource forest cannot be created
• We cannot migrate to Office365
• We cannot use Azure AD
• A new forest containing all users cannot be created

My research on this suggests that I will need to:

1. Deploy ADFS servers in each of the user forests
2. Add the user forest's ADFS farm as Claims Provider Trusts in the resources ADFS environment
3. Add the resource forest's ADFS farm as a Relying Party Trust in each of the user forest's ADFS farms
4. Configure OWA (and ECP) as a Relying Part Trusts in the resource forest.

I have done the above, but this does not appear to be working. When I browse the OWA URL, I get the ADFS log on page listing each of the user forest (I believe these are integrated Identity Providers (IDPs) for each of the Claims Provider Trusts I created with the user forests). Selecting one of these and trying to signing in with a user's UPN returns the "Something went wrong" OWA message with the "UpnClaimMissing" ADFS error in the URL. All Claim Provider Trusts (in the resource ADFS) and the Relying Party Trusts (in the user forest all have the default Acceptance\Issuance transform rules)

Is this the correct approach? Should I be adding the user domains as attribute stores in the ADFS server in the resource forest instead (not sure about this one, but though I'd throw it out there anyway)?

Thank you

Hi,

ou company has a hybrid mod, and I found a problem with rooms. Users who are in cloud, an make a book some of rooms, this event its visible only for users who are in cloud. On premises users didn't see this reservations, and vice versa, on premises users see only on premises reservations. How to make the reservations visible to both users(cloud vs onpremise).

Note: all rooms are ONPREMISE resource, but, i migrate one(for test) to the cloud, butthe result is the same. rooms are not licensed(we have E3 licences).

Thanks for help

Hello All,

I know, there's been a lot of questions regarding this problem, but none of the responses has helped me with an issue. At my Customer's there's a Windows Server 2012 R2 machine with Exchange 2013 Std on it. A previous IT-support company has tried to install a MS Lync server on the same machine which has obviously failed (the IIS ports 80 and 443 are already occupied by Exchange). Then they've left it 'as is'. Now I have a serious problem as I can't connect to Exchange Management Shell.

The error is:

VERBOSE: Connecting to EXCH2K13.xxl.local.
New-PSSession : [exch2k13.xxl.local] Connecting to remote server exch2k13.xxl.local failed with the following error message : The WinRM client cannot process the request. It cannot determine the cont
ent type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.

I've looked for the settings in IIS (WSMAN, Kerberos auth, applicationHost.config etc.) and nothing seem's to help. This is quite hudge issue as it's the only Exchange server in my Customer's environment so any failure of it will simply kill whole company...

There's another issue, that I think is related to this problem: Exchange Toolbox isn't starting (MMC error) that I've read is also caused by WSMAN (here it is described: https://www.msxforum.de/community/index.php/Thread/12664-Exchange-2010-WSMan-error-10153/ ).

In the event log i can find an event 10153:

The WSMan IIS module failed to read configuration. The error received was -2144108477: %%-2144108477 
 Plik XML konfiguracji jest nieprawidłowy. Oczekiwany element XML: "Plugin" nie został znaleziony..
translated: [The XML configuration file is incorrect. An expected XML element: "Plugin" was not found...]

 User Action 
 Make sure both the schema and validation files are present and valid.

I'm getting bold because of this problem and it will be soon a critical one.

Thank you very much in advance and best regards,

Tom