System Center Configuration Manager 2007

  1. ConfigMgr can poll Active Directory to discover containers to which systems assigned in this site belong. Specify how often ...
  2. ConfigMgr can poll Active Directory to discover security groups and the containers in which they belong. Specify how often ...
  3. ConfigMgr can poll Active Directory to discover security groups and the containers in which they belong. Specify how often ...
  4. ConfigMgr can poll Active Directory to discover users and the containers in which they belong. Specify how often to poll ...
  5. ConfigMgr cannot create the specified folder. Refresh the Configuration Manager console and try to create the folder again. ...
  6. ConfigMgr cannot delete the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  7. ConfigMgr cannot delete the specified object. Please verify that you have delete access to the selected object and refresh ...
  8. ConfigMgr cannot export the list of items. Verify that you can write to the output file and that there is sufficient drive ...
  9. ConfigMgr cannot import the specified driver folder. Verify that the folder exists in the specified location and that both ...
  10. ConfigMgr cannot import the specified driver. Verify that the driver exists in the specified location and that the SMS Provider ...
  11. ConfigMgr cannot move the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  12. ConfigMgr cannot move the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  13. ConfigMgr cannot move the specified item(s). Refresh the ConfigMgr Administrator console to verify that another administrator ...
  14. ConfigMgr cannot rename the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  15. ConfigMgr Clients must have the Windows Update Agent installed before they can install updates. We recommend that you let ...
  16. ConfigMgr could not provide the data that you requested. Please refer to the ConfigMgr documentation for troubleshooting ...
  17. ConfigMgr could not update image properties because of the following error: {0} Please confirm that the ConfigMgr provider ...
  18. ConfigMgr failed to connect to the site server's certificate store to validate the certificate based on the thumbprint you ...
  19. ConfigMgr has detected a record that might be conflicting with the following client record in the site database: %1.%12 Possible ...
  20. ConfigMgr has detected that this record has the same hardware ID as an existing client record. You can create a new record ...
  21. ConfigMgr installation cannot complete until the required component, MMC 3.0, is installed. MMC 3.0 is available for download ...
  22. ConfigMgr Service Manager ConfigMgr Service Manager ConfigMgr Service Manager.Document ConfigMgr Service Manager Document ...
  23. ConfigMgr site component manager has exceeded the timeout value. This might be due to slow network response or failure of ...
  24. ConfigMgr sites earlier than version 2.0 SP5 cannot sign data. If you select to not accept unsigned data, sites using an ...
  25. ConfigMgr stopped downloading the following software when this computer disconnected from the private network for your organization. ...
  26. ConfigMgr was unable to complete the action you requested. Object: {0} Verify that the object exists and that you have the ...
  27. ConfigMgr will automatically assign the next available drive letter to this partition. To save this drive letter as a task ...
  28. Configuration data will be collected from the selected reference site to recover any collections, packages, and advertisements ...
  29. Configuration Manager Active Directory schema extensions are not required, for site server installation, but are recommended ...
  30. Configuration Manager cannot access the node you requested. You might be using a customized version of the Configuration ...
  31. Configuration Manager Client has encountered an error while computing compliance based on the selected software updates. ...
  32. Configuration Manager Client has installed a software update that requires a reboot but has been paused by Task Sequence ...
  33. Configuration Manager Client has successfully completed computing compliance based on selected software updates for NAP enforcement. ...
  34. Configuration Manager Client is not in remediation. The client could be compliant with the required software updates or in ...
  35. Configuration Manager Client remediation has detected that there are no software updates that are marked for NAP enforcement. ...
  36. Configuration Manager clients will not download and run package files that are not properly signed. If this rule does not ...
  37. Configuration Manager does not have administrator privileges to the SQL Server. Administrator privileges are required in ...
  38. Configuration Manager hierarchies do not support SMS 2003 Legacy Clients. Any existing Legacy Clients in the site to be upgraded ...
  39. Configuration Manager requires Microsoft SQL Server 2005 SP2 or later. You must upgrade SQL Server %s before installing Configuration ...
  40. Configuration Manager requires Microsoft SQL Server 2005 SP2 or later. You must upgrade SQL Server before installing Configuration ...
  41. Configuration Manager requires that the SQL Server database collation settings of the tempdb database and site database are ...
  42. Configuration Manager Setup requires that site server computer possess administrative rights on the SQL Server and management ...
  43. Configuration Manager Setup requires that the Admin$ administrative share is present on the site system. Setup either could ...
  44. Configuration Manager Setup requires that the logged on user account possess administrative rights on the management point ...
  45. Configuration Manager site server installation requires Windows Server 2003 Service Pack 1 or later. Configuration Manager ...
  46. Configuration Manager site systems may encounter errors without this update. This update applies to Windows Server 2003 SP1 ...
  47. Configuration Manager site systems may encounter WMI enumeration errors without this update. This update applies to Windows ...
  48. Configuration Manager sites have only one security mode. That mode is equivalent to SMS 2003 advanced security mode. All ...
  49. Configuration Manager software update points require Windows Server Update Services (WSUS) version 3.0 or later. If using ...
  50. Configuration Manager System Health Agent facilitates enforcement of software update compliance using Network Access Protection. ...
  51. Configuration Manager System Health Validator failed to find the correct Configuration Manager enumerator in Active Directory. ...
  52. Configuration Manager System Health Validator failed to located the Configuration Manager Container in Active Directory. ...
  53. Configuration Manager System Health Validator failed to lookup the appropriate validation information for the incoming Configuration ...
  54. Configuration Manager System Health Validator has detected that Active Directory is not extended for Configuration Manager. ...
  55. Configuration Manager System Health Validator has detected that Configuration Manager Cache Store is improperly formatted. ...
  56. Configuration Manager System Health Validator has determined that Configuration Manager client is missing SMS SoH information. ...
  57. Configuration Manager System Health Validator has determined that Configuration Manager client's compliance state is Client ...
  58. Configuration Manager System Health Validator has determined that Configuration Manager client's compliance state is Invalid. ...
  59. Configuration Manager System Health Validator has determined that Configuration Manager client's compliance state is Unknown. ...
  60. Configuration Manager System Health Validator has determined that Configuration Manager client's Statement of Health has ...
  61. Configuration Manager System Health Validator has determined that Configuration Manager client's Statement of Health is invalid. ...
  62. Configuration Manager System Health Validator has determined that the Configuration Manager client is non-compliant because ...
  63. Configuration Manager System Health Validator has determined that the Configuration Manager client is non-compliant because ...
  64. Configuration Manager System Health Validator has determined that the Configuration Manager client is non-compliant because ...
  65. Configuration Manager System Health Validator has encountered an invalid Configuration Manager data type in Active Directory. ...
  66. Configuration Manager System Health Validator has encountered Server component failure when verifying Configuration Manager ...
  67. Configuration monitoring for the selected baselines will be disabled. This will affect all existing assignments of the baselines. ...
  68. Configuration of the background intelligent transfer service (BITS) policy will not be applied because BITS is not installed ...
  69. Configures settings and polling intervals to discover resources on the network like subnets, SNMP-enabled devices, and DHCP ...
  70. Content download for the package "%1" - "%2" failed. The download failed because Branch DP was unable to create directory ...
  71. Content download for the package "%1" - "%2" failed. The download failed because either there was not enough disk space to ...
  72. Content download for the package "%1" - "%2" failed. The download failed because no NTFS partition is available. Please specify ...
  73. Content download for the package "%1" - "%2" failed. The download failed because the content downloaded to the client does ...
  74. Content download for the package "%1" - "%2" has failed. The download failed because Branch DP was unable copy content to ...
  75. Content download for the package "%1" - "%2" has failed. The download failed because Branch DP was unable to create share ...