Sorry if this is in the wrong place.

Trying to figure out how if at all possible to do this.

We have a shared exchange server with multiple tenants.  And configured to use adfs for sign-on which is working.

However we now had a situation where customerC wants to have his mailboxes on our servers.  But using his adfs to authenticate for access to them

There isn't a trust setup between the domains either.

I've managed to get our adfs server to send the request over they customers-adfs for authentication.  But once i've been authenticated I get the following error on the owa page

owa/auth/errorfe.aspx?msg=UpnClaimMissing

X-ClientId: VAIG - DBJW - KKED - NZYYEWQ
X-FEServer: TEST08
Date: 5/8/2015 6:05:12 PM

Hi all!

I currently in Exchange 2013 CU12 and would like to update to the latest CU21.

Is it dangerous to update directly (without updating previously to any other CU)? Do you suggest any other roadmap?

Thanks!

SomoIT.net

Hi all,

My environment : 2 Exchange server 2013 CU19 (both CAS + Mailbox roles) Windows server 2008 R2 Enterprise, Domain controller Windows server 2008 R2 Enterprise .
I added 1 more new Windows server 2012 R2 Standard into my domain and promoted it to Domain Controller.
I attempt to transfer 5 FSMO roles from Windows server 2008 R2 to Windows server 2012 R2 later, demote old server 2008 R2 and remove it from my environment later.

Here some information about 2 Exchange servers :

[PS] C:\Windows\system32>Get-ExchangeServer -Identity "exchangeserver1" -status | Select-Object Name,StaticDomainControllers,S
taticGlobalCatalogs,StaticConfigDomainController,StaticExcludedDomainControllers,CurrentDomainControllers,CurrentGlobalC
atalogs,CurrentConfigDomainController,OriginatingServer


Name                            : exchangeserver1
StaticDomainControllers         : {}
StaticGlobalCatalogs            : {}
StaticConfigDomainController    :
StaticExcludedDomainControllers : {}
CurrentDomainControllers        : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentGlobalCatalogs           : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentConfigDomainController   : server2008r2.mydomain.com
OriginatingServer               : server2008r2.mydomain.com

[PS] C:\Windows\system32>Get-ExchangeServer -Identity "exchangeserver2" -status | Select-Object Name,StaticDomainControllers,S
taticGlobalCatalogs,StaticConfigDomainController,StaticExcludedDomainControllers,CurrentDomainControllers,CurrentGlobalC
atalogs,CurrentConfigDomainController,OriginatingServer


Name                            : exchangeserver2
StaticDomainControllers         : {}
StaticGlobalCatalogs            : {}
StaticConfigDomainController    :
StaticExcludedDomainControllers : {}
CurrentDomainControllers        : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentGlobalCatalogs           : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentConfigDomainController   : server2008r2.mydomain.com
OriginatingServer               : server2008r2.mydomain.com

[PS] C:\Windows\system32>Get-AdServerSettings

ConfigurationDomainCont PreferredDomainControll PreferredGlobalCatalog  RecipientViewRoot       ViewEntireForest
roller                  ers
----------------------- ----------------------- ----------------------  -----------------       ----------------
                        {}                                              mydomain.com                 False

So what I need to do to change domain controller for 2 Exchange server ? For ex

Set-ExchangeServer -identity "exchangeserver1" -StaticDomainControllers "server2012r2.mydomain.com" -StaticGlobalCatalogs "server2012r2.mydomain.com"

Set-ExchangeServer -identity "exchangeserver2" -StaticDomainControllers "server2012r2.mydomain.com" -StaticGlobalCatalogs "server2012r2.mydomain.com"

Please give me some advice, thank you very much.

Dears,

We have an existing Exchange server 2010 on a physical server. We installed and configured another two server 2010 SP3 + latest rollout on two virtual machines in DAG mode.

Emails are working fine except for emails that are being sent to a distribution group we are getting an error : 250 2.1.5 resolver.grp.expanded  and anther error about storage transient failure.

When shutting down the two new servers everything is back to normal.

What could be the issue.

Best Regards,

Hello everyone,

I hope this is the correct forum for my problem.  I am attempting to install Exchange 2013 in a somewhat special situation and I have run into some roadblocks.  I am hoping someone with more experience in this than I have can give me some idea of where to go from here.  This is the scenario - 

