Monday, August 5, 2013

Move Public Folder Content from One Public Folder Database to Another Public Folder Database

Use the MoveAllReplicas.ps1 script to move all public folder content from one server to another server
 

To move all public folders in a public folder database on one server to a public folder database on another server, use the MoveAllReplicas.ps1 script. This script replaces a server with a new server in the replication list for all public folders, including system folders. For more information about using public folder scripts, see Scripts for Managing Public Folders in the Exchange Management Shell.

This example moves all public folder content from Server01 to Server02.

cd $EXscripts

.\MoveAllReplicas.ps1 -Server Server01 -NewServer Server02
 
If you are move from Exchange 2007 to Exchange 2010, you had better run the scripts from Exchange 2010 servers.
 
However, I would prefer you run the following script first, and make sure all public folders including system folders are replicated to new server first,
 
1. run Get-PublicFolder -Server OldPFServername -Recurse | FL Name,Replicas
 
If there is any issue, fix it first, say, some of old PF folders may contain leading or trialing whitespace that no longer support in new Exchange server.
 

WARNING: The Name property
contains leading or trailing whitespace, which must be removed.
 

2. use AddReplicaToPFRecursive.ps1 to replicate all Folders to new server
 
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\AddReplicaToPFRecursive.ps1
 

AddReplicaToPFRecursive.ps1 -Server "MyEx2007Server" -TopPublicFolder "\" -ServerToAdd "MyEx2010Server"
 
3.\AddReplicaToPFRecursive.ps1 -Server "MyEx2007Server" -TopPublicFolder "\NON_IPM_Subtree" -ServerToAdd "MyEx2010Server"
 
The above command will add replica of all public folders to exchange 2010 public folder database.
Once the replica is added you can move the replica from Exchange 2007 to Exchange 2010. To do this execute the below EMS command:

4. .\MoveAllReplicas.ps1 -Server "MyEx2007Server" -NewServer "MyEx2010Server"
 
 

OfflineAddressBook, PublicFolderDatabase still points to old Exchange server

 
After migrating your Exchange server   (I've seen this in transition  from Exchange 2003 to Exchange 2007 and from Exchange 2007 to 2010) the PublicFolderDatabase for your OfflineAddressBook is still pointing to the old servers public folder store.
 
When you run the get-OfflineAddressBook | fl command or Get-OfflineAddressbook | FL Server, *public* |FL in an exchange management shell on your new server, you get a result like this:
 
At Server you see the new servername and the PublicFolderDatabase is still pointing to your old server. Public folder replica's and offline address book generation server are already moved to the new server.
 
Solutions: I found if you do the following steps you can change the PublicFolderDatabase.
 
1. Start adsiedit and browse to CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Address Lists Container, CN=Offline Address Lists and open the properties of CN=Default Offline Address List Look for the siteFolderServer attribute, here you will see the old public folder store.
 
2. Choose clear and close with ok, now you may close adsiedit.
 
3. Go to the exchange management console, Organization Configuration, Mailbox, Offline Address Book open the properties of the Default Offline Address List and go to the tab distribution. Uncheck "Outlook version 2 and 3″ at client support and "Enable public folder distribution". Make sure "Web-based distribution" is enabled. Choose apply and ok, then right click on Default Offline Address List and choose update.
4. Go back to properties and distribution and recheck "Outlook client support version 2 and 3″ and "Enable public folder distibution". Again choose apply and ok and right click and choose update. When you go back to the exchange management shell and repeat Get-OfflineAddressbook | FL Server, *public* |FL  now you now will see the PublicFolderDatabase is  pointing to your new public folder server now.
 
 

Tuesday, June 4, 2013

How to Delete Mail from Multiple Mailboxes

How to Delete Mail from Multiple Mailboxes
 
Issue:

I had this recently where a spam email had went around.  I needed to find a way to delete the email from every mailbox. This can be done from Powershell command:
 
NOTICE out of the box these commands are not enabled, you will need to see this article first if you have not already enabled them – Enable Export Mailbox Commands In Exchange 2010
 
 
Once the above is done you can now proceed the following powershell cmdlet:
 
get-mailbox -result unlimited -Server YourServername | Search-Mailbox -SearchQuery 'Subject:"Your XYZ order"', 'from:"mailto:sender@xyz.com%22', 'body:"your body text"' -TargetMailbox hltest -TargetFolder "xyzspam"  -LogLevel full -DeleteContent >C:\deletedxyz10.txt
 
Where  YourServername is your mailbox server and "Your XYZ order" is the subject content, from, and body, you can search for one of them, or combination of two or three
 
You will need to use an account that has the correct permissions to give the correct permissions to the user use this command
get-mailbox -server "yourservername"| add-mailboxpermission -user administrator -AccessRights FullAccess
That command will give the correct rights to the administrator account.
 
With above commands you will be able to remove email from multiple mailboxes in Exchange 2010 and Exchange 2013.

How to Enable Export-Mailbox or Import-Mailbox Powershell commands

When using powershell in  Exchange 2010 or Exchange 2013 and you try Export-Mailbox or Import-Mailbox the commands or delete messages from multiple mailbox, you will get error since these are not available by default, we need to enable them…
 
Note, if you are running exchange 2010 SP1 and above and you are trying to delete multiple emails then go here http://www.techieshelp.com/delete-mail-from-multiple-mailboxes/
IT Solution
1) Check if you have the Exchange Server Admin Tasks installed in the Exchange Management Shell
 

Get-PSSnapin
 
2) It should not be in the list displayed as you cannot run the command. Run the command below to see what is registered.
 

Get-PSSnapin -registered
 
3) Now to install the appropriate "Admin Tasks for the exchange Server" run the command below:
 

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
 
NOTE: for MS Exchange 2007 you should change the point (3) to a command like the one below:
 

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin
 
