SCCM : What are actions to do after updating the detection method

Question

SCCM : What are actions to do after updating the detection method

Izanagi76 240

Hi all,

With SCCM, I created an application deployed to one hundred machines a few weeks ago.

Today, I changed the detection method (updated the powershell script).

What does I have to do to make the change deployed on all existing machines ?*

Just waiting or may I have to do something to accelerate the propagation ?

Also, it seems that I don't have to use "update content" option only used for updated sources files, you confirmed ?

Thanks a lot,

Izanagi

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

AllenLiu-MSFT 49,441 Microsoft External Staff

Hi, @Izanagi76

Thank you for posting in Microsoft Q&A forum.

After updating the detection method for your application in SCCM, the changes will not automatically propagate to existing machines. The client will evaluate the detection method during its regular evaluation cycles. By default, client computers start a deployment reevaluation cycle every 7 days, during which they will check for compliance with the updated detection method.

If you want to accelerate the propagation of the updated detection method, you can manually trigger a policy update in SCCM console, right click the device collection, and select Client Notification > Evaluate Application Deployments.

User's image

Regarding the "Update Content" option, you are correct that it is primarily used for updating source files. It is not necessary to use this option when only changing the detection method.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

Izanagi76 240 Reputation points

2024-10-08T09:14:17.2866667+00:00

Hi @AllenLiu-MSFT

Thank you very much for your answer. However, I realize that I was not precise enough in the description of my problem.

So I precise my question :

What does I have to do to make the change deployed on all existing machines and for applications already installed.

The deployment was set as "available" and target one hundred users (and not machine as I described before sorry). The isssue is for users that have already deployed the application before the change of detection method. For these users, I see in the software center that the application revision is still the previous one, and i need to know how to make the new detection method be taking account for them without redeploying the application.

Thanks for your help.

Have a good day.

Iz.
AllenLiu-MSFT 49,441 Reputation points Microsoft External Staff

2024-10-09T08:18:05.79+00:00

I have test it in my lab, after the client get the user policy, the revision will change to the new one. You my try to manually run User Policy Retrieval & Evaluation Cycle on the client to see if it helps.

If manually trigger the cycle helps, we will consider triggering this cycle in batches.
Izanagi76 240 Reputation points

2024-10-10T13:35:49.7466667+00:00

Hi @AllenLiu-MSFT

Thanks for you answer,

It worked for users that did not install the application yet.

However, for user that have already installed the previous revision, the revision is not up to date.

Have a good day.

Iz.
AllenLiu-MSFT 49,441 Reputation points Microsoft External Staff

2024-10-11T02:28:10.19+00:00

For me, it also works for the user that have already installed the previous revision.
Izanagi76 240 Reputation points

2024-10-11T08:59:33.0733333+00:00

Ok noted. I will deep into this issue.

Iz.