System Center Configuration Manager 2012 R2

  1. User '{0}' has authorized a software update. Details: ID = {1}, QNumbers = {2}, Product = {3}, Title = {4}, Locale = {5}. ...
  2. User '{0}' has authorized software update '{1}'. Details: ID = '{2}', QNumbers = '{4}', Product = '{5}', Title = '{3}', Locale ...
  3. User '{0}' modified a meter rule named '{6}' ({2}) for file '{3}' with a product version of '{5}' and Language ID of '{4}'. ...
  4. User '{0}' modified an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = {1}, DeviceSettingItemID = {2}). . ...
  5. User '{0}' modified software update with CI_ID '{1}'. Details: ID = '{2}', QNumbers = '{3}', CI_UniqueID = {4}, CIVersion ...
  6. User '{0}' modified the address properties for an address of type '{5}' connecting site {2} to {6} on {7} with priority {8}. ...
  7. User '{0}' requested that the CCR be generated for resource '{2}'. But no CCR is generated. Possible cause: this is not a ...
  8. User '{0}' requested that the CCRs be generated for collection '{2}' ({1}). The SMS Provider did not generate CCRs for all ...
  9. User '{0}' requested that the CCRs be generated for query named '{2}' ({1}) targeting the '{3}' class. The SMS Provider did ...
  10. User '{0}' resend software update with CI_ID '{1}' to all child sites. Update Details: ID = '{2}', QNumbers = '{3}', CI_UniqueID ...
  11. User updated the schedule of Deployment (ID=%1), PresentTime and ExpirationTime were changed from %2 to %3, mandatory schedule ...
  12. User updated the schedule of Deployment (ID={0}), PresentTime and ExpirationTime were changed from {1} to {2}, mandatory ...
  13. utility initiated by Site Backup did not complete in timely fashion. Terminating this utility. You may need to get its generated ...
  14. Valid folder names must be less than 127 characters and must not contain any of the following characters: / | \ : ? " < > ...
  15. Verifies SQL Server is configured to reserve at least 8 gigabytes (GB) of memory, 4 gigabytes (GB) for secondary site, by ...
  16. Verifies that a valid Service Principal Name (SPN) is registered in Active Directory Domain Services for the account configured ...
  17. Verifies that all of the clients assigned to the site to be upgraded meet the minimum operating system requirement of Windows ...
  18. Verifies that all site servers in the hierarchy meet the Configuration Manager minimum version that is required for upgrade. ...
  19. Verifies that the machine account of site server has administrative rights on the management point and distribution point ...
  20. Verifies that the Microsoft .NET Framework version 3.5 is installed on Configuration Manager central administration site ...
  21. Verifies that the Microsoft .NET Framework version 4.0 is installed on Configuration Manager Secondary site computers for ...
  22. Verifies that the Microsoft Remote Differential Compression (RDC) library is registered on the computer specified for Configuration ...
  23. Verifies that the operating system meets the minimum requirement of Windows Server 2003 for distribution point installation. ...
  24. Verifies that the site server is processing critical inboxes in a timely fashion, and that inboxes do not contain files older ...
  25. Verifies that the site server operating system meets the minimum requirement of Windows Server 2008 SP1 for site server installation. ...
  26. Verifies that the site server operating system meets the minimum requirement of Windows Server 2008 SP2 for site server installation. ...
  27. Verifies that the site server to be upgraded meets the minimum operating system requirement of Windows Server 2003 SP1 for ...
  28. Verifies that the SQL Server database collation settings of the tempdb database and site database to be upgraded are the ...
  29. Verifies that the SQL Server instance and Configuration Manager site database (if present) are configured to use a supported ...
  30. Verifies that the user account running Configuration Manager Setup has been granted sysadmin SQL Server role permissions ...
  31. Verifies that the user account running Configuration Manager Setup has been granted sysadmin SQL Server role permissions ...
  32. Verifies that the user account running Configuration Manager Setup has been granted sysadmin SQL Server role permissions ...
  33. Verifies that the version of Microsoft SQL Server installed on the computer selected to host the site database meets the ...
  34. Verifies that the version of Microsoft SQL Server installed on the computer selected to host the site database meets the ...
  35. Verify that the site server has available memory and that there is enough free disk space to create the instruction file. ...
  36. Verify the expand primary site is standalone primary site, and has same version, different sitecode to the central site to ...
  37. Verify the following information and click Finish to complete the capture process. If the information is incorrect, click ...
  38. View a list of primary sites located within the source hierarchy and specify the corresponding servers within the Configuration ...
  39. View and manage conflicting records for clients. Use conflicting records to identify clients that might be duplicates because ...
  40. View and manage the status of all sites in the hierarchy by using a hierarchy diagram or a geographical view. The geographical ...
  41. View the properties for the distribution point that is shared by Configuration Manager 2007 and System Center 2012 R2 Configuration ...
  42. Visit the System Center Configuration Manager Community page to get connected with other Configuration Manager community ...
  43. Visit the System Center Configuration Manager Setup/Deployment forum on Microsoft TechNet to get assistance from fellow community ...
  44. Visit the System Center Configuration Manager website to learn more about System Center Configuration Manager and access ...
  45. Wait for BitLocker to complete the drive encryption process on all drives before Configuration Manager continues to run the ...
  46. Warning Could not validate if the service certificate is capable of key exchange. Please ensure your certificate has the ...
  47. Warning The following DNS names were found in the service certificate based on the Subject Name and the Subject Alternate ...
  48. Warning: Mobile Device Management is not yet enabled. To enable use the Add Site System Roles wizard to add the Intune Connector ...
  49. Warning: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate request pending.%12 ...
  50. Warning: The certificate associated with this media will expire in %1!u! hour(s) and %1!u! minute(s). A valid certificate ...
  51. Warning: This computer program is protected by copyright law and international treaties. Unauthorized reproduction or distribution ...
  52. Warning: This computer program is protected by copyright law and international treaties. Unauthorized reproduction or distribution ...
  53. We were able to locate a server successfully, but enrollment could not complete. Please verify your email address and enrollment ...
  54. We were able to locate a server successfully, but enrollment could not complete. Please verify your email address and enrollment ...
  55. When a client requests the content for this package and it is not available on any preferred distribution points for the ...
  56. When a computer already has the Configuration Manager client installed, you can repair, upgrade, or reinstall the client ...
  57. When a software update installation exceeds the maximum run time setting, Configuration Manager no longer monitors the installation. ...
  58. When a system restart is required for a software update installation to complete, clients will be prevented from restarting ...
  59. When a template is used to create a deployment, the deadline setting in the deployment defaults to the time an update is ...
  60. When an error occurs in a task sequence, a dialog box is displayed that is dismissed automatically after a default time-out ...
  61. When any software update deployment deadline is reached, install all other software update deployments with deadline coming ...
  62. When clients sign data and communicate with site systems by using HTTP, this option requires the clients to use SHA-256 to ...
  63. When connecting to "%1", the migration data gathering process encountered a source site code ("%2") already being used for ...
  64. When creating a page blob in Windows Azure, the size must be a multiple of 512 bytes. Make sure any files uploaded as part ...
  65. When CRL checking is enabled, the out of band service point verifies on startup that the AMT provisioning certificate is ...
  66. When deploying a new Virtual Machine, the OSDiskStorageBlob needs to be a location within the App Controller namespace and ...
  67. When joining a virtual machine to a domain, the user name used must be in one of the formats: domain\username or username@domain. ...
  68. When RCM configures dview for table table %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.%0 ...
  69. When RCM creates the linked server for %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.%0 ...
  70. When RCM renames table %1 to %2_RCM for dview, an exception has occurred - %3.%12 Refer to rcmctrl.log for further details.%0 ...
  71. When RCM tries to clean old replicated data on table %1 for dview, an exception has occurred - %2.%12 Refer to rcmctrl.log ...
  72. When recovering a central administration site, you have the option to specify a reference primary site to use as the authoritative ...
  73. When recovering a primary site, you have the option to specify the central administration site to which the primary site ...
  74. When set this value specifies the property name that will be used to select the scope node during a user double-click operation. ...
  75. When software updates are not available on any preferred distribution points, clients can download and install software updates ...