System Center Configuration Manager 2007

  1. SMS Site Component Manager failed to remove all accounts, files, and registry keys associated with the SMS server components ...
  2. SMS Site Component Manager failed to remove all accounts, files, and registry keys associated with the SMS server components ...
  3. SMS Site Component Manager failed to remove the COM access registry for this component from this site system. Possible cause: ...
  4. SMS Site Component Manager failed to remove the performance counters for this component from this site system. Possible cause: ...
  5. SMS Site Component Manager removed the "%2" account from site system "%1". When SMS Site Component Manager installed SMS ...
  6. SMS Site Component Manager successfully configured site system "%1" to receive SMS server components. SMS Site Component ...
  7. SMS Site Component Manager successfully installed the COM access registry keys for this component on this site system.%0 ...
  8. SMS Site Component Manager successfully installed this component, However a reboot is required to complete the installation. ...
  9. SMS Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be ...
  10. SMS Site Component Manager successfully reconfigured site system "%1" to receive SMS server components. SMS Site Component ...
  11. SMS Site Component Manager successfully removed all accounts, files, and registry keys associated with the SMS server components ...
  12. SMS Site Component Manager successfully removed the COM access registry keys for this component from this site system.%0 ...
  13. SMS Site Component Manager successfully used the %1 service to run the following program on site system "%2": %3 %4 %5 The ...
  14. SMS Site Component Manager was instructed by SMS Setup to deinstall the site. SMS Site Component Manager will now deinstall ...
  15. SMS Site Component Manager was instructed by SMS Setup to shut down the site in preparation for a site upgrade, modification, ...
  16. SMS Site Component Manager will not deinstall any SMS server components from site system "%1" because no SMS server components ...
  17. SMS Site Component Manager will not stop any SMS server components on site system "%1" because no SMS server components are ...
  18. SMS Site Component Manager will now cease trying to deinstall all of the SMS server components from site system "%1", as ...
  19. SMS Site Component Manager will now cease trying to stop all of the SMS server components on site system "%1", as requested ...
  20. SMS Site Component Manager will now try again to deinstall all of the SMS server components from site system "%1", as requested ...
  21. SMS Site Component Manager will now try again to stop all of the SMS server components on site system "%1", as requested ...
  22. SMS Site Control Manager aborted the processing of delta site control file %1.%12 Possible cause: The delta site control ...
  23. SMS Site Control Manager added a "%1" item named "%2" to the actual site control file %5.%12 This addition occurred as a ...
  24. SMS Site Control Manager could not completely process delta site control file %1.%12 Possible cause: Some site configuration ...
  25. SMS Site Control Manager could not write a copy of the actual site control file %1 to %2. Consequently, SMS Hierarchy Manager ...
  26. SMS Site Control Manager created serial number %2 of the actual site control file %1 as a result of processing delta site ...
  27. SMS Site Control Manager created serial number %2 of the actual site control file %1.%12 This creation occurred in response ...
  28. SMS Site Control Manager created the temporary file "%1".%12 In a moment, SMS Site Control Manager will rename this file ...
  29. SMS Site Control Manager deleted the "%1" item named "%2" from the actual site control file %5.%12 This deletion occurred ...
  30. SMS Site Control Manager is beginning to process delta site control file "%1".%12 SMS server components and SMS Provider ...
  31. SMS Site Control Manager is configured so that no more heartbeat site control files will be submitted to SMS Hierarchy Manager.%12 ...
  32. SMS Site Control Manager modified the properties of the "%1" item named "%2" in the actual site control file %7.%12 This ...
  33. SMS Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to SMS Hierarchy Manager ...
  34. SMS Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to SMS Hierarchy Manager ...
  35. SMS Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to SMS Hierarchy Manager.%12 ...
  36. SMS Site Control Manager will ignore this site configuration change request ("%1" from site "%2").%12 This change request ...
  37. SMS Site Control Manager will maintain copies of the %1 most recent actual site control files in the directory "%2".%12 The ...
  38. SMS Site Control Manager wrote a copy of the actual site control file %1 to %2.%12 In a moment, SMS Site Control Manager ...
  39. SMS site servers to be upgraded, and all direct child sites of Configuration Manager primary sites must be running SMS 2003 ...
  40. SMS site servers to be upgraded, and all indirect child sites of Configuration Manager primary sites should be running SMS ...
  41. SMS Site System Status Summarizer could not access storage object "%1" on site system "%2".%12 Possible cause: The site system ...
  42. SMS Site System Status Summarizer could not access the "%1" database on SMS Site Database Server "%2". Possible cause: The ...
  43. SMS Site System Status Summarizer could not access the transaction log for the "%1" database on SQL server "%2".%12 Possible ...
  44. SMS Site System Status Summarizer detected that the "%1" database on SMS site database server "%2" has %3 KB of free space, ...
  45. SMS Site System Status Summarizer detected that the "%1" database on SMS site database server "%2" has %3 KB of free space, ...
  46. SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Degraded.%12 ...
  47. SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Failed.%12 ...
  48. SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Offline.%12 ...
  49. SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Online.%0 ...
  50. SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Unknown.%12 ...
  51. SMS Site System Status Summarizer detected that the database "%1" on SMS site database server "%2" has %3 KB of free space, ...
  52. SMS Site System Status Summarizer detected that the storage object "%1" on Branch Distribution Point site system "%2" has ...
  53. SMS Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
  54. SMS Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
  55. SMS Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
  56. SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" ...
  57. SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" ...
  58. SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" ...
  59. SMS Site System Status Summarizer has not been able to access the storage object "%1" on Site Object "%2" for %3 hours. SMS ...
  60. SMS Site System Status Summarizer still cannot access storage object "%1" on site system "%2".%12 Possible cause: The site ...
  61. SMS Site System Status Summarizer still cannot access the "%1" database on SMS Site Database Server "%2".%12 Possible cause: ...
  62. SMS Site System Status Summarizer still cannot access the transaction log for the "%1" database on SQL server "%2".%12 Possible ...
  63. SMS Site System Status Summarizer successfully accessed storage object "%1" on site system "%2".%12 Possible cause: The storage ...
  64. SMS Site System Status Summarizer successfully accessed the "%1" database on SQL server "%2".%12 Possible cause: The database ...
  65. SMS Site System Status Summarizer successfully accessed the transaction log for the "%1" database on SQL server "%2". The ...
  66. SMS Software Inventory Agent could not collect one or more files.%12 Possible cause: Software Inventory Agent needs to make ...
  67. SMS Software Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed ...
  68. SMS Software Inventory Agent raised an exception while attempting to extract file version information from file "%1".%12 ...
  69. SMS Software Inventory Agent successfully collected %1 files, totally %2 KB of data, from this computer. These files will ...
  70. SMS Software Inventory Agent successfully collected software inventory from this computer, created a Software Inventory (SINV) ...
  71. SMS Software Inventory Agent was unable to collect one or more files because the maximum size for collected files of %1 MB ...
  72. SMS Software Inventory Processor failed to process software inventory file "%1" because the file does not have a corresponding ...
  73. SMS Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2."%12 Possible cause: ...
  74. SMS Software Inventory Processor failed to process the file %1 because it is larger than the defined maximum allowable size ...
  75. SMS Software Inventory Processor has removed the oldest revision of collected file "%1" for resource "%2". The maximum revision ...