%11ConfigMgr has detected a record that might be conflicting with the following client record in the site database: %1.%12 Possible cause: %1 has been imaged, recovered from backup, or migrated to a new computer. Solution: In the ConfigMgr console, under Computer Management, in the Conflicting Records node, right click %1 and then choose one of the following options: Merge to match the conflicting record with the existing record, New to create a new client record, or Block to block this record from being a client.%0
ConfigMgr Clients must have the Windows Update Agent installed before they can install updates. We recommend that you let ...
ConfigMgr could not provide the data that you requested. Please refer to the ConfigMgr documentation for troubleshooting ...
ConfigMgr could not update image properties because of the following error: {0} Please confirm that the ConfigMgr provider ...
ConfigMgr failed to connect to the site server's certificate store to validate the certificate based on the thumbprint you ...
ConfigMgr has detected a record that might be conflicting with the following client record in the site database: %1.%12 Possible ...
ConfigMgr has detected that this record has the same hardware ID as an existing client record. You can create a new record ...
ConfigMgr installation cannot complete until the required component, MMC 3.0, is installed. MMC 3.0 is available for download ...
ConfigMgr Service Manager ConfigMgr Service Manager ConfigMgr Service Manager.Document ConfigMgr Service Manager Document ...
ConfigMgr site component manager has exceeded the timeout value. This might be due to slow network response or failure of ...