System Center Configuration Manager 2012 R2

  1. The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription. ...
  2. The server name is limited to between 1 and 15 characters. The server name you have entered does not meet this qualification. ...
  3. The service CName should be a valid unique FQDN, not already used as an existing site system and must match the DNS name ...
  4. The service name should be between 3 and 24 characters in length and should have alphabets and numbers only. It should not ...
  5. The setting must comply with the following attributes. If the value of any attribute is set to Do not verify, it will not ...
  6. The settings object is currently assigned to the collections listed below. Are you sure you want to continue the deletion? ...
  7. The settings that you specify in this policy apply to all Endpoint Protection clients in the hierarchy. Custom policies override ...
  8. The setup login user does not have Full Administrator or Infrastructure Administrator security role on specified site server. ...
  9. The Setup Wizard allows you to change the way ProductName features are installed on your computer or to remove it from your ...
  10. The Setup Wizard will allow you to change the way System Center Configuration Manager Administrative Console is installed ...
  11. The Setup Wizard will allow you to change the way System Center Configuration Manager Policy Module is installed on your ...
  12. The Setup Wizard will complete the installation of Microsoft System Center Configuration Manager Administrative Console on ...
  13. The Setup Wizard will complete the installation of Microsoft System Center Configuration Manager Policy Module on your computer. ...
  14. The Setup Wizard will complete the installation of ProductName on your computer. Click Install to continue or Cancel to exit ...
  15. The share type or the share name has been changed since the content was created. Verify that the share defined for this content ...
  16. The share type or the share name has been changed since the content was created. Verify that the share defined for this content ...
  17. The site code and site name cannot be changed after installation and must be unique throughout your Configuration Manager ...
  18. The site code and site name must be unique in the Configuration Manager hierarchy and cannot be changed after you install ...
  19. The site code that you specified is already in use in the Configuration Manager hierarchy. You must specify a unique site ...
  20. The site has a later version of the Configuration Manager client package than the version on the software update point. Do ...
  21. The site server computer must have at least 5GB of free disk space to install the site server. If the SMS Provider site system ...
  22. The site server computer's machine account does not have Administrator's privileges on the SQL Server selected for site database ...
  23. The site server in the specified site will install the client software. When you do not use this option, the site server ...
  24. The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control ...
  25. The site server notifies pull distribution points when there is content for them to download from a source distribution point. ...
  26. The site server signing certificate has changed. The Policy at this Site will be re-signed by the Site Server using the new ...
  27. The site server signing certificate has expired %1 day(s) ago. Please replace/renew the certificate. The Policies at this ...
  28. The site server signing certificate will expire in %1 day(s). Please ensure that this certificate is renewed for the proper ...
  29. The site server's computer account is used to install the selected site system roles. Ensure that this account is a member ...
  30. The Site System Proxy Server Account provides authenticated access to the proxy server when this site system server connects ...
  31. The site was being recovered using a different build number than the build version of the ConfigMgr backup. The recovery ...
  32. The size of the existing ConfigMgr database is %u megabytes; Setup may take some time to upgrade the database. Do you want ...
  33. The size of the existing ConfigMgr database is %u.%u gigabytes; Setup may take some time to upgrade the database. Do you ...
  34. The slow-network connection timeout, in milliseconds. This threshold is used to determine if the connection is a slow link. ...
  35. The SMS Provider reported an error connecting to the ConfigMgr site database server. Verify that the SQL Server is online ...
  36. The SMS Service Host (CCMEXEC) encountered a failure (%1) when performing Certificate operations.%12 Possible cause: The ...
  37. The SMS Service Host (CCMEXEC) has entered Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which falls ...
  38. The SMS Service Host (CCMEXEC) has recovered from Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which ...
  39. The SMSITMU scanner upgrade was unsuccessful. While the ITMU scan data has been unchanged, the ITMU scanner might not be ...
  40. The software cannot be installed until the computer is restarted. The computer needs to be restarted to complete a previous ...
  41. The software cannot run at this time because a pending software update for it is being applied. Once the update has been ...
  42. The software cannot run at this time because a software update is being applied. Once the update has been installed, you ...
  43. The software has a deadline that requires it to be installed during business hours and can't be rescheduled to non-business ...
  44. The software is not available at this time. If you are offline or connected to the Internet, the files will be available ...
  45. The Software Metering Data Monthly Usage Summarization task has completed, %1 rows have been added or updated in the summary ...
  46. The software that is required to run this application is not installed. Information that is shown in the following section ...
  47. The software update failed to install. Possible cause: Typically such failures are the result of internal errors within the ...
  48. The software update installation did not complete within the allocated time and was stopped by the agent. Possible cause: ...
  49. The software update installation was not attempted due to a low disk space condition. Possible cause: This software update ...
  50. The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer ...
  51. The software update was installed and a restart of the computer was not required for the changes to take effect. The run-time ...
  52. The software update was installed due to an administrator defined enforcement date being met. A restart of the computer is ...
  53. The software update was installed due to an administrator defined enforcement date being met. A restart of the computer was ...
  54. The software update was started, but was cancelled during installation by the user of the computer. Solution: To prevent ...
  55. The Software Updates Installation Agent initiated a system restart because one or more software updates required a restart ...
  56. The software updates installation evaluation returned the following results: %1 Authorized, %2 attempted, %3 failed. Review ...
  57. The software you are about to install is provided as part of System Center Configuration Manager and as such, is subject ...
  58. The source computer cannot be found. Retype the name of the source computer or click Search to search for the source computer. ...
  59. The source directory "%1" for package "%2" does not exist.%12 Solution: Make sure you have specified a valid package source ...
  60. The source directory you entered is not valid. Enter a source directory in the form: Drive:\Directory Path. The following ...
  61. The source directory you entered is not valid. Enter a source directory in the form: Drive:\Directory Path. The following ...
  62. The source directory you entered is not valid. Enter a source directory in the form: \Server\Directory Path. The following ...
  63. The source directory you entered is not valid. Enter a source directory in the form: \Server\Directory Path. The following ...
  64. The Source folder has not been configured. Verify that you have specified the content source folder on the Data Source tab ...
  65. The source hierarchy "%1" specified is not a valid Configuration Manager 2007 top-level site or stand-alone primary site.%0 ...
  66. The source location must be the location of a Windows Azure blob content within the App Controller namespace or a file share ...
  67. The source program uses the package properties for status Management Information Format (MIF) matching. For Configuration ...
  68. The source site uses the File Replication Account to connect to the destination site and to write data to that site's SMS_SITE ...
  69. The specified driver cannot be found in the source location. Verify that the source location is not the same as the package ...
  70. The specified file does not contain a Configuration Manager application. Select a file that contains an application that ...
  71. The specified file does not exist or the computer running the Configuration Manager console has no Read permissions to the ...
  72. The specified folder does not exist or the computer running the Configuration Manager console has no Read permissions to ...
  73. The specified folder doesn't exist or SMS Provider computer has no Read, Write or Delete subfolders and files permissions ...
  74. The specified folder is already being used for another driver package. Specify a UNC path to an empty folder that is not ...
  75. The specified host name is incorrect. The host name must use a valid host name format and cannot contain the following characters: ...