%11Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart Collection Evaluator. You can use Configuration Manager Service Manager, which is invoked from the Configuration Manager Console, to stop and start components.%0
Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source ...
Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the site database. ...
Collection Evaluator failed to update the membership of collection "%1".%12 Possible cause: SQL Server problem. Solution: ...
Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3).%12 Possible cause: Inventory or Resource ...
Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". ...
Collection Evaluator successfully processed %1 client updates for collection %2. Original clients number: %3, added: %4, ...
Collection migration jobs migrate collections and the objects related to the collections that you specify. Object migration ...
Communication issues on mobile devices that are managed by the Configuration Manager client for Windows CE and that are not ...
Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...