This mailbox exceeded the maximum number of large items that were specified for this request

You receive the following error message when you try to move mailboxes to Office 365

FailureType : TooManyLargeItemsPermanentException
FailureSide : Target
Message : Error: This mailbox exceeded the maximum number of large items that were specified for this request. –> MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)

This issue occurs if the user’s mailbox contains one or more messages that exceed the 35-megabyte (MB) message limit. Article ID: 2584294

Here is the small script that will help you locate messages that are larger than 35 MB from the user’s on-premises mailbox and export the information to a CSV file.

# Provide path of CSV file that has the list of all EmailAddresses and the list title is “EmailAddress”

$IDs = Import-Csv .\EmailAddresses.csv

IF (!(Test-Path .\LargeItemReport.csv) -eq $false) {Remove-Item .\LargeItemReport.csv}

ForEach ($ID in $IDs) {

Get-MailboxFolderStatistics -Identity $ID.EmailAddress -IncludeAnalysis -FolderScope All | `

Where-Object {($_.TopSubjectSize -Match “MB”) -and ([int](($_.TopSubjectSize).SubString(0,5)) -GE 35.00)} | `

Select-Object @{Name=”Identity”;Expression={($_.Identity.Split(“\”))[0]}}, FolderPath, TopSubject, TopSubjectSize | `

Export-Csv -Path .\LargeItemReport.csv -NoTypeInformation -Append


You can also download the script from TechNet Gallery – Click Here

Hope it helps all !!!




Move Arbitration mailbox and delete the default database in Exchange Server 2010

After you install a new Exchange 2010 server for mailbox role, it created a default mailbox database with some database ID as suffix.

The name of the database could be something as “Mailbox Database 1514210160”.

This default database contains Arbitration Mailboxes which are not directly visible through Exchange Management Console. The arbitration mailbox is used to store the original message that’s awaiting approval.

By default, one arbitration mailbox is created for moderated transport during setup. It’s used for all moderated recipients.

The list of Arbitration Mailboxes is:

· Microsoft Exchange Approval Assistant

· Microsoft Exchange

· Discovery Search Mailbox

· Microsoft Exchange Federation Mailbox

In case you want to remove this default mailbox database, you will need to first move the arbitration mailboxes to another database and this has to be done through EMS.

Remove Default Database


I hope the above screenshot is self-explanatory and easy to understand. Please let me know through comments if walkthrough guide is required.

Cheers and more posts to follow Smile

“The type initializer for ‘InstanceContext’ threw an exception.” during the installation of Exchange 2007/2010 server

When you try to install Exchange 2007/2010 on a brand new server or virtual machine running Windows Server 2008 operating systems, it throws the following exception when it tries to check the prerequisites installed.

The type initializer for ‘InstanceContext’ threw an exception.

The type initializer for 'InstanceContext' threw an exception.InstanceContext Exception error screenshot

In normal scenarios, you’ll never find this exception occurring. To resolve the issue, you have to make sure that the hostname of the server does not exceed 15 characters which is default limit for NetBIOS name resolution.

If the hostname of the servers is more than 15 characters, you will have to perform the following steps:

  1. Quit the Exchange setup.
  2. Remove the machine from the domain.
  3. Remove few characters from the hostname of the server
  4. Re-add the server to the domain.
  5. Re-run the setup.

This will resolve the issue and the setup will continue without any error.

Installing ConsoleOne for Windows for configuring and managing eDirectory – Part 1

ConsoleOne is a Java-based administration tool that you can use to flexibly manage Novell and third-party products on a variety of platforms. ConsoleOne runs on SUSE Linux Enterprise, NetWare, Red Hat Linux, Solaris and Windows. It provides a single point of administration for your network resources, including Novell eDirectory objects, schema, partitions, replicas, and NetWare servers. It is similar to Microsoft Management Console (MMC) found in Windows operating system.

For more information about ConsoleOne, please refer to the article on the Novell web site. You’ll also find the download link for ConsoleOne software on the same web site.


Pre-requisites for ConsoleOne:

To install ConsoleOne, you’ll need to have Windows XP/Windows 2003 operating system installed with Novell Client for Windows.

Novell Client™ 4.91 for Windows XP/2000 is workstation software that brings an easy-to-use, secure, and manageable networking environment to Windows XP and Windows 2000 users. It enables you to access NetWare® services from Windows XP or 2000 workstations or servers and tightly integrates either product into your NetWare network.

You can download Novell Client for Windows from the following link:


Novell Client for Windows installation walkthrough:






Once the server is rebooted, the logon screen will change.




Proceed with installation of ConsoleOne in the following article:

Installing ConsoleOne for Windows for configuring and managing eDirectory – Part 2

Installing ConsoleOne for Windows for configuring and managing eDirectory – Part 2

Installing ConsoleOne for Windows is also pretty straightforward.

You can download ConsoleOne client for the following link: ConsoleOne 1.3.6h

Follow the steps below to install ConsoleOne.











Installation Complete !!!

Go back to Installing ConsoleOne for Windows for configuring and managing eDirectory – Part 1

Installing Novell eDirectory 8.8 on a Windows Server – Walkthrough

You can install eDirectory 8.8 for Windows without the Novell Client.

Refer to the following Link for more information related to System Requirements, Prerequisites etc. :

Installing Novell eDirectory on Windows


Following is the easy walkthrough on the installation process of eDirectory

At the Windows server, log in as Administrator or as a user with administrative privileges.

If you have Autorun turned off, run setup.exe from the nt folder (32-bit eDirectory) and windows folder (64-bit eDirectory) in the Novell eDirectory 8.8 SP6 CD or from the downloaded file.



The installation program checks for the following components before it installs eDirectory. If a component is missing or is an incorrect version, the installation program automatically launches an installation for that component

NICI 2.7

You might have to reboot the server after the NICI installation.


The eDirectory installation will continue after the reboot.




Specify or confirm the installation path, then click Next


Specify or confirm the DIB path, then click Next.


In eDirectory installation type, Create a New eDirectory Tree


Specify a Tree name, Server object context, and Admin name and password for the new tree.

To install a Windows server into an eDirectory tree that has containers with dots in the names (for example, or C=u.s.a). Using containers with dotted names requires that those dots be escaped with the backslash character. To escape a dot, simply put a backslash in front of any dot in a container name.


In the HTTP Server Port Configuration page, specify the ports to use for the eDirectory administrative HTTP server, then click Next.


In the LDAP Configuration page, specify which LDAP ports to use, then click Next.


Perform the following and click Next.

  1. Select the NMAS™ login methods you want to install.

  2. Specify whether to configure the SecretStore module. By default, the SecretStore option is selected.




Once the installation is complete, setup will close the installation file.


It will be a good idea to restart the computer once after the installation is complete

Once the computer is restarted, go to Control Panel, the Novell eDirectory Services icon should be visible.


Clone Windows Server 2003 image using System Preparation (SYSPREP) tool – Walkthrough Steps

During Windows installation, the computer is assigned a name and a unique computer SID. If a system is cloned after this step the cloned machines will all have identical computer SIDs. You have the option of changing the SID using the NewSID tool, but it is not supported by Microsoft.

The System Preparation tool
The System Preparation tool enables administrators to prepare Windows Server 2003 system images as part of an automated deployment (normally in Virtual environment).

Using SysPrep tool, you can change security identifiers (SIDs), other system settings, and other configuration settings to make them unique. This method is faster and full proof way of changing the security identifiers (SIDs) of the new image.

SysPrep is found in the file in the \Support\Tools folder on your Windows product CD

Walkthrough Step to use the SysPrep tool:

Step # 1

  • Install fresh copy of the operating system in your virtual environment. (Note: Keep the Administrator password blank)
  • Install necessary components like Service Pack, Windows Updates, .Net Framework etc.
  • Install integration components (VMware or Virtual PC) which software you are using.
  • Make sure you have installed everything after which you can move forward to clone the image.
  • Restart the computer once to make sure that the installed updates have taken effect.


Step # 2

Login to the operating system using the Administrator account (Remember, the password is blank)

Map the ISO image of the Windows operating system to the image.

Create two folders in the C: drive of the operating system.

  • C:\Deploy
  • C:\SysPrep

Browse the \Support\Tools folder on your Windows product CD, and extract all file in the to C:\Deploy folder


Copy sysprep.exe and setupcl.exe file from C:\Deploy folder to C:\SysPrep folder


Run setupmgr.exe file in C:\Deploy folder to create configuration and answer file (sysprep.inf) to automate the installation of Windows.






Answer the set of configuration answers as per your requirement and click Next


In the Computer Name section, select Automatically generate computer name

In the Administrator Password section, keep the password field blank.


In the Identification String section enter any string which will help you determine which Sysprep image has been installed and click Finish.


Setup Manager will prompt you the location where the sysprep.inf file will be saved. Click OK and then click Cancel to exit Setup Manager


Confirm that the sysprep.inf file is automatically saved in the C:\Deploy folder and C:\SysPrep folder.

The i386 folder will also be automatically created in C:\SysPrep folder


Run the sysprep.exe file in C:\SysPrep folder. The following message suggesting that Sysprep tool will change the computer security setting will be displayed. Click OK.


The System Preparation Tool 2.0 dialog box will open. Click on Reseal button.


Click Ok for the prompted dialog box


A dialog box saying “Sysprep is working” will appear and once the activity is complete, the system will shut down.



Step # 3

Copy the virtual hard disk (.vhd/.vmdk as the case may be) to another location for future use.

To confirm that the Sysprep image has been properly created, perform the following steps:

  • Copy the above created virtual hard disk (.vhd/.vmdk) file in the folder where you will create the new virtual machine.

In Virtual PC, you will have to manually copy the .vhd file to the destination folder.

In Hyper-V, you’ll have to use the Export-Import option

In VMware Workstation, you can select the option to clone the image.

  • Rename the virtual hard disk file as per your wish, normally similar to your VM config file.
  • Create a new VM config in Virtual PC/VMware and select to map existing hard disk
  • Start the new virtual machine.

The following screen will be displayed. The rest of the activities will be automatically performed.


Once the logon screen appears, login using the Administrator a/c. Remember the password is blank.

!!! Sysprep installation complete !!!