• You have a computer that has Outlook 2003 (SP2) or 2007, Exchange 2007 Management Tools (32-bit version), PowerShell and .NET Framework installed
• Logon with an account that has Exchange Server Administrator and Local Administrator rights
• You have full access to the users’ mailbox on both servers. See the note below on how to do it.

1. Start the Exchange Management Shell and type the following:[PS] C:\>Get-Mailbox –Database “<Exchange Server FQDN>\<Database Name>” | Export-Mailbox –PSTFolderPath C:\PSTFiles to export all users mailbox to a PST file. Press A for Yes to All. Depending on the size of your database, the export procedure could take a long time to complete.
2. Now the mailboxes are exported to the PST files, make sure that the PST file name matches the alias of the users’ account in the other domain.
3. Next, import the PST files to the other Exchange Server by typing the following: [PS] C:\>Get-Mailbox –Database “<Exchange Server FQDN>\<Database Name>” | Import-Mailbox –PSTFolderPath C:\PSTFiles and press A for Yes for All. Wait until the import operation completes.

Note:
To grant the Administrator Full Access rights on the database type the following command:
[PS] C:\>Get-Mailbox -Database “<Exchange Server FQDN>\<Database Name>” | Add-ADPermission -User Administrator -AccessRights GenericAll

Ok, long story short, it all started with a Backup Exec 12.0 job suddenly failing.. One part of the whole job is backuping Exchange Server 2007 using a remote agent and the exchange server. In the job log of Backup Exec, i got a ‘Final error: 0xe000fed1 – A failure occurred querying the Writer status. ‘ ok, initially i thought, this is nothing new.. querying the writer status and seeing what this one’s reporting ..

This is the Backup Exec 12.0 Job log:

Job ended: Donnerstag, 28. April 2011 at 23:00:12
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65233

and this:

Click an error below to locate it in the job log

Backup- server.domain.localV-79-57344-34110 - AOFO: Initialization failure on: "\\server.domain.local\Microsoft Information Store\xyz Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5). 

VssAdmin List Writers reported:

Writer name: 'Microsoft Exchange Writer'
  Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}Writer Instance Id: {c0784b22-2777-47ea-955c-6302ef023141}   State: [5] Waiting for completion
Last error: No error

Checking Event Viewer:

Source: VSS

Event ID: 8193Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid.hr = 0x80070539. Operation:
OnIdentify event
Gathering Writer DataContext:
Execution Context: Shadow Copy Optimization Writer
Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Name: Shadow Copy Optimization Writer
Writer Instance ID: {e439464c-084e-42a6-bebb-79f6c877804e}

i got this solved by following MSFT-David Shen’s tip.. => Just deleted a Profile with a .bak extension..

Hi,

According to the research, the issue may be caused by an invalid entry inside the following registry sub tree.

HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

Please open the registry editor with regedit.

Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer.

Please backup the registry key first, and then delete that entry with the extra ".bak"

Then you may reboot the problematic server to check if it the issue can be fixed.

Ok, this solved the above mentioned error with EventID 8193

But there was another error, kept me from running the backup job successfully..

Source: CAPI2
Event ID: 513
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddCoreCsiFiles : BeginFileEnumeration() failed.

System Error:
Access is denied.
.

Microsoft Technet writes:

Event Details

Product:

Windows Operating System

ID:

513

Source:

Microsoft-Windows-CAPI2

Version:

6.0

Symbolic Name:

MSG_SYSTEMWRITER_ONIDENTITY_FAILURE

Message:

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.%1.

Resolve

Modify the access control list on the registration folder

Component Object Model (COM) applications must be able to access the COM+ catalog files that are stored in the COM catalog folder. If the default access control list is changed on the COM catalog folder within the Windows folder, the Shadow Copy System Writer may not work properly.

To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.

To modify the access control list on the COM catalog folder:

1. Click Start, and then click Computer.
2. Navigate to %systemdrive%\Windows.

   By default, %systemdrive% is located at C:\.

3. Right-click Registration, click Properties, and then click the Security tab.
4. Click Advanced, and then click Edit.
5. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
6. Click Edit to view the special permissions assigned to this folder.
7. Ensure that the access control list matches the following criteria:
   • The local Administrators group has Full Control permissions applied to This folder and files.
   • The Everyone group has List folder/read data, Read attributes, Read extended attributes, and Read permissions applied to This folder and files.
   • The local SYSTEM account has Full Control permissions applied to This folder and files.
