Hi all,
I am having troubles with deploying Applications (in this specific case it's Office 2016 ProPlus C2R) when the detection method has been changed afterwards.
SCCM is updated to version 1606, the client runs Windows 10 Enterprise.
To save some time I copied my existing Office 2013 application, changed the content and deployed it to my test machine. Unfortunately I forgot to change the detection method to something that is unique for Office 2016 and so the existing Office 2013 and the new Office 2016 had the same detection method which caused the Software Center to show the new one as already installed.
So far so dumb, but changing the detection method will fix that issue. At least I thought.
I changed the detection method to Windows Installer and added the new Product Code. Afterwards updating the content on my DP and enforcing the polices on my client. But exactly the same behavior, it's still shown as installed.
As that was two days ago, I had a look at the AppDiscovery.log today and noticed that the client is still trying to detect the old revision.
What am I supposed to do in order to get the discovery process looking for the new revision?
The last time I had such an issue was with the last time we rolled out Office 365. I had a script that for the installation and changed the script afterwards in order to reset the licensing (there were some issues). Even some weeks later there were clients that ran the installation with the old version of the script (they downloaded it the same day as the installation). We never found a solution for this issue.
Maybe I am missing some basic knowledge.
Thank you in advance
Best regards
Fabian