%11Configuration Manager could not locate the "System Management" container in Active Directory (%1). Nor could it create a default container. This will prevent Site Component Manager and Hierarchy Manager from updating or adding any objects to Active Directory. Possible cause: The site server's machine account might not have the correct rights to update active directory. Solution: Either give the Service Account rights to update the domain's System Container, or manually create the "System Management" container in this domain's Active Directory system container, and give the site server computer account full rights to that container (and all children objects.)%0
Configuration Manager clients are only supported on Windows 2003 Server Professional SP2, Windows XP Professional SP3, Windows ...
Configuration Manager cmdlets cannot be run because Windows PowerShell 3.0 is not installed on this computer, install Windows ...
Configuration Manager console allows the user to manage the Configuration Manager site. Any site without a console will have ...
Configuration Manager could not find all of the information required to start client push installation on '{0}'. This might ...
Configuration Manager could not locate the "System Management" container in Active Directory (%1). Nor could it create a ...
Configuration Manager could not provide the data that you requested. Please refer to the Configuration Manager documentation ...
Configuration Manager created a default "System Management" container in Active Directory (%1). This will be used to publish ...
Configuration Manager creates a new revision of an application when new changes to the application or its deployment types ...
Configuration Manager determines whether this deployment type is already on a device based on applicaiton identity listed ...