%11Client Configuration Manager cannot connect to the machine "%1".%12 Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the site server computer account or (if specified) the Client Push Installation account has the required privileges, as specified in the ConfigMgr Documentation. Possible cause: A Client Push Installation account was not specified, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active Client Push Installation accounts are specified in the Configuration Manager console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines.%0
Click OK to delete the displayed {0} and all of their revisions. You can delete specific revisions in the Revision History ...
Click on any item to display details about how to resolve the problem, or view the ConfigMgrPrereq.log to help identify problems. ...
Click Summary to install the new secondary site by using default settings, or click Next to configure settings for the secondary ...
Click the "Browse by" button to see a list of software titles available to you, or search by typing the keywords in the search ...
Client Configuration Manager cannot connect to the machine "%1".%12 Possible cause: The client is not accessible. Solution: ...
Client Configuration Manager cannot find machine "%1" on the network.%12 Possible cause: The client is offline. Solution: ...
Client Configuration Manager cannot install a client to machine "%1", because it is a domain controler. CCM is currently ...
Client Configuration Manager cannot install a client to machine "%1", because it is not a supported platform for this action. ...
Client Configuration Manager cannot install the client to machine "%1". This platform is not supported. Refer to the ConfigMgr ...