Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 6, 2017 1:31 PM
Hi,
I have 2 applications and they both keep installing because the version number of the application did not change even though I have supersedence set. So because of this they both had the same detection method of the version of the .exe file. So I would like to add an "Or" to the detection method of this newest version for a date modified on the .exe file. For some reason, it is not accepting my format:
Any ideas what is wrong with my value?
TIA
All replies (5)
Friday, April 7, 2017 12:17 PM ✅Answered | 1 vote
Thanks for the replies, I found that I had to enter in the date like this 24/10/2016. Month and date and to be reversed. Thank you
Thursday, April 6, 2017 9:01 PM
Hi,
I try to do same on SCCM 1610 and it's ok... So, I ll not be able to help you...
But I enter exactly what is in this picture
If you only enter the date is it ok ?
Cause you can put this information manually
Merci de marquer comme réponse les sujets qui vous ont permis d'avancer afin que cela puisse être bénéfique aux personnes qui rencontrent le même problème.
Friday, April 7, 2017 10:05 AM
I just tried the Value as you wrote and it's a valid date time. So it looks weird that it does not work on your console.
If you put your mouse on the red mark, does it say that it's not a valid date time? Have you tried on another console?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, August 27, 2019 9:09 PM | 1 vote
Reversing the month and day isn't the answer and whoever marked this as the answer is completely wrong. What worked for me is using powershell's Get-ItemProperty command to get the LastWriteTime and then I'd use the following format for detection.
Example: 4/22/2017 9:23:20 PM
Wednesday, November 20, 2019 7:13 PM | 2 votes
It's a regional time, so what works for one person or region won't work for others, which explains why it worked for matteu and Frank but not for Gibson.
The Yamaha solution of using Get-ItemProperty to check the current regional time settings should work for anyone, just remember that you'll need to run it on the SCCM server to get its regional settings rather than your clients' version, if they happen to not be the same.