8. If the permissions on this folder do not match what is listed in this procedure, make the appropriate changes, and then click OK.

Verify

To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.

To verify that the Shadow Copy System Writer is working properly:

1. Click Start, point to All Programs, and then click Accessories.
2. Right-click Command Prompt, and then click Run as administrator.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. In the command prompt window, type vssadmin list writers.
5. Ensure that Writer Name: ‘System Writer’ is displayed in the list.

I started Process Monitor and found an ACCESS DENIED on C:\Windows\winsxs\FileMaps\$$.cdf-ms for the NT AUTHORITY\NETWORK SERVICE. Funny, the guys writing Technet Articles and Help for MS don’t even know their own system in deep .. rofl .. however, granting NT AUTHORITY\NETWORK SERVICE the necessary rights, solved also this issue.

here’s my powershell get-history (including typos and retries ), maybe it will help you:

[PS] C:\Windows\system32>Get-History

  Id CommandLine

  — ———–

  14 .\vssadmin.exe list writers

  15 icacls

  16 icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"

  17 .\vssadmin.exe list writers

  18 icacls /?

  19 .\vssadmin.exe list writers

  20 Takeown /f %windir%\winsxs\filemaps\* /a

  21 icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"

  22 icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"

  23 icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

  24 icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

  25 icacls

  26 icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"

  27 .\vssadmin.exe list writers

  28 .\vssadmin.exe list writers

  29 .\icacls.exe %windir%\winsxs\filemaps\*.* grant "NT AUTHORITY\NETWORK SERVICE:(F)"

  30 .\icacls.exe %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\NETWORK SERVICE:(F)"

  31 .\icacls.exe %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\NETWORK SERVICE:(F)"

  32 .\vssadmin.exe list writers

  33 .\icacls.exe %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\NETWORK SERVICE:(F)"

  34 takeown /f %windir%\winsxs\filemaps\* /a

  35 takeown

  36 takeown /f C:\Windows\winsxs\FileMaps\* /a

  37 icaclc C:\Windows\winsxs\FileMaps\*.* /grant

  44 .\icacls.exe c:\windows\winsxs\filemaps\*.* /grant "NT AUTHORITY\NETWORK SERVICE:(F)"

  45 .\vssadmin.exe list writers

Let’s start with some easy stuff..

Get the number of Public Folders

Get-PublicFolder -Recurse | Measure-Object

Get the sum / number of Mails / Object in all Public Folders

Get-PublicFolderStatistics | Measure-Object -Property ItemCount -Sum

Get the number of Mailboxes

Get-Mailbox | Measure-Object

Get the number of sent messages / emails within a date range

Get-MessageTrackingLog -Start "29.11.2009" -End "30.12.2009" -ResultSize Unlimited | Measure-Object

I’m just upgrading one of our Microsoft Exchange 2007 Servers to Microsoft Exchange Server 2010. I’ve decided to first remove the Exchange 2007 Server and then install the 2010 Version. Well, if you should ever choose the same path, you’ll have to pass a few hurdles… After following the instructions in the links provided below, i finally was able to remove Microsoft Exchange Server 2007. When i then started Microsoft Exchange 2010 Server Setup, i got the message:

Setup.exe – A previous version of Exchange Server is already installed on this machine.

Well, since this Version of Exchange is pretty new and Google nor other search machines give you good results about this issue, i decided to not spend to much time searching the internet but opened the registry editor and searched for Exchange in the HKLM/Software Key.. What i’ve found:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

Rename this Key to _Exchange, start setup.exe again and you’ll be fine ..

Links

This Server is the Source for a Send Connector

Removing Public Folder Databases

How to Remove a Public Folder Database

How to Delete Multiple Public Folders from Your Organization

Get-Mailpublicfolder | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
 
write-output ""
}

or redirect the output into a file for analysis, whatever..

Get-Mailpublicfolder | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
 
write-output ""
} | out-file -filepath c:\publicFolders.txt -encoding ASCII

Get-Mailbox | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
 
write-output ""
} > c:\smtp.txt

or use the out-file cmdlet..

######### Using Out-File Cmdlet ############
 
Get-Mailbox | select name , alias ,EmailAddresses | foreach {
"Name: "+$_.name
"Alias: "+$_.alias
 
$_.EmailAddresses | foreach {
if($_.SmtpAddress){
if($_.IsPrimaryAddress){
"Primary SmtpAddress: $($_.SmtpAddress)"
} else {
"SmtpAddress: $($_.SmtpAddress)"
}
}
}
write-output ""
} | out-file -filepath c:\smtp.txt -encoding ASCII

