Yesterday a client asked me how he could find out, which of his users were the “worst offenders” for mailbox size. Normally a simple Get-MailboxStatistics command would be fine, and we would sort the results in descending order.
Solution
On one of the Exchange servers, launch the Exchange Management Shell.
Issue the following command:
Note: That’s all one command, replace the name PNL-MAIL-2019 with your Exchange server name.
After I managed to break my test Exchange 2013 Server the other week, I built a new one and migrated all the data into it. But while trying to decommission the old Exchange box, the process failed and I was stuck with this error.
Setup previously failed while performing the action "Uninstall".
You can't resume setup by performing the action "Install".
So now I couldn’t uninstall, or attempt to ‘repair install’ in an effort to remove Exchange.
Solution
This happens because when you attempted to uninstall, the process adds some registry key(s) and sets them to the uninstall state, you need to locate and delete them before you can proceed.
1. Windows Key+R > Regedit {Enter} > Navigate to;
[box]
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > ExchangeServer > (version)[/box]
Here you will need to check the sub-keys, for the roles that were installed on this machine, below you can see the ClientAccessRole sub-key has a value called Action, that has been set to Uninstall, that needs to be deleted.
2. Here you can see the mailbox role is clear and requires no action.
Note: This is an Exchange 2013 Server, so it can only be a Mailbox or a Client Access Role Server. With earlier versions of Exchange you may also want to check HubTransportRole.
3. Once the values have been removed you should be able to proceed.
Related Articles, References, Credits, or External Links
With the release of Exchange 2010 Service Pack 3, Exchange 2010 is now supported on Windows Server 2012, but as there (at time of writing) is no media with SP3 slipstreamed into it, installing the product on Windows Server 2012 is a little problematic.
If you got here because you have tried and have got an error, follow the procedure below and you should have the product installed and running without any further problems.
Note: Don’t panic if it appears to hang at 68% for a while!
4. Download this zip file, it contains a .reg file, run it and merge those files into the registry of the 2012 server.
5. Insert the Exchange 2010 DVD, or run setup.exe from the extracted Exchange 2010 install media.
Note: I’m using Exchange 2010 with SP1 included (because its the newest one I can download, and a version with SP2 or SP3 included is not yet available).
6. MAKE SURE, you DO NOT have the ‘Automatically install Windows Server roles and features required for Exchange Server’ option selected or you will see this error.
7. When complete install Service Pack 3.
Errors You May See If You Don’t Follow This Procedure
Error 1.Error:
The following error was generated when "$error.Clear();
if($RoleInstallWindowsComponents)
{
# Install any Windows Roles or Features required for the Management Tools role
Install-WindowsComponent -ShortNameForRole "AdminTools" -ADToolsNeeded $RoleADToolsNeeded
}
" was run: "The system cannot find the file specified".
The system cannot find the file specified
You see this error if you left ‘Automatically install Windows Server roles and features required for Exchange Server’ ticked, simply click back and untick this box then try again.
Error 2
Mailbox Role
Failed
Error:
The following error was generated when "$error.Clear();
$wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
$manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "ScriptsTSCrimsonManifest.man");
Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
" was run: "Process execution failed with exit code 15010.".
Process execution failed with exit code 15010.
Download this zip file, it contains a .reg file, run it and merge those files into the registry of the 2012 server. Then run the setup again.
Know Problem Opening Exchange Management Console
(19/06/13) Update from reader Jeremy Krautkramer.
You may find that on Server 2012, (and Windows 8) You can launch the Exchange Management Console, but are unable to expand any of the objects in the left hand pane.
Jeremy fixed it by dropping to command line and running the following three commands;
[box]set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
“C:Program FilesMicrosoftExchange ServerV14BinExchange Management
Console.msc”[/box]
Note: Change the drive letter and path to match your own server.
Why this happens? The Exchange 2010 Exchange Management Console was built with CLR (Common Language Runtime) version 2.0. Windows 2012/8 by default runs its MMC snap ins with CLR version 4.0.
Related Articles, References, Credits, or External Links
