Exchange 2013 STD - Capacity Limits

Hi,
I plan to deploy, exchange 2013 STD with 400 users.
I understand the exchange STD 2013, supports 5 mounted (active mailbox database).
---> I've seen the mailbox database can grow to 2 TB size limit.
Questions:
1. What is the maximum mailboxes can I create with a single mailbox database? What is the recommended ratio ?
2. I plan to have 100 mailboxes per mailbox database would this be a good idea ?
Thanks,
Paul

Hi Paul,
Same concern has been raised earlier which clarified in this thread. Please checkout this :
http://social.technet.microsoft.com/Forums/exchange/en-US/975492cb-3510-4add-8a4d-f48bda76038a/maximum-number-of-user-mailboxes-supported-by-single-exchange-database-in-2007-2010-2013-?forum=exchangesvradmin

Similar Messages

Exchange 2013 Mail Size Limits

I am having an issue with setting the max send and receive size on Exchange 2013. I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange
server to an external account:
#550 5.3.4
ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##
I have checked the mail sizes and below is the report. I currently have both send and receive set to 100MB. Is there some other setting in 2013 that I am not aware of?
AnonymousSenderToRecipientRatePerHour                       : 1800
ClearCategories
: True
ConvertDisclaimerWrapperToEml                               : False
DSNConversionMode
: UseExchangeDSNs
ExternalDelayDsnEnabled                                     : True
ExternalDsnDefaultLanguage                                  :
ExternalDsnLanguageDetectionEnabled                         : True
ExternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
ExternalDsnReportingAuthority                               :
ExternalDsnSendHtml
: True
ExternalPostmasterAddress                                   :
GenerateCopyOfDSNFor                                        :
HygieneSuite
: Standard
InternalDelayDsnEnabled                                     : True
InternalDsnDefaultLanguage                                  :
InternalDsnLanguageDetectionEnabled                         : True
InternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
InternalDsnReportingAuthority                               :
InternalDsnSendHtml
: True
InternalSMTPServers
JournalingReportNdrTo                                       : <>
LegacyJournalingMigrationEnabled                            : False
LegacyArchiveJournalingEnabled                              : False
LegacyArchiveLiveJournalingEnabled                          : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling                : False
MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
MaxDumpsterTime
: 7.00:00:00
MaxReceiveSize
: 100 MB (104,857,600 bytes)
MaxRecipientEnvelopeLimit                                   : 500
MaxRetriesForLocalSiteShadow                                : 2
MaxRetriesForRemoteSiteShadow                               : 4
MaxSendSize
: 100 MB (104,857,600 bytes)
MigrationEnabled
: False
OpenDomainRoutingEnabled                                    : False
RejectMessageOnShadowFailure                                : False
Rfc2231EncodingEnabled                                      : False
SafetyNetHoldTime
: 2.00:00:00
ShadowHeartbeatFrequency                                    : 00:02:00
ShadowMessageAutoDiscardInterval                            : 2.00:00:00
ShadowMessagePreferenceSetting                              : PreferRemote
ShadowRedundancyEnabled                                     : True
ShadowResubmitTimeSpan                                      : 03:00:00
SupervisionTags
: {Reject, Allow}
TLSReceiveDomainSecureList                                  : {}
TLSSendDomainSecureList                                     : {}
VerifySecureSubmitEnabled                                   : False
VoicemailJournalingEnabled                                  : True
HeaderPromotionModeSetting                                  : NoCreate
Xexch50Enabled
: True

Hello Landfish,
Good Day...
The output gives the information that Size limit set for Receive and Send is 100 mb, but setting could have changed. So you can follow the below steps to resolve the issue.
There are basically three places where you can configure default message size limits on Exchange:
Organization transport settings
Send/receive connector settings
User mailbox settings.
To check your server’s current limit you can open Exchange Management Shell
Try the below commands to check the Message quota size limit
get-transportconfig | ft maxsendsize, maxreceivesize
get-receiveconnector | ft name, maxmessagesize
get-sendconnector | ft name, maxmessagesize
get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize
To change the above size limits based on your requirement.
Set-TransportConfig -MaxSendSize 200MB -MaxReceiveSize 500MB (Size is based on your requirement)
Attachment size limit
To set up the rule you can use the below PowerShell cmdlet, as the method is quite simple
New-TransportRule -Name LargeAttach -AttachmentSizeOver 20MB -RejectMessageReasonText "Message attachment size over 20MB - email rejected."
For More info
https://technet.microsoft.com/en-us/library/bb124708(v=exchg.150).aspx
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts @ Techrid.com

