Hi all 

is there a problem when using a SAN certificate generated from a private CA in exchange 2010 rather than buying a certificae from public CA .

I know that it will not be trusted for users that are not joined the domain but I can send the root certifcate to those users to install it in the trusted root ertiificate on their pc 

Hi all, 

I wonder sometime users  outside the company when configuring outlook for the first time ,sometime it's configured automatically as imap not microsoft exchange account ,keeep in mind that all mailboxes in exchange 2010 has all the the features enabled for mapi,pop3,imap

Hi,

I have Exchange server 2010 SP3 installed.

The WindowsUpdate asks me to install Update Rollup 8-v2:

But I have installed Update Rollup 24 already:

So I started to examine Exchange version and I discovered powershell "Get-ExchangeServer" returns 14.3 123.4:

Get-ExchangeServer | select name, admindisplayversion
Name                                                                                                AdminDisplayVersion
----                                                                                                -------------------
Exchange01                                                                                             Version 14.3 (Build 123.4)

Same in the EMC -> Server Configuration.

The About Exchange Server dialog shows 14.03.0399.00:

Only the powershell "Get-Command ExSetup" returns correct version (Rollup 24):

Get-Command ExSetup | ForEach {$_.FileVersionInfo}

ProductVersion   FileVersion      FileName
--------------   -----------      --------
14.03.0419.000   14.03.0419.000   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

So, is my Exchange Server only partially updated? Are some files still in the old version? It looks like Windows Update thinks so, if it wants to install the old patch ...

hi 

I experinced that someone sent many mails at rate 2 mails per minute for 3 hours ,and only 2 users in my organization their inbox was full because of this mails  ,how can I stop this kind of attack in exchange 

I checked global settings :

it hs only limits for message size not and number of recipients 

I'm checking my Exchange build with the command 

GCM exsetup |%{$_.Fileversioninfo}

It shows 

ProductVersion   FileVersion      FileName
--------------   -----------      --------
14.03.0419.000   14.03.0419.000   D:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

Which is Update Rollup 24 For Exchange 2010 SP3 (KB4458321)

The KB for this roll up does not show in the list of KB's when doing a systeminfo command, should I be concerned? Am I actually on Rollup 24 For Exchange 2010 SP3?

Thanks

Pat

New computer want to put reminders in the calendar and be notified before.

Hi,

I have Exchange server 2010 SP3 installed.

The WindowsUpdate asks me to install Update Rollup 8-v2:

But I have installed Update Rollup 24 already:

So I started to examine Exchange version and I discovered powershell "Get-ExchangeServer" returns 14.3 123.4:

Get-ExchangeServer | select name, admindisplayversion
Name                                                                                                AdminDisplayVersion
----                                                                                                -------------------
Exchange01                                                                                             Version 14.3 (Build 123.4)

Same in the EMC -> Server Configuration.

The About Exchange Server dialog shows 14.03.0399.00:

Only the powershell "Get-Command ExSetup" returns correct version (Rollup 24):

Get-Command ExSetup | ForEach {$_.FileVersionInfo}

ProductVersion   FileVersion      FileName
--------------   -----------      --------
14.03.0419.000   14.03.0419.000   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

So, is my Exchange Server only partially updated? Are some files still in the old version? It looks like Windows Update thinks so, if it wants to install the old patch ...

Hello guys, I would like to ask for your help if you have any idea about the error message when I am trying to reinstall the Exchange Server 2010 Management Tools. I updated my Windows10 version to v1903 and found Exchange Management Tool is not working properly, I uninstalled the application completely and try reinstalling. the below error is what i received. It will be great if someone will be able to provide any suggestion how to solve my issue. Thanks in advance. :) 