You will now find the import and export commands are available in powershell
If you want to add multiple users or groups to be able to run these commands use the command below, it will create two new security groups with the members you specify.
New-RoleGroup -Name "Exchange Mailbox Import Export" -Roles "Mailbox Import Export" -Members "<yourdomainyourgroupname>" -DisplayName ""Exchange Mailbox Import Export" -Description "This group handles permissions to the import and export commands in powershell."
That creates a group and adds users who are allowed access to the import and export powershell commands.
New-RoleGroup -Name "Exchange Support and Diagnostics" -Roles "Support Diagnostics" -Members "" -DisplayName ""Exchange Support Diagnostics" -Description "This group handles permissions to the support diagnostics cmdlets in exchange."."
That creates a group and adds users who are allowed access to all the exchange powershell diagnostics applets
 

Wednesday, May 22, 2013

Get-DistributionGroupMember

1. Get-DistributionGroupMember from a regular DL
 
Get-DistributionGroupMember -identity "mydl" | Export-Csv C:\MyFile.Csv
 
Where mydl is our distribution group, and myfile.csv is the resulting CSV file.
 
2. Get-DistributionGroupMember from a Dynamic DL
 
$members = Get-DynamicDistributionGroup -Identity "dynamicgroupname"
 
Get-Recipient -RecipientPreviewFilter $members.RecipientFilter > C:\MyDDLmembersall.txt

 

How to create or remove ForeignConnector Exchange 2010

After migrating from Exchange 2007 to Exchange 2010, we are in process of decommiossion of Exchange 2007. Since we have AccuRoute Fax, so we need to change Fax ForeignConnector from Exchange 2007 Hub to Exchange 2010 Hub.
 
Here is the cmdlet we used for the migration,
 
Remove-ForeignConnector "AccuRoute Fax Connector"
New-Foreignconnector "AccuRoute Fax 10 Connector" -AddressSpaces "FAX:*;1" -SourceTransportServers "hub10-1","hub10-2", "Hub10-3"
Set-Foreignconnector -Identity "AccuRoute Fax 10 Connector" -Maxmessagesize 20Mb -dropdirectory "file://fax-10/Drop$"
 
If you need the connected be scoped for local AD site, the following cmdlet need to be run:
 
Set-Foreignconnector -Identity  "AccuRoute Fax 10 Connector" -Isscopedconnector true$
 

Wednesday, May 1, 2013

Email Routing Using Exchange Cost for Multiple AD Sites In Exchange 2010

Exchange 2010 uses AD Sites and Services information to route emails from one AD site to another. All site links will have a default AD cost of 100. Smaller companies might leave the configuration as it is, as they will only have a single site in most cases.
 
Larger organizations will have fairly good number of AD sites and the AD site links will be configured with the appropriate AD cost for the links. By default, Exchange 2010 uses the link which has the least AD cost to send emails from one AD site to another. You may come across organizations where the AD costs will have to be altered for an efficient email routing, but you won't be given the go ahead. This mostly happens in large organizations, as changing the existing AD site costs may affect the production network or the AD team just don't want to make any changes.
Exchange 2010 (actually 2007 as well) has a solution for the above scenario. There is a way by which you can change the email routing without making any changes to the AD site link costs. It is known as "Exchange Cost" and is not configured by default.
Once an exchange cost for a site link is specified, it overrides the AD link costs for email routing.  By going so, it only overrides the email routing topology.
 
Set-ADSiteLink –identity "link name" –ExchangeCost "cost"
The maximum message size that passes through a site link can be restricted as well. It will come in handy if the link between the site is not great. Run the command below to specify a size limit for communications between various AD sites.
Set-ADSiteLink –identity "link name" –MaxMessageSize "size"

Tuesday, April 30, 2013

How to restore Exchange 2007 /2010 Organizational Form Library from Backup Tape

We run issue, all suddenly all of our Exchange 2010 Orgnaizational Forms Library are missing. We have full backup of Exchange 2007 public folder server. Here are the steps we did to restore the forms only to Exchange org:
 
1. Setup a restore server in Lab with different domain from production. Install Exchange 2007 server with the same SP with production.
2. Create a public folder database with the same public folder Database name (note: storage group name could be different). right click the Database, enable the database can be overwitten by a restore.
3. create Organizational forms Library (same as production)
4. follow the following link:
you may skip step 3 if you are working on Exchange 2007 server.
5. dismount the public folder database
6. run restore from backup tape (we use Symantec Backup Exec 2012 R3) (note only select the database, don't select log files)
7. After the restore, the public DB was mounted  automatically.
Note: 1). we had issue to see Organizational Forms Library from Outlook when I missed Step 4 above
Note: 2). after step4 to setup PR-EForm-Local-ID 1033 (for English), I was able to see the Organization Form Library, but there are no forms at all and got error load forms failed. You don't have permission, etc.
Double check restore LAB, realized there is another Exchange 2007 public folder database but DB was dismounted due to missing drive. So move the DB to different drive with -configurationOnly option using ps cmdlet. then mount the DB with empty DB. Then enable replication from the restored the public folder server to that empty public DB for Organization Forms Library only.
8. Create mailbox on a mailbox DB with Client public folder pointing to the restored public DB.
Open Outlook, now I see all forms there.
9. follow the following link to save the resored Orgnaizational forms to PST file.
Copy the pst to a Outlook profile with production mailbox, then copy the forms from the pst to Organizational Forms Library in production.
 
Note: If your organization users still depends on Organizational Forms Library, the follow the link to make a copy of forms to a pst file to make your life easy : http://support.microsoft.com/kb/190994
 

Thursday, April 25, 2013

Setting Message Size Limits ifor Exchange 2010 organization

 
Although you may have setup Max message size on every Hub sending /receiving connectors to more than 10 MB, say 20 MB, your users may still the following error:
 
The recipient won't be able to receive this message because it's too large.
The maximum message size that's allowed is 9 MB. This message is 10 MB.
 
The organizational send and receive size limits apply to all Exchange servers in the Organization. The default is 10MB.
You can modify the organizational message size limits using the Set-TransportConfig cmdlet from the Exchange shell:
 
Set-TransportConfig -MaxReceiveSize 20MB -MaxSendSize 20MB

Exchange 2010 Legacy Relay needs to increase maximum connections per source

Move Exchange 2010 Legacy Relay (PowerPMTA) from Exchange 2003  connector server to Exchange 2010 Hub
 
you will see connections per source exceed the limit error. By default, Exchange 2010 Hub only offer 20 connection per source IP.
 