Exchange 2013 Mailbox Size Limits

Are there any hard limits on mailbox sizes in Exchange 2013 (either in terms of mailbox size or item count)?
Note: I am aware of the public folder mailbox size limits as well as the hard limit of 2TB for mailbox databases.

I believe the max mailbox size is 100 GB
http://blogs.technet.com/b/ashwinexchange/archive/2012/12/17/3541150.aspx
Major changes in Information Store
Managed Store
Newly rewritten Information Store processes, Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe.
Each database runs under its own process, allowing for isolation of store issues to a single database.
Tightly integrated with MSExchangeRepl.exe to provide higher availability through improved resiliency.
Public Folder Database no longer exist.
Exchange 2013 it supports up to 100 GB of Mailbox size, with OL2013 OST file size can be controlled.
Exchange 2013 Enterprise Edition can only mount 50 databases on a mailbox server

Installation MS Exchange 2013 Failed

Hello,
Today I make a fresh install of the windows server 2012 STD, installed differents roles et promote my server like Domain controller.
After, I installed MS Exchange 2013 STD on this server with following procedure https://social.technet.microsoft.com/wiki/contents/articles/14506.how-to-install-exchange-2013-on-windows-server-2012.aspx and I encountered the following error during setup
progress (installation GUI).
Erreur :
L'erreur suivante est survenue lors de l'exécution de "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " : "Échec de l'installation du produit « D:\Donnees Entreprise\Messagerie\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASEntIRS.MSI ». Erreur irrécupérable lors de l’installation. Le code
d'erreur est 1603.".
I uninstall MS Exchange, demote DC and delete the folders created during exchange install and reboot.
After, I promote, reinstall exchange and I have a same error. I verify that the IP V6 is enable, I downloaded the source installation a second time (from MVLS), verify that my computer account is member of the exchange admin group...
Could you help me please because I have not got any solution?
Thanks and kind regards
Guillaume

Hello,
Today I make a fresh install of the windows server 2012 STD, installed differents roles et promote my server like Domain controller.
After, I installed MS Exchange 2013 STD on this server with following procedure https://social.technet.microsoft.com/wiki/contents/articles/14506.how-to-install-exchange-2013-on-windows-server-2012.aspx and I encountered the following error during setup
progress (installation GUI).
Erreur :
L'erreur suivante est survenue lors de l'exécution de "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " : "Échec de l'installation du produit « D:\Donnees Entreprise\Messagerie\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASEntIRS.MSI ». Erreur irrécupérable lors de l’installation. Le code
d'erreur est 1603.".
I uninstall MS Exchange, demote DC and delete the folders created during exchange install and reboot.
After, I promote, reinstall exchange and I have a same error. I verify that the IP V6 is enable, I downloaded the source installation a second time (from MVLS), verify that my computer account is member of the exchange admin group...
Could you help me please because I have not got any solution?
Thanks and kind regards
Guillaume

Exchange 2013 DCOM Event ID 10028

I am running two virtual Exchange 2013 Std servers (CAS and MBX on both) on Server 2012 Std in two different sites (no DAG...yet). When connecting from EX01 through ECP or EMS and I try to retrieve configuration for something from the other server (EX02)
it will take up to 5 minutes before I get the information and the System Event viewer will have the following:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          8/21/2013 9:08:47 AM
Event ID:      10028
Task Category: None
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      EX02.domain.com
Description:
DCOM was unable to communicate with the computer EX02.domain.com using any of the configured protocols; requested by PID     26ec (c:\windows\system32\inetsrv\w3wp.exe).
Event Xml:
<Event xmlns="http :// schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10028</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-21T14:08:47.915595500Z" />
    <EventRecordID>15029</EventRecordID>
    <Correlation />
    <Execution ProcessID="744" ThreadID="19976" />
    <Channel>System</Channel>
    <Computer>EX02.domain.com</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="param1">EX02.domain.com</Data>
    <Data Name="param2">    26ec</Data>
    <Data Name="param3">c:\windows\system32\inetsrv\w3wp.exe</Data>
    <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3734343B382F32312F323031332031343A383A34373A3931353B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D313436313B466C6167733D303B506172616D733D303B3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3734343B382F32312F323031332031343A383A34373A3931353B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D3135333B466C6167733D303B506172616D733D343B7B506172616D23303A2D323134363839333030367D7B506172616D23313A347D7B506172616D23323A36383132367D7B506172616D23333A317D3E</Binary>
