Quick Info: Placement of Servers in Microsoft IT Exchange Server 2010 Environment

July 19th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

If you have been through the Architecture and Design document published by Microsoft IT you would get some quick information on placements on Exchange Servers at Microsoft spread across for 4 datacenters…..

Server role

Redmond

Dublin

Singapore

Sao Paulo

Technology

Mailbox

41

16

16

4

Exchange DAGs
Hub Transport

11

5

4

0

Automatic load balancing through Mail Submission Service
Hardware load balancers for incoming mail connectivity
Client Access

28

14

12

0

Hardware load balancers internally and externally
Unified Messaging

5

3

3

0

Automatic round-robin load balancing between Unified Messaging servers
Multiple voice over IP (VoIP) gateways per dial plan
Multiple-Role

0

0

0

2

Not applicable

And a quick look at the DAG Configurations….

DAG model Location Number of actual mailboxes Number of supported mailboxes Storage architecture Disk type
11 node Redmond

29,913

33,000

JBOD

3.5” 1-terabyte SAS
11 node Redmond

28,861

33,000

JBOD

3.5” 1-terabyte SAS
10 node Redmond

26,171

30,000

JBOD

3.5” 1-terabyte SAS
16 node Dublin

33,260

48,000

JBOD

3.5” 1-terabyte SAS
16 node Singapore

37,698

48,000

JBOD

3.5” 1-terabyte SAS
4 node Sao Paulo

2,299

12,000

JBOD

3.5” 1-terabyte SAS

This is a good document to refer if you are designing Enterprise Messaging environments of similar sizes. Download it here http://www.microsoft.com/downloads/details.aspx?FamilyID=accec9cd-9c09-4f7e-91c6-41f0e201b680&displayLang=en

AddThis Social Bookmark Button

Microsoft IT: Exchange Server 2010 Design and Architecture

July 19th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

Brief Description

By replacing Exchange Server 2007 servers with servers running Exchange Server 2010, Microsoft IT created new opportunities to drive down costs and system complexities while at the same time increasing security and deploying new features not available in previous versions of Exchange Server.

Quick Details

File Name: 0941_ExchangeServer2010ArchitectureTWP.docx
Version: 07/2010
Date Published: 7/12/2010
Language: English
Download Size: 8.2 MB

Download here http://www.microsoft.com/downloads/details.aspx?FamilyID=accec9cd-9c09-4f7e-91c6-41f0e201b680&displayLang=en

AddThis Social Bookmark Button

Exchange 2007 SP3 Password Reset Tool

June 21st, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

Though we can change passwords using OWA, but what happens if your password is expired or it is the case of first logon password change, in such cases OWA was never the tool to use. Unlike previous versions IISADMPWD Web application is not available in Windows Server 2008, resulting in that not being an option for administrators…

With Exchange Server 2007 SP3 there is a new IIS 7 Module in Client Access server (CAS) that that detects expired passwords and redirects users to a new change password page.

Now that this feature is disabled by default, to avail this Password Reset feature administrators need to enable this…..To enable the password reset feature

  1. Log on Client Access Server | Registry Editor
  2. Go to HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA
  3. Create the following DWORD value if it does not already exist:
    Value name: ChangeExpiredPasswordEnabled
    Value type: REG_DWORD
    Value data: 1

You are all set !

 

AddThis Social Bookmark Button

Exchange Server 2007 SP3 supports Windows Server 2008 R2

June 21st, 2010 Nitin Gupta Posted in Exchange, Geekism, General 1 Comment »

Exchange-2010-Logo-733341Microsoft has already made Exchange Server 2007 SP3 available for download and with that comes a wonderful news….. Yes, it supports Windows Server 2008 R2 also…..

Exchange Server 2007 SP3 supports all Exchange 2007 roles on the Windows Server 2008 R2 operating system. Exchange 2007 SP3 provides imagesupport only for a new installation of Exchange on Windows Server 2008 R2. Exchange 2007 SP3 is not supported in an upgrade scenario on Windows Server 2008 R2.

