System Center Configuration Manager 2007

  1. The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the SMS ...
  2. The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting ...
  3. The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting ...
  4. The "%1" item in the actual site control file %2 does not contain a "%3" item named "%4", or that item is corrupt. As a result, ...
  5. The "%1" namespace has been removed or has become corrupted.%12 Possible cause: The SMS Hardware Inventory Agent cannot continue ...
  6. The %1 package is currently set as not having source files. You can create this access account, but doing so will have no ...
  7. The %1 SMS client application on the local computer did not respond to SMS Site Backup's stop request.%12 Possible cause: ...
  8. The %1 SMS client application on the local computer did not respond to SMS Writer's stop request.%12 Possible cause: %1 is ...
  9. The Active Directory (AD) Cache Client failed to search the AD Forest for NAP-related ConfigMgr Health Information. The error ...
  10. The Active Directory forest designed to store the Configuration Manager health state references has not been extended with ...
  11. The active software update point communicates with the Windows Server Update Services(WSUS) server, configures software updates ...
  12. The actual site control file %1 does not contain a "%2" item.%12 Solution: The SMS server components cannot run without this ...
  13. The actual site control file %1 does not exist.%12 Solution: The SMS server components cannot function without this file. ...
  14. The Add Boot Image Wizard could not be successfully completed. The wizard detected the following problems when creating a ...
  15. The Add Operating System Image Wizard could not be successfully completed. The wizard detected the following problems when ...
  16. The add operating system install package wizard could not be successfully completed. The wizard detected the following problems ...
  17. The address to site "%1" is invalid.%12 Possible cause: The destination share name is missing. Solution: Define a valid address ...
  18. The address to site "%1" is invalid.%12 Possible cause: The destination site server name is missing. Solution: Define a valid ...
  19. The addresses from the parent site to the new site are shown below. ConfigMgr will select the addresses in priority order ...
  20. The advertised program is currently marked as disabled so its advertisements will not be displayed or run. Do you want to ...
  21. The advertised program is currently marked as disabled so its advertisements will not be displayed or run. Do you want to ...
  22. The Advertised Programs client agent has not been enabled for this ConfigMgr site so advertisements to clients at this site ...
  23. The Advertised Programs client agent has not been enabled for this ConfigMgr site so advertisements to clients at this site ...
  24. The advertisement "%1" ("%4" - "%5") failed to locate the package content on a distribution point that is not on the internet. ...
  25. The advertisement "%1" ("%4" - "%5") is waiting for package content from an Intranet-based Distribution Point. The system ...
  26. The advertisements of the program are listed below. Deleting the program will also delete these advertisements, so clients ...
  27. The advertisements to the collection are listed below. Deleting the collection will also delete these advertisements, so ...
  28. The agent encountered an error while querying WMI to collect data from this computer. The first query to fail was "%1".%12%0 ...
  29. The agent has not collected files matching the file name "%1" or the path "%2" from this computer because the files exceed ...
  30. The application could not remove the unsummarized use of licensed product "%1" version "%2" ("%3", "%4", "%5", "%6").%12%0 ...
  31. The application could not remove the unsummarized use of unlicensed product "%1" version "%2" ("%3", "%4", "%5", "%6").%12%0 ...
  32. The application could not update the summarized use of licensed product "%1" version "%2" ("%3", "%4", "%5", "%6").%12%0 ...
  33. The application could not update the summarized use of unlicensed product "%1" version "%2" ("%3", "%4", "%5", "%6").%12%0 ...
  34. The baselines to the collection are listed below. Deleting the collection will also delete these baselines, so clients will ...
  35. The basic SMS client services were successfully installed on this computer.%12 The SMS Client Component Installation Manager ...
  36. The boot image will be removed from the references of the following task sequences. Please go to the Task Sequence Properties ...
  37. The cache location has been modified. The cache was previously located at %2. The cache is now located at %3. The current ...
  38. The capture process must be started from the operating system you wish to capture. Please reboot the machine and re-run the ...
  39. The category "{0}" exceeds the maximum length allowed for the category name. Only the first 512 characters will be used while ...
  40. The category {0} has been assigned to one or more configuration items or baselines. Are you sure you want to delete the selected ...
  41. The certificate information from the selected certificate file could not be loaded. Verify that the certificate file is valid. ...
  42. The class alias you have selected can be joined to the existing query in more than one way. Please create this class alias ...
  43. The class alias you have selected has no known relationship with those in the existing query. Please create this class alias ...
  44. The Clear Install Flag for Undiscovered Clients task has completed, %1 rows have been updated in system discovery tables.%12%0 ...
  45. The Client Access License Usage Data Summarization task has completed, %1 rows have been added or updated in the summary ...
  46. The client configuration items from the site control file were written to the files %1 and %2. Either the SMS Service generated ...
  47. The client connection account %s that you have specified on Setup command line or in the SMSAccountSetup.ini file does not ...
  48. The client failed to compile one or more policies. For more information see PolicyAgentEvaluator.log on the client machine. ...
  49. The client installation package version published to WSUS is incorrect and does not match the actual client version installed ...
  50. The collection cannot be deleted from the database because it contains one system which is currently serving as a branch ...
  51. The collection name you have entered is already in use in the ConfigMgr environment. Please enter a unique collection name. ...
  52. The collections listed have query rules that are limited to the collection being deleted. Deleting the collection will also ...
  53. The combination of IP address and subnet mask is invalid. All of the bits in the host adapter portion of the IP address are ...
  54. The component raised an exception but failed to handle it and will be stopped immediately. Component name: %1 Executable: ...
  55. The condition can no longer be edited and will need to be created using the new format. To create a new condition select ...
  56. The ConfigMgr Administrator console could not connect to the ConfigMgr site database because of missing or incomplete registration ...
  57. The ConfigMgr Administrator console could not connect to the ConfigMgr site database because the registration information ...
  58. The ConfigMgr Administrator console could not connect to the ConfigMgr site database. Use a registry editor to verify that ...
  59. The ConfigMgr Administrator console could not connect to the ConfigMgr site database. Use a registry editor to verify that ...
  60. The ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify that the ConfigMgr Administrator ...
  61. The ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify your user has read permissions ...
  62. The ConfigMgr administrators who can view resources in the collection are listed below. If the resources are not in other ...
  63. The ConfigMgr Advanced Client received policy that could not be verified. For more information see PolicyAgent.log on the ...
  64. The ConfigMgr Advanced Client rejected the site server signing certificate due to a revocation-related failure (%1).%12%0 ...
  65. The ConfigMgr Advanced Client rejected the site server signing certificate due to an expiration-related failure (%1).%12%0 ...
  66. The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity ...
  67. The ConfigMgr database will be created using the SQL Server default settings which may not be optimal for your installation. ...
  68. The ConfigMgr Microsoft Updates Inventry Tool is already installed. To install this version please uninstall the previous ...
  69. The ConfigMgr Provider reported an error connecting to the ConfigMgr site database server. Verify that the SQL Server is ...
  70. The ConfigMgr System Health Validator Registry Settings failed to get loaded properly. This will prevent the ConfigMgr System ...
  71. The Configuration Manager 2007 Setup Wizard could not be completed. You can review the ConfigMgrSetup.log and ConfigMgrPrereq.log ...
  72. The console cannot display the selected node. Verify that the node is displayed in the console tree and that you have rights ...
  73. The content "%1" - "%2" could not be deleted from the share %3. One or more files may be in use, or the system may not have ...
  74. The content downloaded can't be trusted as unable to verify the certificate attached to the content, or no certificate was ...
  75. The content downloaded can't be trusted, unable to verify the certificate attached to the content, or no certificate was ...