</EventData>
</Event>
This error can be repeatedly triggered with no problem. If I'm on EX01 on EMS and run:
Get-OWAVirtualDirectory -Server EX02
it will take nearly 4 minutes before I get the details and the System Event ID 10028 DistributedCOM will appear on EX01. Same occurs if I reverse the process from EX02. I have turned off the Windows Firewall to see if that makes a difference - no change.
I have remove AV from both servers - no change.
Any ideas will be appreciated.
~Rick

Having the same setup and running in the same problem. Remote-Powershell doesn't work properly. Any remote query needs minutes.
Two Exchange Server 2013 STD on Windows Server 2012, both with MBX & CAS (no DAG), placed in two different sites. CU2 is installed, the system is fully patched. The sites are connected over a IPSec-Tunnel with a acceptable RTT of 50 to 150ms. The Firewall
in between is open for the whole Servernetwork-Segments. The local Windows Firewall is deactivated by GPO. I can portping all needed ports (TCP/80,443,5985) on remote system with success. AutoDiscover is working properly, the Test-Outlook-Clients can connect
automatically to the server, in each site localy. Im using on both servers SAN-Certificates, created on the internal MS-CA. The external part does not exist until now, but there will be a reverse proxy (netscaler) with the official SAN-Certificate, on both
sites with separate internet access.
Another issue is very strange and I don't understand what causes that behavior: The administrators mailbox is on SRV1. When I connect to ECP over "https://fqdnOfSRV1/ECP/" works perfect. But when I connect over "https://fqdnOfSRV2/ECP/" to the same mailbox,
which is on SRV1, the IIS redirects me to the WebApp of administrator. I did test it inverse and using a administrator2 account, which is on a DB on SRV2. Same issue when I connect over SRV1.
I have much more issues and hope some of them will be addressed with CU3.
Did you have any update on this case?
Regards
Patrick

External companies with Barracuda firewalls not able to deliver mail to our Exchange 2013 environment reliably.

We upgraded to Exchange 2013 about a year ago. Since that time we've been having issues with certain companies having their mail delayed or rejected when sending to us. No problems us sending to them though. Eventually through troubleshooting I have
determined that all of these different companies have one thing in common: a barracuda firewall.
In the year since the installation I have updated Exchange all the way to SP1 but we still have this issue. The messages usually arrive to us, but quite often a day later, etc. Here is the message from one from the 26th that was rejected:
#< #4.0.0 X-Spam-&-Virus-Firewall; conversation with
mail.domain.ca[64.46.58.226] timed out while sending MAIL FROM> #SMTP#
Original message headers:
X-ASG-Debug-ID: 1406427098-0499ef4412c2d00001-3TTufb
Received: from DEVPMTLEXC2.devp.org ([192.168.1.202]) by
barracuda.devp.org
with ESMTP id EiJxT4ex1jxAnxdL; Sat, 26 Jul 2014 22:11:38 -0400 (EDT)
X-Barracuda-Envelope-From: [email protected]
X-ASG-Whitelist: Client
Received: from DEVPMTLEXC2.devp.org ([192.168.1.202]) by
DEVPMTLEXC2.devp.org
([192.168.1.202]) with mapi id 14.03.0195.001; Sat, 26 Jul 2014 22:11:37
-0400
From: "Farid, Sara" <[email protected]>
To: >
Subject:
X-ASG-Orig-Subj:
Thread-Index: AQHPqUAYJnlCbEpneUasDGYYczT9uw==
Date: Sun, 27 Jul 2014 02:11:37 +0000
Message-ID: <[email protected]>
References: <[email protected]>,<[email protected]>,<[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Content-Type: multipart/mixed;
boundary="_015_7FA4F0153A8D4D739357AED074A05ECFdevporg_"
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[192.168.1.202]
X-Barracuda-Start-Time: 1406427098
X-Barracuda-URL: http://172.16.1.200:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at devp.org
X-Barracuda-BRTS-Status: 1
Our Environment:
2x Exchange 2013 Std. SP1 Servers, All roles, DAG. We only use the built-in Exchange tools for anti-spam, traffic flows to and from exchange directly through NAT.

Hi, yesterday we had a very large outbound queue on our Barracuda's.
I did some investigation and found that all remote servers are Exchange servers. After some telnet smtp tests they all had the same problem. After sending the RCPT TO: command it takes between the 60 and 120 seconds to get the Recipient OK response. While
other servers answer in a second.
Before I contacted Barracuda I found your article.
I contacted Barracuda about this and they said it's a problem of the remote exchange servers which won't respond within the accepted time and not a Barracuda issue. The barracuda disconnects after 60 seconds and the official RFC describes that
the whole process should only take a few seconds.
They said that I could be that the remote server is doeing a spam or RBL lookup which cannot be done and causes too much delay. And because of this timeout the SMTP process takes much too time and the barracuda will disconnect before the
exchange server responds OK.
The outgoing timeout in the barracuda can't be changed manually and it should be fixed at the recipients side but the Barracuda support did make a change deep level in the config so our time out has been set to 120 seconds now and works for us but this only
works until we apply new firmware.
I suggest that you do some Telnet tests with your exchange if you could find if and why the RCPT TO: hangs for such a long time to respond. Please let me know if you'll find something so I can inform the remote companies which affects this.
Regards
Gert

Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
Note
If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
Based on you installation scenario, follow one of these steps to configure ARR:
If you are performing a clean setup, run the following command:
ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
config –cert path to the certificate file –hostnames host names for Exchange Server",
when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
domain I figured it would be ok to run the risk.. ;)

