System Center Configuration Manager 2012 R2

  1. Setup has detected that this is an existing component server of an existing site. You can only install the Configuration ...
  2. Setup has detected that you did not select any new components. This means that Setup will not make any changes to your site ...
  3. Setup has detected that you have cleared some previously installed components. Do you want to remove these components from ...
  4. Setup has detected this site has enabled the logon discovery and installation features. Configuration Manager no longer supports ...
  5. Setup has enabled available installation options based on the installed operating system and any existing System Center Configuration ...
  6. Setup has finished installing all required installation components. You can click Next to finish the Configuration Manager ...
  7. Setup has finished upgrading all required installation components. You can click Next to finish the Configuration Manager ...
  8. Setup has not detected an existing installation of a primary site server, secondary site server, site system, or administrator ...
  9. Setup has not detected an existing installation of a primary site server, secondary site server, site system, or Configuration ...
  10. Setup has not detected an existing installation of site server, site system, or Configuration Manager console on this computer. ...
  11. Setup is checking for potential installation problems. If installation problems are found, Setup will display details about ...
  12. Setup is checking for potential installation problems. If problems are found, Setup will display details about how to resolve ...
  13. Setup is now installing and configuring Configuration Manager. Installation time will vary depending on your installation ...
  14. Setup is unable to connect to SQL Server with the connection information provided. Verify the following: . The SQL Server ...
  15. Setup is unable to establish a remote connection to WMI on the secondary site. Typical causes can include network connectivity ...
  16. Setup reached maximum retry limit for copying the public key of site recovering to server {0}. Manually copy the public key ...
  17. Setup requires .NET Framework 3.5 SP1 to continue; however, it was not found on this computer. (see C:\ConfigMgrSetup.log ...
  18. Setup requires prerequisite files. Setup can automatically download the files to a location that you specify, or you can ...
  19. Setup was unable to retrieve the site code for the specified central administration site server. Verify that you have entered ...
  20. Setup was unable to retrieve the site code for the specified primary site server. Verify that you have entered the correct ...
  21. Setup will install the Configuration Manager console in following installation folder. To select a different folder, click ...
  22. Setup will install the Configuration Manager policy module in the following installation folder. To select a different folder, ...
  23. Show notifications messages on the client computer when the user needs to run a full scan, update definitions, or run Windows ...
  24. Sign in with a Microsoft Intune organizational account and password to complete the wizard. You can get a organizational ...
  25. Site "%1" (%2) has the same site code as another site. Possible cause: Hierarchy Manager has detected that a child site has ...
  26. Site "%1" (%2) is trying to report to a site that already reports to site "%1". This configuration is illegal because it ...
  27. Site %1 is requesting initialization for replication group %2 from site %3.%12 Refer to rcmctrl.log for further details.%0 ...
  28. Site assignment and configuration will be automatically specified. Specify any additional installation properties to use ...
  29. Site Backup could not connect to the registry on the SQL Server machine. Aborting the backup operation. Verify that the site ...
  30. Site Backup could not find the registry entries on the SQL Server machine. SMS SQL Backup service might not be running on ...
  31. Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. Please ...
  32. Site Backup could not start the "%1" executable on the local computer.%12 Possible cause: "%1" does not exist in the specified ...
  33. Site Backup could not start the "%1" executable on the local computer.%12 Possible cause: "%1" is not found in the specified ...
  34. Site Backup could not start the %1 ConfigMgr client application on the local computer.%12 Possible causes: %1 is not in the ...
  35. Site Backup could not start the %1 service on site system %2.%12 Possible cause: Site Backup does not have sufficient access ...
  36. Site Backup could not stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows application ...
  37. Site Backup could not stop the %1 ConfigMgr client application on the local computer.%12 Possible cause: %1 does not exist ...
  38. Site Backup could not stop the %1 service on site system %2.%12 Possible cause: Site Backup does not have sufficient access ...
  39. Site Backup failed to initialize the VSS services. Aborting the backup operation. Please verify that the VSS services are ...
  40. Site Backup failed while trying to copy the files to the destination. Backup operation is not completed. Possible Cause: ...
  41. Site Backup failed. The error reported by the service is %1. Backup operation is not completed. Please see smsbkup.log for ...
  42. Site Backup found syntax errors on the following lines:%1 in backup control file. Site backup did not occur.%12 Possible ...
  43. Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the site database. It cannot ...
  44. Site Backup is ignoring the invalid definition on line %1 of the backup control file. This problem may cause part of the ...
  45. Site Backup is ignoring the invalid section starting on line %1 of the backup control file. This problem might cause part ...
  46. Site Backup reported that the backup control data ended unexpectedly at line %1. This problem might cause part of the site ...
  47. Site Backup task is starting. This task will interact with the windows VSS services and the appropriate writers to create ...
  48. Site Backup was run, but the %1 token had no value. Site backup did not occur.%12 Possible cause: The current site's "Backup ...
  49. Site Backup was run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur.%12 Possible cause: ...
  50. Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: ...
  51. Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: ...
  52. Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. ...
  53. Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. ...
  54. Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: Site Backup was unable to connect to or set backup ...
  55. Site Backup was unable to initiate command file "%1" .%12 Possible cause: Unable to find command shell to execute this file. ...
  56. Site Backup was unable to open control file "%1". Site backup did not occur.%12 Possible cause: Wrong name specified or permissions ...
  57. Site Backup was unable to run command line "%1" (error #%2).%12 Possible cause: "%1" does not exist at the specified location ...
  58. Site Component Manager cannot install this component on this site system because %1 bytes are required on the drive containing ...
  59. Site Component Manager could not access site system "%1" due to an unexpected failure within the network abstraction layer ...
  60. Site Component Manager could not access site system "%1".%12 Possible cause: The site system is turned off, not connected ...
  61. Site Component Manager could not add machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3". Possible ...
  62. Site Component Manager could not copy file "%1" to "%2".%12 Site Component Manager reports this error when it fails to: 1. ...
  63. Site Component Manager could not copy file "%1" to "%2".%12 Site Component Manager reports this error when it fails to: 1. ...
  64. Site Component Manager could not create the "%2" account on site system "%1".%12 Possible cause: The site system is turned ...
  65. Site Component Manager could not create the Configuration Manager Server Components' installation directory "%2" on site ...
  66. Site Component Manager could not deinstall the %1 service from site system "%2".%12 Possible cause: Site Component Manager ...
  67. Site Component Manager could not detect how much disk space was available in the "%1" directory on this site system.%12 Possible ...
  68. Site Component Manager could not detect which version of the Microsoft Windows Server operating system is running on site ...
  69. Site Component Manager could not find an NTFS partition on site system "%1" to hold the Configuration Manager Server Components' ...
  70. Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
  71. Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
  72. Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
  73. Site Component Manager could not read the Network Connection account data, which is stored in the installation directory ...
  74. Site Component Manager could not remove the "%2" account from site system "%1".%12 Possible cause: The site system is turned ...
  75. Site Component Manager could not remove the Configuration Manager installation directory "%2" on site system "%1".%12 Possible ...