System Center Configuration Manager 2012 R2

  1. The specified IPv4 address is not valid for multicast. Specify IPv4 multicast addresses in the range 224.0.1.0 to 239.255.255.255 ...
  2. The specified path does not contain a valid operating system or you do not have permission to access it. Specify a valid ...
  3. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and ...
  4. The specified server is already a site system for site {0}. You cannot install the SMS Provider on a server that is already ...
  5. The specified share is a hidden Windows drive share or a hidden Windows Admin share. Specify a different share name on the ...
  6. The specified share is a hidden Windows drive share or a hidden Windows Admin share. Specify a different share name on the ...
  7. The specified source hierarchy contains a site that has the same site code as another site that was previously migrated from ...
  8. The specified source hierarchy contains one or more site codes in use by the destination hierarchy. To continue you must ...
  9. The specified subscription Id did not match with the one in the PublishSettings file. Ensure the file specified is valid ...
  10. The specified task sequence is deployed but currently disabled. To enable and deploy this task sequence, click Yes. To deploy ...
  11. The specified threat could not be found in the definitions. Verify you typed in correct name and the Endpoint Protection ...
  12. The specified UNC path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path. ...
  13. The specified Windows Phone app package -. xap file could not be opened. Verify the file is a valid Windows Phone app package ...
  14. The specified Windows Phone app package file could not be opened. Verify that the file is a valid Windows Phone app package ...
  15. The SQL Reporting Services datasource on Reporting point server "%1" is missing or has been changed outside of Configuration ...
  16. The Sql Server Agent is not running on server {0}. You must start this service before you can create or edit a subscription. ...
  17. The SQL server name specified during setup must match the Name in sys.servers of the SQL server. For more information on ...
  18. The SQL Server name specified is configured for SQL authentication security. It is recommended to configure the SQL Server ...
  19. The SQL Server name specified is configured for SQL authentication security. It is recommended to configure the SQL Server ...
  20. The SQL Server on {0} has insufficient free disk space for the Configuration Manager database instance. Free up additional ...
  21. The SQL Server Service Broker %1 used by Notification Manager is disabled.%12 Possible cause: Enable the SQL Server Service ...
  22. The SQL Server Service Broker configuration could not be created. Save the analysis report and logs for further diagnosis. ...
  23. The State Migration Point can not authenticate the client %1. Possible cause: Client machine is not part of the domain or ...
  24. The State Migration Point failed to read and configure the registry keys necessary for this component. Possible cause: The ...
  25. The State Migration Point has reached the maximum client threshold on all drives on computer %1. Possible cause: Restoring ...
  26. The State Migration Point has reached the minimum disk space threshold of %1 %2 on drive %3 of computer %4. Current free ...
  27. The State Migration Point reached the minimum disk space threshold on all drives of computer %1. Possible cause: Restoring ...
  28. The State System failed to read and configure the registry keys necessary for this component.%12 Possible cause: The registry ...
  29. The State System message file processing could not process file '%1' and moved it to the corrupt directory. Review the statesys.log ...
  30. The State System message file processing experienced a severe error and suspended file processing. Review the statesys.log ...
  31. The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log ...
  32. The Status Message Viewer could not find the persistent query for QueryID = %s. The viewer will be invoked with a default ...
  33. The Status Viewer could not initialize successfully. rc="BAD PARMS" passed to the Initialize() function. The Status Viewer ...
  34. The Status Viewer is unable to connect to the registry key : %s]. This key points to the dll required to resolve some status ...
  35. The Status Viewer is unable to find the EventMessageFile registry entry for key : %s]. This key points to the dll required ...
  36. The Status Viewer is unable to load the resource dll: %s]. The Viewer may not be able to resolve some status message properties ...
  37. The Status Viewer was unable to determine the current user. Delete authority on Configuration Manager Status Messages will ...
  38. The storage blob URI specified is not valid. It should be in the format http://{storageservicename}.blob.core.windows.net/{containername}/{blobname}. ...
  39. The summarization of this deployment has been scheduled to be updated throughout the hierarchy. Allow time for the system ...
  40. The summarization of update group compliance status has been scheduled to be run and will be updated throughout the hierarchy. ...
  41. The summarization request for this deployment failed. To run summarization, you must be granted deployment rights for the ...
  42. The supplied credentials of user '%1' do not have remote control rights for device '%2'. Enter new credentials as domain\username ...
  43. The supported application and one or more of the deployment types selected would create a dependency/supersedence loop, which ...
  44. The supported platforms information has not been read completely. If you click Yes, some information may be lost. Do you ...
  45. The system account runs the Mac OS X installer, and does not require any user interaction. Depending on the configuration ...
  46. The System Center Virtual Machine Manager console must be installed on this computer to upload a virtual hard disk to VMM ...
  47. The system failed to suspend Bitlocker before a required system restart. The error returned from the suspend operation was: ...
  48. The system is low on virtual memory and the component failed a memory allocation. The component will retry the allocation ...
  49. The system restart, snooze and scheduling actions are only allowed for users with administrative permissions on this computer. ...
  50. The system security setting group includes typical settings for system security, such as firewall, automatic updates, virus ...
  51. The target folder name '{0}' has exceeded the maximum character limit of 255 characters. Rename the source folder name to ...
  52. The task "%1" is configured to run today, but it could not run within the scheduled time. %12 Possible cause: The task has ...
  53. The task runs on a dynamic interval to update the Application Catalog database cache unless it is scheduled to run on a fixed ...
  54. The task sequence cannot be cancelled once the Windows Preinstallation Environment has been staged as it may leave the machine ...
  55. The task sequence execution engine failed evaluating the condition for the action (%2) in the group (%3). Error code %4.%12%0 ...
  56. The task sequence execution engine failed executing the action (%2) in the group (%3) with the error code %4 Action output: ...
  57. The task sequence execution engine failed to install (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12%0 ...
  58. The task sequence execution engine failed to install application %5(%6) that was specified through TS variable for action ...
  59. The task sequence execution engine failed to install application that was specified through task sequence variable for 'Install ...
  60. The task sequence execution engine received an external shutdown request during execution of the action (%2) in the group ...
  61. The task sequence execution engine skipped the action (%2) in the group (%3) because the condition was evaluated to be false.%12%0 ...
  62. The task sequence execution engine successfully completed the action (%2) in the group (%3) with exit code %4 Action output: ...
  63. The task sequence execution engine successfully installed (%6) package (%5) for action (%2) in the group (%3) with exit code ...
  64. The task sequence execution engine timeout in executing the action (%2) in the group (%3) Partial action output: %5%6%7%8.%12%0 ...
  65. The task sequence failed to install application %5(%6) for action (%2) in the group (%3) because a 'requirement was not met' ...
  66. The task sequence failed to install application %5(%6) for action (%2) in the group (%3). Please update maximum run time ...
  67. The task sequence failed to install application that was specified in the 'Install Application' action. Please update maximum ...
  68. The task sequence has attempted to set UDA for users: %5 with assignment mode: %6 for action (%2) in the group (%3) with ...
  69. The task sequence has failed to set UDA for users: %5 with assignment mode: %6 for action (%2) in the group (%3) with exit ...
  70. The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of %1 was returned.%12%0 ...
  71. The task sequence successfully installed application %5(%6) that was specified through TS variable for action (%2) in the ...
  72. The task sequence successfully installed application that was specified through task sequenbce variable for 'Install Application' ...
  73. The Task Sequence XML is invalid. The task sequence may contain steps from an extension, such as the Microsoft Deployment ...
  74. The task you clicked does not yet have an underlying system task to connect to which is independent of the owner module. ...
  75. The templates to the collection are listed below. Deleting the collection will also delete these templates, so deployments ...