A client has an Exchange 2010 single-server running the very-antique SP3 UR4. No later URs will install; they roll back and sometimes damage OWA in the process. (We know...we've tried!)

We want to migrate them to O365, and they're large enough that we need to do hybrid, not cutover. But we need the latest or second-to-latest UR to do hybrid.

The only way I know of to do this--

1. Build a new EX2010 SP3 UR4 single-server VM.
2. Migrate mailboxes, PFs, CAS, etc. from old to new server.
3. Decommission old server.
4. Upgrade new server to current UR.
5. Proceed with O365 hybrid migration.

Expensive and time-consuming. Assuming there's no way to get the current UR on the old server, is there any other way to get to hybrid? Pretty sure the answer's no, but have to ask.

Thanks!

Hi All,

I have one mailbox database for 2 nodes: Mail2, Mail3 in DAG.

Now, mail2 is die. I only use one Mail3 to work. And, how i can remove mail2 out of mailboxdatabase copies ?

I would like to use one Mailbox database for mail3.

Thanks,

Tony

Dears,

We've Exchange 2010 in our environment. We've set multiple SMTP domains on our Exchange. Issue is with only domain, when users try to set Autoreply for Out of office, it gives an error " Your autoreply replies setting cannot be displayed, server is currently unavailable".

Appreciate your assistance to fix this issue.

Regards,

Ammar

Hi all,

I was just running a simple Set-WebServicesVirtualDirectory command in my Exchange 2010 On-premise server and it complained  "EWSServiceCredentials could not be loaded".  

I went to the actual web.config file line 2426 and I saw the following.

     <EWSServiceCredentials>
      <issuedTokenAuthentication certificateValidationMode="None">
       <knownCertificates />
      </issuedTokenAuthentication>
     </EWSServiceCredentials>

Is my config file missing something?

Details of the error message is below.

Set-WebServicesVirtualDirectory -Identity "WEBMAIL\EWS (Default Web Site)" -WSSecurityAuthentication $False

The type 'Microsoft.Exchange.Services.Wcf.EWSServiceCredentialsElement, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSServiceCredentials' could not be loaded. (C:\Program
Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2426)
At C:\Users\user\AppData\Local\Temp\tmp_vu5qnkou.kpj\tmp_vu5qnkou.kpj.psm1:57997 char:9
+         $steppablePipeline.End()
+         ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (WEBMAIL\EWS (Default Web Site):ADObjectId) [Set-WebServicesVirtualDirectory], ConfigurationErrorsException
    + FullyQualifiedErrorId : C9B73B43,Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebServicesVirtualDirectory
    + PSComputerName        : domain.com.au

Hello,

I have followed the procedures to set up federation trust between 2 sites.

The link to MFG seems to work by running Test-FederationTrust from both sites and we have established org relationship between the 2 sites.

However, we could not see each other's free/busy data.

I ran Test-organisationrelationship with verbose from each site.  They both generated errors as follows.

Did anyone encounter this before?

Site A error is "Invalid Security Token"
=======================

VERBOSE: [03:35:54.901 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service failed to be called at 'https://autodiscover.siteA.com.au/autodiscover/autodiscover.svc/WSSecurity' because the following error occurred: SoapExcept
ion.Code = http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd:InvalidSecurityToken
Exception:
System.Web.Services.Protocols.SoapHeaderException: An error occurred when processing the security tokens in the message.

Site B error is "HTTP status 401: Unauthorised"
=============================

VERBOSE: [07:09:06.136 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service failed to be called at 'https://autodiscover.siteB.com.au/autodiscover/autodiscover.svc/WSSecurity' because the
following error occurred: WebException.Response = <cannot read response stream>
Exception:
System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

We recently changed our public IP addresses, and now mobile email apps no longer work while away from the network. I updated our external DNS host to include two new A records for mail and autodiscover, so outgoing and incoming emails are coming through fine within the network. 

We use Exchange 2010 and Windows Server 2012; both are behind a SonicWall firewall. I have updated the local DNS records and the firewall accordingly. The X1 (primary) and X2 (backup) interfaces reflect the new IP address info. I also created new public_mail and private_mail address objects. 

I used the Microsoft Remote Connectivity Analyzer and found that autodiscover is not working (pasted below). It looks like port 443 is not listening/opening. However, I am not sure why. It is configured to open. Any help is much appreciated. Please let me know if you need more information regarding the problem.

Thanks,

Kevin

 The Microsoft Connectivity Analyzer is attempting to test Autodiscover for k Testing Autodiscover 
failed.
Additional Details Elapsed Time: 5071 ms. Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method. Additional Details
Elapsed Time: 5071 ms.
Test Steps
Attempting to test potential Autodiscover URL https://westm                   
.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed.
Additional Details Elapsed Time: 3303 ms.
Test Steps
Attempting to resolve the host name westm                   .com in DNS. The host name resolved 
successfully.
Additional Details
IP addresses returned: 104. Elapsed Time: 38 ms.
by GoDaddy
Testing TCP port 443 on host westminstervillagein.com to ensure it's listening and open. The port 
was opened successfully.
Additional Details Elapsed Time: 162 ms.
Testing the SSL certificate to make sure it's valid. The certificate passed all validation 
requirements.
Additional Details Elapsed Time: 517 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server 
westm                   .com on p The Microsoft Connectivity Analyzer successfully obtained the 
remote SSL certificate.

Additional Details
Validating the certificate name.
The certificate name was validated successfully. Additional Details
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=west                      .com. 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=DST Root CA 
X3, O=Digital Signatur Elapsed Time: 29 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 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 = 7/12/2019 8:26:20 PM, NotAfter = 10/10/2019 8:26:20 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: 1252 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


7/28/2019                                                                                          
  Microsoft Remote Connectivity Analyzer
Elapsed Time: 1332 ms. Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL 
https://west.com:443/Autodiscover/Autodiscover.xml for user  one@westm.com.
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:
Transfer-Encoding: chunked Connection: keep-alive Keep-Alive: timeout=20
Vary: Accept-Encoding,Accept-Encoding
Link: <https://westminstervillagein.com/wp-json/>; rel="https://api.w.org/" WPE-Backend: apache
Cache-Control: no-cache, must-revalidate, max-age=0 Content-Type: text/html; charset=UTF-8
Date: Sun, 28 Jul 2019 22:54:49 GMT
Expires: Wed, 11 Jan 1984 05:00:00 GMT Server: nginx
Elapsed Time: 1331 ms.
Attempting to test potential Autodiscover URL https://autodiscover.west                      
.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed.
Additional Details Elapsed Time: 1385 ms.
Test Steps
Attempting to resolve the host name autodiscover.westm                   .com in DNS. The host name 
resolved successfully.
Additional Details
IP addresses returned: 216.2 Elapsed Time: 26 ms.
Testing TCP port 443 on host autodiscover.westm                   .com to ensure it's listening and 
open. The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 1358 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to 
contact Autodiscover using the HTTP Redirect method failed.
Additional Details Elapsed Time: 367 ms.
Test Steps
Attempting to resolve the host name autodiscover.westm                  n.com in DNS. The host name 
resolved successfully.
Additional Details
IP addresses returned: 216.2 Elapsed Time: 12 ms.
Testing TCP port 80 on host autodiscover.westm                   .com to ensure it's listening and 
open. The port was opened successfully.
Additional Details Elapsed Time: 130 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.westm                   .com 
for an HTTP redirect to the Autodiscov The Microsoft Connectivity Analyzer failed to get an HTTP 
redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body 
of the response: You do to view this directory or page.
HTTP Response Headers:
Content-Length: 58 Content-Type: text/html
Date: Sun, 28 Jul 2019 22:54:51 GMT
Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET Elapsed Time: 223 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV 
redirect method. Additional Details
Elapsed Time: 9 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.westm                   .com in DNS. The 
Autodiscover SRV record wasn't found in DNS.
https://testconnectivity.microsoft.com/#&&6bcC5mCLIouoADw0Cig+2vSiG8pTcCTQJcd+stP++aHikM5dxPV+EL3774
yp3duvmVT5ySfoC5a991pnFqE…     2/3

7/28/2019                                                                                          
  Microsoft Remote Connectivity Analyzer
https://testconnectivity.microsoft.com/#&&6bcC5mCLIouoADw0Cig+2vSiG8pTcCTQJcd+stP++aHikM5dxPV+EL3774
yp3duvmVT5ySfoC5a991pnFqE…     3/3
Sta
Tell me more about this issue and how to resolve it Additional Details
Elapsed Time: 9 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'west                      
.com' for Office 365. Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in 
Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it Additional Details
There is no Autodiscover CNAME record for your domain 'westmi                       m'.

Hi

I have exchange 2010

I'm trying to delete old ActiveSync Device to user (using EMC)but it say that it "cannot be found"

any idea?

I think that in the past I delete the device object from AD 

Hello all,

I was wondering what the logging file size estimation for a year would be for a 2016 Exchange server with 300 Mailboxes and around maybe 50 Messages per user a day. With high times being 8-4 With maybe 70 or so users being very active, I wouldn't say all 300 users send the 50 per day maybe just the 70 highly active. We have some users that may send twice a week, any who I am moving from Exchange 2010 fairly soon. With two servers in the DAG and 5 DB's in the server, my CIO wants to know if we could supply the server with the storage to hold our log files for a year. While the excel sheet that calculates is useful it only shows storage of logs per Server, DAG, Environment not per day, week, month, year total unless there is a field I am overlooking.

Thanks!  

Hi,

After a migration of Exchange 2010 to 2016, i have the following error:

[08/01/2019 10:46:46.0737] [1] Setup failed previously while performing the action Uninstall.  Looking for the failed task with ID ClientAccessOwaComponent___5effe7121e1740c083904cc189687464.
[08/01/2019 10:46:46.0737] [1] 71 tasks were found to execute.
[08/01/2019 10:46:46.0737] [1] Processing component 'OWA Configuration' (Installing/Removing Outlook Web App Component.).
[08/01/2019 10:46:46.0737] [1] Executing:
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
       
[08/01/2019 10:46:46.0799] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'MAIL15.domain.local', Preferred Global Catalog: 'MAIL15.domain.local', Preferred Domain Controllers: '{ MAIL15.domain.local }'
[08/01/2019 10:46:46.0799] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\System32\inetsrv\appcmd.exe' -Args:'uninstall module exppw'
[08/01/2019 10:46:46.0815] [2] Starting: C:\Windows\System32\inetsrv\appcmd.exe with arguments: uninstall module exppw
[08/01/2019 10:46:47.0298] [2] Process standard output: Failed to initialize command processor: Failed to initialize command object configuration. (HRESULT=c00ce558).

[08/01/2019 10:46:47.0298] [2] Process standard error:
[08/01/2019 10:46:47.0345] [2] [ERROR] Unexpected Error
[08/01/2019 10:46:47.0345] [2] [ERROR] Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [2] Ending processing Start-SetupProcess
[08/01/2019 10:46:47.0345] [1] The following 1 error(s) occurred during task execution:
[08/01/2019 10:46:47.0345] [1] 0.  ErrorRecord: Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [1] [ERROR] The following error was generated when "$error.Clear();
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
        " was run: "Process execution failed with exit code -1072896680.".
[08/01/2019 10:46:47.0345] [1] [ERROR] Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponent___5effe7121e1740c083904cc189687464 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[08/01/2019 10:46:47.0345] [1] Setup is stopping now because of one or more critical errors.

I already those soltutions:

1. Go into IIS manager
2. go to the servername (Global configuration)
3. Go into Modules
4. Lookfor exppw - it might exist, just remove it :-)
5. Select "Configure NAtive Module"
6. In the dialog - select Register, type "exppw" as Name
7. Click the browse button for Path, and browse to f.ek. "c:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\Auth\" and Select exppw.dll
8. Press okey and okey - the exppw should be in the list Again, for Exchange Setup to remove :-)
9. re-run setup to uninstall Exchange 2010, and it should now run without problems.

And tried with another  file :C:\Windows\System32\inetsrv\config\applicationHost.config

Could you please give me some help?

Regards,

DB