Hello,

We have Exchange 2013 CU21 hybrid environment. One of the O365 user is not able to send email with attachment of size 16MB to On-premises user.

Maxreceivesize on transport config is 20MB.

Receive connector limit is also 20MB.

Getting below error on message tracking log.

I am trying to export all the mailbox in our environment with the following field.

Name

DisplayName

SamAccountName

EmailAddresses

PrimarySmtpAddress

Database

TotalItemSize

ItemCount

Can anyone please check if the below script is correct or not?

$report = @()
$Mbxs = Get-Mailbox -resultsize unlimited
foreach ($Mbx in $Mbxs)
{
   $TotalItemSize = (Get-MailboxStatistics $Mbx).TotalItemSize
   $ItemCount  = (Get-MailboxStatistics $Mbx).ItemCount

    $reportObj = New-Object PSObject
    $reportObj | Add-Member NoteProperty -Name "Name" -Value $mbx.Name
    $reportObj | Add-Member NoteProperty -Name "DisplayName" -Value $mbx.DisplayName
    $reportObj | Add-Member NoteProperty -Name "SamAccountName" -Value $mbx.SamAccountName
    $reportObj | Add-Member NoteProperty -Name "EmailAddresses" -Value $mbx.EmailAddresses
    $reportObj | Add-Member NoteProperty -Name "PrimarySmtpAddress" -Value $mbx.PrimarySmtpAddress
    $reportObj | Add-Member NoteProperty -Name "Database" -Value $mbx.Database
    $reportObj | Add-Member NoteProperty -Name "TotalItemSize" -Value $TotalItemSize
    $reportObj | Add-Member NoteProperty -Name "ItemCount" -Value $ItemCount
    $report += $reportObj

}

After installing CU 22 for Exchange 2013 Standard, our third-party Symantec Mail Security product can no longer carry out antivirus scans.  That product is installed directly on the server.  The vendor examined the server, and observed that when https://mail.customername.com/ews/exchange.asmx is accessed from a web browser on the Exchange server, the browser prompts for credentials to authenticate over and over, even when valid credentials are specified (we tried 2 different usernames/passwords).  Eventually, a blank page loads.  

If that same URL is accessed from a browser on another computer on the network, the authentication succeeds and the default "Service--You have created a service.  To test this service [...]" landing page loads. Again, we used two different sets of valid credentials to confirm.

Checked the EWS virtual directory, it's https://mail.customername.com/ews/exchange.asmx for both internalURL and externalURL, as it should be.

Back on the server, the vendor had us configure their product to use https://servername.local/ews/exchange.asmx instead of https://mail.customername.com/ews/exchange.asmx, and Symantec started working again.  Sure enough, if you browse to https://servername.local/ews/exchange.asmx on the server, and authenticate when prompted, you get right through to the test page.  Using the other URL still fails.

Here's why I'm pointing to CU 22 as the possible culprit: we restored a month-old backup of this Exchange server, running CU 20, and browsing to https://mail.customername.com/ews/exchange.asmx and authenticating lets us right in to the landing page, no problem.

It's probably obvious since we do manage to get prompted for credentials, but I should note that the server with CU22 is able to resolve the URL that doesn't work in DNS, so it's not a DNS issue.

Exchange 2013 CUs can't be rolled back--what should I do to correct this?  Symantec characterized their solution as a 'workaround', and said we should investigate whether something went wrong with the CU.

Thanks!

Dear All, 

I created a signature using owa in exchange 2016 and enable the option "Automatically include my signature on messages I send". Its work fine when i use owa to compose any email or send email my signature is added without any issue. But this is not the case with outlook client 2016, i am not getting any signature when i try to send or compose via Outlook 2016. Is owa signature is enough to sync with outlook 2016 or there is something different way to handle signature for outlook.  

After installing Exchange Server 2013 Service Pack 1 I'm getting 6003 error in the event log:

