%11PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2.%12 Possible cause: PXE service point encountered an error when connecting to SQL Server. Solution: Verify that the SQL Server is properly configured to allow PXE Service Point access. Verify the account used by the PXE service point to connect to the SQL Server is a member of the SMS_SiteSystemToSQLConnection_group on the SQL Server, that the account is not locked out, and that the account password is not expired. Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL Server SPNs are correctly registered. %0
Provisioning for %1 %2 failed due to an improper or missing provisioning certificate.%12 Possible cause: This condition is ...
PXE and Multicast are no longer enabled on this distribution point. Do you want Configuration Manager to remove Windows Deployment ...
PXE control manager could not update its settings to the new values.%12 Possible cause: PXE may be overloaded. Solution: ...
PXE Control Manager detected PXE service point is not responding to PXE requests. The error is %1.%12 Possible cause: PXE ...
PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2.%12 ...
Query rule "{0}" is invalid. The rule may be based on a Hardware Inventory class not collected at the destination, or be ...
Query timed out while verifying the account permissions. Clients may not be able to execute the program. Do you still want ...
RCM has finished processing resync for replicationgroup %1 to version %2.Please refer to rcmctrl.log for further details.%0 ...
Read the existing "%1" inbox definition. The inbox should exist on the Client Access Point with the relative path "%2".%12%3%4%5%6%7%8%9%10%0 ...