Solution:
 
Create a dedicated receiving connector for PMTA. from Exchange 2010 Powershell
 
get-receiveconnector -id "hubServername\From PMTA" |FL
 
to see what parameters need to be modified to meet your needs, then run
set-receiveconnector -id "hubServername\From PMTA"  -MaxInboundConnectionPerSource 500 -MaxInboundConnectionPercentagePersource 10
 
Note: by default, MaxInboundConnection per server is set 5000, thus 500/5000 =10%

Just finished Exchange 2010 Project

will update my Blog soon.
 

Thursday, October 18, 2012

Site Mailboxes , Shared Mailboxes and Public Folder Exchange 2013 Outlook 2013

A site mailbox brings Exchange emails and SharePoint documents together. For users, a site mailbox serves as a central filing cabinet, providing a place to file project emails and documents that can be only accessed and edited by site members.
 

What is the difference between site mailboxes, shared mailboxes and public folders?

Site mailboxes

For groups of people that are working together on a shared set of deliverables. They want to keep important emails and documents in one place.
The content is scoped to a particular project that a small team is working on. As such, all content in that mailbox is highly relevant to the team members.
User will not see a site mailbox in their Outlook client unless they are an owner or member of that site mailbox.

Shared mailboxes

A group of people is working on behalf of a virtual entity (e.g. help@contoso.com). They are triaging incoming emails against a shared inbox and responding on behalf of the virtual entity.
Integrated document collaboration is not a requirement for this scenario.
Users will usually only do this for one shared mailbox and the mailbox is added manually to the user's Outlook profile.

Public folders

Public folders hold the full body of shared email knowledge in an organization.
Public folders are a great technology for distribution group (DG) archiving. A public folder can be mail enabled and added to the DG. Emails that are sent to the DG will be automatically added to the public folder for later reference.
Documents should not be stored in public folders since they don't support co-authoring or version management like SharePoint.
 
 

Tuesday, September 18, 2012

Make sure UPN Values Are The Same As Primary Email Addresses

If you are running Exchange 2007 or newer:
  1. Launch the Exchange Management Shell from your Start Menu (available in Exchange 2007 and newer versions)
  2. Copy and paste the following command into the window:
Get-User | Where { -Not [string]::IsNullOrEmpty($_.WindowsEmailAddress) } | ForEach { Set-User -Identity $_.Guid.ToString() -UserPrincipalName $_.WindowsEmailAddress.ToString() }
What this script and command will do is change the UPN of all user's to be the same value as their Primary email address. Once the command finishes, launch the Active Directory Users and Computers snap-in and verify that the UPN is the same value as the email address.
You're now ready to perform a directory synchronization!
 

How to Add a UPN Suffix to a Forest

  1. Open Active Directory Domains and Trusts.
  2. Right-click Active Directory Domains and Trusts in the Tree window pane, and then click Properties.
  3. On the UPN Suffixes tab, type the new UPN suffix that you would like to add to the forrest.
  4. Click Add, and then click OK.
Now when you add users to the forest, you can select the new UPN suffix to complete the user's logon name.

Thursday, May 10, 2012

One or more users cannot be added to the folder access list. Non-local users cannot be given rights on this server

One or more users cannot be added to the folder access list. Non-local users cannot be given rights on this server
 
Keyword: Public Folder permission sharing, Exchange 2007, public folder permission, Distribution list, security group
 
Once I tried to share a public folder to the DL, I got the following error:
"One or more users cannot be added to the folder access list. Non-local users cannot be given rights on this server"
 
The first reaction is I have to concert the DL to security group and set it as Universal Group type as an MS KB (support.microsoft.com/kb/941318) mentioned. I used ADUC to make the change. However, it still doesn't work.
 
I know since Exchange 2007, you cannot assign a public folder to a shared mailbox and we have to run
 
set-mailbox -id "username" -type regular
 
I checked members of the group, and changed some of shared mailbox to regular, however, I still got the same error.
 
Why this has happened.
 
This has been a known problem since Exchange 2007. Essentially there's an active directory attribute called "msExchRecipientDisplayType" that does not get changed properly when you convert the group using the GUI interface.
 
How to Fix it
Exchange 2007
Run the following Powershell command in the Exchange Management Shell:
 
Set-DistributionGroup -Identity "thegroupname"

Exchange 2010
 
If you run that command on Exchange 2010, you will see the error (shown above)
"Members can't remove themselves from security groups. Please set the group to Closed for requests to leave."
 
You need to run the following Powershell command, in the Exchange Management Shell instead:
 
Set-Distributiongroup–identity {group name} –MemberDepartRestriction Closed
 
After that, update your Global address list, offline address list, restart Exchange file disitribution services on your all CaS servers, and f9 to download update your offline address on your Outlook. Or use online Outlook profile if you are in rush, you should be all set.
 
Summary
 
Issue:
 
You got error: "One or more users cannot be added to the folder access list. Non-local users cannot be given rights on this server" once you try to assign a DL to public folder permission.
 
You tried

1. You converted the DL to security group and changed the group type to Universal Group using ADUC
 
2. You checked member of the group and make sure you changed shared mailbox type to regular using the following cmdlet:
 
set-mailbox -ID username -type regular
 
3. You set the group using the following cmdlet:
 
for Exchange 2007
 
Set-DistributionGroup -Identity "thegroupname"
 
For Exchange 2010,

Set-Distributiongroup–identity "thegroupname" –MemberDepartRestriction Closed

Tuesday, May 8, 2012

Troubleshooting Exchange 2010 DAGs Across WANs

After we established Exchange 2010 LAB across three sites, Exchange 2010 Database Availability Groups across multiple sites and WAN connectivity work most of time. However, once our network connectivity experiences issue between sites, I recently found myself troubleshooting an inconsistent issue at one remote site.
 
The issue reported by the following link, however, it seems there is no resolution yet.
http://social.technet.microsoft.com/Forums/eu/exchange2010/thread/40a37573-d967-41b0-b0d2-8a9f7ae530eb 
 