Exchange 2007 SP3 does not support the following installation scenarios:

  • A new Exchange 2007 SP3 installation on a Windows Server 2008 R2-based computer that has been upgraded from Windows Server 2008
  • Upgrading Exchange 2007 SP2 to Exchange 2007 SP3 on a Windows Server 2008 R2-based computer that has been upgraded from Windows Server 2008
  • Upgrading the operating system from Windows Server 2008 to Windows Server 2008 R2 on a computer that has Exchange 2007 SP3 installed

To see how to install Exchange 2007 SP3 on Windows Server 2008, refer http://technet.microsoft.com/en-us/library/bb691354(EXCHG.80).aspx

AddThis Social Bookmark Button

Exchange Server 2007 Service Pack (SP) 3 – Available for Download

June 21st, 2010 Nitin Gupta Posted in Exchange, Geekism, General 1 Comment »

Folks, the Exchange 2007 SP3 bits have been released by Microsoft……

Overview:

Microsoft Exchange Server 2007 Service Pack 3 (SP3) has been designed specifically to meet the challenges facing our customers and to help address the needs of all the different businesses and organizations utilizing our Exchange Server 2007 enterprise messaging system.

Exchange Server 2007 SP3 is a mission-critical communications tool that enables employees to be more productive and access their information anywhere and anytime while providing a messaging system that enables rich, efficient access to e-mail, calendar items, voice mail, and contacts.

For administrators, Exchange Server 2007 SP3 provides further flexibility with the addition of Windows Server 2008 R2 support for server roles and Windows 7 support for the Exchange management tools. These additions, along with enhancements for the advanced protection options against e-mail security threats, such as spam and viruses and the tools which help manage internal compliance and high availability needs provide Exchange administrators with the tools they need to manage their Exchange 2007 environments efficiently.

Note: Clean installations of Exchange 2007 SP3 on a new server are possible by using this download in the same manner as you would install Exchange 2007 RTM, Exchange 2007 SP1 or Exchange 2007 SP2.

Quick Details

Version: 8.03.0083.006
Date Published: 6/20/2010
Language: English
Download Size: 878.9 MB - 1773.2 MB*
Download Here: http://www.microsoft.com/downloads/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en
Files:  E2K7SP3EN32.exe &  E2K7SP3EN64.exe

Please review:

So, go ahead and install Exchange 2007 SP3 !!!

Technorati Tags: ,,

 

AddThis Social Bookmark Button

Exchange 2010 SP1: Add/Modify Mailbox Folder Permissions (Add-MailboxFolderPermission and Set-MailboxFolderPermission)

June 21st, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

In Exchange 2010 RTM,  a new cmdlet “Add-MailboxFolderPermission” was added that enabled Administrators (with necessary permissions) to delegate folder-level permissions for all folders within a user’s mailbox. The limitation of this cmdlet was that, once a user was given permission to a mailbox folder, then you could not change the permissions, you had to remove the user permission using “Remove-MailboxFolderPermission” and then re-assign the permissions.

With Exchange 2010 SP1 (beta), we now have a new cmdlet “Set-MailboxFolderPermission”, that helps in editing an existing permission entry. To be able to use Set-MailboxFolderPermission cmdlet on a mailbox for assigning permissions to a user, an entry should already be present. So this means, before running Set-MailboxFolderPermission on a mailbox, we need to set permissions for a user with Add-MailboxFolderPermission first.

Let me explain this with an example.

Let us first look at the Add-MailboxFolderPermission cmdlet…In my example I will give permissions to user “Quest-User99” the “Reviewer” permissions on Inbox folder of the mailbox “Nitin Gupta”.

Add-MailboxFolderPermission -Identity ngupta@quest-demo.com:\Inbox -User quest-user99@quest-demo.com -AccessRights ReadItems

Set-MailboxFolderPermission Mailbox Folder Permissions

Once this is done, we will use the Get-MailboxFolderPermission cmdlet to check the permissions….

Get-MailboxFolderPermission -Identity ngupta@quest-demo.com:\Inbox

Set-MailboxFolderPermission Mailbox Folder Permissions

So far so good, now let us try to use Add-MailboxFolderPermission cmdlet to change the permissions of ‘”Quest-User99” on the mailbox “Nitin Gupta”  to FolderVisible….