Hi
found this on
https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
"Ok just an update for anyone else how has this issue.
The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
of a better word. I should have retyped the whole command from scratch and it would have been right!
Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
From Microsoft:
We have tested on your environment and here is the investigation result from our senior engineer:
================================================================
Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
The one we check (compare) is ‘-‘ which has the code 0x45.
So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
Best Regards,
Johnny Chen
Microsoft Partner Support Community Technical Support Engineer
Microsoft Global Partner Services"

Accessing Exchange 2013 Mailboxes from Terminal Server hosted on Server 2003 Std - Cert Issues

We are in the midst of deploying an Exchange 2013 SP1 CU5 environment and have run into some issues. Currently there is a good coexistence between a single Exchange 2007 server and the 5 2013 servers. Mail is flowing through 2013 and then being
relayed to 2007 when necessary.
We have a number of Server 2003 Terminal Servers. On two separate machines, both running the lastest rollups of Outlook 2010, any user with a 2013 mailbox receives a password prompt after launching Outlook. It is trying to connect to one of the
two CAS, fills in the user's account, and will not accept any password. In addition, a window pops up behind stating "There is a problem with the proxy server's security certificate. the name on the security certificate is invalid or does
not match the name of the target site mail.pvschemicals.com. Outlook is unable to connect to the proxy server. (error code 0)." 2007 mailboxes are not affected.
We have checked pretty much everything that we can think of. Virtual Directories are good, certificate is good, etc. The strange thing is that only happens on 2003 TS machines, so I have to think that it's related. Our 2008 TS' are just
find.
We have applied the 2003 SHA2 certificate hotfix.

Hi,
According to your description, the configurations of Outlook Anywhere are proper. And based on my research, the issue can be related to the version of the terminal server 2003. Thus, please check if your terminal 2003 server is 2003 R2 SP2 or later.
For more information, you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/295bf2bc-584b-4de2-85fb-94096fac52e7/outlook-connectivity-problem-on-2003-term-server-exchange-2013?forum=exchangesvrclients
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

MT Exchange 2013 and Public Folder Limits