Environment:

We have an Active Directory domain with a functional level of Windows Server 2008. There are 3 DCs, 2 in geographically different locations (1 is Server 2016 and the other is Server 2008) and a 2016 server in Azure. We were originally setup with Exchange Online/Office 365 in a Hybrid environment.

Situation:

The first week of April, we experienced a power event which caused a major outage at our Primary Data Center. When the situation was finally resolved, the existing Exchange server no longer functioned. There are only a couple functions that we still need it for, but they are important to aspects of the business.

Steps Attempted:

We initially engaged Microsoft Support to assist in getting a new Exchange server installed, after we had completely removed the old server from the domain. After several days, they managed to get the software installed on a spare piece of hardware, but it wasn’t fully functional. Some services weren’t starting and the server itself was unable to connect consistently to the network. There were other aspects of the old server that were still showing up in the domain. We finally ended up uninstalling the Exchange software on the physical server and removed it from AD.

With the current attempt at an installation, we created a new VM of Windows Server 2012 R2 and Exchange 2013 SP1 (installed from an ISO downloaded from the Volume License site). This completed with this error:

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

         if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )

         {

           Update-RmsSharedIdentity -ServerName $RoleNetBIOSName

         }

       " was run: "Microsoft.Exchange.Management.Tasks.RmsSharedIdentityUserNotFoundException: RMS Shared Identity user FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 not found.

  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, Boolean reThrow)

  at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()

  at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()

  at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

  at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

After checking AD, the default accounts usually created by an Exchange Installation are not there (i.e. SystemMailbox, FederatedEmail, DiscoverySearchMailbox). They had been removed as part of the original cleanup of the previous installation. Initially, I was able to connect to the Exchange Management Shell. Unfortunately, after attempting to upgrade to CU20 in the hopes of creating those users with that installation (and receiving similar errors), I was no longer able to log into the EMS. The error message is as follows:

VERBOSE: Connecting to hq-exchange1.sonobello.hq.

New-PSSession : [hq-exchange1.sonobello.hq] Connecting to remote server hq-exchange1.sonobello.hq failed with the following error message : The WinRM client cannot process the request. It cannot determine the content 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], PSRemotin

  gTransportException

   + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed

There is no access to the Exchange Administrative Center, I assume because there is no Mailbox on the server. I am now unable to even uninstall Exchange through Control Panel. Is there a way to create those users outside the installation routine? Can I create a Mailbox without the AD user there?

Other interesting (but perhaps irrelevant) information:

After installation of CU20, the Network Location Awareness service in Windows seems to have problems starting, causing an issue with its ability to see that it is on a domain network and thus being able to access the system remotely.  Waiting for a period of time (20+ minutes) and restarting that service clears the issue until the next reboot.

Any help, ideas, suggestions would be greatly appreciated.

Thanks!

david

Hi there,

Originally with 2 sets exch2013cu6 in DAG, all DBs typically mounted on primary server, secondary server really not for daily usage just for BCP purpose.

Understood significantly lag behind for CU patching, earlier this week decided to patch to CU21, but as such a huge gap, to play safe we decided to first patch to CU15 then further patch to CU21.

We first installed CU15 on the secondary exch2013, after verified no issues, failover all DBs to secondary exch2013 & patch primary exch2013.  After that, when try to login EAC from primary exch2013, it give me error page as below:

Server Error in '/owa' Application.

---

Could not find a part of the path 'd:\program files\microsoft\exchange server\v15\frontend\httpproxy\eac_owa\auth\15.0.1263\themes\resources\logon.css'.