MSExchangeHMHost: Exchange failed to create the log directory D:\MonitoringDiagnosticLogs\MSExchangeHMHost ...

I can't believe it but see for yourself: this "D:\..." path is HARDCODED to "\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.Components.dll"  !!!

How could it be and how to deal with this error!?

Alexey Kuznetsov,
Relief Software
More than 80 free add-ins for Outlook

It may not be an issue, but I updated a users title in AD on Thursday and today (monday) it had not updated in the GAL or in ECP. I updated the users profile information manually in ECP, but I wonder if there is a way to validate what information is syncing from active directory into exchange, and what that interval is.

(i might have just needed to wait longer, but I know the default is 24 hours).

Our exchange 2013 is on premises, but we do have Office365 (just not for mail...yet)

Hello,

I need help in locating who deleted a user mailbox in Exchange.

The AD logs show that the user was deleted by Exchange Mailbox server. I want to know how and where to check the logs in exchange side to trace who deleted that user mailbox.

I have hunch that the mailbox was deleted in EAC but I do not know where exactly to check.

Thanks in advance!

Hi,

I'm looking for some guidance on this if possible.  We've rolled out our first Exchange 2013 environment and we're receiving the following event log entries:

Hi Everyone

Yesterday evenything was working fine, and then this morning, I`m unable to establish a connection with the Exchange shell. I receive the following errors. Any help is appreciated.

         Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Tip of the day #55:

Want to view the mounted status of all mailbox databases? Type:

 Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted

VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
VERBOSE: Connecting to .
New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value
"http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer="
to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
At line:1 char:30
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+                              ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-PSSession], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand

[PS] C:\Windows\system32>

Ernie Prescott

Updated information.

I can succussfully connect to the exchange powershell from a remote computer, using this method.

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<FQDN of Exchange 2013 Client Access server>/PowerShell/ -Authentication Kerberos

Import-PSSession $Session

So the problem is localised on the server.

Regards

Hi,

We deploy, manage and maintain Hybrid Exchange environments for a number of customers. Some are 2013 based, some are 2016.

In most cases new users are created correctly using either the New-RemoteMailbox or Enable-RemoteMailbox cmdlets with the On-premises Exchange Shell.

However, from time to time somebody accidentally creates a Cloud only user using the Office 365 Admin Center, and then creates a local on-premises AD user with a soft match occurring at the next Azure AD Connect sync cycle. After a couple of weeks somebody else usually realizes the error was made due to some calendaring or global address list issues, and the accounts are removed and recreated from scratch. Email data has to be exported to PST and re-imported to the new correctly created mailbox. The end user at the customer end is often inconvenienced due to the error and subsequent rework.

I've been able to work around this in the past using ADSIEdit and attribute editor. This article suggests a similar technique to correct this - http://www.expta.com/2016/05/creating-remote-mailbox-in-exchange.html?m=1

I'm curious to get feedback from Microsoft whether soft matching the accounts, running Enable-RemoteMailbox and updating the ExchangeGUID of the remote mailbox on-prem to match the ExchangeGUID of the Cloud mailbox is a supported technique to recover from the incorrect creation of the mailbox.

Feedback from non-Microsoft forum members is obviously welcome too.

Cheers

Hello,

I have an issue with setting delegates for a single mailbox in my organization. When I try to save the delegates in Outlook I receive the following error:

The delegate settings were not saved correctly. Cannot activate free/busy information.

The version of Exchange is 2013 and Outlook 2013.

I found this: https://support.microsoft.com/en-us/kb/958443, so I tested it, but it doesn't work. /cleanfreebusy switch is deprecated in Outlook 2013.

I'm able to set delegates via OWA, but when allow delegates to see private items, this doesn't work in Outlook.

Can you please help.

Hello all,

We have been journaling exchange emails to a dedicated DB and mailbox, this works great.

We then extract the journaled mailbox to PST every day and hold the PST file for X amount of time.

The emails which are journaled to the journal mailbox show as message attachments, not as an email message, is there a process or a tool which can extract the emails which are attachments from the journal and have them just as the original email?

Not sure If I'm clear but if not please ask!

Thanks

Cheers, Andy andrewDOTstoryATjameswalkerDOTbiz

I enabled OWA light by running this command in EMS:

 Set-OWAVirtualDirectory –LogonPageLightSelectionEnabled $true

I also enabled public/private computer selection.

Then I tried to use iisreset /noforce to force the changes, but it didn't work so I used iisreset instead.  After that, OWA no longer worked.  I get this page after logging in:

I tried restarting the server but it didn't help.  Then I disabled the light version and public/private computer selection and restarted again but it still doesn't work.  I also tried reseting the OWA virtual directory and then restarting, but no luck.

What I've noticed is that it WILL work on IE11, as this FORCES the light version.  

I don't see anything in the event logs related to this, and this is all I see in the IIS logs:

POST /owa/service.svc action=GetOwaUserConfiguration 443 pjdist\nmuleski 10.100.10.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+WOW64;+Trident/6.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+.NET4.0C;+.NET4.0E;+InfoPath.3) 500 0 64 124

If anybody could help me out I'd greatly appreciate it!

Hello,

I have an on-prem mailbox and for some requirements I need to setup a forwarding. I tried setting it up in admin center under the mailbox feature-->mail flow but I cannot find the mailbox where I need to forward to that is on O365. Is there a command to do this?

Thanks!

Beginning this weekend, EAC is incredibly slow and users are receiving an error that states "The operation can't be performed because you're running another time-consuming operation".

Any ideas on how to identify this "time-consuming operation"?

The issue is happening across all 4 on-prem Exchange 2013 servers and only appears to affect the admin console. OWA works normally. The shell works normally. We're not seeing anything unusual in the event log. Resource utilization looks fine. IIS resets and rolling reboots haven't resolved the issue.

Hello, all!

I'm working through an Exchange 2013 deployment and have come up against a problem I've not seen before.  

The A/D domain is test.net (for example) and the email domain is test.com.  According to the usual rules I should be able to add a new email address policy and have the new policy as default.  That way mail for users at test.net and test.com get mail, and new mail automatically gets the test.com domain on sent messages.

Problem is:  in the EAC, when I specify the email address format and click "save" in the address format page, the window goes back to the New Email Address Policy page, but doesn't update the email address format box.  There's an SMTP type shown, but nothing in the address format part.

When I try to save,  I get an error "The address 'SMTP:undefined' is invalid: The SMTP e-mail address template "undefined" is invalid."  That makes sense since the address format isn't shown.  If I edit the email address format again, the changes I made don't show, as though they weren't saved.

Event logs don't show anything weird related to this change.  This happens on my test server and on the production stack I'm trying to deploy.  It also doesn't matter if I choose which users to apply the change to.

I haven't tried to make this change using PowerShell yet; I need the EAC to work reliably so that all admins can make changes to the installation.

Any thoughts on this one?

Thanks to all for looking!

Gregg

Our team recently renewed our Federation Gateway certificate which is working. However, we now have the old certificate that is still on our Exchange servers but has expired. When we try to remove the expired certificate, we get an error. We issued the PowerShell command "Get-FederationTrust | Select Org*Certificate" and we can see that the old certificate Thumbprint is listed in theOrgPrevPrivCertificate field. We have searched through TechNet, but have not found any procedure that describes how to remove the old certificate after it has been replaced with a new certificate. Any help would be greatly appreciated.

Our environment is Exchange Server 2013 CU15

I want to clear or remove mailbox database log file (E000000000A.log many file) in exchange server 2016, If I remove the log file, the (mailboxdatabase.edb) will be no damage?

I hope, Please share me exact clear or remove documentation for exchange server 2016