So having some real trouble trying to digest this data from a multi-tenant perspective.
Total public folders in hierarchy
10,000
Although you can create more than 10,000 public folders, it isn’t supported. Create
a Public Folder
Sub-folders under the parent folder
10,000
Although you can create more than 10,000 sub-folders under a parent folder, it isn’t supported.FolderHierarchyChildrenCountReceiveQuota parameter on the Set-Mailbox cmdlet.
So if my hierarchy consists of root folders 0-9,A-Z. Then below those top levels I place tenant domain level folders. Then below that I actually have folders for tenant data. Which of the above category applies? Sub-folders under
the parent folder is somewhat misleading? Does that mean in my above scenario I would only have 36 "parent" folders then would be able to have a total of 10k subfolders under those parents?
Or does it effectively mean 10k folders, that is all. One parent folder and 9,999 sub-folders? Or some combination of the two?
I had very high expectations for the redesigned public folders with incorporation into the DAG, but this solution seems MUCH less scalable and flexible then the legacy design. Additionally the recommendation of 2k concurrent users per PF mailbox, with
a max number of PF mailboxes at 100 effectively sets an org limit of 200k total mailboxes.
I can't help but feel this is just another nail in the coffin of non O365 Exchange resellers.

Hi,
Based on my research, the public folder size can be up to 100GB in the hosted Exchange 2013 environment:
http://www.wisnet.com/blog/hosted-exchange-2013-is-available-now/
As long as the total number is beyond the limit, we can at most have 100 public folder mailboxes ,10k public folders, 10k subfolders under one public folder and 200 concurrent users for one public folder mailboxes.
For more information about the public folders in Exchange 2013, you can refer to the following articles:
Public folders
http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
FAQ: Public Folders
http://technet.microsoft.com/en-us/library/jj552408.aspx
Public folders in the new Office
http://blogs.technet.com/b/exchange/archive/2012/11/08/public-folders-in-the-new-office.aspx
Exchange 2013 Modern Public Folders
http://windowsitpro.com/blog/exchange-2013-modern-public-folders
Public Folder Hierarchy and PF Mailboxes for Hosted setup
http://social.technet.microsoft.com/Forums/exchange/en-US/e9062abe-f484-462b-bc5e-ebdcb0862760/public-folder-hierarchy-and-pf-mailboxes-for-hosted-setup
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question about Exchange server, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working

Goal:
I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
At the very bottom of the page are three different methods. I have tried the first (per-user) and the third (untrusted) methods, with identical results. For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
information (although that is configured in the production domain and I would use it if it were possible).
Situation:
When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible. If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
will be visible, and sometimes it will not. When it is not, the area is filled with diagonal lines and hovering over it says “No Information”. The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
Adatum or Fabrikam.
I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person. They are quickly eroding what little confidence I had in them already. I’m posting here because
I’m desperate, and web searches for my errors turn up zero results. I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
to heave about anyone getting this to work, or not.
Setup:
There are three separate domains I am working with (names changed to protect the innocent). Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers. Adatum.local is a test domain set up fresh with Exchange
2013 SP1. Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels. The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012.
Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites. Adatum has a single site, and has two CAS and two mailbox servers. Fabrikam has one internet facing server to connect
to. A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets. Routing between them is completely unimpeded. The Fabrikam server sits on another network across the internet, but firewalls have
been configured and I can browse the availability website from the Contoso CAS servers.
The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum. The number of actual users on Exchange 2013 in Contoso is
~10. In Adatum, there are only a handful of mailboxes configured. The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability.
None of our testing/configurations have involved the Exchange 2007 servers. There are no SPNs configured for the other domains in AD.
Errors:
There are three basic errors that are returned in Outlook diagnostics. The first is the timeout error. For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error. If it doesn’t timeout, then it will respond with the Correct Response.
Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls. Less frequently, it will return Availability Error 2. If a mailbox server returns the first Availability
Error, then it will continue to return that error until it times out again or starts working. Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work. There is never an issue accessing availability information for users in the same domain as the request.
If the remote Exchange is in an errored state, then the response includes the error. For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
There are no Event Log errors that correspond to failed requests of any type. IIS logs don’t show anything beyond what is shown in the Outlook diagnostics. There are no DNS or Active Directory Replication errors in the Event Logs.
Timeout error:
CalendarEvents       : {}
ViewType             : None
MergedFreeBusyStatus : {}
WorkingHours         :
Result               : Error
ErrorCode            : ErrorTimeoutExpired
ErrorMessage         : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
                       . Name of the server where exception originated: Mailbox01
ErrorDetails         : {}
ErrorProperties      : {}
Availability Error:
CalendarEvents       : {}
ViewType             : None
MergedFreeBusyStatus : {}
WorkingHours         :
Result               : Error
ErrorCode            : ErrorProxyRequestProcessingFailed
ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
                       . Name of the server where exception originated: Mailbox01
