Exchange 2013 Archive mailbox best practise

Current senario:
Migrating to Exchange 2013 CU3 from lotus Domino
in lotus domino the customer is having huge archive files(nfs file size is around 30 GB, like wise users are having multiple archive file with same size.)
Requirement is all these file need to migrated to exchange 2013 CU3. whcih we are taking care by using thrid party tool.
My concern is exchang e2013 support for huge mailbox size. if so what maximum size supported for online mailbox and archive mailbox.
can I assign multiple archive mailbox to users.
we have got separate Exchange 2013 archive server in place
We would like know the best practise/guide line for archive mailbox/live mailbox size.
refered below link:
http://blogs.technet.com/b/ashwinexchange/archive/2012/12/16/major-changes-with-exchange-server-2013-part-1.aspx

The key decision is that the content in the primary mailbox is synchronized with the client when in cached mode, while the content in the archive is not. So I'd want to keep the primary mailbox populated with the content the user needs on a daily basis,
and put the rest in the archive. Unfortunately, that answer is not a number, and it isn't the same for all users.
Each user can have zero or one archive mailboxes, not multiple.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Exchange 2013 Archiving question

Hi all,
I have a question on Exchange 2013 Archiving.
In the Default MRM Policy it has the Default 2 year move to archive tag.
When this runs it moves any emails over 2 years old to the users Archive mailbox.
I also know it will recreate the folder structure that was in the inbox.
My question is once it's moved to the users Archive what policy is applied to the emails and folders by default?
When you look at them it just says Using Parent folder Policy.
Would the parent folder be the Archive - %username it's self? Or is nothing applied and the users must go in a assign a tag to it?
Thanks

Hi,
If you apply one retention policy to a mailbox, then this retention policy will be applied to the primary and archive mailbox, this means that the archive mailbox have the same retention policy as primary mailbox.
Here is an example to help you to understand this.
You can use a DPT with the Move to Archive action to move items to the archive mailbox in two years, and a DPT with a deletion action to remove items from the mailbox
in seven years. Items in both primary and archive mailboxes will be deleted after seven years.
You can refer to the following article for more information.
http://technet.microsoft.com/en-gb/library/dd297955(v=exchg.150).aspx
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 Health Mailbox filling up security logs

I'm doing security audits and having the Exchange 2013 Health Mailbox fill up my security logs. I've read that if I delete the mailboxes and re-create them and restart the service the errors will go away. My question is how do I delete them?
I found the full mailbox name with this command.
get-mailbox -monitoring | select-object -expandproperty name
Do I use this method?
Remove-Mailbox -Identity contoso\johnor this one?Remove-Mailbox -Identity contoso\john -Permanent $trueOr something else?
Thanks!
Fernando