[DirectoryNotFoundException: Could not find a part of the path 'd:\program files\microsoft\exchange server\v15\frontend\httpproxy\eac_owa\auth\15.0.1263\themes\resources\logon.css'.]
   System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +338
   System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) +1430
   System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) +211
   System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost) +187
   System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost) +90
   Microsoft.Exchange.Clients.Owa.Core.OwaPage.<InlineCss>b__5(String fullFilePath) +56
   Microsoft.Exchange.Clients.Owa.Core.OwaPage.InlineResource(String fileName, String partialFileLocation, ResoruceCreator createResource, Dictionary`2 resourceDictionary) +373
   Microsoft.Exchange.Clients.Owa.Core.OwaPage.InlineCss(String fileName) +177
   Microsoft.Exchange.Clients.Owa.Core.OwaPage.InlineCss(ThemeFileId themeFileId) +137
   ASP.auth_logon_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +543
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +131
   System.Web.UI.Page.Render(HtmlTextWriter writer) +40
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +150
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5363

Then I look at "d:\program files\microsoft\exchange server\v15\frontend\httpproxy\eac_owa\auth", from there only have "15.0.995" & "current" folders, no more.  Further verified the secondary exch2013 server which was the first to apply CU15, also only have "15.0.995" & "current" folders, no sign of the "15.0.1263' folder.

Tried to run d:\program files\microsoft\exchange server\v15\bin\updatecas.ps1 but it didn't help.

Any idea what's wrong & how to fix?  

Should I reinstall CU15 again?  

Or as I want to make it CU21, should I install CU21 even with such problem on hand?

Many thx!

Hello,

I have two mailboxes that have <g class="gr_ gr_83 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="83" id="83">unlimited</g> quota and I'm trying to migrate them over to the 2013 box. I see a PreserveMailboxSizeLimit attribute but that applies to Exchange 2007. I search for something similar for 2013 but nothing shows up. 

Is there one for Exchange 2013? 

Hello,

I've just started at a company who have a single Exchange 2013 server.  it's not huge (about 80 users) but it is on CU9 so more than a few updates behind. Ultimately the company wants to migrate to Office 365, having already a subscription for Office apps and onedrive.

Typically I'd upgrade the server to the latest CU before starting anything but here is the problem and the reason food the question.  The company has recently become a 24/7 operation and has declared that as such they can't afford for email to be unavailable for the length of time it takes to run the CU updates (there are also a lot of Windows updates to apply). What I am thinking here is that we need to add a second exchange to the domain,  make it highly avaliabe from a cas perspective (even if we don't create a dag) then migrate the mailboxes away from the first server so it can be updated without any downtime. I can no longer get CU9 so would be looking at the latest CU version for the new server. Does anyone see any potential issues with my plan? Naturally load balancing will be employed for external and MX etc

Are their any other options? Would either a cut over migration or migration software like code two help here?

All advice welcome

Thanks

Hi all,

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

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

Rollup resolves:

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

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

Hi

We are having intermittent issues with Outlook Client for some not working and also web portal not working for some.

I am struggling to find out where the problems are stemming from as each user seems to have a different issue.

Here are the results on a connectivity test it looks like we cant resolve SCP or DNS and finally we get the xml from HTTPS.

I have looked at SCP service binding information which is pointing to https://cas.itn.co.uk/autodiscover/autodiscover.xml;

I could access that link this morning and retrieved the XML with error code 600 however since this afternoon with zero changes all of a sudden I can no longer browse to that location!!!

Then if I go to https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml

I get

<?xml version="1.0" encoding="UTF-8"?>

-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">

-<Response>

-<Error Id="1220493987" Time="16:48:11.7485757">

<ErrorCode>600</ErrorCode>

<Message>Invalid Request</Message>

<DebugData/>

</Error>

</Response>

</Autodiscover>

here are results of connectivity analyzer - I hope someone can help!

The Microsoft Connectivity Analyzer is attempting to test Autodiscover for racheal.hitchcock@itn.co.uk.
	Autodiscover was tested successfully.
	Additional Details   Elapsed Time: 9357 ms.
	Test Steps   Attempting each method of contacting the Autodiscover service.   The Autodiscover service was tested successfully.   Additional Details   Elapsed Time: 9357 ms.   Test Steps   Attempting to test potential Autodiscover URL https://itn.co.uk:443/Autodiscover/Autodiscover.xml   Testing of this potential Autodiscover URL failed.   Additional Details   Elapsed Time: 4007 ms.   Test Steps   Attempting to resolve the host name itn.co.uk in DNS.   The host name resolved successfully.   Additional Details   IP addresses returned: 65.52.128.33 Elapsed Time: 301 ms. Testing TCP port 443 on host itn.co.uk to ensure it's listening and open.   The port was opened successfully.   Additional Details   Elapsed Time: 227 ms. Testing the SSL certificate to make sure it's valid.   The certificate passed all validation requirements.   Additional Details   Elapsed Time: 470 ms.   Test Steps   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server itn.co.uk on port 443.   The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.   Additional Details   Remote Certificate Subject: CN=*.itn.co.uk, OU=Web, O=Independent Television News Limited, L=London, C=GB, Issuer: CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US. Elapsed Time: 411 ms. Validating the certificate name.   The certificate name was validated successfully.   Additional Details   Host name itn.co.uk was found in the Certificate Subject Alternative Name entry. Elapsed Time: 0 ms. Certificate trust is being validated.   The certificate is trusted and all certificates are present in the chain.   Test Steps   The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=*.itn.co.uk, OU=Web, O=Independent Television News Limited, L=London, C=GB.   One or more certificate chains were constructed successfully.   Additional Details   A total of 1 chains were built. The highest quality chain ends in root certificate CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US. Elapsed Time: 18 ms. Analyzing the certificate chains for compatibility problems with versions of Windows.   Potential compatibility problems were identified with some versions of Windows.   Additional Details   The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Elapsed Time: 1 ms. Testing the certificate date to confirm the certificate is valid.   Date validation passed. The certificate hasn't expired.   Additional Details   The certificate is valid. NotBefore = 3/7/2018 12:00:00 AM, NotAfter = 9/22/2018 12:00:00 PM Elapsed Time: 0 ms. Checking the IIS configuration for client certificate authentication.   Client certificate authentication wasn't detected.   Additional Details   Accept/Require Client Certificates isn't configured. Elapsed Time: 1516 ms. Attempting to send an Autodiscover POST request to potential Autodiscover URLs.   Autodiscover settings weren't obtained when the Autodiscover POST request was sent.   Additional Details   Elapsed Time: 1491 ms.   Test Steps   The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://itn.co.uk:443/Autodiscover/Autodiscover.xml for user racheal.hitchcock@itn.co.uk.   The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.   Additional Details   A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown. HTTP Response Headers: strict-transport-security: max-age=31536000; preload; includeSubDomains Content-Length: 22560 Cache-Control: no-cache, must-revalidate, max-age=0 Content-Type: text/html; charset=UTF-8 Expires: Wed, 11 Jan 1984 05:00:00 GMT Server: Microsoft-IIS/10.0 X-Powered-By: PHP/5.6.36,ASP.NET Date: Tue, 24 Jul 2018 15:34:36 GMT Elapsed Time: 1490 ms. Attempting to test potential Autodiscover URL https://autodiscover.itn.co.uk:443/Autodiscover/Autodiscover.xml   Testing of this potential Autodiscover URL failed.   Additional Details   Elapsed Time: 4198 ms.   Test Steps   Attempting to resolve the host name autodiscover.itn.co.uk in DNS.   The host name resolved successfully.   Additional Details   IP addresses returned: 40.97.130.24, 40.97.128.232, 40.97.113.184, 40.97.166.168, 2603:1036:3:106::8, 2603:1036:3:11a::8, 2603:1036:3:12e::8, 2603:1036:4:4b::8 Elapsed Time: 72 ms. Testing TCP port 443 on host autodiscover.itn.co.uk to ensure it's listening and open.   The specified port is either blocked, not listening, or not producing the expected response.    <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl01_ctl01_tmmArrow">Tell me more about this issue and how to resolve it</label>   Additional Details   A network error occurred while communicating with the remote host. Elapsed Time: 4126 ms. Attempting to contact the Autodiscover service using the HTTP redirect method.   The Autodiscover service was successfully contacted using the HTTP redirect method.   Additional Details   Elapsed Time: 1150 ms.   Test Steps   Attempting to resolve the host name autodiscover.itn.co.uk in DNS.   The host name resolved successfully.   Additional Details   IP addresses returned: 40.97.130.24, 40.97.128.232, 40.97.113.184, 40.97.166.168, 2603:1036:3:106::8, 2603:1036:3:11a::8, 2603:1036:3:12e::8, 2603:1036:4:4b::8 Elapsed Time: 11 ms. Testing TCP port 80 on host autodiscover.itn.co.uk to ensure it's listening and open.   The port was opened successfully.   Additional Details   Elapsed Time: 20 ms. The Microsoft Connectivity Analyzer is checking the host autodiscover.itn.co.uk for an HTTP redirect to the Autodiscover service.   The redirect (HTTP 301/302) response was received successfully.   Additional Details   Redirect URL: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml HTTP Response Headers: Pragma: no-cache X-FEServer: DM5PR2001CA0004,DM5PR2001CA0004 X-RequestId: f8aa5061-ea14-4732-ac83-0a30be107ff6 Strict-Transport-Security: max-age=31536000 Connection: close Content-Length: 0 Cache-Control: no-cache Date: Tue, 24 Jul 2018 15:34:40 GMT Location: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Elapsed Time: 7 ms. Attempting to test potential Autodiscover URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml   Testing of the Autodiscover URL was successful.   Additional Details   Elapsed Time: 1111 ms.   Test Steps   Attempting to resolve the host name autodiscover-s.outlook.com in DNS.   The host name resolved successfully.   Additional Details   IP addresses returned: 40.97.166.34, 40.97.131.146, 40.97.130.210, 40.97.147.210, 2603:1036:3:8e::2, 2603:1036:3:11c::2, 2603:1036:3:17::2, 2603:1036:3:40::2 Elapsed Time: 11 ms. Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.   The port was opened successfully.   Additional Details   Elapsed Time: 44 ms. Testing the SSL certificate to make sure it's valid.   The certificate passed all validation requirements.   Additional Details   Elapsed Time: 75 ms.   Test Steps   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.   The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.   Additional Details   Remote Certificate Subject: CN=outlook.com, O=Microsoft Corporation, L=Redmond, S=Washington, C=US, Issuer: CN=DigiCert Cloud Services CA-1, O=DigiCert Inc, C=US. Elapsed Time: 21 ms. Validating the certificate name.   The certificate name was validated successfully.   Additional Details   Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry. Elapsed Time: 1 ms. Certificate trust is being validated.   The certificate is trusted and all certificates are present in the chain.   Test Steps   The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.   One or more certificate chains were constructed successfully.   Additional Details   A total of 1 chains were built. The highest quality chain ends in root certificate CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US. Elapsed Time: 17 ms. Analyzing the certificate chains for compatibility problems with versions of Windows.   Potential compatibility problems were identified with some versions of Windows.   Additional Details   The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Elapsed Time: 1 ms. Testing the certificate date to confirm the certificate is valid.   Date validation passed. The certificate hasn't expired.   Additional Details   The certificate is valid. NotBefore = 9/13/2017 12:00:00 AM, NotAfter = 9/13/2018 12:00:00 PM Elapsed Time: 0 ms. Checking the IIS configuration for client certificate authentication.   Client certificate authentication wasn't detected.   Additional Details   Accept/Require Client Certificates isn't configured. Elapsed Time: 21 ms. Attempting to send an Autodiscover POST request to potential Autodiscover URLs.   The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.   Additional Details   Elapsed Time: 959 ms.   Test Steps   The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user racheal.hitchcock@itn.co.uk.   The Autodiscover XML response was successfully retrieved.   Additional Details   Autodiscover Account Settings XML response: <?xml version="1.0"?> <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">   <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">     <User>       <DisplayName>Hitchcock, Racheal</DisplayName>       <LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=18c4723ffd8f48b5a7dae1b5f1acc4e3-Hitchcock,</LegacyDN>       <DeploymentId>82024f5b-3097-4495-82a6-477c705efa26</DeploymentId>     </User>     <Account>       <AccountType>email</AccountType>       <Action>settings</Action>       <Protocol Type="mapiHttp">         <Port>0</Port>         <DirectoryPort>0</DirectoryPort>         <ReferralPort>0</ReferralPort>         <MailStore>           <ExternalUrl>https://outlook.office365.com/mapi/emsmdb/?MailboxId=bd839d4a-31f7-42ce-a8ef-cbb3959ebb1c@itn.co.uk</ExternalUrl>         </MailStore>         <AddressBook>           <ExternalUrl>https://outlook.office365.com/mapi/nspi/?MailboxId=bd839d4a-31f7-42ce-a8ef-cbb3959ebb1c@itn.co.uk</ExternalUrl>         </AddressBook>       </Protocol>       <Protocol>         <Type>WEB</Type>         <Port>0</Port>         <DirectoryPort>0</DirectoryPort>         <ReferralPort>0</ReferralPort>         <Internal>           <OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>           <Protocol>             <Type>EXCH</Type>             <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>           </Protocol>         </Internal>         <External>           <OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/itn.co.uk/</OWAUrl>           <Protocol>             <Type>EXPR</Type>             <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>           </Protocol>         </External>       </Protocol>       <Protocol>         <Type>EXHTTP</Type>         <Server>outlook.office365.com</Server>         <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>         <OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>         <OABUrl>https://outlook.office365.com/OAB/45c6052f-47d9-4b56-9ba5-310d5d442644/</OABUrl>         <UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>         <Port>0</Port>         <DirectoryPort>0</DirectoryPort>         <ReferralPort>0</ReferralPort>         <SSL>On</SSL>         <AuthPackage>Basic</AuthPackage>         <EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>         <EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>         <SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>         <EcpUrl>https://outlook.office365.com/owa/</EcpUrl>         <EcpUrl-um>?path=/options/callanswering</EcpUrl-um>         <EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>         <EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=itn.co.uk</EcpUrl-mt>         <EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>         <EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>         <EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>         <EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>         <EcpUrl-connect>?path=/options/socialnetworks&amp;ignore1=&lt;Action&gt;&amp;ignore2=&lt;Provider&gt;</EcpUrl-connect>         <EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=itn.co.uk</EcpUrl-tm>         <EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=itn.co.uk</EcpUrl-tmCreating>         <EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=itn.co.uk</EcpUrl-tmEditing>         <EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>         <ServerExclusiveConnect>On</ServerExclusiveConnect>       </Protocol>     </Account>   </Response> </Autodiscover> HTTP Response Headers: request-id: e3187c83-af3d-4766-aeff-711b6cc60d2d X-CalculatedBETarget: am0pr07mb4324.eurprd07.prod.outlook.com X-RUM-Validated: 1 X-DiagInfo: AM0PR07MB4324 X-BEServer: AM0PR07MB4324 Cache-Control: private Content-Type: text/xml; charset=utf-8 Set-Cookie: X-BackEndCookie2=hitchcockr@itn.co.uk=u56Lnp2ejJqBns/HycmdyZnSm8rJzdLLyMjP0sbOmczSy8zJzc7Gz5zOnsaagZaLkdGckNGKlIHNz87H0s/H0s3Mq87KxczLxcvOgZqKjY+Nm8/I0Y+NkJvRkIqLk5CQlNGckJKBzw==; expires=Thu, 23-Aug-2018 15:34:41 GMT; path=/Autodiscover; secure; HttpOnly,X-BackEndCookie=hitchcockr@itn.co.uk=u56Lnp2ejJqBns/HycmdyZnSm8rJzdLLyMjP0sbOmczSy8zJzc7Gz5zOnsaagZaLkdGckNGKlIHNz87H0s/H0s3Mq87KxczLxcvOgZqKjY+Nm8/I0Y+NkJvRkIqLk5CQlNGckJKBzw==; expires=Thu, 23-Aug-2018 15:34:41 GMT; path=/Autodiscover; secure; HttpOnly Server: Microsoft-IIS/10.0 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET X-FEServer: DM5PR0101CA0022 Date: Tue, 24 Jul 2018 15:34:41 GMT Content-Length: 5209 Elapsed Time: 727 ms. The Microsoft Connectivity Analyzer is attempting to retrieve XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user racheal.hitchcock@itn.co.uk.   The Autodiscover XML response was successfully retrieved.

Hi guys...

Trying to move a mailbox from ex 2007 to ex online (stage migration) and getting error above.

Get-MoveRequestStatistics "user.com" | fl   gives error like

FailureSide                              :

Message                                  : Request was quarantined because of following error: Object reference not

                                           set to an instance of an object.

Any idea?

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?

Hi,

We would like to upgrade our Active directory and Exchange Email systems to its latest version.

Let me give a brief about our enviroment.

We have 6 Active Directory servers, 3 Client Access Servers and 3 Mailbox Servers (DAG). The email setup is hybrid

(60% mailboxes in Office 365 and 40% is on premises)

We are planning to upgrade it to 2016.

I request your comments and feedback about the best practice approach for performing this activity.

If any one have a valid document ,kindly share to my personal email ashruakkode@gmail.com

Thanks & Regards

Ashraf

Ashraf

Hello

     Your system have been configure hybrid , now normal when new user I must

     - create Ad user -> enable mailbox on on-premises -> sync user to office365 -> login to exchange online and create migrate batch this user to cloud

    how to skip enable mailbox on-premises and migrate mailbox to cloud ? I want after create user ad and sync to cloud then create mailbox in cloud

Best Regards,

Thanks 

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 was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:

Step 8 of 15: Mailbox role: Transport service

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

The only option on the screen was exit, so I did.  I checked the start menu, and there were two new Exchange icons, but I did not click them.  I ran the installer again, and it detected an incomplete install, the only option was to click next to finish the install, so I clicked next.  This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service."  I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013 came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh.  Any suggestions?

Hi all,

My environment : 2 Exchange server 2013 CU19 (both CAS + Mailbox roles) Windows server 2008 R2 Enterprise, Domain controller Windows server 2008 R2 Enterprise .
I added 1 more new Windows server 2012 R2 Standard into my domain and promoted it to Domain Controller.
I attempt to transfer 5 FSMO roles from Windows server 2008 R2 to Windows server 2012 R2 later, demote old server 2008 R2 and remove it from my environment later.

Here some information about 2 Exchange servers :

[PS] C:\Windows\system32>Get-ExchangeServer -Identity "exchangeserver1" -status | Select-Object Name,StaticDomainControllers,S
taticGlobalCatalogs,StaticConfigDomainController,StaticExcludedDomainControllers,CurrentDomainControllers,CurrentGlobalC
atalogs,CurrentConfigDomainController,OriginatingServer


Name                            : exchangeserver1
StaticDomainControllers         : {}
StaticGlobalCatalogs            : {}
StaticConfigDomainController    :
StaticExcludedDomainControllers : {}
CurrentDomainControllers        : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentGlobalCatalogs           : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentConfigDomainController   : server2008r2.mydomain.com
OriginatingServer               : server2008r2.mydomain.com

[PS] C:\Windows\system32>Get-ExchangeServer -Identity "exchangeserver2" -status | Select-Object Name,StaticDomainControllers,S
taticGlobalCatalogs,StaticConfigDomainController,StaticExcludedDomainControllers,CurrentDomainControllers,CurrentGlobalC
atalogs,CurrentConfigDomainController,OriginatingServer


Name                            : exchangeserver2
StaticDomainControllers         : {}
StaticGlobalCatalogs            : {}
StaticConfigDomainController    :
StaticExcludedDomainControllers : {}
CurrentDomainControllers        : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentGlobalCatalogs           : {server2008r2.mydomain.com, server2012r2.mydomain.com}
CurrentConfigDomainController   : server2008r2.mydomain.com
OriginatingServer               : server2008r2.mydomain.com

[PS] C:\Windows\system32>Get-AdServerSettings

ConfigurationDomainCont PreferredDomainControll PreferredGlobalCatalog  RecipientViewRoot       ViewEntireForest
roller                  ers
----------------------- ----------------------- ----------------------  -----------------       ----------------
                        {}                                              mydomain.com                 False

So what I need to do to change domain controller for 2 Exchange server ? For ex

Set-ExchangeServer -identity "exchangeserver1" -StaticDomainControllers "server2012r2.mydomain.com" -StaticGlobalCatalogs "server2012r2.mydomain.com"

Set-ExchangeServer -identity "exchangeserver2" -StaticDomainControllers "server2012r2.mydomain.com" -StaticGlobalCatalogs "server2012r2.mydomain.com"

Please give me some advice, thank you very much.

Hello all,

I have search for an answer to this and haven't found much. Does Microsoft support a Exchange 2013/2016 deployment on an Hyper-Converged platform?

Hi 

I have a server that is 2013 only on Cu6, I need to get this to the latest CU, but any CU 7 / 8 /9 that I have download will not run on the server comes up say that the update patch cannot be run due to application missing, I have tried the setup.exe to run the patch but its the same issue. From what I can see no-one has updated this server since this Patch was release the OS on the other hand has been patched, windows 2012 r2 datacenter ver 9600, OS Updates are installed 21/7/2018 is the last one that is installed on the server. 

Anyone come across this >?

Ta 

Ste

PS: username is my Gamertag :(