SCCM Client Deployment detection failing

%3CLINGO-SUB%20id%3D%22lingo-sub-1502910%22%20slang%3D%22en-US%22%3ESCCM%20Client%20Deployment%20detection%20failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1502910%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20All.%26nbsp%3B%20I'm%20using%20Intune%20with%20AutoPilot%2C%20and%20I've%20gotten%20everything%20working%20well%2C%20even%20HAADJ%20over%20VPN.%20(Thanks%20for%20the%20VPN%20support!!!)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20problem%20I%20seem%20to%20be%20having%20at%20the%20moment%20is%20that%20I'm%20deploying%20the%20SCCM%20client%20via%20Intune%20in%20the%20User%20Scope%2C%20and%20it%20installs%20fine.%26nbsp%3B%20Intune%20recognizes%20that%20the%20device%20is%20now%20being%20co-managed%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20no%20matter%20what%20I've%20tried%2C%20the%20detection%20rule%20for%20the%20SCCM%20client%20continues%20to%20fail%2C%20marking%20it%20as%20a%20failed%20deployment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20MSI%20using%20the%20Product%20GUID%2C%20detecting%20the%20ccmexec.exe%20with%20Version%2C%20a%20custom%20detection%20rule%20that%20looks%20for%20various%20files%2Ffolders%2Fregistry%20keys%2C%20but%20nothing%20will%20identify%20the%20deployment%20of%20the%20client%20as%20successful.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20client%20is%20deployed%20as%20a%20Win32%20app.%26nbsp%3B%20The%20Windows%20version%20is%201909.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20reviewed%20the%20Intune%20Management%20Extension%20logs%2C%20and%20other%20than%20saying%20that%20the%20detection%20rule%20failed%2C%20I%20don't%20see%20anything%20else%20helpful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1502910%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

Hello, All.  I'm using Intune with AutoPilot, and I've gotten everything working well, even HAADJ over VPN. (Thanks for the VPN support!!!)

 

The only problem I seem to be having at the moment is that I'm deploying the SCCM client via Intune in the User Scope, and it installs fine.  Intune recognizes that the device is now being co-managed, etc.

 

However, no matter what I've tried, the detection rule for the SCCM client continues to fail, marking it as a failed deployment.

 

I've tried MSI using the Product GUID, detecting the ccmexec.exe with Version, a custom detection rule that looks for various files/folders/registry keys, but nothing will identify the deployment of the client as successful. 

 

The client is deployed as a Win32 app.  The Windows version is 1909.

 

I've reviewed the Intune Management Extension logs, and other than saying that the detection rule failed, I don't see anything else helpful.

 

Any ideas would be appreciated.

4 Replies
Highlighted

@relRGB Hi, I'm struggeling with the same problem but I am not even that far I think.

I receive receive errors regarding AAD token request failed when I want to install using Winapp32.

 

May I ask which method and command line you are using?

 

Highlighted

@Matthias_Hei

@relRGB 

 

Hi, we had the same issue. We´re using an regkey as detection. I´ve attached a PDF how we do it (german).

 

Hope that helps.

 

Update: cant upload files. I will send both of you an link.

BR

Tim

Highlighted

@Matthias_Hei I got the command line from the SCCM Console.

 

Go to Administration/Cloud Services/Co-management

Right-click on CoMgmtSettingsProd

Choose Properties

 

On the Enablement tab, you can see at the bottom of the screen the command line arguments to use to install.

 

Highlighted

@relRGB Try to use a key under Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup
Other keys like CCM are not yet available at the moment the detection is performed, they`re added short after that.