ErrorDetails         : {}
ErrorProperties      : {}
Availability Error 2:
CalendarEvents       : {}
ViewType             : None
MergedFreeBusyStatus : {}
WorkingHours         :
Result               : Error
ErrorCode            : ErrorProxyRequestProcessingFailed
ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
                          at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
organizationId, String domainName)
                          at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
emailAddress)
                       . Name of the server where exception originated: Mailbox02
ErrorDetails         : {}
ErrorProperties      : {}
Working:
CalendarEvents       : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
ViewType             : FreeBusyMerged
MergedFreeBusyStatus : {Free, Free, Free, Free...}
WorkingHours         : Microsoft.Exchange.WebServices.Data.WorkingHours
Result               : Success
ErrorCode            : NoError
ErrorMessage         :
ErrorDetails         : {}
ErrorProperties      : {}
Start : 04/09/2014 00:00:00
End : 04/12/2014 00:00:00
Subject :
Location :
Testing Methodologies:
While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time. Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
post them here to help anyone in the future.
Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers. At least by default, it seems to pick a mailbox server in the same
site, but which mailbox server in the site appears to be random. It will typically pick the same one repeatedly for a while.
The first script uses the Microsoft Exchange Web Services Managed API 2.1.
http://www.microsoft.com/en-us/download/details.aspx?id=42022
You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address. The CAS proxies the request to the mailbox server which either responds with a failure
or the free/busy data.
The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly. That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
server the CAS happens to select. I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times. I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
ADs to verify it wasn’t failing authentication. (A failed authentication also generates a 401 error that is returned to the client.) I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
errors ever.
First Script:
# Import the Exchange Web Services module
Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
# Create the services object used to connect to Exchange
# You can specify a specific Exchange version, which I had to do to connect to 2007
# Exchange2007_SP1
# Exchange2010
# Exchange2010_SP1
# Exchange2010_SP2
# Exchange2013
# $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
# $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
$Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
$Service.UseDefaultCredentials = $true
# Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
# This is used to distinguish resolving from the 2007 server versus 2013
#$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
$Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
# Increase the amount output at the end to include the SOAP commands
$Service.TraceEnabled = $true
# Specify time frame to get free/busy for
$StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
$EndTime = $StartTime.AddDays(7)
# Create the various objects needed to perform the EWS request
$drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
$AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
$AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
$Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
$attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
# Specify SMTP addresses of accounts to request availability for
#$Attendeesbatch.Add("[email protected]")
$Attendeesbatch.Add("[email protected]")
#$Attendeesbatch.Add("[email protected]")
#$Attendeesbatch.Add("[email protected]")
# Clear out old results so that a failed request doesn't show information still
$availresponse = ""
# Request the availability information from Exchange
$availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
# Show summary information that would include errors
$availresponse.AttendeesAvailability
# Show all of the appointments in the requested time period
foreach($avail in $availresponse.AttendeesAvailability){
foreach($cvtEnt in $avail.CalendarEvents){
"Start : " + $cvtEnt.StartTime
"End : " + $cvtEnt.EndTime
"Subject : " + $cvtEnt.Details.Subject
"Location : " + $cvtEnt.Details.Location
Second Script:
# Change the server in this URL to specify which mailbox server to access
$url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
# Uncomment the below lines if you want to query EWS using credentials other than
# the ones used to run the script.
#If(!(Test-Path variable:global:cred))
# $cred = Get-Credential
function Execute-SOAPRequest
[Xml] $SOAPRequest,
[String] $URL
write-host "Sending SOAP Request To Server: $URL"
$soapWebRequest = [System.Net.WebRequest]::Create($URL)
# These appear to be the only things needed in the headers when making the request
$soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
$soapWebRequest.Accept = "text/xml"
$soapWebRequest.Method = "POST"
If(Test-Path variable:global:cred)
$soapWebRequest.Credentials = $cred
Else
$soapWebRequest.UseDefaultCredentials = $true
write-host "Initiating Send."
$requestStream = $soapWebRequest.GetRequestStream()
$SOAPRequest.Save($requestStream)
$requestStream.Close()
write-host "Send Complete, Waiting For Response."
$resp = $soapWebRequest.GetResponse()
$responseStream = $resp.GetResponseStream()
$soapReader = [System.IO.StreamReader]($responseStream)
$ReturnXml = [Xml] $soapReader.ReadToEnd()
$responseStream.Close()
write-host "Response Received."
return $ReturnXml
# The specing and line returns in the below variable are important for some reason
# For example, there must be a line return after the @' on the first line, or it's invalid...
# Change the line with this:
# <t:Address>[email protected]</t:Address>
# to the email address in the domain you want to query
$soap = [xml]@'
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<t:RequestServerVersion Version="Exchange2013_SP1" />
<t:TimeZoneContext>
<t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US & Canada)" Id="Central Standard Time">
<t:Periods>
<t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
<t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
<t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
</t:Periods>
<t:TransitionsGroups>
<t:TransitionsGroup Id="0">
<t:RecurringDayTransition>
<t:To Kind="Period">Dlt/1</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>4</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>1</t:Occurrence>
</t:RecurringDayTransition>
<t:RecurringDayTransition>
<t:To Kind="Period">Std</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>10</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>-1</t:Occurrence>
</t:RecurringDayTransition>
</t:TransitionsGroup>
<t:TransitionsGroup Id="1">
<t:RecurringDayTransition>
<t:To Kind="Period">Dlt/2007</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>3</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>2</t:Occurrence>
</t:RecurringDayTransition>
<t:RecurringDayTransition>
<t:To Kind="Period">Std</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>11</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>1</t:Occurrence>
</t:RecurringDayTransition>
</t:TransitionsGroup>
</t:TransitionsGroups>
<t:Transitions>
<t:Transition>
<t:To Kind="Group">0</t:To>
</t:Transition>
<t:AbsoluteDateTransition>
<t:To Kind="Group">1</t:To>
<t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
</t:AbsoluteDateTransition>
</t:Transitions>
</t:TimeZoneDefinition>
</t:TimeZoneContext>
</soap:Header>
<soap:Body>
<m:GetUserAvailabilityRequest>
<m:MailboxDataArray>
<t:MailboxData>
<t:Email>
<t:Address>[email protected]</t:Address>
</t:Email>
<t:AttendeeType>Required</t:AttendeeType>
<t:ExcludeConflicts>false</t:ExcludeConflicts>
</t:MailboxData>
</m:MailboxDataArray>
<t:FreeBusyViewOptions>
<t:TimeWindow>
<t:StartTime>2014-04-03T00:00:00</t:StartTime>
<t:EndTime>2014-04-10T00:00:00</t:EndTime>
</t:TimeWindow>
<t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
<t:RequestedView>DetailedMerged</t:RequestedView>
</t:FreeBusyViewOptions>
</m:GetUserAvailabilityRequest>
</soap:Body>
</soap:Envelope>
$ret = Execute-SOAPRequest $soap $url
# Uncomment out one of the below two lines to get output in different alternative formats
#$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
#$ret.InnerXml
# If the request is successful, show the appointments, otherwise show the failure message
If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
$ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
Else
$ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage

In this case, the SMTP domain is the same as the AD domain. If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
RunspaceId            : abb30c12-c578-4770-987f-41fe6206a463
ForestName            : adatum.local
UserName              : adatum\availtest
UseServiceAccount     : False
AccessMethod          : OrgWideFB
ProxyUrl              :
TargetAutodiscoverEpr :
ParentPathId          : CN=Availability Configuration
AdminDisplayName      :
ExchangeVersion       : 0.1 (8.0.535.0)
Name                  : adatum.local
DistinguishedName     : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
                        Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
Identity              : adatum.local
Guid                  : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
ObjectCategory        : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
ObjectClass           : {top, msExchAvailabilityAddressSpace}
WhenChanged           : 4/15/2014 12:33:53 PM
WhenCreated           : 4/15/2014 12:33:35 PM
WhenChangedUTC        : 4/15/2014 5:33:53 PM
WhenCreatedUTC        : 4/15/2014 5:33:35 PM
OrganizationId        :
OriginatingServer     : dc01.contoso.local
IsValid               : True
ObjectState           : Unchanged

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - Out of office unavailable when shared mailboxes added in

Good Morning all,
I have a strange issue with our MS Exchange 2013 environment concerning out of office.
When certain users try and access the OOO it gives them the below error message:
"Out
Of Office cannot be display because the server is currently unavailable"
As I mentioned, this is not affecting all users, here comes the strange part(I think so anyway)
The users in question have a shared mailbox added, if I remove the mailbox VIA ECP / Outlook client, out of office begins to work, once I add the mailbox back in, everything works, until the next day or some sort of refresh takes place and then OOO becomes
unavailable again.
Any help would be greatly appreciated.
Thanks,
San.

Did you recently installed windows update?
If yes, then check this, see if it applies by uninstalling the update.
http://windowsitpro.com/blog/update-causes-outlook-2013-fail-open-archive-mailboxes
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

High Amount of Spam on Exchange 2013 - Content Filtering is Enabled but Pfizer Spam Filling Up Everyone's Mailboxes

Hello
Previously I used Exchange 2010 with Forefront Threat Protection installed and this used to do a good job of stopping all the spam.
However since updating to Exchange 2013 earlier this year and enabling the integrated spam filtering everyone noticed a sudden increase in the amount of spam which was getting through which has been bad for a long time.
We have been living with it but in the last 3 weeks everyone has started getting about 40 emails a day from Pfizer for Viagra. All these seem to defeat the content filtering as Viagra is spelt with an extra I and the email address is always different.
Also images in emails are blocked by default but somehow all the images on these spam messages appear for everyone.
I am not sure the spam filtering is working at all and I'm not sure how to tell as ForeFront gives you a nice graphical dashboard but I can find nothing similar to this in Exchange and PowerShell seems the only way to configure the limited functionality
of the content filter.
Is there any way to get rid of these messages as it doesn't look very good when they are constantly popping up for everyone?
Thanks
Robin
Robin Wilson

Hello ManU
Thanks for the reply.
I have checked the logs and see this quite often:
AcceptMessage,,SCL,not available: policy is disabled
But other times it says this:
RejectMessage,550 5.7.1 Message rejected as spam by Content Filtering
Which seems to indicate it is rejecting some.
This is what one of the email headers look like:
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
RWS-MAIL.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38 via Mailbox Transport; Sat, 28 Dec 2013 10:59:26 +0000
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
rws-mail.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38; Sat, 28 Dec 2013 10:58:38 +0000
Received: from [90.169.106.204] (90.169.106.204) by mail.rwsservices.net
(192.168.2.151) with Microsoft SMTP Server id 15.0.775.38 via Frontend
Transport; Sat, 28 Dec 2013 10:58:37 +0000
Date: Sat, 28 Dec 2013 12:05:58 +0200
From: US.Pfizer eStore <[email protected]>
To: robin.wilson <[email protected]>
Message-ID: <[email protected]>
Subject: Dear robin.wilson up to 65% OFF!
X-Mailer: Airmail (223)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="dd2ee3ea_586bb9e4_6f04"
Return-Path: [email protected]
X-MS-Exchange-Organization-PRD: 001-taxis.co.uk
X-MS-Exchange-Organization-SenderIdResult: Neutral
Received-SPF: Neutral (rws-mail.rwsservices.net: 90.169.106.204 is neither
permitted nor denied by domain of [email protected])
X-MS-Exchange-Organization-Network-Message-Id: e8825204-1f32-48be-a331-08d0d1d30209
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.13223.464;SID:SenderIDStatus Neutral;OrigIP:90.169.106.204
X-EXCLAIMER-MD-CONFIG: 079171ba-394f-46d5-a160-56e416712e8e
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: rws-mail.rwsservices.net
X-MS-Exchange-Organization-AuthAs: Anonymous
The emails use a different sender email address every time and there is always a poem in very light grey writing in the body of the email. The drugs are always misspelt as well. Is this why these are getting through?
Thanks
Robin
Robin Wilson

Error while adding member to the dag in exchange 2013 sp1

I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
Senior Technical Consultant, MDS Computers

When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
[PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
+ CategoryInfo : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
+ FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
mConfigurationTasks.SetDatabaseAvailabilityGroup
+ PSComputerName : <server>
Also, this is logged in the eventlog:
Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
ErrorReportingEnabled: True
Definitely looks like a problem creating the filewitness share.
Frank.

Exchange 2013 SP1 and SCOM 2012 R2

Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
Cheers

FYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 STD - Capacity Limits

Similar Messages

Maybe you are looking for