System Center Configuration Manager 2007

  1. The content for "%4" - "%2" can not be located. This SMS client will attempt to locate this content again. Possible cause: ...
  2. The content for "%4" - "%2" could not be located. This SMS client will no longer attempt to locate this content. Possible ...
  3. The content for "%4" - "%2" has been removed from the cache. This content has been deleted because either the cache has been ...
  4. The content source location that you have entered is invalid. Please ensure that the source location is not the same as the ...
  5. The contents hash for baseline content %4 (%3), version %5 provided in policy does not match with the contents downloaded.%0 ...
  6. The contents of the cache have been cleared by user request. The cache is currently located at %3 and %7 MB of space is allocated.%0 ...
  7. The control 3 on dialog 2 can accept property values that are at most 5 characters long. The value 4 exceeds this limit, ...
  8. The control 3 on dialog 2 needs the icon 4 in size 5]x[5], but that size is not available. Loading the first available size ...
  9. The control 3 on dialog 2 received a browse event, but there is no configurable directory for the present selection. Likely ...
  10. The Copy Packages Wizard completed copying the following packages to the destination distribution point. However there are ...
  11. The current query statement will return all system resources that you have access to in the ConfigMgr database. Depending ...
  12. The currently logged-in user does not have rights to access the client machine. You must provide the username, domain, and ...
  13. The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was not signed ...
  14. The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed ...
  15. The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed ...
  16. The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed ...
  17. The database must already exist on the SQL Server. The minimum database size is %d MB, the transaction log size should be ...
  18. The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and ...
  19. The Delete Inactive Client Discovery Data task has completed, %1 inactive clients have been removed from the database.%12%0 ...
  20. The Delete Obsolete Client Discovery Data task has completed, %1 obsolete clients have been removed from the database.%12%0 ...
  21. The delta site control file %1 contains a corrupt site configuration change request. This site configuration change request ...
  22. The delta site control file %1 contains a site configuration change request submitted by the "%2" SMS Provider client running ...
  23. The delta site control file %1 contains a site configuration change request submitted by the server component "%2" running ...
  24. The delta site control file %1 contains a site configuration change request that is missing a "%2" item, or that item is ...
  25. The deployment package contains the software update files that will be available to clients as part of the deployment. Select ...
  26. The deployments to the collection are listed below. Deleting the collection will also delete these deployments, so clients ...
  27. The desired configuration management client agent is not enabled for this site. You must enable the desired configuration ...
  28. The desired configuration management client agent is not enabled for this site. You must enable the desired configuration ...
  29. The destination folder is not on a valid local drive or is encrypted. Ensure that the folder is on a local NTFS drive and ...
  30. The destination specified is not valid. Either specify local absolute path (Example: c:\bkupdest) or UNC path to a network ...
  31. The details associated with the address type must be specified before this address can be used. To specify the details for ...
  32. The details associated with the sender type must be specified before this sender can be used. To specify the details for ...
  33. The Device Client can only download from BITS-enabled distribution points. Please enable BITS on the following selected distribution ...
  34. The directory path contains illegal characters. The following characters are not allowed in the directory path: " + , / ; ...
  35. The directory path is limited to between 1 and 255 characters. The path you have entered does not meet this qualification. ...
  36. The distribution point group you specified does not exist. Check the distribution point group name and specify an existing ...
  37. The distribution point group you specified does not exist. Check the distribution point group name and specify an existing ...
  38. The distribution point group you specified does not exist. Check the distribution point group name and specify an existing ...
  39. The distribution points not currently storing the package are listed below. Select the distribution points you want to copy ...
  40. The distribution share name specified for this package is already in use by the %1 package. Each package must have a unique ...
  41. The distribution share name specified for this package is already in use by the {0}-{1} package. Each package must have a ...
  42. The drive letter you specified is a mapped drive rather than a local drive on the site server. Specify a local drive on the ...
  43. The file '%1' is a system file. If you remove it, your computer or one of your programs may no longer work correctly. %3 ...
  44. The File Cache Store could not be persisted to disk properly. This will potentially cause the ConfigMgr System Health Validator ...
  45. The file cache store in the System Health Validator point failed to initialize properly. The error encountered was %1.%0 ...
  46. The File Cache Store update failed. This will potentially cause the ConfigMgr System Health Validator to not validate the ...
  47. The file name is limited to between 1 and 255 characters. The file name you have entered does not meet this qualification, ...
  48. The file that you selected does not have header information, so ConfigMgr cannot read the name or version number from the ...
  49. The filename is limited to between 1 and 255 characters. The filename you have entered does not meet this qualification, ...
  50. The files you have selected for import contain updates to the following configuration items and baselines already in the ...
  51. The first character must be a letter (A to Z or a to z) or the symbol "_". Characters following the first character can include ...
  52. The folder '%1' is a system folder. If you delete it, Windows or another program may no longer work correctly. Are you sure ...
  53. The following Active Directory sites exist in this site server's forest. Select an Active Directory site to use it as a ConfigMgr ...
  54. The following configuration types are available. Configuration types vary by platform, so consider this when making your ...
  55. The following driver will be permanently removed from the driver catalog. This driver will no longer be available for computers ...
  56. The following file(s) contain invalid or inconsistent data. Possible causes could be: Malformed xml data. Invalid schema. ...
  57. The following rules contain configuration items and configuration baselines to define how compliance will be assessed on ...
  58. The following software updates are available for installation. Mandatory software updates will automatically install on the ...
  59. The following software updates have been targeted for installation. However, a system restart is currently in progress and ...
  60. The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration ...
  61. The format for this field is: \ \ \ . The server name may be up to 15 chars and may not include any of the following chars: ...
  62. The FQDN for the public and private DNS servers is the same. It is recommended that you do not use the same FQDN internally ...
  63. The Internet Information Server (IIS) default website is not running on the destination computer. The default website must ...
  64. The item you have selected is not available. You do not have rights to the object, the ConfigMgr database or reporting point ...
  65. The license count for a product was truncated to 2,147,483,647. "%5" licenses were lost for product "%1" ("%2","%3","%4").%12%0 ...
  66. The licensed product "%1" (version "%2") is inactive on the computer "%3" (User: "%4", Time: "%5", Software metering server: ...
  67. The list below shows the prompts used in the SQL statement that returns the data in the report. You can view the SQL statement ...
  68. The list below shows the reports and dashboards that link to this report. When you change the prompts in this report, you ...
  69. The list below shows the values that are currently available for the view and column you selected. Select the value that ...
  70. The list of applications to install consists of a series of task sequence variables with a common base name plus a numeric ...
  71. The list of CAPs from the site control file has been written to the file %1. Either CAPs in the site control file have changed, ...
  72. The list of CAPs in the site control file is empty.%12 If you want to specify CAPs, use the SMS Administrator console, Site ...
  73. The local directory for the software metering server files, "%1", is in an unrecognizable format. The software metering server ...
  74. The location to log status you entered is not valid. Please enter a location of the form: \Server\DirectoryPath\Filename ...
  75. The location to log status you entered is not valid. Please enter a location of the form: \Server\DirectoryPath\FileName ...