Microsoft Exchange Installation Wizard

The component Microsoft Exchange Messaging and Collaboriation Server cannot be assigned the action “Remove” because:

- This server is the Recipient Update Server for the domain “someDomain.tld”. You cannot uninstall this server until you select a different Recipient Update Server for this domain.

Exchange_2003_removal_RUS_assigned

The trick to remove Microsoft Exchange Server 2003 from your organization is reassigning the Recipient Update Service (RUS). Setup will not allow you to uninstall Microsoft Exchange Server 2003 until the Recipient Update Service (RUS) has been reassigned to another server. This is ironic since Exchange Server 2007 doesn’t even use the Recipient Update Service. However, this task must be performed to proceed the uninstallation of Microsoft Exchanger Server 2003.

Reassigning the Recipient Update Service is fairly easy. Begin the process by opening the Exchange System Manager. Now, navigate through the console tree to Recipients | Recipient Update Service.

Exchange_2003_removal_RUS_reAssign

There are two listings for the Recipient Update Service. There is an enterprise listing, and a domain listing.

At this point in the process, you must right click on the enterprise listing for the Recipient Update Service, and then choose the Properties command from the resulting shortcut menu. When you do, the Exchange System Manager will display the Recipient Update Service properties sheet.

Exchange_2003_removal_RUS_Properties

You will notice that the Recipient Update Service has been assigned to a specific Exchange server. By default, the server that is listed is an Exchange 2003 server. You must click the Browse button, and then choose an Exchange 2007 server from the list. After doing so, click OK to close the Recipient Update Service properties sheet.

Now it’s time to turn our attention to the domain listing for the Recipient Update Service. We will do the exact same thing for this listing that we did for the enterprise listing. Right-click on the domain listing and choose the Properties command from the resulting shortcut menu to reveal the Recipient Update Services properties sheet. Now, click the Browse button next to the listing for the Exchange server, and choose an Exchange 2007 server from the list. Click OK to close the properties sheet, and you’re done.

Conclusion

Now that the Recipient Update Service has been reassigned you should have no trouble uninstalling Exchange server 2003. Simply run the Exchange Server 2003 Setup program, and then use the Change/Remove option to complete the uninstallation process.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
 test@christiano.ch
SMTP error from remote mail server after MAIL FROM:<sunny@christiano.ch> SIZE=6841:
host xyz.christiano.ch [194.123.18.170]: 530 5.7.1 Client was not authenticated

Then you have to change the Receive Connector to allow anonymous connections (probably) ..
You can do this using the Microsoft Exchange Management Shell (EMS)

Set-ReceiveConnector -Identity "Default <SERVERNAME>" -PermissionGroups "AnonymousUsers"

or in the GUI using Microsoft Exchange Management Console (EMC)

Navigate to Microsoft Exchange | Server Configuration | Hub Transport | Receive Connectors

Microsoft_Exchange_Management_Console_ReceiveConnector_Allow_AnonymousUsers

In environments without an Edge server role, these need to be installed manually on the Hub Transport server(s).

To install anti-spam agents on a Hub Transport server, start Exchange Management Shell (EMS), navigate to the “%ProgramFiles%\Microsoft\Exchange Server\Scripts” folder
(by default C:\Program Files\Microsoft\Exchange Server\Scripts)

Microsoft_Exchange_2007_Install-AntispamAgents

Now run/execute:

Microsoft_Exchange_2007_Install-AntispamAgents_PowerShell

[PS] C:\Program Files\Microsoft\Exchange Server\Scripts>.\install-AntispamAgents.ps1

Now restart the Microsoft Exchange Transport Service

Microsoft_Exchange_2007_TransportServiceRestart

Once installed successfully, the command will show each agent installed, whether it is enabled or not, and its priority

Anti-Spam Agents on Hub Transport serverAfter the anti-spam agents are installed, you can see the Anti-spam tab in Organization Configuration | Hub Transport node in Exchange Management Console.
(If your console was open during installation, you will need to restart it).

Microsoft_Exchange_2007_AntiSpamAgents

Alternatively you can run Get-TransportAgent

Microsoft_Exchange_2007_PowerShell_Get-TransportAgents

[PS] C:\>Get-TransportAgent

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
sunny@christiano.ch
SMTP error from remote mail server after RCPT TO:<sunny@christiano.ch>:
host christiano.ch [100.120.200.30]: 550 No Such User Here