you can see our network (Exchange 2010) settings via the following link:
 
 
Once this happened, from remote site server EMC, Mailboxes Database Status across WAN is shown as Unknown and from NY and WM (site)  servers, copy status for all database copies on SIXLABMBX-1 as "ServiceDown." Running Get-MailboxDatabaseCopyStatus against the DAG member(s) in the remote data center reflected the same results. Databases in an "Unknown" mount state corresponded to cases where the database was activated in one data center and status was being queried across the WAN from the other data center.
There were several Windows event logged on both SI and NY servers:
 
Event ID 2060
 
The Microsoft Exchange Replication service encountered a transient error while attempting to start a replication instance for NYXLABMBX1DB-1\SIXLABMBX-1. The copy will be set to failed. Error: The NetworkManager has not yet been initialized. Check the event logs to determine the cause.

Event ID 2153
 
The log copier was unable to communicate with server 'NYXLABMBX-1.exlab.randomhouse.com'. The copy of database 'NYXLABMBX1DB-1\SIXLABMBX-1' is in a disconnected state. The communication error was: Communication was terminated by server 'NYXLABMBX-1.exlab.randomhouse.com': Data could not be read because the communication channel was closed. The copier will automatically retry after a short delay.
 
Event ID 2058
 
The Microsoft Exchange Replication service was unable to perform an incremental reseed of database copy 'NYXLABMBX-1DB3\SIXLABMBX-1' due to a network error. The database copy status will be set to Disconnected. Error An error occurred while communicating with server 'NYXLABMBX-1.exlab.randomhouse.com'. Error: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
 
This doesn't happen between WM and NY servers.
 
We found out the only solution for this is to reboot the server one by one, then DAG will show healthy after that. That's a big headache.
 
After digging and digging, we have found a link that talking about MTU (Maximum Transmission Unit). By default, Windows NIC is automatically set MTU (1500), and Windows operating system uses MTU (Maximum Transmission Unit) determines the maximum size of the largest protocol data packet unit (including the size of the transport header) that can be transmitted over the underlying network layer. MTU parameters usually appear in association with a communications interface (NIC, serial port, etc.), and is configured separately for each network interface. We can test MTU settings across WAN by pinging remote IP with -f -l (packet size) option,
For example, from NY server, we can ping 10.102.52.18 -f -l 1200,  where 1200 is packet size, we want to test…, then try 1300, 1400, 1500 …
By default, router's MTU is set between 1480 to 1500, deducting some packet transport headers, from NY to WM server, we can ping wmxhub-1 –f –l 1470 with no problem, failed 1475. That's normal. However, from NY to SI site, it only allow maximum packet size around  (1365), it failed 1370 (ping 10.102.52.17 -f -l 1365, OK and ping 10.102.52.17 -f -l 1370 failed). We talked with Network team about this, I was told that this is due to fact that we have private circuit between WM and NY, and only VPN connection between SI and NY that offset a bigger packet overhead. Usually server and network equipment will adjust packet size automatically.
We use "netsh interface ipv4 show subinterfaces " command to check default MTU size on the mailbox servers that are member of DAG and found out default NIC MTU is 1500, while Microsoft set Cluster NIC MTU to 1300. Since we don't use dedicated NIC for replication traffic, thus the server will use default NIC to transport replication traffic, and it seems Windows cannot automatically adjust MTU accordingly.
 
Then we use the following command to set default NIC MTU to 1300
 
netsh interface ipv4 set subinterface "Local Area Connection 3" mtu=1300 store=persistent
 
and use netsh interface ipv4 show subinterfaces to show MTU to make sure both cluster NIC and default NIC have the same size of MTU (1300)
 
After we did these on all mailbox servers that are member of DAG, then we restarted replication services on all DAG members, the issue has been resolved automatically.
 
 

Monday, April 16, 2012

Use MDSPushvsPull.exe to trace Blackberry Device Data usage for troubleshooting

We had issue with one of our BES users whose data usage was over 2.5 GB per month, our regular users' usage is less than 500 MB per month. We use BES 5.0.3. After we installed resources Kits, we are able to check data usage per device on our BES server and found out one of applications the user installed on the device may have bug that caused consistent data connection to its server.
C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry AMT Tools>MDSPushvsPull.exe -p E -OL D:\test -L "E:\BlackBerry Enterprise Server\20120318"
where "E:\BlackBerry Enterprise Server\20120318" is log file location of BES.
The output is a *.cvs file with following columns:
 
Type Source Destination Date Time Port Size
Pull PIN i.huffpost.com 2/11/2012 11:48:17.176 EST 80 103
Pull PIN i.huffpost.com 2/11/2012 11:48:18.082 EST 80 93
Pull PIN i.huffpost.com 2/11/2012 11:48:19.348 EST 80 83
Pull PIN i.huffpost.com 2/11/2012 11:48:20.317 EST 80
88
 
Where Size in question is Bytes

Tuesday, March 27, 2012

Is it possible the following scenario - Physical server 2008 VHD backup file, created by wbadmin.exe to run in Hyper-V server?

Is it possible the following scenario - Physical server 2008 VHD backup file, created by wbadmin.exe to run in Hyper-V server?
 
One of our physical web servers is running Windows Server 2008 Standard x64, and is being backuped daily by default backup utility for server 2008 (wbadmin.exe).
I am curiuous is it possible to restore this VHD backup file into Hyper-V server (said in other way to create new VM using that VHD image).
If it's possible - what are the steps to successfully do this?
Nope, won't work.
But, this will:
- Prepare a fresh VM with the same OS.
- Shut down the VM and mount the VHD file on another VM
- Mount the "backup" VHD you'd like to restore from the same VM
- Use robocopy /purge /b /e /copyall to take all the data from the backup vhd to the new VHD
After this, shut down the VM, and you should be able to create a new VM using the destination VHD file. It will boot - all you have to do is install integration services.
Now for some more "magic":
You can use vshadow.exe to create a VSS snapshot of a running physical OR virtual machine and expose it to a drive letter (yes, boot drive also), and use the robocopy trick above to perform P2Vs or V2Vs. What's good about this method is that you can do a first pass with the machine still servicing requests, then stop all critical services and do another pass to complete the process. Typically takes about 2-3 minutes, depending on how much data has changed. Robocopy will only copy files which are different, and also copies NTFS permissions.
 
