Exchange Server 2016

  1. The federation trust doesn't contain the same certificates published by the security token service in its federation metadata. ...
  2. The federation trust has changed to prepare for the usage of a new certificate for Federation. You should update all TXT ...
  3. The federation trust has changed to use a new certificate for Federation. You should update all TXT proof-of-ownership records ...
  4. The field %s contains an embedded null character. Data loss will occur if this value is translated to text.Do you want to ...
  5. The file "{0}" couldn't be found. You have to deploy this assembly again or disable the cmdlet extension agent that refers ...
  6. The file %4 is missing and could not be backed-up. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  7. The file %s is in use by another application. Setup can't determine which application(s) or service(s) is using this file, ...
  8. The file '{0}' isn't in the correct format for custom greetings. The file format must be 'PCM/16bit/8Khz/Mono', because there ...
  9. The file name that was supplied isn't valid. The file name must not be an absolute or relative path and should have a .wma ...
  10. The file name wasn't detected because there are some invalid characters in "{1}", the alias of mailbox {0}. Please provide ...
  11. The file system reports that the database file at %1 has a sector size of %2 which is greater than the page size of %3. This ...
  12. The file system reports that the database file at %4 has a sector size of %5 which is greater than the page size of %6. This ...
  13. The file system reports that the log file at %1 has a sector size of %2 which is unsupported, using a sector size of 4096 ...
  14. The file system reports that the log file at %4 has a sector size of %5 which is unsupported, using a sector size of 4096 ...
  15. The file version of '%1' installed on the local server is not current. Looking at servers in the site for a current version. ...
  16. The file version of '%1' installed on the local server is not current. Unable to locate a correct version on any server in ...
  17. The file you are installing is older than the file it will replace. Do you want to continue installing and remove the existing ...
  18. The FIP-FS Filtering Management Service was unable to acquire a scanner within the specified timeout. The process will be ...
  19. The FireWall probe has failed at least {0} times in last {1} seconds. Please reboot the machine once the network is recovered. ...
  20. The first argument in SipCultureInfo.CreateInstance should be a System.Globalization.CultureInfo object, not a derivative. ...
  21. The first Exchange Mailbox server installation in an Exchange 2000 or Exchange 2003 organization requires that you enable ...
  22. The folder couldn't be moved between the mailboxes of different users. Please select a target mailbox and source mailbox ...
  23. The folder couldn't be moved into the same mailbox. Please select a target mailbox that is different from the source mailbox. ...
  24. The folder hierarchy is in an inconsistent state because the destination mailbox doesn't contain the source folder '{0}'. ...
  25. The folder name can be modified only for a Managed Custom Folder. You cannot modify the folder name for managed default folder. ...
  26. The FolderType attribute on the managed folder {0} has changed in the Active Directory. The folder type changed from {1} ...
  27. The following accepted domains '{0}' don't have an Outbound Connector to deliver mail to your On-premise mail servers. Make ...
  28. The following categories of clients have latencies greater than the threshold value of {2} ms: {1}, as reported by the performance ...
  29. The following custom prompt files were not found for UM dial plan "%1": "%2". If new custom prompt files have been published ...
  30. The following DAGs will be excluded from DAG selector. DAGs that don't meet the minimum active hub servers restriction: %1. ...
  31. The following error occurred while processing %1. %2. The meeting request couldn't be processed. Correct the problem and ...
  32. The following error occurred while reporting client data. The root cause may be that the server has not been upgraded to ...
  33. The following error was received while removing the Organization Management role group : {0}. You need to remove the group ...
  34. The following folders in mailbox '%1' have items that exceed the message size limit in the archive. The oversized items will ...
  35. The following message tracking log file is corrupted: '%1'. The corrupted record won't be included in the search results. ...
  36. The following messages were loaded at startup before Transport crashed. To avoid further crashes, it is recommended that ...
  37. The following Microsoft Exchange 2003 back-end servers aren't enabled for Outlook Anywhere. If you want to enable them, use ...
  38. The following objects are still critical on server '{1}', even after attempting to move them off: `n{0}). Errors from Move ...
  39. The following options control whether this tool will automatically check the Web for a newer version of the configuration ...
  40. The following parameters on the "{1}" management role entry of the "{0}" management role can't be removed because they don't ...
  41. The following parameters that you tried to add to the "{1}" management role entry on the "{0}" management role can't be added ...
  42. The following parameters that you tried to add to the "{1}" management role entry on the "{0}" management role can't be added ...
  43. The following properties cannot change on a Provisioned server: StaticDomainControllers, StaticGlobalCatalogs, StaticConfigDomainController, ...
  44. The following ProxyAddresses were not provisioned since they are already used by some existing Users: ProxyAddress | Existing ...
  45. The following retention policies already exist and are different than those in the file:{0} These policies will be updated ...
  46. The following retention tags already exist and are different than those in the file:{0} These tags will be updated with the ...
  47. The following rule(s) reference more than {0} distinct regular expression text processor(s) and may impact performance: {1}. ...
  48. The following rule(s) reference more than {0} terms from distinct custom keyword text processor(s) and may impact performance: ...
  49. The following servers have been added to the database availability group but not to the cluster: {0}. This is usually the ...
  50. The following servers in the Windows Failover Cluster are not in Active Directory: {0}. This is usually the result of an ...
  51. The following users can't be added to the owners or members list: {0}. Individual users can be added, but distribution groups ...
  52. The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install ...
  53. The format "{0}" is incorrect. Use the format "Prefix Suffix", where Prefix and Suffix can contain text strings or any of ...
  54. The format of '{0}' is invalid. ConfiguredAttributes properties must be specified as "name, type", where "name" is the name ...
  55. The format of '{0}' is invalid. ConfiguredAttributes properties must be specified as "name, type", where "name" is the name ...
  56. The format of the recipient e-mail address isn't valid. Valid SMTP e-mail addresses can contain only letters, numbers, hyphens, ...
  57. The format of the recipient email address isn't valid. Valid SMTP email addresses can contain only letters, numbers, hyphens, ...
  58. The format of the secondary address {0} isn't valid. The secondary address must be a valid extension or an E164 number (for ...
  59. The format of the SIP resource identifier that you specified isn't valid. Use the format in the following example: [email protected]. ...
  60. The format you provided, "{0}", is unknown. The correct format is "X509: CN=Issuer CN=Subject". Note that the issuer part ...
  61. The forms-based authentication public time-out value is currently {0} and the private time-out value is {1}. The public time-out ...
  62. The forms-based authentication setting of path {0} (metabase property id {1}) couldn't be modified. Are you sure you have ...
  63. The frequency at which each sample is taken. Typical values would be 30 seconds, one minute, or five minutes; under normal ...
  64. The fully qualified domain name (FQDN) of the local computer matches the SMTP address of recipient policy '{0}'. Setup can't ...
  65. The fully qualified domain name (FQDN) value on the default receive connector named '{3}' on server {2} has been changed. ...
  66. The fully qualified name of this computer ("%s") matches the SMTP domain in the recipient policy "%s". You must rename this ...
  67. The fully-qualified domain name of SMTP virtual server '{3}' on server {2} does not match the DNS resolved server name. This ...
  68. The fully-qualified domain name of SMTP virtual server '{3}' on server {2} does not match the fully-qualified domain name ...
  69. The Function Call log (FCL) shows that the {0} process experienced long wait times in calls to the directory. Please check ...
  70. The Function Call log (FCL) shows {1} in progress calls to Virus Scanner, and there are only {2} threads available for virus ...
  71. The generation of the quarantine message may fail because of an error reading the spam quarantine mailbox configuration from ...
  72. The geocoordinates in '{0}' has an invalid format. You must specify either "latitude;longitude" or "latitude;longitude;altitude". ...
  73. The global '{3}' limit used by Exchange Server 2003 and Exchange 2000 Server conflicts with the corresponding organization ...
  74. The goal for Time-Based Assistants is to process 99% of interested and viable mailboxes within the workcycle time interval ...
  75. The goal for Time-Based Assistants is to process 99% of interested and viable mailboxes within the workcycle time interval ...