If you want your Microsoft Exchange Server to take such mails and put them in a common mailbox, you could use the nice Microsoft Exchange 2007 Transport Protocol Agent which provides the (MTA) catchall functionality from Wilbert De Graaf. The Agent is Open Source published on www.codeplex.com. To download the Agent, click here and click on download..

Setup is quite easy.

The instruction has been taken from the install notes from Wilbert de Graaf..
CatchAllAgent: Exchange 2007 Transport Protocol Agent
=====================================================

Introduction
————
CatchAllAgent is an Exchange 2007 Transport Protocol Agent. If a message comes in, and a
recipient of that message does not exist (unknown recipient), the recipient typically gets
rejected by the Recipient Filtering feature (which is also a Transport Protocol Agent).
The CatchAllAgent can be configured to rewrite the recipient address for unknown recipients
such that such messages end up in a dedicated mailbox. The configuration allows for multiple
domains, but you can only specify a single target address for each of those domains.

Configuration
————-
The configuration is called config.xml and should be found at the same location of the agent’s
assembly (DLL). The contents looks something like this:
<config>
<domain name=”domain1.com” address=”catchall@domain1.com” />
<domain name=”domain2.com” address=”admin@domain2.com” />
</config>
This says that messages to unknown recipients @ domain1.com should be redirected to
“catchall@domain1.com”, and messages to unknown recipients @ domain2.com should be
redirected to “admin@domain2.com”. Recipients that are either known at those domains,
or at other domains (either known or unknown) are unaffected.
Changes to the configuration file will be picked up on the fly. If there is an error
in the configuration file, the (new) content will be ignored.

Installation Steps
——————
1. Create a directory on your Transport server (either Edge or Internet Facing Hub role)
2. Unzip the ExchangeCatchAll.zip file in that directory
3. Edit the config.xml according to your needs
4. Open the Exchange 2007 Management Shell and run the following command to install
the agent, assuming the directory with the CatchAll agent is c:\catchallagent:
[PS] C:\catchallagent>install-transportagent -Name "CatchAll Agent" -TransportAgentFactory:CatchAll.CatchAllFactory -AssemblyPath:"C:\catchallagent\CatchAllAgent.dll"
Identity Enabled Priority
——– ——- ——–
CatchAll Agent False 18
WARNING: Please exit Powershell to complete the installation.
WARNING: The following service restart is required for the change(s) to take effect : MSExchangeTransport
5. Now the priority of the CatchAllAgent needs to be smaller that the priority of the Recipient
Filtering agent. So you first need to figure that out using the get-transportagent task:
[PS] C:\catchallagent>get-transportagent
Identity Enabled Priority
——– ——- ——–
Transport Rule Agent True 1
Journaling Agent True 2
RMS Encryption Agent False 3
AD RMS Prelicensing Agent False 4
Connection Filtering Agent True 12
Content Filter Agent True 13
Sender Id Agent True 14
Sender Filter Agent True 15
Recipient Filter Agent True 16
Protocol Analysis Agent True 17
CatchAll Agent False 18

So in this case (Internet facing Hub) the priority of the Recipient Filtering Agent is 16, and since
11 is available, that’d be a good pick. Use the following command to set the priority:
[PS] C:\catchallagent>set-transportagent "CatchAll Agent" -Priority:11
WARNING: The following service restart is required for the change(s) to take effect : MSExchangeTransport
6. Now the agent can be enabled:
[PS] C:\catchallagent>enable-transportagent "CatchAll Agent"
WARNING: The following service restart is required for the change(s) to take effect : MSExchangeTransport
7. Restart the Transport service:
net stop MSExchangeTransport
net start MSExchangeTransport

Troubleshooting
—————
The agent supports standard .NET tracing. To enable tracing, you have to add the following
section to the application configuration file (edgetransport.exe.config):
<configuration>
<system.diagnostics>
<trace autoflush=”false” indentsize=”4″>
<listeners>
<add name=”myListener”
type=”System.Diagnostics.TextWriterTraceListener”
initializeData=”traces.log” />
<remove name=”Default” />
</listeners>
</trace>
</system.diagnostics>
</configuration>
The result is that traces will be written to file “traces.log” in the applcation’s directory.
There will only be traces for configuration changes, and not when a recipient gets processed.

Links

CatchAllAgent for Microsoft Exchange 2007 Transport Protocol Agent on www.codeplex.com