Add-MailboxFolderPermission -Identity ngupta@quest-demo.com:\Inbox -User quest-user99@quest-demo.com -AccessRights FolderVisible

So what happens, as mentioned in the beginning we encounter an error….

An existing permission entry was found for user: Quest-User99.
    + CategoryInfo          : NotSpecified: (0:Int32) [Add-MailboxFolderPermission], UserAlreadyExis…nEntryException
    + FullyQualifiedErrorId : CACE8CC4,Microsoft.Exchange.Management.StoreTasks.AddMailboxFolderPermission

Set-MailboxFolderPermission Mailbox Folder Permissions

This means that Add-MailboxFolderPermission cannot be used to modify an existing permission, so what was the workaround till Exchange 2010 RTM, remove the permissions and re-assign…

What happens now with Exchange 2010 SP1 (beta)….

With SP1, we now have “Set-MailboxFolderPermission” that we will use to modify the permissions….

Set-MailboxFolderPermission -Identity ngupta@quest-demo.com:\Inbox -User quest-user99@quest-demo.com -AccessRights FolderVisible

Set-MailboxFolderPermission Mailbox Folder Permissions

Set-MailboxFolderPermission Mailbox Folder Permissions

Wonderful, now let us look at the option where there is no permission entry for a user on a mailbox. To see, let us remove the permissions of “Quest-user99”” from the Inbox folder on mailbox “Nitin Gupta”

Remove-MailboxFolderPermission -Identity ngupta@quest-demo.com:\Inbox -User quest-user99@quest-demo.com

Set-MailboxFolderPermission Mailbox Folder Permissions

Set-MailboxFolderPermission Mailbox Folder Permissions

So now “Quest-User99” does not have any permission on mailbox “Nitin Gupta”. Let us run the cmdlet, Set-MailboxFolderPermission

[PS] C:\>Set-MailboxFolderPermission -Identity ngupta@quest-demo.com:\Inbox -User quest-user99@quest-demo.com -AccessRights Owner

There is no existing permission entry found for user: Quest-User99.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-MailboxFolderPermission], UserNotFoundInPermissionEntryException
    + FullyQualifiedErrorId : 4A3CC18C,Microsoft.Exchange.Management.StoreTasks.SetMailboxFolderPermission

Set-MailboxFolderPermission Mailbox Folder Permissions

This shows that a permission entry is required, before we can use Set-MailboxFolderPermission to edit/modify the permissions

 

