System Center Configuration Manager 2012

  1. Processes the CcmDCOMAplication table and checks to see if the DCOM Component is being updated. If so, passes that information ...
  2. Provisioning failed because of an unsupported provisioning scenario. 12 Possible causes: WinHTTP Proxy is being used between ...
  3. Provisioning for %1 %2 failed due to all accounts failed to authentication with target device.%12 Possible cause: The remote ...
  4. Provisioning for %1 %2 failed due to an improper or missing provisioning certificate.%12 Possible cause: This condition is ...
  5. PXE and Multicast are no longer enabled on this distribution point. Do you want Configuration Manager to remove Windows Deployment ...
  6. PXE control manager could not update its settings to the new values.%12 Possible cause: PXE may be overloaded. Solution: ...
  7. PXE Control Manager detected PXE service point is not responding to PXE requests. The error is %1.%12 Possible cause: PXE ...
  8. PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2.%12 ...
  9. Query rule "{0}" is invalid. The rule may be based on a Hardware Inventory class not collected at the destination, or be ...
  10. Query timed out while verifying the account permissions. Clients may not be able to execute the program. Do you still want ...
  11. RCM has finished processing resync for replicationgroup %1 to version %2.Please refer to rcmctrl.log for further details.%0 ...
  12. Read the existing "%1" inbox definition. The inbox should exist on the Client Access Point with the relative path "%2".%12%3%4%5%6%7%8%9%10%0 ...
  13. Read the existing "%1" inbox definition. The inbox should exist on the named export "%2" with the relative path "%3".%12%4%5%6%7%8%9%10%0 ...
  14. Read the existing "%1" inbox definition. The inbox should exist on the Site Server with the relative path "%2".%12%3%4%5%6%7%8%9%10%0 ...
  15. Read the existing "%1" inbox definition. The inbox should exist on the SQL Server with the relative path "%2".%12%3%4%5%6%7%8%9%10%0 ...
  16. Read the existing inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. ...
  17. Read the existing inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. ...
  18. Read the existing inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 ...
  19. Read the existing inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10%0 ...
  20. Read the existing inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. ...
  21. Read the existing inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. ...
  22. Received drs_syncstart message for replicationgroup %1], however it is pending resync. Please refer to dmpuploader.log for ...
  23. Recently installed software requires your computer to restart in {0} minutes to complete the installation. No additional ...
  24. Recurrence not set. After maintenance window expiration, software packages and software updates will not install on the computers ...
  25. Remediation failed to create SQL Server Broker login for sites: {0}. Please retry replication link analyzer by logging on ...
  26. Remote Control allows you to log on to computers over the network and is typically used for troubleshooting scenarios. To ...
  27. Remove components that depend on {0}? If you disable {0}, the following components that depend on it will also be disabled: ...
  28. Removing the Asset Intelligence synchronization point will prevent further communication with System Center On-line. This ...
  29. Removing the Distribution Point role from this site system will cause existing advertisements to fail when run by clients. ...
  30. Replication initialization cannot send replication content from site {0} to site {1} as the file replication route is closed ...
  31. Replication initialization failed to fully initialize the following replication groups for site {0}: {2}. Replication link ...
  32. Replication initialization failed to fully initialize the following tables for site {0}: {2}. Replication link analyzer is ...
  33. Replication initialization is aborted on site {1} for the replication groups: {2}. Replication link analyzer recommends reinitializing ...
  34. Replication initialization is in progress for another link on site {0}. The replication link analyzer recommends running ...
  35. Replication initialization is in progress for site {0} from site {1} for the replication groups: {1}. This action may take ...
  36. Replication initialization is in progress for site {0} from site {1} for the replication groups: {2}. This action may take ...
  37. Replication initialization is unable to apply replication package from site {1} to site {0} for the replication groups: {2}. ...
  38. Replication initialization is unable to apply replication package from site {1} to site {0} for the replication groups: {2}. ...
  39. Replication initialization is unable to create the replication package from site {0} to site {1} for the replication groups: ...
  40. Replication initialization is unable to create the replication package from site {1} to site {0} for the replication groups: ...
  41. Replication initialization is unable to send or receive replication content from site {0} to site {1} for the replication ...
  42. Replication initialization is unable to send or receive replication content from site {0} to site {1} for the replication ...
  43. Replication initialization is unable to send or receive replication content from site {1} to site {0} for the replication ...
  44. Replication initialization is unable to send replication package from site {0} to site {1} for the replication groups: {2}. ...
  45. Replication initialization is unable to send replication package from site {1} to site {0} for the replication groups: {2}. ...
  46. Replication link analyzer detected Database {0} does not have a valid security scope for Local System Account. Please make ...
  47. Replication link analyzer detected the following replication groups on site {0} are degraded. The current replication queue ...
  48. Replication link analyzer detected the link failed on site {0}. The link failure may have been caused by previously detected ...
  49. Replication link analyzer is unable to launch analysis engine. Look at the replication link analysis log for further diagnosis. ...
  50. Replication link analyzer is unable to register class {1} with .NET Framework 3.5 SP1 and restart SMS Executive service on ...
  51. Replication link analyzer is unable to reinitialize the following replicated tables on site {0}: {2}. Replication link analyzer ...
  52. Replication link analyzer is unable to reinitialize the following replication groups on site {0}: {2}. Replication link analyzer ...
  53. Replication link analyzer is unable to remediate this issue. Save the analysis and remediation logs and the rcmctrl.log files ...
  54. Replication link analyzer is unable to remediate this issue. Save the analysis and remediation logs for further diagnosis. ...
  55. Replication link analyzer is unable to remediate this issue. Save the analysis and remediation logs on site {1} for further ...
  56. Replication link analyzer is unable to remediate this issue. Save the analysis report and and logs for further diagnosis. ...
  57. Replication link analyzer recommends enabling the SQL Server Service Broker on SQL Server {0} for following databases: {3}. ...
  58. Replication link analyzer recommends registering class {1} on site server {0} with .NET Framework 3.5 SP1. After this is ...
  59. Replication link analyzer recommends reinitializing the following replicated tables on site {0}: {2}. This action may take ...
  60. Replication link analyzer recommends reinitializing the following replication groups on site {0}: {2}. This action may take ...
  61. Replication link analyzer recommends resetting change tracking and reinitializing all replication groups on site {0}. This ...
  62. Replication link analyzer recommends verification of registration for class {2} on site server {1} with .NET Framework 3.5 ...
  63. Replication Manager received files from the "%1" component at a child site, but that component is not enabled at the current ...
  64. Requests a retry after the current task sequence step is completed. If this task sequence variable is set, the SMSTSRebootRequested ...
  65. Resource Explorer cannot start. The ConfigMgr client software might not be installed on the selected site system, or the ...
  66. Resource Explorer cannot start. The Configuration Manager client software might not be installed on the selected site system, ...
  67. Restarting this computer is only allowed for users with administrative permissions, or your IT department does not allow ...
  68. Retrives the ConfigMgr client installation directory from the MSI's Session object and the path to the Remote Control's resource ...
  69. Retry detach secondary from parent primary - check ConfigMgrSetup.log in the root of the secondary site server system drive ...
  70. Retrying in 10 minutes, initially unable to decompress secondary site server installation files - check SMS_BOOTSTRAP.log ...
  71. Review and configure requirements for this deployment type. Requirements with a status of New have been extracted from the ...
  72. Review both actions that you must take and actions that Configuration Manager will use to control the scope of the migrated ...
  73. Review the objects that might be modified by Configuration Manager during migration or that might require additional configuration ...
  74. Review the previous status messages from this component for SQL Server errors. 2. Verify that this computer can access the ...
  75. Rules in following configuration items are using "{0}" setting. ConfigMgr will delete rules in "{1}" configuration item . ...