“GetDPLocations failed with error 0x80072efd” when trying to install the SCCM 2012 Client

I am trying to install the ConfigMgr 2012 Client on some machines but it’s failing for ALL the Clients on the subnet. If I look ccm.log it doesn’t shows any errors.

However, in ccmsetup.log I see the following:

GetDPLocations failed with error 0x80072efd

“Microsoft SQL Server reported SQL message 8169, severity 16: [42000][8169][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting from a character string to uniqueidentifier.”

I’ve noticed the Client Registration process is unsuccessful for ConfigMgr 2012 SP2/ R2 SP1 Clients I reinstall.

If I look in Ddm.log on the Site Server I see:

Microsoft SQL Server reported SQL message 8169, severity 16: [42000][8169][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting from a character string to uniqueidentifier. : SMSDBMON_ClientKeyData_PfxCertsClientKeyData_Chg_upd

Why doesn’t the Exchange Server Connector perform a full sync when multiple concurrent remote PowerShell connections are active at the same time on the same Exchange Online account?

For some reason I’ve noticed that the Exchange Server Connector doesn’t perform a full synchronisation when multiple concurrent remote PowerShell connections are active at the same time on the same Exchange Online account.

Why are Clients being Assigned to the wrong Site when I use Automatic Site Assignment?

I am trying to use Automatic Site Assignment to assign my Clients. However, my Clients are being assigned to the wrong Site.

Why after installing or upgrading the Mac Client then trying to renew the Certificate does the “Preference” pane turn blank and the “Enroll” button become active yet the certificate isn’t expired?

I’ve noticed that if I either install the Mac Client using CMEnroll or upgrade the Mac Client from Service Pack 1 (SP1) Cumulative Update 1, and then try to renew the Client Certificate the Preferences pane turns blank and the Enroll button becomes active.

However, the Client remains enrolled and the certificate isn’t expired.

Why if I Reassign an Internet-based Workgroup Client to a New Site does the Client continue to stay Assigned to the original Site until it connects to the intranet?

I’ve reassigned a Workgroup Client that’s Internet-based to a new Site whilst the Client is on the Internet. However, the Client continues to stay assigned to the original Site until it connects to the intranet.

“MSI: Setup was unable to compile the file DiscoveryStatus.mof The error code is 8004100E” when trying to deploy the SCCM 2012 Client

I am trying to install the ConfigMgr Client on some machines but it just won’t install. If I look in ccmsetup.log I see the following line:

MSI: Setup was unable to compile the file DiscoveryStatus.mof The error code is 8004100E

“CcmSetup failed with error code 0x80004005”

I am trying to install the re-install the ConfigMgr Client on a machine that used to have the Client installed but it’s failing.

If I look in ccmsetup.log on the machine it shows the following:

Current AD site of machine is
Attempting to query AD for assigned site code
Performing AD query: ‘(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow=168512907))))’
Performing AD query: ‘(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.5.1.0)(mSSMSRoamingBoundaries=)))’
Failed to get assigned site from AD. Error 0x80004005
GetADInstallParams failed with 0x80004005
Couldn’t find an MP source through AD. Error 0x80004005
No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue.
Failed to parse ‘ccmsetup’ with error 0x80004005
A Fallback Status Point has not been specified. Message with STATEID=’100′ will not be sent.
A Fallback Status Point has not been specified. Message with STATEID=’307′ will not be sent.
CcmSetup failed with error code 0x80004005

Clients not showing as Assigned despite Boundaries configured correctly

I have some Clients showing as not being assigned to a Site despite the boundary/ boundary group being setup correctly.

Why is my Client not using the Management Point specified by the CCMSetup installation property “/mp:”

I’ve installed some clients and specified the “/mp:” Command-line Property with CCMSetup.

However, post installation my Client is not using the Management Point specified.