The List of Permissions that can be set using the AccessRights parameter are as follows [Source: http://technet.microsoft.com/en-us/library/dd298062(EXCHG.140).aspx]

  • ReadItems   The user has the right to read items within the specified folder.
  • CreateItems   The user has the right to create items within the specified folder.
  • EditOwnedItems   The user has the right to edit the items that the user owns in the specified folder.
  • DeleteOwnedItems   The user has the right to delete items that the user owns in the specified folder.
  • EditAllItems   The user has the right to edit all items in the specified folder.
  • DeleteAllItems   The user has the right to delete all items in the specified folder.
  • CreateSubfolders   The user has the right to create subfolders in the specified folder.
  • FolderOwner   The user is the owner of the specified folder. The user has the right to view and move the folder and create subfolders. The user can’t read items, edit items, delete items, or create items.
  • FolderContact   The user is the contact for the specified public folder.
  • FolderVisible   The user can view the specified folder, but can’t read or edit items within the specified public folder.

The AccessRights parameter also specifies the permissions for the user with the following combination:

  • None   FolderVisible
  • Owner   CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
  • PublishingEditor   CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
  • Editor   CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
  • PublishingAuthor   CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
  • Author   CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
  • NonEditingAuthor   CreateItems, ReadItems, FolderVisible
  • Reviewer   ReadItems, FolderVisible
  • Contributor   CreateItems, FolderVisible

The following roles apply specifically to calendar folders:

  • AvailabilityOnly   View only availability data
  • LimitedDetails   View availability data with subject and location

 

AddThis Social Bookmark Button

Exchange 2010 – Set Default Language in Outlook Web App (OWA)

June 20th, 2010 Nitin Gupta Posted in Exchange, Geekism, General 2 Comments »

When a new user logs into Outlook Web App, he/she is prompted to choose the Language and Time Zone.

OWA - Language

 

The default value for Language setting is 0, i.e. not defined resulting in users being prompted to choose a language the first time that they sign in to Outlook Web AppAdministrators can specify the default language, so that the users are not prompted to select Language as shown above. The Default language for OWA can be set using the following command.  

Set-OWAVirtualDirectory “owa (Default Web Site)” -DefaultClientLanguage <Language code>

OWA - Default Language

In this example I have changed the default client language to Catalan, this causes the default folders names to be renamed based on the specified language i.e. Catalan.

OWA - Default Language

Note:

  • Once the default client language is specified when the users try to login for the first time (ever) in OWA, they are not prompted to choose a language and OWA Time Zone is picked up from the time zone of Client Access Server.
  • In OWA then The Users can use Regional Settings in Outlook Web App to change Client language and time zone after they sign in.
  • The change does not affect users who had already logged in once, before the default Language is specified
  • List of Language Codes can be found here: http://technet.microsoft.com/en-us/library/aa997435.aspx

A Weird Issue:

Now that I belong to India, I tried to set Default Language to Hindi and bum, I was in for a surprise, I encountered an error

[PS] C:\>Set-OwaVirtualDirectory “owa (Default Web Site)” -DefaultClientLanguage 1081
Invoke-Command : Cannot bind parameter ‘DefaultClientLanguage’ to the target. Exception setting “DefaultClientLanguage”
: “DefaultClientLanguage contains the value “1081″ which is not a supported LCID value.”

At C:\Users\Administrator\AppData\Roaming\Microsoft\Exchange\RemotePowerShell\w2k8r2-dc-msx.quest-demo.com\w2k8r2-dc-ms
x.quest-demo.com.psm1:54539 char:29
+$scriptCmd = { & <<<<  $script:InvokeCommand `
    + CategoryInfo          : WriteError: (:) [Set-OwaVirtualDirectory], ParameterBindingException
    + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirt
   ualDirectory

Well, I can set the same at the initial login screen though…

OWA Hindi

Well I have raised this with the product team ! I have not checked to see what all Languages give this error.

 

AddThis Social Bookmark Button

Exchange Server – Documentation (Topic Status)

June 20th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

Over a period of time, I have seen lot of people asking questions on errors in Exchange documentation. It is imperative that one be aware of STATUS of the topic, before pointing it out to the Product Team & Technical Writers. Though Microsoft makes the documentation available, there is a clear status on every topic on the accuracy and progress.

Every Topic starts with the status

Exchange Documentation Topic Status

The list of all Topic Status is as follows…..

Value

Description

Writing Not Started The topic is present in the table of contents, but it contains either no content or incomplete content. Incomplete content could include legacy Exchange documentation.
Writing Content is being written or updated.
Ready for Tech Review Content is ready to be reviewed by subject matter experts.
In Tech Review Content has been submitted for review.
Revising Per Tech Review Review comments are being analyzed and incorporated by the writer.
Editing Content is being edited for syntax, structure, and technical accuracy.
Revising Per Edit Edits are being analyzed and incorporated by the writer.
Back to Editor Content has been revised per edits and is being analyzed and incorporated by editor.
Ready for Copy Edit Content is ready for copy edit.
Revising Per Copy Edits Copy edits are being analyzed and incorporated by the editor.
Milestone Ready Content has been reviewed for technical accuracy and edited.
Content Complete Content is complete

Same applies to Exchange 2010 SP1 documentation that has been made available, most of it is not Content Complete.

Technorati Tags: ,

 

AddThis Social Bookmark Button

OT - Active Directory Migration Tool (ADMT) version 3.2

June 20th, 2010 Nitin Gupta Posted in Geekism, General No Comments »

Ok, ADMT 3.2 is finally out. The Active Directory Migration Tool version 3.2 (ADMT v3.2) provides an integrated toolset to facilitate migration and restructuring tasks in an Active Directory Domain Services infrastructure.

The Active Directory Migration Tool version 3.2 (ADMT v3.2) simplifies the process of migrating objects and restructuring tasks in an Active Directory® Domain Service (AD DS) environment. You can use ADMT v3.2 to migrate users, groups, service accounts, and computers between AD DS domains in different forests (inter-forest migration) or between AD DS domains in the same forest (intra-forest migration). ADMT can also perform security translation (to migrate local user profiles) when performing inter-forest migrations.

File Name: admtsetup32.exe
Version: 3.2
Date Published: 6/18/2010
Language: English
Download Size: 4.1 MB
 

 System Requirements

  •  
  • Supported Operating Systems: Windows Server 2008 R2
  • ADMT can be installed on any computer capable of running the Windows Server 2008 R2 operating system, unless they are Read-Only domain controllers or in a Server Core configuration.
  • Target domain: The target domain must be running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
  • Source domain: The source domain must be running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
  • The ADMT agent, installed by ADMT on computers in the source domains, can operate on computers running Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

Download Here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=20c0db45-db16-4d10-99f2-539b7277ccdb

Technorati Tags:

 

AddThis Social Bookmark Button

Update Rollup 4 for Exchange Server 2010 (KB982639)

June 18th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

Update Rollup 4 for Exchange Server 2010 has been released and resolves issues that were found in Exchange Server 2010 since the software was released.

Note: This update rollup is highly recommended for all Exchange Server 2010 customers.

File Name: Exchange2010-KB982639-x64-en.msp
Version: 14.0.702.1
Knowledge Base (KB) Articles: KB982639 
Date Published: 6/17/2010
Language: English
Download Size: 34.2 MB

Issues that the update rollup fixes

Prerequisites

The following list contains prerequisites for the Update Rollup 4 for Exchange Server 2010 RTM:

  • Install Exchange Server 2010 RTM on the computer before you apply this update rollup.
  • Remove all interim updates for Exchange Server 2010 before you apply this update rollup.

Restart requirement

The required services are automatically stopped and then restarted when you apply this update rollup.

Removal information

To remove Update Rollup 4 for Exchange Server 2010 RTM, use Add or Remove Programs in Control Panel. Then, remove update 982639.

AddThis Social Bookmark Button

Microsoft Exchange Server Jetstress 2010 (64 bit) - Tool

June 17th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

Brief Description

Simulate disk I/O load on a test server running Exchange to verify the performance and stability of your disk subsystem before putting your server into a production environment.

Overview

Use Jetstress 2010 to verify the performance and stability of a disk subsystem prior to putting a Microsoft Exchange Server 2003, 2007 and 2010 server into production. Jetstress helps verify disk performance by simulating Exchange disk Input/Output (I/O) load. Specifically, Jetstress simulates the Exchange database and log file loads produced by a specific number of users. You use Performance Monitor, Event Viewer, and ESEUTIL in conjunction with Jetstress to verify that your disk subsystem meets or exceeds the performance criteria you establish. After a successful completion of the Jetstress Disk Performance and Stress Tests in a non-production environment, you will have ensured that your Exchange disk subsystem is adequately sized (in terms of performance criteria you establish) for the user count and user profiles you have established. It is highly recommended that the Jetstress user read through the tool documentation before using the tool.

System Requirements

  • Supported Operating Systems: Windows 2000 Service Pack 4; Windows Server 2003; Windows Server 2008; Windows Server 2008 R2
  • Microsoft Exchange 2003
  • Microsoft Exchange 2007
  • Microsoft Exchange 2010

File Name: Jetstress.msi
Version: 14.01.0180.003
Date Published: 6/17/2010
Language: English
Download Size: 996 KB

Download Here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=13267027-8120-48ed-931b-29eb0aa52aa6

AddThis Social Bookmark Button

Exchange Load Generator 2010 (64 bit & 32 bit)

June 16th, 2010 Nitin Gupta Posted in Exchange, Geekism, General 1 Comment »

Brief Description:
Exchange Load Generator is a simulation tool to measure the impact of MAPI, OWA, ActiveSync, IMAP, POP and SMTP clients on Exchange servers.

Overview:
Use Microsoft Exchange Load Generator 2010 (LoadGen) as a simulation tool to measure the impact of MAPI, OWA, ActiveSync, IMAP, POP and SMTP clients on Exchange 2010 and 2007 servers. LoadGen allows you to test how a server running Exchange 2010/2007 responds to e-mail loads. To simulate the delivery of these messaging requests, you run LoadGen tests on client computers. These tests send multiple messaging requests to the Exchange server, thereby causing a mail load. LoadGen is a useful tool for administrators who are sizing servers and validating a deployment plan. Specifically, LoadGen helps you determine if each of your servers can handle the load to which they are intended to carry. Another use for LoadGen is to help validate the overall solution.

These version are intended for Microsoft Exchange 2010 and 2007 Servers only.

Exchange Load Generator 2010 (64 bit)
File Name: Loadgen.msi
Version: 14.01.0180.003
Date Published: 6/15/2010
Download Size: 13.9 MB

Exchange Load Generator 2010 (32 bit)
File Name: Loadgen.msi
Version: 14.01.0180.003
Date Published: 6/15/2010
Download Size: 14.1 MB

Important: LoadGen should be used only in laboratories that have no connection to the production environment. This tool should not be used in any way in a production environment or an environment that is mission critical or contains important information of any kind anywhere in the network.

Note: There are now three OWA modules:

  • OWA2007Module (Exchange 2007),
  • OWA2010Module (Exchange 2010 RTM) and
  • OWAModule (Exchange 2010 SP1 or latest).

Please use the correct version for your environment.

Technorati Tags:
AddThis Social Bookmark Button

How to Import PST files into Personal Archive Mailbox in Exchange 2010 SP1 Beta

June 16th, 2010 Nitin Gupta Posted in Exchange, Geekism, General 7 Comments »

One of the limitations of Exchange 2010 RTM was that there was no administrative way to move historical (PST) data into the online archive. One of the method was to manually drag and drop messages from PST into online archive, but was it practical for enterprise or even medium sized businesses.

With Exchange 2010 SP1 beta things have changed and now we have the functionality out of box to import historical mailbox data from .pst files directly to the user’s personal archive or primary mailbox using the New-MailboxImportRequest cmdlet. This would help the administrators to be able to perform bulk import and export of PST files without using Outlook client.

To be able to import PST file or export to PST files, the administrator must have the appropriate permissions within Exchange. As of today, no RBAC Role Group provides permissions for this functionality. So what do we do….

  • We first need to create a new role group that grants access to the *-MailboxImportRequest and *-MailboxExportRequest cmdlets.

    New-RoleGroup “Mailbox Import-Export Management” -Roles “Mailbox Import Export”

Exchange 2010: Import Mails from PST to Personal Archive

  • Now we need to add the Exchange Administrators who will be allowed to perform these activities to the role group:Add-RoleGroupMember “Mailbox Import-Export Management” -Member <user account>

Exchange 2010: Import Mails from PST to Personal Archive

So, now we are all set, we will my Mailbox “Nitin Gupta” that has 6 mails in the Personal Archive Mailbox….

Exchange 2010: Import Mails from PST to Personal Archive

So here is my PST File that I will be importing into my Personal Archive

Exchange 2010: Import Mails from PST to Personal Archive

So now we will use the New-MailboxImportRequest cmdlet to import the PST into my Personal Archive. To import into an Archvie we need to use the switch -IsArchive

New-MailboxImportRequest -Mailbox “Nitin Gupta” -FilePath \\W2K8R2-DC-MSX\C$\PSTs\NitinGupta_Old.pst -IsArchive

Exchange 2010: Import Mails from PST to Personal Archive 

To see if the Import has completed use the command Get-MailboxImportRequest

Exchange 2010: Import Mails from PST to Personal Archive

Once the Import is completed, you would see the mails in the Personal Archive! There we 6 mails in Archive already and now after coping 15 mails from PST the total is 21 :-) !

Exchange 2010: Import Mails from PST to Personal Archive

Please note that I did not use any Target Folder so it copied all mails to Root, and since my mails were in folder call Inbox it copied them to Inbox of Personal Archive.

In case you want to copy all Old mails from PST maybe in a Folder called “Old Mails” under the root then you need to specify –TargetRootFolder. The TargetRootFolder parameter specifies the top-level mailbox folder that the imported content is placed in. If you don’t specify this parameter, the command imports folders to the top of the folder structure in the target mailbox or archive. If the folder already exists, content is merged under existing folders, and new folders are created if they don’t already exist in the target folder structure.

I would use same PST again to copy mails in Target Root Folder “Old Mails”, we would use

New-MailboxImportRequest -Mailbox “Nitin Gupta” -FilePath \\W2K8R2-DC-MSX\C$\PSTs\NitinGupta_Old.pst –IsArchive –TargetRootFolder “Old Mails”

Exchange 2010: Import Mails from PST to Personal Archive

So what it has done is created a root Folder called Old Mails in my inbox and copied all the 15 mails from PST to that, under a folder called Inbox

Exchange 2010: Import Mails from PST to Personal Archive

Note:

  • The Exchange Trusted Subsystem Security Group should be provided Full Control/Owner permissions on file share where PSTs files are going to be stored.
  • You have to use the UNC path only, if you do not, then you will encounter the following error
    FilePath ‘C:\folder\filename.pst’ is not a valid UNC path.
    + CategoryInfo          : InvalidArgument: (c:\psts\NitinGupta_Old.pst:LongPath) [New-MailboxImportRequest], NonUNCFilePathPermanentException
    + FullyQualifiedErrorId : 5DBAAACE,Microsoft.Exchange.Management.RecipientTasks.NewMailboxImportRequest
  • If the Microsoft Exchange Mailbox Replication service is not running then you will encounter the following error
    There are no available servers running the Microsoft Exchange Mailbox Replication service.
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxImportRequest], NoMRSAvailableTransientException
    + FullyQualifiedErrorId : 2D6A95BC,Microsoft.Exchange.Management.RecipientTasks.NewMailboxImportRequest

So a wonderful feature that will make lives of Administrators easy !!

 

 

AddThis Social Bookmark Button

Mailbox Server Role Storage Requirement Calculator (Latest versions) for Exchange 2010 and Exchange 2007

June 15th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

Microsoft has updated the Mailbox Server Role Requirements Calculator for Exchange 2010 and 2007 once more…. :-) !

Calculator for Exchange 2007 -

Version: 17.5
File Size: 224.1kB
Bug Fixes & Enhancements:

  • Fixed the IOPS calculation formula to take into account the scenario where both the IOPS Multiplication Factor is set to a value above 1 and the Outlook client type is Online Mode.
  • The calculator now correctly evaluates the formatted disk capacity of disks, as opposed to estimating it.

Download here http://msexchangeteam.com/files/12/attachments/entry438481.aspx

Calculator for Exchange 2010 -

Version: 7.7
File Size: 347.9kB
Bug Fixes:

  • Fixed an issue in site resilient designs where the number of HA copies between datacenters was asymmetrical that resulted in a condition where the number of activated copies after a server failure was less than the number of copies during normal runtime.
  • Fixed log and restore LUN disk formatted capacity calculation formulas to accurately calculate formatted capacity as opposed to estimating it.
  • Fixed an issue to prevent a situation where the number of activated database copies per server in the primary datacenter was greater than the total number of copies per server.
  • Improved the calculations for the number of required servers in the secondary datacenter, as well as, the number of lagged copy servers by rounding up, as opposed to simply rounding.
  • Improved the number of active database calculations for 2-member DAGs deployed in a site resilient configuration.
  • Improved the cross-site database failover calculations during double server failure events in the primary datacenter (where a portion of the databases are activated in the secondary datacenter).
  • Fixed the Number of Required Mailbox Processor Cores (Secondary Datacenter) calculation to only consider solutions that have HA copies in the secondary Datacenter.
  • Fixed and improved various comments throughout the calculator.

Enhancements :

  • Added two new columns to the primary datacenter “Active Database Configuration / DAG” table.  These columns now expose the total number of databases activated in each site after server failure events.  This change was added to expose cross-site database failover events.
  • The calculator now includes an option to activation block secondary datacenter mailbox servers that host HA database copies.  This allows you to design a solution where you can activate the secondary datacenter in the event of a primary datacenter failure mode, or choose to activate a copy in the secondary datacenter manually, but prohibits Active Manager from automatically activating a copy in the secondary datacenter.  This may be useful in certain environments where WAN costs are high, or utilization of the WAN is high, and thus you want to control when users access data from the secondary datacenter.  From a server planning perspective, enabling cross-site database failover has the potential to impact the primary datacenter server design (e.g., can increase the design to support double server failure events, which can impact memory and CPU sizing), while disabling cross-site database failover, can potentially increase your outage scenarios, but allows you to control the situation better.
  • Over the years, many requests have come in asking to increase the number of mailbox tiers in the calculator. Well finally we did something about it. In this version, we’ve added a fourth mailbox tier.
  • Added support for 32-cores.
  • Originally, the IOPS Multiplication Factor calculations worked as follows:
    Base IOPS + (Base IOPS * IOPS Multiplication Factor) = New IOPS Profile
    This was often times confusing, especially with regards to third-party applications that had multiplication factors, so we’ve simplified the formula as follows:(Base IOPS * IOPS Multiplication Factor) = New IOPS Profile
    which means that if previously you entered in a value of say .5 as the multiplication factor, you now need to enter into the calculator a value of 1.5.

Download here http://msexchangeteam.com/files/12/attachments/entry453145.aspx

AddThis Social Bookmark Button

Exchange 2010: Features not available in Exchange Management Console (EMC)

June 14th, 2010 Nitin Gupta Posted in Exchange, Geekism, General No Comments »

There has been a lot of work gone into bringing lot of functionality into Exchange Management Console, but there is still a lot than can only be performed from Exchange Management Shell (EMS).

Here is a list of all the features that are managed from EMS, though with SP1 things are changing…..

  • Address rewriting
  • Administrator audit logging
  • Attachment filter agent
  • Client access array
  • Cmdlet extension agents
  • Database availability group network encryption and compression
  • Database availability groups: Datacenter Activation Coordination mode
  • Database availability groups: replication port
  • Delivery agent connectors
  • Edge synchronization (EdgeSync) service settings, configure
  • EdgeSync, forcing or testing
  • Exchange ActiveSync connectivity, test
  • Exchange ActiveSync log, export
  • Exchange Control Panel connectivity, test
  • Exchange Search
  • Global address lists (GALs)
  • IMAP4 connectivity, test
  • Import\export mailbox data
  • Information Rights Management (IRM), configure
  • IP Allow and Block List providers, test
  • IP site link costs, Exchange-specific
  • Message flow, test
  • Messaging records management (MRM) 1.0: Managed folders
  • MRM 2.0: Retention policies
  • Multi-Mailbox Search
  • Offline address book virtual directory, create
  • Outlook client connectivity, test end-to-end
  • Outlook Protection Rules
  • Outlook Web App connectivity, test
  • Outlook Web App virtual directories, create or remove
  • Outlook Web services connectivity, test
  • POP3 connectivity, test
  • PowerShell, test connectivity
  • PowerShell, virtual directories
  • RBAC management role assignment Policies
  • RBAC management role groups
  • RBAC management roles
  • RBAC management role entries
  • RBAC management role assignments
  • RBAC management scopes
  • Recovery database, create
  • Recovery database, extract data
  • Recovery items
  • Routing group connectors
  • Safelist aggregation, force
  • Sender ID, test
  • Service e-mail channel
  • Transport agents
  • Transport latency, calculating
  • Transport pipeline analysis
  • UM connectivity, test
  • UM incoming calls, view active
  • Web services connectivity, test
  • X.400 authoritative domains

In days to come more and more of these will move to EMC or ECP (and are moving like RBAC) !

Source: http://technet.microsoft.com/en-us/library/dd351160.aspx

 

Update: Thanks Amit for the correction Shell ~ Console ;-) !

AddThis Social Bookmark Button