System Center Configuration Manager 2007

  1. SMS WSUS Configuration Manager has detected that Software Updates Point is not configured yet. client boot-strapper packag ...
  2. SMS WSUS Configuration Manager has detected that WSUS Server "%1" cannot sync from the parent WSUS Server as there is no ...
  3. SMS WSUS Configuration Manager successfully published client boot-strapper package "%1" with version "%2" to the Software ...
  4. SMS WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" to the Software Updates Point.%12%0 ...
  5. SMS WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" with version "%2" to the Software ...
  6. SMS WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server of version 3.0 or greater ...
  7. SMS WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server remoting API's of version ...
  8. Software metering could not find the "%1" ODBC Driver.THIS DRIVER IS REQUIRED FOR SOFTWARE METERING. Only the following ODBC ...
  9. Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was downloaded and updated ...
  10. Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was not available.%12%0 ...
  11. Software update installation failed: the scheduled installation window expired while software update installation was not ...
  12. Software update installation was postponed: awaiting system restart. Possible cause: Previous installations might have replaced ...
  13. Software update point site system role does not exist. Create software update point site system role before running MSAC ...
  14. Software updates allows administrators to assess software update compliance and provides tools to generate and track software ...
  15. Software updates cannot be installed because a system restart is in progress. To install this update, please try again after ...
  16. Software updates evaluation failed: could not determine the advertisement assignment schedule. This is needed to calculate ...
  17. Software updates evaluation failed: could not load software updates authorization list %1. Possible cause: authorization ...
  18. Software updates evaluation failed: could not locate the scan component of the specified software update inventory tool. ...
  19. Software updates evaluation failed: could not run the scan component of the specified software update inventory tool on the ...
  20. Software updates evaluation failed: error loading Win32_PatchState class from WMI. Possible cause: This is most likely a ...
  21. Software updates evaluation failed: error storing Win32_PatchState class into WMI. Possible cause: This is most likely a ...
  22. Software updates evaluation failed: invalid syntax or value for the specified scheduled installation window (/l). Possible ...
  23. Software updates evaluation failed: unable to load resource file. Possible cause: file not present. Solution: Verify that ...
  24. Software updates evaluation was ended due to a scheduled installation window violation (installation started too early.) ...
  25. Software updates evaluation was ended due to a scheduled installation window violation (installation started too late.) Solution: ...
  26. Software Updates Installation Agent completed successfully and suppressed the required system restart because the program ...
  27. Software Updates Installation Agent completed successfully and suppressed the required system restart because the program ...
  28. Software updates installation was automatically postponed: a pre-installation restart was required, but the user did not ...
  29. Software updates installation was automatically postponed: the user did not choose to install the updates and the grace period ...
  30. Software updates installation was postponed: The user postponed the required pre-installation restart. Possible cause: Previous ...
  31. Software updates installation was postponed: the user rescheduled the required system restart. Possible cause: Previous installations ...
  32. Some custom hardware inventory modifications may conflict with the default hardware inventory settings provided by Configuration ...
  33. Some or all of the MP Component Managers could not be started.%12 Possible cause:MP didn't get installed properly. Solution: ...
  34. Some or all of the MP Component Managers could not be stopped.%12 Possible cause:MP didn't get installed properly. Solution: ...
  35. Source site {0} specified in the XML file is not in the connected site hierarchy. Do you want to proceed with the current ...
  36. Specified installation location for the provider is same as the current provider location. Would you like to reinstall the ...
  37. Specify a network path (UNC) where ConfigMgr will maintain drivers added to this package. The directory will be created if ...
  38. Specify an existing ConfigMgr user to modify, or add a new user by typing a user name in the form domain\user. If you enter ...
  39. Specify rules containing configuration items and configuration baselines to define how compliance will be assessed on client ...
  40. Specify the accounts to use to install the ConfigMgr Client. ConfigMgr will try the accounts in order until it finds an account ...
  41. Specify the client installation options that are used to install ConfigMgr client to a collection, a query, or a computer. ...
  42. Specify the default settings on all clients to indicate that a remote control session is active. These settings apply only ...
  43. Specify the directory that contains the source files for this package. Click the "editions" tab to specify the operating ...
  44. Specify the existing collection that you want to advertise the program to, or create a new collection to receive the advertisement. ...
  45. Specify the filter to apply when viewing the column values. When applying the filter, ConfigMgr treats the column data as ...
  46. Specify the image file that contains the {0} for this package. If the file contains multiple images, use the Image tab to ...
  47. Specify the location of the source files for the package. The source directory must be accessible to the site server computer ...
  48. Specify the locations to store the site data backup and site database backup. The site server machine account must have full ...
  49. Specify the locations to store the site data backup. The site server machine account must have full control of the destination ...
  50. Specify the name and path of the output files which will be written to the selected media type. If multiple pieces of media ...
  51. Specify the names of users and groups permitted to view and control client computers by using ConfigMgr Remote Tools and ...
  52. Specify the number of collections, packages, and advertisements that were created at this site after the site was last backed ...
  53. Specify the numbers of collections, packages, and advertisements created at this site after it was last backed up to ensure ...
  54. Specify the organization specific text displayed to users when deploying software, operating system deployments, or software ...
  55. Specify the package to add this driver to. Drivers must be added to packages and deployed to distribution points before computers ...
  56. Specify the settings for System Health Validator points. These settings are used by all System Health Validator points in ...
  57. Specify the site code and type for a site that was set as a child of the selected parent site after the backup on monday, ...
  58. Specify the SQL statement to return the data for the report. The order of the columns in the SQL statement determines the ...
  59. Specify the user accounts on the source computer to migrate to the destination computer. If no user accounts are specified, ...
  60. Specify when the program will be advertised to members of the target collection. You can also create an assignment to make ...
  61. Specify when the program will be advertised to members of the target collection. You can also create assignments to make ...
  62. Specify where this package is stored on distribution points. These settings apply to all distribution points receiving the ...
  63. Specify whether at deadline Wake On LAN will be used to send wake-up packets to computers that require updates in this deployment. ...
  64. Specify whether the PXE service point will create a self-signed certificate or if the certificate will be imported by the ...
  65. Specify whether the state migration point should reject new requests to store state migration data and respond only to restore ...
  66. Specify whether this package contains source files. If it does, specify the initial location of the files and set additional ...
  67. Specify whether this site system will gather status information from client computers unable to communicate with site systems ...
  68. Specify whether this site system will provide a location where clients can determine which management point to communicate ...
  69. Specify whether this site system will provide a location where clients can exchange data with the ConfigMgr site services. ...
  70. Specify whether this site system will receive status information from clients unable to communicate with their management ...
  71. Specify whether to advertise a program from this package to client resources. If the program is not advertised, the package ...
  72. Specify whether to allow clients that are within the boundaries for one or more protected distribution points to download ...
  73. Specify whether to allow clients that are within the boundaries of one or more protected distribution points to download ...
  74. Specify whether to enable a recurring schedule for installing required software updates on this computer before the configured ...
  75. Specify whether to link to computer details or to another report. If you link to computer details, specify which column in ...