System Center Configuration Manager 2012 R2

  1. Network Discovery failed to enumerate the computers on one or more domains.%12 Possible cause: The specified domains do not ...
  2. Network Discovery failed to execute a query from CIM Object Manager. Network discovery will continue, but slowly.%12 Possible ...
  3. Network Discovery failed to export a device to the Discovery Data Manager. Therefore, discovered devices will not appear ...
  4. Network Discovery failed to export a network to the Discovery Data Manager. Therefore, discovered devices will not appear ...
  5. Network Discovery failed to perform a WinSock operation relating to multicast membership. Network Discovery will not discover ...
  6. Network Discovery failed to perform a WinSock operation.%12 Solution: Ensure that the TCP/IP stack is installed and running. ...
  7. Network Discovery failed to read information from CIM Object Manager. Network Discovery cannot continue.%12 Possible cause: ...
  8. Network Discovery failed to read information from CIM Object Manager. Network Discovery will continue, but slowly.%12 Possible ...
  9. Network Discovery failed to write information to CIM Object Manager. Network Discovery cannot continue.%12 Possible cause: ...
  10. Network Discovery failed to write information to CIM Object Manager. Network discovery will continue, but slowly.%12 Possible ...
  11. Network Discovery is exporting devices and networks to the Discovery Data Manager. This process can take a long time when ...
  12. Network Discovery is retrieving information about previously discovered devices and networks from CIM Object Manager.%12 ...
  13. Network Discovery is starting protocol operations. Network Discovery is querying network devices to discover devices related ...
  14. Network Discovery is storing currently discovered devices and networks in CIM Object Manager, which can take a long time ...
  15. Never install the Configuration Manager &client on domain controllers unless specified in the Client Push Installation Wizard ...
  16. New Extensions for Microsoft Intune are available. Extensions can be enabled on Configuration Manager as soon as they become ...
  17. New software updates are available and will automatically begin installing in %1!s!. A system restart may be enforced at ...
  18. New software updates are available for installation and will automatically be installed on %1!s!. A system restart may be ...
  19. New software updates have been targeted for installation, and a system restart may be enforced in %1!s!. Click here to view ...
  20. New software updates have been targeted for installation, and a system restart may be enforced on %1!s!. Click here to view ...
  21. No information will be sent to Microsoft. You won't be alerted if unclassified software is detected running on your computer. ...
  22. No maintenance window is defined to accommodate at least one update in the deployment %1. Possible Cause:There is only one ...
  23. No network credentials specified when logging on to server {0}. All subsequent server requests will use Windows integrated ...
  24. No objects can be selected in this type of job, please select another type of migration job or check the data gathering jobs ...
  25. No objects depend on the selected collections. Clear the Migrate objects that are associated with the specified collections ...
  26. No packages are found that need to be updated. Do you want to proceed without any update and close this dialog? If you press ...
  27. No shares available to copy resources. In the Virtual Machine Manager console add a library share and assign it to a cloud. ...
  28. No site system has the out of band service point role assigned. You must enable this site system role and provision computers ...
  29. No strings are displayed when the "Resolve Property Strings" option is turned off. To turn it back on, choose "Options." ...
  30. No user account was found corresponding to your user name or e-mail address. Correct the entry and try again. Contact the ...
  31. None of the applications you tried to install began installation successfully. Investigate the reason for the installation ...
  32. Not all selected content is currently available for access on the selected distribution points. Modify selection of distribution ...
  33. Not all selected software updates are currently available on current site. Distribute the updates to the site first and then ...
  34. Not properly signed drivers that you selected could fail to be injected into selected 64-bit boot image. Do you want to continue ...
  35. Note that if you choose to recover the auto-saved documents, you must explicitly save them to overwrite the original documents. ...
  36. Note: If you decide not to install this software now, you can install it later from the Application Catalog or the Software ...
  37. Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides ...
  38. Note: The site code must be unique in the Configuration Manager hierarchy and cannot be changed after you install the site. ...
  39. Note: To ensure the highest level of functionality and compatibility, it is recommended that you make sure this location ...
  40. NOTE: Uninstalling this secondary site will not remove it from its parent site hierarchy. You must manually delete this secondary ...
  41. Note: You can use the same alternate path to install multiple sites. Always verify that the alternate path contains the most ...
  42. Notification Manager failed to initialize.%12 Possible cause: Failed to initialize with error code %1. To help identify the ...
  43. Notification Server on %1 failed to connect to the site database %2.%12 Possible cause: Notification Server failed to connect ...
  44. Notification Server on %1 failed to initialize the TCP listener on port %2.%12 Possible cause: TCP port %3 might be in use ...
  45. Notification Server on %1 failed to initialize.%12 Possible cause: Failed to initialize with error code %2. To help identify ...
  46. Number of corrupt .SVF files received by SMS_STATUS_MANAGER via the Status Manager inbox since SMS_STATUS_MANAGER was last ...
  47. Number of status messages replicated at high priority by SMS_STATUS_MANAGER to the parent site since SMS_STATUS_MANAGER was ...
  48. Number of status messages replicated at low priority by SMS_STATUS_MANAGER to the parent site since SMS_STATUS_MANAGER was ...
  49. Number of status messages replicated at normal priority by SMS_STATUS_MANAGER to the parent site since SMS_STATUS_MANAGER ...
  50. Number of status messages reported by SMS_STATUS_MANAGER to the Windows NT Application Event Log on the site server since ...
  51. Object %1 with path %2 have failed to migrate as part of migration job %3 (%4) which ran on site server %5 with error %6.%0 ...
  52. object is associated with only this security scope. To delete this scope, you must first associate this object with another ...
  53. Object migration jobs migrate only the objects that you specify. Objects modified after migration jobs migrate objects that ...
  54. Object Replication Manager failed to process Object %1 of Type %2. This Object has been retried %3 times and has reached ...
  55. Object Replication Manager failed to process Object %1 of Type %2. This Object will be retried %3 times on the next processing ...
  56. Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle.%12 Solution: ...
  57. Object Replication Manager failed to process Object Replication File %1 as Object %2 of Type %3 referenced object of type ...
  58. Object Replication Manager failed to process Object Replication File %1. This Object Replication file has been retried %2 ...
  59. Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software ...
  60. Object {0} is missing a dependency {1}. Confirm the configuration of object {0} in the source environment and retry the migration. ...
  61. objects are associated with only this security scope. To delete this scope, you must first associate these objects with another ...
  62. of monthly traffic Out quota for Cloud Distribution Point is reached. Monthly Traffic Out quota: {1} Gb Actual Value: {2} ...
  63. Offer Status Summarizer cannot process a status message because it contains the invalid deployment ID "%6". As a result, ...
  64. Offer Status Summarizer cannot process a status message because it does not contain a deployment ID. As a result, the deployment ...
  65. Offer Status Summarizer cannot process a status message because it has an invalid message ID %1. The message ID must be within ...
  66. Offline Image Servicing Manager cannot write to the image package source location for the image with ID %1. Please make sure ...
  67. Offline Image Servicing Manager determined that update with ID %1 is not required on image with ID %2 (image index %3).%0 ...
  68. Offline Image Servicing Manager does not support image with ID %1 (image index %2) and therefore will not process this image.%0 ...
  69. Offline Image Servicing Manager failed because there is not enough free disk space left on the staging drive %1. Required ...
  70. Offline Image Servicing Manager failed to apply one or more updates on image with package ID %1 (image index %2), but continued ...
  71. Offline Image Servicing Manager failed to unmount image with ID %1 (image index %2) from mount directory %3. Error : %4.%0 ...
  72. Offline Image Servicing Manager started copying updated image with ID %1 from staging folder to the image package folder.%0 ...
  73. On site %1, found service broker queue %2 disabled. It has been enabled now.%12 Refer to the SQL view vLogs for more information.%0 ...
  74. On the dialog 2 the next control pointers do not form a cycle. There is a pointer from 3 to 4], but there is no further pointer ...
  75. One or more branch distribution points are targeted for this (package or deployment). This (package or deployment) can only ...