I did help on the setup in Exchange server folder. Looks like prepares Active Directory forest for Exchange Install. /PrepareAD, /p So this is what I'm supposed to run?
C:\Program Files\Microsoft\Exchange Server\V15\Bin>setup /?
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
For detailed help, type one of the following options:
Setup /help:Install - Install Exchange server roles.
Setup /help:Upgrade - Upgrade an existing Exchange server.
Setup /help:Uninstall - Uninstall Exchange server roles.
Setup /help:RecoverServer - Recover an existing Exchange server.
Setup /help:PrepareTopology - Prepare your topology for Exchange.
Setup /help:Delegation - Delegate server installations.
Setup /help:UmLanguagePacks - Add or remove Unified Messaging
language packs.
C:\Program Files\Microsoft\Exchange Server\V15\Bin>Setup /help:PrepareTopology
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Microsoft Exchange Server 2013 Setup Parameter Help
Prepare Topology Usage:
Setup /PrepareAD [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareSchema [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareDomain [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareDomain:<domainA, domainB> [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareAllDomains [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
--Prepare Topology Required Parameters--
/PrepareAD, /p
Prepares the Active Directory forest for the Exchange
installation.
Fernando

Exchange 2013 archiving

Hello,
i have a problem with exchange 2013 in-place archiving.
Archive mailbox is in different database that mailbox database.
Yesterdey i have activated archiving for a first mailbox; when i activated archive many "Not read" message were sent.
Seem that when archive is active message sent to user that have request of read but that have not answer like "read" for the user when they are stored in archive mailbox send out reply to sender with "Not read: " in the subject.
I have checked "retention policy" and "retention tags" properties via exchange management shell but i did not find any field to disable unread in archive or something like.
Please can i have support for this problem?
Thanks in advance.

Hi,
Before going further, I’d like to confirm how many senders are affected by the issue.
Please check if there is any Outlook rule about the unread message notification.
And we can also check if the sender select the option “always send read receipt”:
File>options>mail>tracking
Best regards,
Angela Shi
TechNet Community Support

Exchange 2013 SP1 mailbox role on 2012 R2 and 2012

Hi,
We have a client who were running the following setup:
2 x Exchange 2013 CU2 CAS servers / Win Srv 2012
2 x Exchange 2013 CU2 MBX servers / Win Srv 2012
Active Directory etc, basically everything else, runs on Win Server 2012.
Due to upgrading etc, one of the mailbox servers has been removed. It is to be installed with Ex2013 SP1 with 2012 R2 from scratch, and eventually also upgrade the remaining CAS and MBX srvers with SP1 and 2012 R2.
So my question is..will this present a problem? Is it possible to have one MBX running 2013 CU2 on Server 2012 and one MBX running 2013 SP1 on Server 2012 R2?
I've read that failover clustering service is not possible between 2012 and 2012 R2, but i'm not sure how this effects Exchange.
Thanks for your time.

Hi,
Each member of the DAG should be running the same operating system. It is not supported to run a DAG member on Windows Server 2012 R2 and run another member on Windows Server 2012.
What's more, upgrading the OS is not supported on Exchange server.
Here are some helpful threads for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
Exchange 2013 CU2 and Upgrading from Server 2012 to Server 2012 R2 issues
http://social.technet.microsoft.com/Forums/exchange/en-US/afba40de-efb6-4916-ae42-b09cff35e5d7/exchange-2013-cu2-and-upgrading-from-server-2012-to-server-2012-r2-issues
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 linked mailbox

I am administering Exchange 2013 in organization where we have two separate forests witch two separate Exchange 2013 servers. There is AD trust between forests. Each user has two mailboxes connected in Outlook, one from forest A and one from forest B. Let's
say [email protected] and [email protected] There is a plan that users from forest A will use and have only one mailbox connected in Outlook and get all emails data on Exchange server within forest A. What is a best approach
to do it smoothly? We do not want to remove the email addresses from forest B because a lot of people outside the company know only this email address as a contact point.
I am thinking about creating linked mailboxes. Any other ideas or advice's?

Hi ,
just remove the email address (i.e
[email protected])
from the mailbox in forest B and add it as an secondary smtp address on the mailbox residing on the mailbox in forest A.
In case if you don want the mailbox for user 1 in forest B you can simply delete it instead of removing the email address.
Note : Simply you cannot remove the email address (i.e
[email protected])
from the Mailbox of the user 1 in forest B is set as primary smtp address. So on such case just make some dummy email address as primary smtp address and simply remove
the address [email protected]
and add as an secondary smtp address on user 1 mailbox in forest A .
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Exchange 2013 Monitoring Mailboxes

I'm running exchange 2013 and it seems to have problems with health mailboxes (monitoring mailboxes). I have 5 mailbox databases on this server, DB1, DB2, DB3, DB4 and DB5.
I know there are 2 health mailboxes per mailbox database.
The command `Get-Mailbox -monitoring | Get-MailBoxStatistics` shows that several of these have not been accessed since December, even though they are in mounted Databases and powershell shows they are healthy.
There is also 2 health mailboxes that are missing from the below output because I got warninings saying these mailboxes have not been logged into yet.
[PS] C:\windows\system32> Get-Mailbox -monitoring | Get-MailBoxStatistics
DisplayName : HealthMailbox98fb2dc7692341ad8a3325ea2b14bbcc
ItemCount : 17426
LastLogonTime : 12/8/2012 3:28:04 PM
Database : DB1
DisplayName : HealthMailboxe27d88df28ae4d53af620604a83aca4d
ItemCount : 12386
LastLogonTime : 2/4/2013 3:29:46 PM
Database : DB1
DisplayName : HealthMailbox815f0ff077a342f7889a53ef38e40256
ItemCount : 291
LastLogonTime : 12/8/2012 3:26:43 PM
Database : DB3
DisplayName : HealthMailboxbca2f3409f1d4ae99098f48b574fc36d
ItemCount : 579
LastLogonTime : 12/8/2012 3:26:05 PM
Database : DB2
DisplayName : HealthMailbox2412e1a0e5d9415b8328f653b2e42efe
ItemCount : 209
LastLogonTime : 2/3/2013 6:08:41 PM
Database : DB3
DisplayName : HealthMailbox594b739a129941e688eafee6bbdfece6
ItemCount : 209
LastLogonTime : 2/3/2013 6:09:52 PM
Database : DB2
DisplayName : HealthMailboxc401cae2a70d4d659f5758908582406e
ItemCount : 210
LastLogonTime : 2/4/2013 3:28:59 PM
Database : DB4
DisplayName : HealthMailbox4b81211d555c4accad1f61a98700382e
ItemCount : 212
LastLogonTime : 2/3/2013 6:09:46 PM
Database : DB5
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox2c62876ca1bb45849c0daf2ecee6d715`, so there is no data to return. After the user logs on, this warning will no longer appear.
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox4399c592609a464d95c993ecee46f671`, so there is no data to return. After the user logs on, this warning will no longer appear.
I am also getting a lot of queued messages in the inboundproxy.com queue that have the subject line "Undelieverable: Inbound Proxy Probe". I dont know how to get these to stop. I just have to clean out the queue once a day to prevent it from getting
to large.
The last thing I notice is that I get a lot of audit errors in the event log when the system is trying to login to these mailboxes. That might be what is causing the issue. Here is one of the messages:
An account failed to log on.
Subject:
Security ID:
SYSTEM
Account Name:
<computer name here>$
Account Domain:
<AD DOMAIN>
Logon ID:
0x3E7
Logon Type: 8
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
HealthMailboxbca2f3409f1d4ae99098f48b574fc36d@<domain.tld>
Account Domain:
Failure Information:
Failure Reason:
Unknown user name or bad password.
Status:
0xC000006D
Sub Status:
0xC0000064
Process Information:
Caller Process ID:
0x1265c
Caller Process Name:
C:\Windows\System32\inetsrv\w3wp.exe
Network Information:
Workstation Name:
<computer name here>
Source Network Address:
::1
Source Port:
34602
Detailed Authentication Information:
Logon Process:
Advapi
Authentication Package:
Negotiate
Transited Services:
Package Name (NTLM only):
Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
As you can see, the system can not login to to this health mailbox account. The one in my example one of the mailboxes that has not been logged into since december.
Is there anywhere to troubleshoot these? or possibly rebuild them? The is a huge lack of documentation on these mailboxes from microsoft, I can not find any commands to interact with these other then 'get-mailbox -monitoring'

Because I KNOW it can lead to problems and do NOT know whether it can ever help me or not.
Here is one example of why I don't want it enabled:
http://social.technet.microsoft.com/Forums/exchange/en-US/7ed96489-92dd-441a-93e0-3d805b807dc3/maildeliveryprobemaildeliveryprobecom-and-inboundproxyinboundproxycom-in-the-logs
In my opinion there's one more strangeness about Managed Availability in Exchange 2013:
http://blogs.technet.com/b/exchange/archive/2012/09/21/lessons-from-the-datacenter-managed-availability.aspx
"When something is unhealthy its first action is to attempt to recover that component. Managed Availability provides multi-stage recovery actions – the first attempt might be to restart the application pool, the second attempt might
be to restart service, the third attempt might be to restart the server, and
the final attempt may be to offline the server so that it no longer accepts traffic.
If these attempts fail, managed availability
then escalates the issue to a human through event log notification."
...am I getting it right that Managed Availability is not going to alert an administrator BEFORE restarting/taking the server offline...just AFTER and in case it was unable to fix the issue??????!!!!!

Exchange 2010 users cannot open Exchange 2013 shared mailbox

Title says it all.
We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
Is this just how it is, or is there a way around it?

Hi,
I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 shell mailbox move requests showing up on 2010 hub server

We're in the process of migrating from exchange 2010 to 2013. All servers are patched and up to date. We have two 2010 CASs (one for external OWA use only) and a mailbox cluster. Our exchange 2013 setup is almost a mirror with the exceptions of how the exchange
server roles have changed.
Any new-moverequest commands entered from the either of our exchange 2013 CAS servers fail to show up in the EAC/recipients/migration page.
If the local move request is done in the EAC the batch(es) show up just fine.
The more perplexing part is: while I was going through a 2010 hub (looking for a different issue) I noticed ALL the batches/mailbox moves that weren't showing up in the 2013 EAC were listed in the 2010 move request section.
I can't get any info on the moves in the 2010 console (because they're 2013 jobs) but i can get statistics and such from a 2013 shell.
any ideas?

Are you running ex2013SP1 CU6? Can you try to update n check?
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

Hi,
I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
Thank you!

Hi,
It is possible to open a shared mailboxes on a legacy server.
Your problem could be caused by:
Not having one of the later CU installed (read CU4 or CU5)
Incorrect authentication methods configured (see link below)
Outlook is not at the latest patch level
Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139
Martina Miskovic

Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
problems or the Exchange server is down for maintenance".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 - Shared Mailbox Permissions

Here is what I am trying to do. I would like to create a shared mailbox in exchange 2013 for time off requests for my employees. I will have the mailbox to be something like
[email protected] If an employee is sick or requesting time off, they can email this shared mailbox or send a meeting request.
I would then like the ability for ALL employees to be able to have read access to the mailbox and Calendar associated with it, and I would like to have managers have Full access to it and to be able to approve calendar requests so that they are entered into
the calendar.
Is this possible? How can I set read only to the inbox and calendar for a shared mailbox? I would also like to be able to have the shared mailboxes automatically added to all user's Outlook.
Thanks!

Simply grant Full Access to the managers. Then for everyone else you can grant read only access to just the Calendar.
Here is an example on how to do this -
http://exchangeshare.wordpress.com/2009/07/07/how-to-setup-read-only-mailbox-in-exchange-20032007/.
Let me know if that works.
JAUCG - Please remeber to mark replies as helpful if they were or as answered if I provided a solution.

Migrating Exchange 2013 public mailboxes to a new server

We have a client that is leaving their current Hosting company and wants to move to our hosting facility. We have recreated their DC,an Exchange Hub, and Exchange Store. We have exported and imported all of their recipient mailboxes and flipped the switch
and all mail flow is now going through our hosting facility. The problem lies in that I can not figure out how to move the public mailboxes out of the old exchange server and import it into the new server. Both are Exchange 2013 and running on windows server
2012. Any help would be greatly appreciated.

You're looking at a third-party product. MigrationWiz does public folders. There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013: Correcting mailbox delegation - Full Access

Not sure how to correct this issue. I have an Admin that setup the Exchange 2013. The admins account is now added to every new account (Resources, shared mailboxes etc.) I know how to remove the auto mapping so it does not show in the admin
OWA and outlook.
I would like to just correct the setting so the account is not automatically added. (Tester is not the real name of the account.)

Hi Friday77,
Check the AdminAuditLogs to see by who and when it is getting added.
View the administrator audit log
Search the role group changes or administrator audit logs
Search-AdminAuditLog -StartDate 05/04/2015 -EndDate 10/04/2015 -ObjectID contoso.com/Users/NewUSerName1
Search-AdminAuditLog -Cmdlets Add-MailboxPermission -Parameters AccessRights -StartDate 05/04/2015 -EndDate 10/04/2015
Normally this wouldn't be the case, however you might want to have a look at this as well.
Get-CmdletExtensionAgent "Mailbox Permissions Agent"
Cmdlet extension agents are components in Microsoft Exchange Server 2013 invoked by Exchange 2013 cmdlets when the cmdlets run.
Agents can modify, replace, or extend functionality of Exchange Management Shell cmdlets. An agent can provide a value for a required parameter that isn't provided on a command, override a value provided by a user, perform other actions outside of the cmdlet
workflow while a cmdlet runs, and more.
You can use the Scripting agent cmdlet extension agent in Exchange 2013 to insert your own scripting logic into the execution of Exchange cmdlets. Using the
Scripting agent, you can add conditions, override values, and set up reporting.
Every Exchange 2013 server includes the file ScriptingAgentConfig.xml.sample in the <installation path>\V15\Bin\CmdletExtensionAgents folder. This file must be renamed to ScriptingAgentConfig.xml on every Exchange 2013 server if you enable
the Scripting Agent cmdlet extension agent.
If its still .xml.sample, no need to worry about it.
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 - Disabled Mailbox not showing up immediately in the Connect a Mailbox

I have disable a mailbox over an hour ago but it doesn’t show in the
connect a mailbox section in the ECP Exchange 2013. immediately. The reason why I disable the email as I want to attach it to a new AD user which I have created.
I know you have to wait for replication so it appears in the connect a mailbox but I’m not sure how long and we forced an AD replication to see if that works.
I know with Exchange 2010, to get the disconnected mailbox to show immediately, I used to write a command Clean-MailboxDatabase “DB” to get it to appear in the disconnected mailbox but that doesn’t work with Exchange 2013 anymore.
Anyone have any suggestions?

I'm having a same problem.
I did disable-mailbox to one mailbox over 24 hours ago. The mailbox is lost. Maintenance schedule was last night, but there is no change when i list disconnected mailboxes at the database.
In this environment a new user account is created everytime the cost center of the employee is changed. So i need to do disable mailboxes every day. This is not a first time when the mailboxes have been lost. Many times the mailboxes are seen
at the database straight after the disable-mailboxes are done. Some mailboxes are seen at the database after the maintenance schedule. But every now and then, the mailboxes are lost. Because the nature of this environment, this is getting really annoying.
I should not use restore of the backup for this...
Right now i'm looking mailbos statistics of the mailbox that got lost (i have started to take statistics to see if the mailbox is empty or not). The mailbox had 864 items and total item size was 33.18 MB.
If the maintenance schedule is not cabable to update the status of the mailbox, then there is no use of using update-storemailboxstate? At least for me this command is doing nothing when i am having this problem.

Exchange 2013 Archive mailbox best practise

Similar Messages

Maybe you are looking for