System Center Configuration Manager 2012 R2

  1. Client Push installation is supported on Windows operating systems only. You can download clients for additional operating ...
  2. Client reassignment completed. It might take some time for the new site code to be displayed in the Configuration Manager ...
  3. Clients can always download and install the content in this package. You can also allow clients to install the content in ...
  4. Clients cannot access the software updates in this deployment package until you specify a distribution point or distribution ...
  5. Clients may not be able to communicate with site systems if an alternate port is not defined for client request services. ...
  6. Clients use these site systems as the content source location for content deployment. When content is not available on these ...
  7. Clients will always try to get content from the local distribution points. In addition, interaction with remote distribution ...
  8. Clients will receive this advertisement but will not be able to run it until appropriate access accounts are defined for ...
  9. Clients with malware that may have changed system settings. Refer to product documentation for a list of settings that may ...
  10. Cloud Content Manager was unable to connect to the cloud distribution point service when trying to distribute package %1.%0 ...
  11. Cloud Services Manager has failed to authenticate for subscription Id %1. Please check that the management certificate is ...
  12. Cloud Services Manager has failed to uninstall service %1. Please delete the deployment using the Windows Azure portal.%0 ...
  13. Cloud Services Manager is unable to connect to Windows Azure for subscription Id %1. Please check your proxy configuration.%0 ...
  14. Cloud services that are created will not have any deployments. Only cloud services which have no deployments can be deleted. ...
  15. CloudUserSync - Duplicate principal names found for users in cloud collection. Some users were not enabled for cloud services. ...
  16. CloudUserSync - Empty principal names found for users in cloud collection. Some users were not enabled for cloud services. ...
  17. Collection "%1" has no name. Collection Evaluator cannot continue processing the collection without a name.%12 Solution: ...
  18. Collection Evaluator failed to connect to the site database.%12 Possible cause: SQL Server problem. Solution: 1. Review the ...
  19. Collection Evaluator failed to delete collection "%1".%12 Possible cause: SQL Server problem. Solution: 1. Review the immediately ...
  20. Collection Evaluator failed to enumerate collections.%12 Possible cause: SQL Server problem. Solution: 1. Review the immediately ...
  21. Collection Evaluator failed to enumerate discovery architectures because it cannot retrieve the discovery architecture list ...
  22. Collection Evaluator failed to enumerate members of collection "%1" at site "%2".%12 Possible cause: SQL Server problem. ...
  23. Collection Evaluator failed to enumerate membership rules for collection "%1".%12 Possible cause: SQL Server problem. Solution: ...
  24. Collection Evaluator failed to evalute some of the query rules for collection "%1" (%2).%12 Possible cause: Inventory or ...
  25. Collection Evaluator failed to find collection "%1". Collection Evaluator received a .udc (update collection) or .adc (create ...
  26. Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle.%12 ...
  27. Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings has been retried %2 ...
  28. Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings will be retried %2 ...
  29. Collection Evaluator failed to process Collection Settings Replication File %1 as Collection %2 referenced object of type ...
  30. Collection Evaluator failed to process Collection Settings Replication File %1. This Collection Settings Replication file ...
  31. Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule.%12 Possible cause: An SMS ...
  32. Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source ...
  33. Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the site database. ...
  34. Collection Evaluator failed to update the membership of collection "%1".%12 Possible cause: SQL Server problem. Solution: ...
  35. Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3).%12 Possible cause: Inventory or Resource ...
  36. Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". ...
  37. Collection Evaluator successfully processed %1 client updates for collection %2. Original clients number: %3, added: %4, ...
  38. Collection migration jobs migrate collections and the objects related to the collections that you specify. Object migration ...
  39. Communication issues on mobile devices that are managed by the Configuration Manager client for Windows CE and that are not ...
  40. Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
  41. Component Status Summarizer detected that component "%1" running on computer "%2" has reported %3 or more Informational status ...
  42. Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status ...
  43. Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status ...
  44. Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Informational ...
  45. Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status ...
  46. Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status ...
  47. Component Status Summarizer detected that entry "%1" of the Component Thresholds property list in the site control file is ...
  48. Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Degraded.%12 ...
  49. Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Failed.%12 Possible ...
  50. Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Offline.%12 ...
  51. Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Unknown.%12 ...
  52. Component Status Summarizer detected that the list of Component Status Display Intervals specified in the site control file ...
  53. Component Status Summarizer has not received a status message from component "%1", running on computer "%2", in %3 hours.%12 ...
  54. Component Status Summarizer received a status message from component "%1", running on computer "%2", but there is no record ...
  55. Component Status Summarizer received a status message that was reported by component "%1", running on computer "%2" at site ...
  56. Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the ...
  57. Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the ...
  58. Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the ...
  59. Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the ...
  60. Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the ...
  61. Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" ...
  62. Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" ...
  63. Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" ...
  64. Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" ...
  65. Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" ...
  66. Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the ...
  67. Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the ...
  68. Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the ...
  69. Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the ...
  70. Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the ...
  71. Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK.%12 Component Status Summarizer ...
  72. Component Status Summarizer set the status of component "%1" running on computer "%2" to Warning.%12 Possible cause: The ...
  73. Component Status Summarizer set the status of component "%1", running on computer "%2", to Critical.%12 Possible cause: The ...
  74. Computer account: Use the computer account of the top-tier site of your destination hierarchy to connect to the Configuration ...
  75. Computer clock synchronization between {0} and {1} exceeds maximum tolerance level of 5 minutes. The computer clocks on these ...