SCCM 2012 R2 Detection Rule not working

[DalekSec]

I've created an update application in SCCM 2012 R2 for fusion 360, as it needs to updated regularly.

 

The problem i have is as soon as i deploy it it comes back saying 'The application was not detected after installation completed' Which i think it's lying as it comes back instantly saying this.

 

It's installed via a script install and then the Detection Rule works on Folder detection. Is there a better detection method?

 

I don't think it's the install as i used the same settings for the previous update which worked fine (Just changed the install .exe each time), but since the first update it's not been working.

Edited October 3, 2017 by ZeroHour

[skell]

File version on the main exe might be a better way to go, if it changes between releases.

[Steve21]

If it's a 64bit/32bit install on 64bit machine etc did you check the box to allow it to work on both? Else could be detecting in wrong program files etc.

 

But was pretty sure the detection method is file based not folder? You got a screenie of what you got setup?

 

Steve

[DalekSec]

File version on the main exe might be a better way to go, if it changes between releases.

 

It does but the .exe doesn't make it's way onto the client, it stays on the server. So won't know if the client is updated

If it's a 64bit/32bit install on 64bit machine etc did you check the box to allow it to work on both? Else could be detecting in wrong program files etc.

 

But was pretty sure the detection method is file based not folder? You got a screenie of what you got setup?

 

Steve

 

Yes the box is ticked and it is folder based.

 

[skell]

Any .dll files change? A file on the client should reliably change.

 

You could also look at the registry and see if the client version is indicated there as well.

[Steve21]

Did you try it without the time? I know most of the SCCM stuff requires an AM/PM variable even when a time shouldn't need one, might be worth trying it with just the date as a quick test?

 

It's like when scheduling an automated shutdown you need to use like 18:00 PM etc, even though logic says 18 is PM!

 

Steve

[Arthur]

Yes the box is ticked and it is folder based.

For the operator 'Greater than or equal to' might be a better choice than just 'Greater than' otherwise it won't match.

[DalekSec]

The folder does change with every update, i now think it's not detection.

 

As I've manually installed the update on one PC and it's come back saying it's installed on the deployment, which shows the detection rule is working surely?

 

Might try re-creating the whole application

[Geoff]

Sounds like your installer is guffed if it works manually.

[DalekSec]

Sounds like your installer is guffed if it works manually.

Yepp, which is strange as it was the same settings as i used for the last install which worked fine!

[DalekSec]

Well, I've just re-made the application and deployed it and it seems to be working now... i don't know what the problem was, it was setup the same as the one that didn't work!