System Center Configuration Manager 2012 R2

  1. Computer clock synchronization between {0} and {1} exceeds maximum tolerance level of 5 minutes. The computer clocks on these ...
  2. Computer name: {1} Domain: {2} Detection time(UTC time): {3} Malware file path: {4} Remediation action: {5} Action status: ...
  3. Computer name: {1} Malware names: {2} Last detection time(UTC time): {3} Detection interval (minutes): {4} Number of infections: ...
  4. Computers which do not meet the Windows 7 minimum hardware requirements for memory, processor speed and free disk space. ...
  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. Verify that you have delete access to the selected object and refresh the Configuration ...
  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 move the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  10. ConfigMgr cannot move the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  11. ConfigMgr cannot move the specified item(s). Refresh the ConfigMgr Administrator console to verify that another administrator ...
  12. ConfigMgr cannot rename the specified folder. Refresh the ConfigMgr Administrator console to verify that another administrator ...
  13. ConfigMgr failed to connect to the site server's certificate store to validate the certificate based on the thumbprint you ...
  14. ConfigMgr has detected that this record has the same hardware ID as an existing client record. You can create a new record ...
  15. ConfigMgr server cannot accomplish tasks in Active Directory.%12 Possible cause: The credentials used to connect to the Domain ...
  16. ConfigMgr stopped downloading the following software when this computer disconnected from the private network for your organization. ...
  17. Configuration is corrupted for %1. Possible cause: incorrectly set configuration through SDK. Solution: delete and reset ...
  18. Configuration Item contains rules that are referencing to settings no longer available. Remove these rules before making ...
  19. Configuration items define a configuration and associated validation criteria to be asserted for compliance on client devices. ...
  20. Configuration items define a configuration and associated validation criteria to be assessed for compliance on client devices. ...
  21. Configuration items in Configuration Manager 2007 might contain rules that are not supported by Configuration Manager 2012. ...
  22. Configuration items inherit properties from parent configuration items when a relationship is defined. Configuration items ...
  23. Configuration Manager 2012 Client has encountered an error while computing compliance based on the selected software updates. ...
  24. Configuration Manager 2012 Client has installed a software update that requires a reboot but has been paused by Task Sequence ...
  25. Configuration Manager 2012 Client has successfully completed computing compliance based on selected software updates for ...
  26. Configuration Manager 2012 Client has successfully installed all the software updates that were marked for NAP enforcement. ...
  27. Configuration Manager 2012 Client remediation has detected that there are no software updates that are marked for NAP enforcement. ...
  28. Configuration Manager 2012 R2 Configuration Manager Out of Band Management Version: {0} Warning: This computer program is ...
  29. Configuration Manager 2012 System Health Agent facilitates enforcement of software update compliance using Network Access ...
  30. Configuration Manager 2012 System Health Validator failed to find the correct Configuration Manager enumerator in Active ...
  31. Configuration Manager 2012 System Health Validator failed to located the Configuration Manager Container in Active Directory. ...
  32. Configuration Manager 2012 System Health Validator failed to lookup the appropriate validation information for the incoming ...
  33. Configuration Manager 2012 System Health Validator has detected that Active Directory is not extended for Configuration Manager. ...
  34. Configuration Manager 2012 System Health Validator has detected that Configuration Manager Cache Store is improperly formatted. ...
  35. Configuration Manager 2012 System Health Validator has determined that Configuration Manager client is missing SMS SoH information. ...
  36. Configuration Manager 2012 System Health Validator has determined that Configuration Manager client's compliance state is ...
  37. Configuration Manager 2012 System Health Validator has determined that Configuration Manager client's compliance state is ...
  38. Configuration Manager 2012 System Health Validator has determined that Configuration Manager client's compliance state is ...
  39. Configuration Manager 2012 System Health Validator has determined that Configuration Manager client's Statement of Health ...
  40. Configuration Manager 2012 System Health Validator has determined that Configuration Manager client's Statement of Health ...
  41. Configuration Manager 2012 System Health Validator has determined that the Configuration Manager client is non-compliant ...
  42. Configuration Manager 2012 System Health Validator has determined that the Configuration Manager client is non-compliant ...
  43. Configuration Manager 2012 System Health Validator has determined that the Configuration Manager client is non-compliant ...
  44. Configuration Manager 2012 System Health Validator has encountered an invalid Configuration Manager data type in Active Directory. ...
  45. Configuration Manager 2012 System Health Validator has encountered Server component failure when verifying Configuration ...
  46. Configuration Manager 2012 uses the Windows Management Instrumentation (WMI) Query Language (WQL) to query the site database. ...
  47. Configuration Manager Active Directory schema extensions are not required for site server installation, but are recommended ...
  48. Configuration Manager Bootstrap service aborted because of timeout. Please review SMS_BOOTSTRAP.LOG or SMSSETUP.LOG on secondary ...
  49. Configuration Manager Bootstrap service is waiting for ConfigMgr setup CD. Please review SMS_BOOTSTRAP.LOG or SMSSETUP.LOG ...
  50. Configuration Manager can create an alert when synchronization fails on any site. You can check for synchronization failure ...
  51. Configuration Manager cannot access the certificate store for the server {0}. Check that the server name successfully resolves, ...
  52. Configuration Manager cannot access the node you requested. You might be using a customized version of the Configuration ...
  53. Configuration Manager cannot back up all the user accounts for this association because the source computer is associated ...
  54. Configuration Manager cannot complete the action that you requested for these objects: {0} Verify that these objects have ...
  55. Configuration Manager cannot connect to the Active Directory container you specified. Example: {0} Error code: 0x{1:X8} Error ...
  56. Configuration Manager cannot create the object "%1" in Active Directory (%2). Possible cause: The site server's machine account ...
  57. Configuration Manager cannot delete the object "%1" in Active Directory (%2). Possible cause: The site server's machine accountmay ...
  58. Configuration Manager cannot delete this application because other applications or task sequences reference it or it is configured ...
  59. Configuration Manager cannot import the specified driver folder. Verify that the folder exists in the specified location, ...
  60. Configuration Manager cannot import the specified driver. Verify that the driver exists in the specified location and that ...
  61. Configuration Manager cannot make your requested changes. Make sure that you specify a different value from the current value, ...
  62. Configuration Manager cannot obtain AMT information about this resource. Verify that you have permission for this resource. ...
  63. Configuration Manager cannot run the Out of Band Management console because the computer does not have Microsoft XML Core ...
  64. Configuration Manager cannot run the Out of Band Management console because the computer does not have Windows Remote Management ...
  65. Configuration Manager cannot stop the data gathering process for the selected source site. Before you stop gathering data ...
  66. Configuration Manager cannot stop the data gathering process for the selected source site. The source site still has an active ...
  67. Configuration Manager cannot update the already existing object "%1" in Active Directory (%2). Possible cause: The site server's ...
  68. Configuration Manager cannot update the dNSHostName property for the existing object "%1" in Active Directory (%2). This ...
  69. Configuration Manager central administration sites require a Microsoft SQL Server database to store site settings and data. ...
  70. Configuration Manager child sites cannot be upgraded until the parent site replication status is Replication Active. Try ...
  71. Configuration Manager clients are only supported on Windows 2003 Server Professional SP2, Windows XP Professional SP3, Windows ...
  72. Configuration Manager cmdlets cannot be run because Windows PowerShell 3.0 is not installed on this computer, install Windows ...
  73. Configuration Manager console allows the user to manage the Configuration Manager site. Any site without a console will have ...
  74. Configuration Manager could not find all of the information required to start client push installation on '{0}'. This might ...
  75. Configuration Manager could not locate the "System Management" container in Active Directory (%1). Nor could it create a ...