System Center Configuration Manager 2007

  1. Specifying a local drive on the site server or a single network path will store the site data backup and the database backup ...
  2. Specifying a local drive on the site server or a single network path will store the site data backup at the same location. ...
  3. SQL Backup path is empty or invalid. For remote SQL scenarios you should provide either a UNC path for entire backup or provide ...
  4. SQL Server cannot be started on computer %s. Either the Windows server is not responding or the SQL Server is not fully installed. ...
  5. SQL Server installation is currently in progress and cannot be halted. If you quit Setup now, you must run SQL Server setup ...
  6. Status messages reported by the Available Programs Manager when a specific advertised program runs and completes successfully. ...
  7. Status messages reported by the Available Programs Manager when a specific advertised program runs and completes unsuccessfully. ...
  8. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it detects that the basic SMS client services were installed. ...
  9. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to deinstall the Advertised Programs Client Agent. ...
  10. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to deinstall the Event to Trap Translator Client ...
  11. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to deinstall the Hardware Inventory Client Agent. ...
  12. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to deinstall the Software Inventory Client Agent. ...
  13. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to deinstall the Software Metering Client Agent. ...
  14. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to install the Advertised Programs Client Agent. ...
  15. Status messages reported by the SMS Cli. Comp. Instl. Mgr. when it fails to install the Event to Trap Translator Client Agent. ...
  16. Status messages reported by the SMS Client Configuration Manager when it fails to process a client configuration request ...
  17. Status messages reported by the SMS Component Status Summarizer when a server component has reported too many status messages. ...
  18. Status messages reported by the SMS Site System Status Summarizer when a storage object is inaccessible, low on storage space ...
  19. Summary Information: In the past 24 hours, SMS Windows NT Remote Client Installation Manager examined %1 discovery data records ...
  20. Supports server-based package distribution. Can support native mode operation, Internet connected clients, and BITS transfers. ...
  21. Supports server-based package distribution. Can support secure mode operation, Internet connected clients, and BITS transfers. ...
  22. surplus licenses of "%2" (ProdRef="%3") were removed from the license store at the site server and added to the software ...
  23. Synchronization component failed: the synchronization component (type = %1) failed to download %2, error code: %3. Possible ...
  24. Synchronization component failed: the synchronization component failed to update the Distribution Points for the catalog ...
  25. Synchronization component failed: the synchronization component failed to update the Site Database for the catalog (type ...
  26. Synchronization component failed: Unable to read from %2. Type = %1. Possible cause: Typically, this error results when the ...
  27. Synchronization component failed: Unable to write to %2. Type = %1. Possible cause: Typically, this error results when the ...
  28. Syntax: REMOTE 2 \Site Server Name\ where Address = valid IP Address or Host Name or REMOTE 0 \Site Server Name\ where Resource ...
  29. Systems Management Server cannot create the object "%1" in Active Directory. Possible cause: This site's SMS Service account ...
  30. Systems Management Server cannot delete the object "%1" in Active Directory. Possible cause: This site's SMS Service account ...
  31. Systems Management Server cannot update the already existing object "%1" in Active Directory. Possible cause: This site's ...
  32. Systems Management Server cannot update the dNSHostName property for the existing object "%1" in Active Directory. This property ...
  33. Target site {0} is off-line, upgrading, or being installed and should not be modified until it returns to an active state. ...
  34. Task Sequence: %1!s! has failed with the error code ( 2!08lX!). For more information, please contact your system administrator ...
  35. Templates can be used to define deployment properties, such as target collection, package, and client settings. The properties ...
  36. The "%1" item in a site configuration change request in delta site control file "%2" does not specify the password for the ...
  37. The "%1" item in a site configuration change request in delta site control file %2 contains information for the software ...
  38. The "%1" item in a site configuration change request in delta site control file %2 does not contain configuration information ...
  39. The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as ...
  40. The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site ...
  41. The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site ...
  42. The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site ...
  43. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
  44. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SMS Service ...
  45. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SMS site ...
  46. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the software ...
  47. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator ...
  48. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator ...
  49. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL server ...
  50. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL server ...
  51. The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
  52. The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
  53. The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of ...
  54. The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting ...
  55. The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting ...
  56. The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation ...
  57. The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. ...
  58. The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted ...
  59. The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted ...
  60. The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive ...
  61. The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted ...
  62. The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted ...
  63. The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not ...
  64. The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does ...
  65. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that ...
  66. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ...
  67. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that ...
  68. The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match ...
  69. The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account ...
  70. The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account ...
  71. The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting ...
  72. The "%1" item in a site configuration change request in delta site control file %2 specifies an SMS Service account name ...
  73. The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should ...
  74. The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at ...
  75. The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than ...