Note:
 
1) You may need to use DriverInjection (http://www.911cd.net/forums//index.php?showtopic=22523&st=0) or something similar if the standard IDE driver is not present on the source.
2) You may have to edit boot.ini to point to partition 1 - some system manufacturers have a utility partition as #1.
Otherwise you should be good to go.
 
References:
 
How to configure WSB with the support for Hyper-V VSS writer.

Windows 2008 Hyper-V and Windows 2008 Backup

Windows 2008 (or R2) comes with Wondows backup application. It uses Microsoft volume snapshot technology to snapshot volume and copy the configuration and Data in *.vhd format, that is used for Microsoft Hyper-V server, to local attached storage or network storage. For quick data volume recovery, you just mount the *.vhd file to any Hyper-V server and you are done. You don't need any restore time you may need for the traditional tape backup to speed up SLA. If you need to recover systems, you will have to install Windows via CD or image and choose system recovery option during setup and specify where is system volume backup file is located, local media, UNC path, etc. since Microsoft doesn't support to make backup image *.vhd bootable.
 
You use wbadmin command to schedule backup job and restore.
 
You can run Wbadmin by following these steps:
1. Click Start, click All Programs, and then click Accessories to open the Accessories menu.
2. Start an elevated command prompt by right-clicking Command Prompt and then selecting Run As Administrator.
3. In the Command Prompt window, enter the necessary command text or run a script that invokes Wbadmin.

Wbadmin has a number of associated commands:
DELETE SYSTEMSTATEBACKUP Deletes the system state backup or backups from a specified location.
DISABLE BACKUP Disables scheduled daily backups so that they no longer run.
ENABLE BACKUP Enables or modifies a scheduled daily backup.
GET DISKS Lists the disks that are currently online for the local computer. Disks are listed by manufacturer name, type, disk number, GUID, total space, used space, and associated volumes. GET ITEMS Lists items contained in a specified backup.
GET STATUS Reports the status of the currently running backup or recovery job.
GET VERSIONS List details about the available backups stored in a specific location, including the backup time and backup destination.
START BACKUP Starts a one-time backup using the specified parameters. If no parameters are passed and scheduled backups are enabled, the backup uses the settings for scheduled backups.
START RECOVERY Initiates a recovery of volumes, applications, or files using the specified parameters.
START SYSTEMSTATEBACKUP Starts a system state backup using the options specified.
START SYSTEMSTATERECOVERY Starts a system state recovery using the specified parameters.
STOP JOB Stops the currently running backup or recovery job. Stopped jobs cannot be restarted from where they were stopped.

When you are working with Wbadmin, you can get help on available commands:
1.To view a list of management commands, type wbadmin /? at the command prompt.
2.To view the syntax for a specific management command, type wbadmin Command /?, where Command is the name of the management command you want to examine, such as wbadmin stop job /?.

When you work with Wbadmin, you'll find that just about every command accepts parameters and specific parameter values that qualify what you want to work with. To see more clearly how this works, consider the following syntax example:
wbadmin get versions [-backupTarget:{VolumeName | NetworkSharePath}] [-machine:BackupMachineName] 
The brackets tell you that –backupTarget and –machine are optional. Thus, you could type the following to get information on recoverable backups on the local computer:
wbadmin get versions 
You could type the following to get information on recoverable backups for C:
wbadmin get versions -backuptarget:f: 
Or you could type the following to get information on recoverable backups for C on Server88:
wbadmin get versions -backuptarget:f: -machine:server88 
Many Wbadmin commands use the –backupTarget and –machine parameters. The backup target is the storage location you want to work with, and can be expressed as a local volume name (such as F:) or as a network share path, such as \\FileServer32\backups\Server85. The –machine parameter identifies the computer you want to work with for backup or recovery operations.

Tuesday, February 14, 2012

Event ID 4113 Error: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time

You have Exchange 2010 (up to SP2) DAG setup with multiple sites, remote server cannot see status of another party Database Status. From EMC, it shows Dababase Status unknown and with the following event logged:
 
Log Name:      Application
Source:        MSExchangeRepl
Date:          2/13/2012 6:04:32 PM
Event ID:      4113
Task Category: Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DREXMBX-1.exlab.mydomain.com
Description:
The Microsoft Exchange Replication service was unable to perform an incremental reseed of database copy 'EXMBX-1\DREXMBX-1' due to a network error. The database copy status will be set to Disconnected. Error An error occurred while communicating with server 'EXMBX-2.exlab.mydomain.com'. Error: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="49156">2058</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-02-14T14:02:34.000000000Z" />
    <EventRecordID>13852</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DREXMBX-1.exlab.mydomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>EXMBX-1\DREXMBX-1</Data>
    <Data>An error occurred while communicating with server 'EXMBX-2.exlab.mydomain.com'. Error: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.</Data>
  </EventData>
</Event>
 
Resolution:
 
run follow command:
 
netsh int tcp show global
 
and make sure you have disabled all of following three (autotuninglevel, chimney, and rss), if not, please run the following command:
 
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
 
 
 
 

Thursday, January 26, 2012

How to Remove Failed Server from DAG in Exchange Server 2010

When an Exchange Server 2010 Mailbox server that is a member of a Database Availability Group has failed, part of the recovery process is to remove it from DAG membership.

In some scenarios this process may result in an error "A quorum of cluster nodes was not present to form a cluster". The full error text is below.

[PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2

Confirm
Are you sure you want to perform this action?
Removing Mailbox server "EX2" from database availability group "dag".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file
"C:\ExchangeSetupLogs\DagTasks\dagtask_2010-11-25_03-48-09.814_remove-databaseavailabiltygroupserver.log".
There was a problem changing the quorum model for database availability group dag. Error: An Active Manager operation f
ailed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"SetClusterQuorumResource() f
ailed with 0x1725. Error: A quorum of cluster nodes was not present to form a cluster"' failed..
+ CategoryInfo : InvalidArgument: (:) [Remove-DatabaseAvailabilityGroupServer], DagTaskProblemChangingQuo
rumException
+ FullyQualifiedErrorId : 80D96894,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveDatabaseAvailabili
tyGroupServer

To resolve this issue use the -ConfigurationOnly switch instead to remove the failed Mailbox server from the Exchange 2010 DAG. In this example server EX2 is being removed.

[PS] C:\>Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer EX2 -ConfigurationOnly

Next, evict the failed node from the Windows Failover Cluster.

Note: you need to import the Failover Cluster module into your Exchange Management Shell session to perform this task.

[PS] C:\>Import-Module FailoverClusters
[PS] C:\>Get-ClusterNode EX2 | Remove-ClusterNode -Force

The failed server has now been removed from the Exchange 2010 DAG and the Windows Failover Cluster.

Friday, January 20, 2012

Get-MailboxDatabase Size list

Exchange 2007

There are a couple methods you can use to get this information in Exchange 2007. Here is a great example posted by Gary Siepser; it's a one-liner that retrieves the database size using WMI, allowing you to run it against clustered mailbox servers:
Get-MailboxDatabase | foreach-object {add-member -inputobject $_ -membertype noteproperty -name mailboxdbsizeinGB -value ([math]::Round(([int64](get-wmiobject cim_datafile -computername $_.server -filter ('name=''' + $_.edbfilepath.pathname.replace("\","\\") + '''')).filesize / 1GB),2)) -passthru} | Sort-Object mailboxdbsizeinGB -Descending | format-table identity,mailboxdbsizeinGB

Exchange 2010

Fortunately, the Get-MailboxDatabase cmdlet in Exchange 2010 provides this information for us out of the box. All you need to do is use the Status parameter and you can access the information using the DatabaseSize property. Here is an example:
Get-MailboxDatabase -Status | select ServerName,Name,DatabaseSize

Wednesday, November 16, 2011

Windows 2008 R2 Powershell script error

For security, Windows 2008 R2 won't run PowerShell scripts by default (Disabled). Thus we need to adjust the ExecutionPolicy to allow PowerShell scripts to run. The better method is to issue this instruction at the PowerShell command line:
 
set-ExecutionPolicy RemoteSigned

Thursday, September 8, 2011

Weak and Strong Host Behavior in Windows for multihomed Computer

Weak and Strong Host Behavior in Windows
Windows XP and Windows Server® 2003 use the weak host model for sends and receives for all IPv4 interfaces and the strong host model for sends and receives for all IPv6 interfaces. You cannot configure this behavior. The Next Generation TCP/IP stack in Windows Vista and Windows Server 2008 supports strong host sends and receives for both IPv4 and IPv6 by default on all interfaces except the Teredo tunneling interface for a Teredo host-specific relay. Figure 4 lists the commands that you can use to configure send and receive behavior for both IPv4 and IPv6 on a per-interface basis. Note that InterfaceNameOrIndex is either the name of the interface from the Network Connections folder or its interface index. You can obtain the interface index of an interface from the display of the command:
 
 Commands to configure strong and weak send and receive behavior
• netsh interface ipv4 set interface [InterfaceNameOrIndex] weakhostsend=enabled|disabled
• netsh interface ipv4 set interface [InterfaceNameOrIndex] weakhostreceive=enabled|disabled
• netsh interface ipv6 set interface [InterfaceNameOrIndex] weakhostsend=enabled|disabled
• netsh interface ipv6 set interface [InterfaceNameOrIndex] weakhostreceive=enabled|disabled
 
netsh interface ipv6 show interface
Reference:
 
 

Wednesday, September 7, 2011

MailboxServer is partially configured – ExBPA


When running ExBPA against an Exchange 2007 mailbox server, the following error text may be noted:
===========================================================

Error: 'MailboxServer' is partially configured
Server: <SERVER>

'MailboxServer' is partially configured on server <SERVER>.contoso.com. Either setup is configuring it right now or setup failed while configuring it. Please rerun setup if it isn't currently running.


Or if you tried to install some third party application that require mailbox role installed, you may get message that you cannot install the the application since there is no mailnox role installed though you know your mailbox server functions very well


Cause: Once you intially ran Exchange Setup, setup might failed and you fixed the error and installed the mailbox server sucessfully.


Resolution: Make sure your mailbox server role works properly and then using regedit


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\MailboxServer]
"Action"="Install"
"Watermark"=REG_SZ:7448a073

"UnpackedVersion"=REG_SZ:8.3.83.6


remove "Watermark"=dword:7448a073


Remove "Action"="Install"


Add


"ConfiguredVersion"=REG_SZ:8.3.83.6


After, we will see


"ConfiguredVersion"=REG_SZ:8.3.83.6

"UnpackedVersion"=REG_SZ:8.3.83.6


your mileage may vary for the version value:


runn ExBPA against the Exchange 2007 mailbox server again, you should be fine.


Reference



Tuesday, August 16, 2011

Event ID 20280 {user@mycompany.com} DoICS() failed: ERR_FAIL

BES 5.0.3 SP3 MR 2, Exchange 2007 SP3 Rollups4
 
Multiple Instance of Each:
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::CheckSelectedFolders - OpenEntry (0x80004005) failed
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::MAPIAttachtoRIMAttach - OpeProperty (0x80004005) failed
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::MAPIAttachtoRIMAttach - GetAttachmentTable (0x80004005) failed
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::IsMAPIMessageSecureEmail - pMessage -> GetAttachmentTable (0x80004005) failed

Event ID 20530
{user@mycompany.com} ConstructPIMFolder - Failed to open the memo folder for user (0x80004005)
 
Event ID 20529
{user@mycompany.com} ConstructPIMFolder - Failed to open the task folder for user (0x80004005)
 
Event ID 20528
{user@mycompany.com} ConstructPIMFolder - Failed to open the contact folder for user (0x80004005)
 
Event ID 20205
(user@mycompany.com} AddRefIDProp(): ERR_FAIL, EntryId=58(xx) (many incrementing)

Event ID 20280
{user@mycompany.com} DoICS() failed: ERR_FAIL
 
Event ID 20043
CallCSAgent::Sych: Could not reload synchronization state for User12345
 
Event ID 20048
CallCSAgent:: - LoadSyncInfo Create BlackBerryHandheldInfo Folder (0x80004005) failed for User12345
 
Event ID 20048
CallCSAgent:: - SaveSyncInfor Create BlackBerryHandheldInfo Folder (0x80004005) failed for User12345
 
Event ID 20455
{user@mycompany.com} MAPIMailbox::CheckUserOriginatedItem - OpenEntry (0x80004005)failed
 
Event ID 20185
{user@mycompany.com} GetRIMMessage() failed: ERR_FAIL
 
 
 
Solution:
 
remove user from BES
Close Outlook on users machine
run Outlook with /resetfolders switch
Add user back to BES
reactivate device
 

Friday, July 29, 2011

The Exchange binary files are not installed but the backup registry key is present. Only build-to-build upgrade mode is available.

First, once you applied SP3, it will start check prerequite, then to remove exchange binarnies files, and to install Exchange 2007 SP3 binaries. If your installation failed with corrupt of installation file, say, Exchangeserver.msi file, etc, installation would fail with error and it cannot roll back to previous Exchange build you ran on the server. Once you try to re-apply Exchange 2007 SP3, or reboot your Exchange server and reapply SP3:
 
You Receive a Message That States That Only the Build-Build Upgrade Mode Is Available When You Install Exchange 2007 Service Pack 3
 
 
This topic provides information about how to troubleshoot an installation error that may occur when you try to install Microsoft Exchange Server 2007  Service Pack 3 (SP3).
 
When you run the Setup program to install Exchange Server 2007 SP3, you receive the following error message:

The Exchange binary files are not installed but the backup registry key is present. Only build-to-build upgrade mode is available.
This issue may occur if the Exchhelp.chm file is missing from the Exchange Server\Bin folder on the Exchange server.
To resolve this issue, follow these steps:
  1. Extract the Exchange 2007 SP3 files from the installation package. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. Change to the directory that contains the E2K7SP1En64.exe file.
    3. Type e2k7sp3en64.exe /x, and then press ENTER.
    4. In the Choose Directory For Extracted Files dialog box, type the path where you want to extract the files, and then click OK. For example, type c:\exchange2007sp3files.
    5. When the Extraction Complete message appears, click OK.
  2. Copy the appropriate language version of the Exchhelp.chm file from the location where you extracted the files to the Exchange Server\Bin directory on the Exchange server. For example, copy the C:\Exchange2007sp3\Setup\Serverroles\Common\mui\0409\Exchhelp.chm file to the %ProgramFiles%\Exchange Server\Bin directory.
  3. Verify that the following services are set to an Automatic startup type and that the services are started:
    • IIS Admin Service (IISADMIN)
    • HTTP SSL (HTTPFilter)
      Note   This service is not present on a Windows Server 2008-based computer.
    • World Wide Web Publishing Service (W3SVC)
  4. Verify that all the Exchange-related services are set to an Automatic startup type and that the services are started.
  5. Start the Exchange 2007 SP3 installation from a command-line, and specify the upgrade option. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, move to the directory to which you extracted the Exchange 2007 SP3 installation files. For example, move to the C:\Exchange2007sp1files directory.
    3. Type setup.com /mode:upgrade, and then press ENTER. The Microsoft Exchange Server 2007 Unattended Setup program starts.
Note: The above procedures tested OK in LAB even if you remove all Exchange 2007 related services registry keys....
 
 

Send connector Intra-Organization SMTP Send Connector has failed to authenticate with your remote server IP:25. The response from the remote site is 454 4.7.0 Temporary authentication failure

In a Microsoft Exchange Server 2007 environment or in a Microsoft Exchange Server 2010 environment, some e-mail messages are stuck in a remote delivery queue that should have been transferred to another Exchange server in the Exchange organization. If you open the Queue Viewer tool from the Toolbox node on the Exchange Management Console, the Last Error field displays an error message that resembles the following:
 
Send connector Intra-Organization SMTP Send Connector has failed to authenticate with 172.18.102.95:25. The response from the remote site is 454 4.7.0 Temporary authentication failure
 
Event ID: 1035 is logged when some e-mail messages are stuck in a remote delivery queue in a Microsoft Exchange Server 2007 environment or in a Microsoft Exchange Server 2010 environment.
 
Cause: This issue occurs if the Exchange server cannot authenticate with the remote Exchange server. Exchange servers requires authentication to route internal user messages between servers. The issue can be caused by one of the following reasons:
  • The Exchange server is experiencing Time synchronization issues
  • The Exchange server is experiencing Service Principle Name (SPN) issues
  • The required TCP/UDP ports for the Kerberos protocol are blocked by the firewall.
To resolve this issue, follow these steps:
  1. Check the clock on both servers and domain controllers that might be used to authenticate the servers. All clocks should be synchronized to within 5 minutes of one other.
  2. Verify that the Service Principle Name (SPN) for SMTPSVC is registered correctly on the target server.
    • Make sure that the SMTP and SMTPSVC entries are added correctly to the machine account by using the SetSPN tool. For example:
      SetSPN -L <ExchangeServerName>
      SMTP/<ExchangeServerName>
      SMTP/<ExchangeServerName>.example.com
      SMTPSVC/<ExchangeServerName>
      SMTPSVC/<ExchangeServerName>.example.com
    • Check for duplicate SPNs by using the SetSPN tool. There should only be one entry of each:
      SetSPN -x
      Processing entry 0
      found 0 group of duplicate SPNs.
  3. Verify that the ports required for Kerberos are enabled.
  4. If the previous steps do not work, you can turn on logging for Kerberos on the Server that is registering the Event 1035 message, which may provide additional information. To do this, follow these steps:
    1. Click Start, click Run, type Regedit, and then click OK.
    2. Locate the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
    3. On the Edit menu, point to New, and then click DWORD Value.
    4. In the details pane, input the new value LogLevel, and then press Enter.
    5. Right-click LogLevel, and then click Modify.
    6. In the Edit DWORD Value dialog box, under Base, click Decimal.
    7. In the Value data box, type the value 1, and then click OK.
    8. Close Registry Editor.
    9. Again check the System Event log for any Kerberos errors.
Please note: Make all Exchange servers and all DCs. All clocks should be synchronized to within 5 minutes of one other.
 
ref:
 
 

Wednesday, July 20, 2011

How to Reindex Outlook 2007 or later

If you search for items in Microsoft Office Outlook 2007 or later and do not receive the results that you expect, the indexing of your Microsoft Windows and Microsoft Office system data files (the search catalog) may not be complete.
 
Symptoms of an incomplete index include the following:
Partial or no search results are returned.
Items that you expect to appear based on your search criteria are not displayed.
You can rebuild the search catalog, which restarts the indexing of your data files. The search catalog is a file where all of your Outlook and Microsoft Windows items (data files) are indexed. To rebuild your search catalog, do the following:
1.Exit Outlook.
2.In Microsoft Windows, click the Start button, and then click Control Panel.
3.Do one of the following:
 
1) Windows 7 Click Index Option
2) Windows Vista     Click System Maintenance, and then click Indexing Options.
    Note   In Classic view, double-click Indexing Options.
3) Microsoft Windows XP     Under See Also, click Other Control Panel Options, and then click Indexing Options.
    Note   In Classic view, double-click Indexing Options.
4.Click Modify, select the check boxes for the locations you want to index (Outlook), and then click OK.
5.Click Advanced.
6.Click Rebuild.
7.Restart Outlook.
If rebuilding the search catalog does not correct your search problem and retrieve the expected search results, see Instant Search is not finding all the items I expect for additional information.

Tuesday, July 19, 2011

Cannot delete Default Exchange 2010 Mailbox Database

When an Exchange 2010 mailbox role is installed, a default mailbox database is created. In Exchange 2007, the default database is named "Mailbox Database" whereas in 2010, it comes with a random numbering at the end of the "Mailbox Database" name since you cannot have the same Mailbox Database in your Org with multiple server environments. This is to make the mailbox database name unique. Mine is named "Mailbox Database 0683456784".
 
As most of the admins, your first instinct is to remove the default database and create ones with your company's naming convention or the names of your choice. You created a new database named "MDB1" and tried deleting the default one, only to be greeted with the error below.
 
"This mailbox database contains one or more mailboxes or arbitration mailboxes. Before you can remove this mailbox database, you must disable, move or remove user mailboxes and move arbitration mailboxes"
 
Technet explains arbitration mailboxes as the mailboxes used for managing approval workflow. For example, an arbitration mailbox is used for handling moderated recipients and distribution group membership approval.
 
You moved your user mailboxes to another database and ran the following command to find the arbitration mailboxes.
 
Get-Mailbox –Database "Mailbox Database 0683456784" –arbitration
 
You moved the arbitration mailboxes as well to the second database with the command below.
Get-Mailbox –Database "Mailbox Database 0683456784" –arbitration | New-MoveRequest – TargetDatabase MDB1
You confirmed that the arbitration mailboxes were successfully moved using the
Get-MoveRequest cmdlet.
Once the mailbox move was completed, you could delete your default database!
 

Friday, June 24, 2011

BES AgentOptimizeAlgorithm

I had been long looking for the feature to distribute agents evening to speed up mailbox scanning processing particular after we upgrade Exchange 2003 to Exchange 2007 a couple years ago. I was always told that sorry we cannot do that by RIM support. Finally I got the postive answer from RIM by editting register key.
 
By default, if you run MSDE, BES only supports two dynamic agents per server. If you run Full MS SQL edition for BES database, you can run as many as 20 agents (RIM recommends you should run less than 10 agents per BES). BES assigns users to agents per Exchange servers and up to 400 users per agent. Since we had migrated all 5000 user mailboxes to one Exchange 2007 CCR server, for about 700 users per BES HA, by default, it will allocate 400 users for two dynamic agents, the message delivery significantly delays whenever we failover BES (it could take about two hours to complete the sync) that made BES failover useless.
 
Now that after we have implemented AgentOptimizeAlgorithm, and changed from two agents to five agents for 800 users per HA server, message delivery delay has been reduced from 2 hours to 15 minutes.
 
Also if you use Exchange 2010, BES basically sees the CAS as the mailbox with 2010 (instead of the actual mailbox server the user is on, assuming you have installed the CAS on a separate server). Because of this, if you have multiple CAS behind a load balancer, it throws the "keep users from the same exchange server on the same BES" rule out. This is our situation and the guidance given to us by RIM is to implement the AgentOptimizeAlgorithm to 1 (simple algorithm) to randomly assign users to an Agent instead of keeping an Agent to one mail server:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Dispatcher.
DWORD value is 1 - the simple algorithm is used.
DWORD value is 2 - the complex algorithm is used.
The Default value is 2. a complex algorithm, Note: if you don't see the key, create the REG-Dword key.
 
Enabling Simple Messaging Agent Distribution Algorithm
 
The distribution algorithm can be changed with the DWORD registry key AgentOptimizeAlgorithm located in
32 bit - HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Dispatcher.
64bit - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Dispatcher.
DWORD value is 1 - the simple algorithm is used.
DWORD value is 2 - the complex algorithm is used.
The Default value is 2.
 
If the registry key does not exist, create it.
 
No advanced logic is used in this process.
 
BlackBerry smartphone users are simply distributed evenly across the number of agents specified in the DWORD registry key NumAgents located in:
32bit - HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents.
64bit - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Agents.
Default value is 5, do not increase it higher than 10.
Note: If the above registry keys do not exist, they need to be created.
 
Note: A maximum of 2 Messaging Agents will be created if the configuration database is on Microsoft SQL Database Engine (MSDE).  Move the configuration database to SQL 2005 Express using KB03112.
 
 After talking with RIM on this one, it is my understanding that if you are completely Exchange 2010 or 2007 (instead of mixed mode with 2003) and you have implemented EWS using the traittool on the global level (and not per server or agent) then you can completely uninstall MAPI since it is no longer being used (KEEP CDO THOUGH!). Of course I would test in a lab first, but this is what I intend to do after we are finished migrating to 2010.
 
Note: We run BES 5.0.3 HA with Intel Powerful processors (16 virtual processors with 32 GB RAM)