System Center Configuration Manager 2012 R2

  1. Specify the security roles that are associated with this administrative user or group. Security roles define a collection ...
  2. Specify the servers that run the Network Device Enrollment Service. These servers must be configured with a PKI client authentication ...
  3. Specify the settings for Intel AMT-based computers to be managed out of band. During AMT provisioning, Configuration Manager ...
  4. Specify the settings for Intel AMT-based computers to use for 802.1X authentication on a wired and wireless network connection. ...
  5. Specify the settings for System Health Validator points. These settings are used by all System Health Validator points in ...
  6. Specify the settings to be enforced for users. Use the checkbox to add or remove individual settings for this custom setting. ...
  7. Specify the settings to be enforced on client devices. Use the checkbox to add or remove individual settings for this custom ...
  8. Specify the site database server details. The instance name that you use for the site database must be configured with a ...
  9. Specify the site system servers that are associated with this boundary group so that clients can use for policy and content. ...
  10. Specify the software updates to apply to the selected image. You can limit available software updates by the applicable system ...
  11. Specify the source hierarchy to use for migration. When you change the source hierarchy or migration job settings, this action ...
  12. Specify the Source Site Account to use to access the SMS Provider for the source site server. This account requires Read ...
  13. Specify the Source Site Database Account to use to access the SQL Server for the source site server. This account requires ...
  14. Specify the space to reserve on each drive that is used by this distribution point. You can use drive space reserve to determine ...
  15. Specify the store name where the client certificate is located in the Computer store when you do not use the default store ...
  16. Specify the subscription ID for the cloud service that hosts this distribution point, and specify the management certificate ...
  17. Specify the TCP port number for SQL Server Service Broker. Configuration Manager uses Service Broker to replicate data between ...
  18. Specify the variables to use during the task sequence deployment. You can also enable a prestart command that will run prior ...
  19. Specify when software updates are available. After this rule is run, software updates are distributed to the content server. ...
  20. Specify when software updates are available. Software updates are available as soon as they are distributed to the content ...
  21. Specify when the program will be advertised to members of the target collection. You can also create assignments to make ...
  22. Specify when to use a proxy server for software updates. You must configure the site system role to use a proxy server before ...
  23. Specify whether Exchange Server allows external mobile device management. Mobile devices that are enrolled with Configuration ...
  24. Specify whether the Distribution Point will create a self-signed certificate or if the certificate will be imported by the ...
  25. Specify whether this will be the first site in a new hierarchy or if this site will expand an existing stand-alone primary ...
  26. Specify whether to allow clients outside these boundary groups to fall back and use this site system as a source location ...
  27. Specify whether to install the Configuration Manager client on domain controllers when you use site-wide client push installation ...
  28. Specify whether to install the Configuration Manager console to manage the Configuration Manager site from this computer. ...
  29. Specify whether to join the primary site to an existing Configuration Manager hierarchy or install the primary site as a ...
  30. Specify whether to make this task sequence available to Configuration Manager clients, and whether it is available to run ...
  31. Specify whether to update distribution points with the image after software updates are successfully applied. The image might ...
  32. Specifying a local drive on the site server or a single network path will store the site data backup and the database backup ...
  33. Specifying a local drive on the site server or a single network path will store the site data backup at the same location. ...
  34. SQL Server Backup path is empty or invalid. For remote SQL Server scenarios you should provide either a UNC path for entire ...
  35. SQL Server memory should not be left to its default configuration of unlimited memory usage. Please configure SQL server ...
  36. StartUpload replicationgroup %1 last sync version %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log ...
  37. State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are SMP ...
  38. Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number ...
  39. Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message ...
  40. Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message ...
  41. Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" running ...
  42. Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. The ...
  43. Status Manager successfully initialized the "SMS Status Messages" performance object. Every time Status Manager receives ...
  44. Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
  45. Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
  46. Status Manager was instructed by a Status Filter Rule to execute program and command-line arguments "%1" upon receipt of ...
  47. Status Manager will no longer forward status messages to the summarizer component %1 because the summarizer was disabled. ...
  48. Status messages reported by the Available Programs Manager when a specific advertised program runs and completes successfully. ...
  49. Status messages reported by the Available Programs Manager when a specific deployed program runs and completes unsuccessfully. ...
  50. Status messages reported by the SMS Client Configuration Manager when it fails to process a client configuration request ...
  51. Status messages reported by the SMS Component Status Summarizer when a server component has reported too many status messages. ...
  52. Status messages reported by the SMS Site System Status Summarizer when a storage object is inaccessible, low on storage space ...
  53. Step 1: Download a Certificate Signing Request from Microsoft Intune using the Request APNs Certificate Service Request dialog ...
  54. Successfully created {0} of {1} reports, review any warning or error messages below by double clicking the report item in ...
  55. Successfully submitted request to recreate Sql Server Broker login for sites: {0} on site database servers: {1}. This may ...
  56. Summary of computers which have the specified App-V application shortcut as created using the Application Virtualization ...
  57. Support for deploying MSADP apps through existing Windows app packages(*.appx, *.appxbundle) deployment type to Windows 8.1 ...
  58. Synchronization component failed: the synchronization component (type = %1) failed to download %2, error code: %3. Possible ...
  59. Synchronization component failed: the synchronization component failed to update the Distribution Points for the catalog ...
  60. Synchronization component failed: the synchronization component failed to update the Site Database for the catalog (type ...
  61. Synchronization component failed: Unable to read from %2. Type = %1. Possible cause: Typically, this error results when the ...
  62. Synchronization component failed: Unable to write to %2. Type = %1. Possible cause: Typically, this error results when the ...
  63. Syncml(202): Accepted for processing. The request to either run a remote execution of an application or to alert a user or ...
  64. Syncml(203): Non-authoritative response. The request is being responded to by an entity other than the one targeted. The ...
  65. Syncml(204): The request was successfully completed but no data is being returned. The response code is also returned in ...
  66. Syncml(205): The source SHOULD update their content. The originator of the request is being told that their content SHOULD ...
  67. Syncml(206): The response indicates that only part of the command was completed. If the remainder of the command can be completed ...
  68. Syncml(207): Conflict resolved with merge. The response indicates that the request created a conflict; which was resolved ...
  69. Syncml(208): Conflict resolved with client's command "winning". The response indicates that there was an update conflict; ...
  70. Syncml(209): Conflict resolved with duplicate. The response indicates that the request created an update conflict; which ...
  71. Syncml(210): Delete without archive. The response indicates that the requested data was successfully deleted, but that it ...
  72. Syncml(212): Authentication accepted. No further authentication is needed for the remainder of the synchronization session. ...
  73. Syncml(214): Operation cancelled. The SyncML command completed successfully, but no more commands will be processed within ...
  74. Syncml(413): The recipient is refusing to perform the requested command because the requested item is larger than the recipient ...
  75. Syncml(414): The requested command failed because the target URI is too long for what the recipient is able or willing to ...