Saturday, March 27, 2010

Home /Exchange 2010 / Exchange 2010 - Large Mailbox Vision

Exchange 2010 - Large Mailbox Vision

Giving your users the ability to store more e-mail has many advantages. Large mailboxes keep e-mail on the Exchange Server instead of allowing it to be scattered in Outlook Data Files (.PST files). That helps reduce the risk of data loss, improve regulatory compliance, and increase productivity among both workers and IT staff. The main barrier to implementing large mailboxes is the perceived cost and complexity of storing large amounts of e-mail data.

Microsoft® Exchange Server 2010 is specifically designed to overcome these barriers. It enables you to give your users larger mailboxes at lower cost without sacrificing performance or reliability. Built-in high availability and disaster recovery, storage system improvements, and self-healing from disk faults let you use large, inexpensive disks in configurations that maximize data redundancy. And, Exchange Server 2010 lets you keep your users online during mailbox moves. With these changes, the benefits of large mailboxes are now within the grasp of all organizations.

image

image

image

You can download the entire document from here.

SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

1 comments:

Gather information early, make every dordle guess purposeful, balance both boards, recognize patterns, and let the clues guide your decisions.

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...