Exchange Server 2010

  1. CAS Intra-Site Redirection Later to Earlier Version is the number of times that users are redirected within the same site ...
  2. Categorizer directory logon failure count exceeds an average of {7} per day for SMTP instance '{3}' on server {2}. There ...
  3. Categorizer directory service failure count exceeds an average of {7} per day for SMTP instance '{3}' on server {2}. There ...
  4. Categorizer non-retryable error count exceeds an average of {7} per day for SMTP instance '{3}' on server {2}. There may ...
  5. Categorizer out of memory failure count exceeds an average of {7} per day for SMTP instance '{3}' on server {2}. There may ...
  6. Categorizer retryable error count exceeds an average of {7} per day for SMTP instance '{3}' on server {2}. There may be a ...
  7. Causes the script to raise events reporting the status of each database; MSExchangeRepl event 4114 if the database has sufficient ...
  8. Caution: Because passwords are sent in clear text, you should configure a secure channel (SSL) to encrypt data transferred ...
  9. Change the scope Select Default to use the implicit write scope for each assigned role, or select an existing custom scope. ...
  10. Changes have been made to the xml file '{0}'. To protect your system the file will not be loaded. To make the {1} page visible ...
  11. Changes made to recipients while using the forest scope may not be immediately viewable in the result pane or when filtering ...
  12. Changes made to recipients while using the forest scope may not be immediately viewable in the result pane or when filtering ...
  13. Changes to the Exchange ActiveSync mailbox policy couldn't be saved because the application list is either larger than {0} ...
  14. Changes to the master category list can't be saved because changes made to it by another client couldn't be read. Use the ...
  15. Changes to {0} will only take effect after the Microsoft Exchange Unified Messaging service is restarted on server {1}. {2} ...
  16. Changing the account namespace of an existing federation trust will result in new federated accounts being created in Windows ...
  17. Changing the FQDN to "{0}" requires updating databases currently configured to use the old FQDN. To fix the affected databases ...
  18. Changing the FQDN to "{0}" requires updating databases currently configured to use the old FQDN. To fix the affected databases ...
  19. Character sets Sets are lower- and upper-case letters, numbers, and symbols. To require passwords that include characters ...
  20. Check the server configuration for this service. For example, check the capabilities that the server supports. You can use ...
  21. Check the server configuration for this service. For example, check the capabilities that the server supports. You can use ...
  22. Check whether there are common destinations shared by messages in the 'Local delivery' queue (this step is conducted only ...
  23. Check whether there are common destinations shared by messages in the queue (this step is conducted only when the server ...
  24. Checkpoint depth for storage group '{3}' on server {2} is not set to the recommended value of 5242880 (5 MB) on this cluster. ...
  25. Checks that databases have enough configured and healthy copies. Active and passive copies are both counted; a mounted copy ...
  26. Choose how mail will be handled. Rules will be applied in the order shown. If you don't want a rule to run, you can turn ...
  27. Choose how your calls will be handled when you don't answer the phone. Calls will be answered with a system-generated greeting ...
  28. Circular logging for Database '{3}' on server {2} is enabled. This configuration only supports the recovery of database {3} ...
  29. Circular logging for Database {3} on server {2} is enabled. This configuration only supports the recovery of database {3} ...
  30. Circular logging for storage group '{3}' on server {2} is disabled and this is a front-end server. Front-end servers do not ...
  31. Circular logging for storage group '{3}' on server {2} is disabled. If this is a bridgehead or message routing server, circular ...
  32. Circular logging for storage group '{3}' on server {2} is enabled. This configuration will not provide good recovery options ...
  33. Circular logging parameter change will not be applied on this database before it is remounted. Dismount and remount database ...
  34. Cleanup has completed on deleted mailboxes that are past the retention date on database %5. %1 deleted mailboxes (%2 KB) ...
  35. Cleanup has completed on deleted mailboxes that are past the retention date on database %5. %1 deleted mailboxes (%2 KB) ...
  36. Cleanup of content index failed items is complete. Mailbox Database: %1 Items Scanned: %2 Items Cleaned: %3 Cleanup Time ...
  37. Cleanup of content index failed items is complete. Mailbox Database: %1 Items Scanned: %2 Items Cleaned: %3 Cleanup Time ...
  38. Cleanup of items past retention date for Item Recovery is complete for database %5. Start: %1 items; %2 Kbytes End: %3 items; ...
  39. Cleanup of items past retention date for Item Recovery is complete for database %5. Start: %1 items; %2 Kbytes End: %3 items; ...
  40. Cleanup of the DeliveredTo table for database '%1' detected an entry with an invalid submission time. However, the message ...
  41. Cleanup of the DeliveredTo table for database '%1' detected an entry with an invalid submission time. However, the message ...
  42. Cleanup of the DeliveredTo table for database '%1' failed with error %2. %3 entries were purged (out of %4 entries visited) ...
  43. Cleanup of the DeliveredTo table for database '%1' failed with error %2. %3 entries were purged (out of %4 entries visited) ...
  44. Cleanup of the DeliveredTo table for database '%1' removed an entry with an invalid submission time and/or message delivery ...
  45. Cleanup of the DeliveredTo table for database '%1' removed an entry with an invalid submission time and/or message delivery ...
  46. Cleanup of the DeliveredTo table for database '%1' was preempted because the database engine's version store was growing ...
  47. Cleanup of the DeliveredTo table for database '%1' was preempted because the database engine's version store was growing ...
  48. Cleanup of the Event History table for database '%1' failed with error %2. %3 entries were purged (out of %4 visited) before ...
  49. Cleanup of the Event History table for database '%1' failed with error %2. %3 entries were purged (out of %4 visited) before ...
  50. Cleanup of the Event History table for database '%1' was preempted because the database engine's version store was growing ...
  51. Cleanup of the Event History table for database '%1' was preempted because the database engine's version store was growing ...
  52. Cleanup of the Event History Watermarks table for database %1 was successful. %2 entries were purged (out of %3 visited). ...
  53. Cleanup of the Event History Watermarks table for database %1 was successful. %2 entries were purged (out of %3 visited). ...
  54. Cleanup of the Event History Watermarks table for database '%1' failed with error %2. %3 entries were purged (out of %4 visited) ...
  55. Cleanup of the Event History Watermarks table for database '%1' failed with error %2. %3 entries were purged (out of %4 visited) ...
  56. Cleanup of the Event History Watermarks table for database '%1' was pre-empted because the database engine's version store ...
  57. Cleanup of the Event History Watermarks table for database '%1' was pre-empted because the database engine's version store ...
  58. Cleanup of the Folder Tombstone table for database '%1' failed with error %2. %3 entries were purged before the failure was ...
  59. Cleanup of the Folder Tombstone table for database '%1' failed with error %2. %3 entries were purged before the failure was ...
  60. Cleanup of the Folder Tombstone table for database '%1' was preempted because the database engine's version store was growing ...
  61. Cleanup of the Folder Tombstone table for database '%1' was preempted because the database engine's version store was growing ...
  62. click '{1}', and then select the file. After you've selected the file, click '{2}'. The file will be uploaded to your message. ...
  63. Click Add to add a server to this database availability group, or select an existing member, and click the X to remove the ...
  64. Click Cancel to go back to the message compose view and remove the recipients who don't have digital IDs or to remove message ...
  65. Client Access server "%1" couldn't find a Client Access server of version %2 to redirect traffic for mailbox "%3" within ...
  66. Client Access server "%1" couldn't find a Client Access server of version %2 to redirect traffic for mailbox "%3" within ...
  67. Client Access server "%1" couldn't find a Client Access server of version %2 to redirect traffic for mailbox "%3". Outlook ...
  68. Client Access server "%1" couldn't find a Client Access server of version %2 to redirect traffic for mailbox "%3". Outlook ...
  69. Client Access server "%1" tried to proxy or redirect Outlook Web App traffic for mailbox "%2". This failed because one of ...
  70. Client Access server "%1" tried to proxy or redirect Outlook Web App traffic for mailbox "%2". This failed because one of ...
  71. Client Access server "%1" tried to proxy Outlook Web App traffic to "%2". This failed because "%2" couldn't verify that the ...
  72. Client Access server "%1" tried to proxy Outlook Web App traffic to "%2". This failed because "%2" couldn't verify that the ...
  73. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because "%2" didn't ...
  74. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because "%2" didn't ...
  75. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because "%2" didn't ...