Detection Rule for MSI Version failes

Hello @ll,
A few month ago I created an application to install Adobe Reader Version 11.0.07. The detection rule is very simple "MSI Product Code = {xxxx} and MSI Version Greater or Equal 11.0.07". Due a small mistake, some clients have installed an update for
the Adobe Reader and the MSI Version is now 11.0.08. Shouldn't be a problem but the detection failes and the agent try to install 11.0.07.
AppDiscovery.log
Performing detection of app deployment type Adobe Reader Update 11.0.07(ScopeId_5951BA16-C34F-419B-8335-E0843816720D/DeploymentType_7e8e9e26-0de0-4209-af64-5f11296bd054, revision 4) for system.
+++ Application not discovered. [AppDT Id: ScopeId_5951BA16-C34F-419B-8335-E0843816720D/DeploymentType_7e8e9e26-0de0-4209-af64-5f11296bd054, Revision: 4]
+++ Did not detect app deployment type Adobe Reader Update 11.0.07(ScopeId_5951BA16-C34F-419B-8335-E0843816720D/DeploymentType_7e8e9e26-0de0-4209-af64-5f11296bd054, revision 4) for system.
Used PS to verify ProductCode and ProductVersion
ProductName ProductCode ProductVersion
Adobe Reader XI (11.0.08) - Deutsch {AC76BA86-7AD7-1031-7B44-AB0000000001} 11.0.08
I've no idea why the detection rule does not work

Yes, I know those dots are required in those version numbers, that was not the point I was trying to make. I was trying to say that it returns that specific version numbers as a string instead of an integer, which causes the equation to fail.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

  • How to correctly set detection rules for date modified

    How are application detection rules for modified or created date calculated.  For example if I want the detection rule to use a file that was modified today or any day after today do I set it as Greater than or equal to or less then or equal to in
    the Detection rule?

    You would use Greater than Or Equal To. Greater than or equal to means that time or anything after. The latter would be that time or before
    Dustin Estes - MCP | www.dustinestes.com

  • Detection rule for Office 365

    Hi
    I'm about to create a application for Office 365 in Configuration Manager 2012 R2.
    I've seen recommendation to look for %programfiles%\Microsoft Office 15\root\Office15. But will that not break when office is upgraded on the client?
    In registry I've HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\O365ProPlusRetail - en-us. And for the looks of it I cannot use this if a user decides to download and install a different version than en-us.
    Any idea on what detection rule I should use for Office 365 that works for next versions of Office 365 (office 2015)?

    Using folder check for "%programfiles%\Microsoft Office 15\root\Office15", might be a bad
    idea.
    You need to use the full path to WINWORD.exe or something.
    If you install Visio using Office 365 it will end up in the same folder, and that will make wrong detection of the application!
    You don't have to worry about the version of Office when running Office 365, but you can get the version directly from the
    WINWORD.exe if you for some reason wants to use it...
    I would recommend that you don't check for the version though.
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
    @ronnipedersen

  • Detection Rule for Office 2010 SP2 deployment

    Hello Everyone,
    Could anyone please put me on the right track configuring a Office 2010 SP2 deployment? 
    The Office 2010 SP2 is a EXE file and not a MSI and I am not sure witch Clause to use as detection method.
    Thank you

    Use the MSI guid that's found in the proplusww.msi, this file can be found from the Office installation files...

  • Detection Method of Date Modified fails due to copied files date modified change

    I've been working through an issue for some time now and I think it's a bug with SCCM 2012 SP1. I've built literally 50 deployments in "Application Management" in SCCM 2012, but I've been chasing my tail on a few of them throwing the
    "succeeded but couldn't detect" error. The few that have given me problems are all copying text files and then detect the modified date to verify that the file is there. All worked when I initially built them in Windows 8 but are now failing
    randomly...even on a machine where they previously worked and I deleted the files to test the deployment again. 
    What I'm doing:
    My java deployment requires policies which we control with the Deployment.config, deployment.properties and java.policy files. A simple script creates the directories and copies the files. I then create a deployment type for this "ConfigFileCopy.cmd"
    and create a detection rule for each file that I am moving over. The detection rule looks for a "date modified" date between the beginning and end of the date for the day I modified the file. This allows me to modify the files to change our
    java policies and then redeploy them with the "new" modified date as the detection rule, which forces the update.
    The problem:
    When I first created my deployment, everything worked pretty well. The files copy out and the script runs successfully. There were some minor tweaks I need to make to my scripts, so I did and then updated the content for the deployment type. I believe this
    is where things go a little wonky. At this point, my deployment starts failing with the "0x87D00324" error.
    Looking through the logs, everything looks good. The reason configuration manager is failing on detecting the modified date for those files, as it turns out, is because the modified dates don't meet the criteria. So that part is properly failing the detection.
    The problem is that the modified dates are correct on the server but not the client. Looking in c:\windows\ccmcache, I can see multiple folders....presumably one for each version of the application that I updated. Looking at any of the newer content folders
    for this app, the modified dates are the date and time the file was copied out to the workstation, which is incorrect as the file hasn't been modified during that process.
    The odd part, is that this doesn't happen EVERY time on EVERY machine. My primary desktop is windows 8.1 and received the files correctly and installed without issue. My test win 8.1 laptop initially received them correctly, but then as I refined the scripts
    it began picking up the wrong modified dates and started failing.
    I found a similar issue to this existed in SCCM 2007 (http://support.microsoft.com/kb/2276865) so I suspect that this is truly just a bug that hasn't been addressed (or maybe is fixed in R2). Unfortunately
    we have business reasons we can't upgrade to R2 at this time so I'm hoping someone has experienced this and has some sort of work around that might get me by for now. If someone can confirm it is fixed in R2, that would help my case to upgrade as well.  
    I can work around the issue by changing my logic to detect any date greater than a specific date. But I shouldn't have to do that and I'm concerned there are scenarios I haven't thought of that will cause unexpected behavior or failures with that.
     

    This outlines the behavior. It's apparently by design. 
    "SCCM has a habit of changing the ‘Date Modified’ timestamp of all files it delivers when it detects an ‘upgrade’ of the source files for that application. It typically does not touch the timestamp
    of the source files if it delivers a brand new install to a client that has never received the software, however if a single file in the source folder is changed for that application, then SCCM tries to use a previous version of the application in the cache
    (C:\windows\ccmcache) and only downloads the new file that has change. This results in all files having their ‘Data Modified’ timestamp changing (except for the brand new file). Therefore determining if that application has delivered
    successfully using ‘Date Modified’ timestamps is not recommended. The key to seeing this process in action is looking at the file properties in the
    C:\windows\ccmcache\<sccm code> folder for that application, particularly before and after a file is updated in the original source SCCM application folder."
    http://blog.kloud.com.au/tag/sccm/

  • SCUP detection for APSB14-01 failed for Adobe Reader version 10.1.2

    The detection rule ran and found that the patch was not required for reader version 10.1.2.
    Anyone know how the detection rule works and what is it looking for?

    Further investigation shows that the update is for "Acrobat and Reader".  The users have Acrobat 9.4.2 and Reader 10.0.1 and the update has a link to 10.0.2 readme, so it was assumed only Reader 10 was being modified.  Acrobat 9.4.2 is what is actually being updated, but the patch doesn't reference 9.x.  Confusing to everyone.
    Thanks for confirming no 10.0.2 update for Reader (whew)!
    Russell

  • - 0 fatal error(s), 3 error(s)     ----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 -----------  ERROR: Key not valid for use in specified state.    ERROR: Install MSI payload failed with error: 1603 - Fatal error durin

    I keep getting this error code when trying to download         
    - 0 fatal error(s), 3 error(s) ----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 ----------- ERROR: Key not valid for use in specified state. ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation. MSI Error message: Key not valid for use in specified state. ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

    Generally this error happens because of an encrypted folder or insufficient permissions on that folder: http://support.microsoft.com/kb/834484 (MS Explanation)
    Adobe has a page here: Error 1603: A fatal error occurred during installation

  • I can not uninstall the newest Muse, the error that i get is: ERROR: The older version of Adobe Muse CC 2014 cannot be removed.  Contact your technical support group.    ERROR: Install MSI payload failed with error: 1603 - Onherstelbare fout bij installat

    Can somebody please help me, i can not work on my websites anymore. Thanks !!

    ERROR: The older version of Adobe Muse CC 2014 cannot be removed.  Contact your technical support group. 
    ERROR: Install MSI payload failed with error: 1603 - Onherstelbare fout bij installatie.
    MSI Error message: The older version of Adobe Muse CC 2014 cannot be removed.  Contact your technical support group. 
    ERROR: Third party payload installer Muse_2014_2_CC_LS24.msi failed with exit code: 1603

  • Creating A CSS Rule For Version 13.1

    I am new to Dreamweaver CS6 or any Dreamweaver and I am trying to create a new CSS Rule for Version 13.1. I am taking a class and the material is written for ver 12 and not 13. Does Version 13 not have the Classic View as well.
    Any help is greatly appreciated.
    Thanks
    Mark

    It was worth a try.
    As Jon points out, a lot has changed in Dreamweaver since CS6 was first released in May 2012. There have been two updates for Creative Cloud subscribers, which made significant changes to the interface. Dreamweaver CC was released in June this year, and has since had one update.
    The whole idea of the Creative Cloud is to release new features as they become available, which makes documentation and training courses difficult to follow. I have just finished recording Adobe Dreamweaver CC: Learn by Video, which is due to be published next month. It's based on Dreamweaver 13.1, so it will be up to date for a few months - and then a new version will almost certainly be released, which will make at least part of it out of date.
    Rather than learning the mechanics of Dreamweaver, it's important to learn the basics of HTML and CSS. Once you understand them, it will be a lot easier to find your way around the Dreamweaver interface without being constantly confused.
    Good luck.

  • BETA UEFI Releases for MSI 990FXA-GD65 [MS-7640 PCB 3.0] [E7640AMS.Jxx versions]

    Where you move the "BETA UEFI Releases for MSI 990FXA-GD65 [MS-7640 PCB 3.0] [E7640AMS.Jxx versions]" was in the link https://forum-en.msi.com/index.php?topic=151619.0?
    That it´s ended?
    Tank you
    José Crispim
    Portugal

    >>Beta BIOSes<<

  • Compiling connman fails, asks for glib version already installed.

    I just installed enlightenment and am trying to compile connman for network management. While checking dependencies it fails asking for glib version 2.22 or higher. I have glib 2.30.2 installed from core installed.
    Any idea how to fix this?
    Output of config.log http://paste.pocoo.org/show/518680/
    Thanks in advance.

    That worked, glad it was something simple. Thanks for the help.

  • [SOLVED]system fails to boot since adding udev rules for automounting

    Hello
    I have recently been trying to use udev rules to automount, and putting together stuff from the wiki, forums and general googling around have produced the following set of rules:
    # automounts usb hdd and pendrives as usbhd-sdx; no messing around with
    # volume labels or other confusing stuff
    # matches all sdx devices except the internal hdd, sda
    KERNEL=="sd[b-z]", NAME="%k", SYMLINK+="usbhd-%k", GROUP="users", OPTIONS="last_rule"
    # imports filesystem information
    ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
    # creates mount points and sets up symlinks
    ACTION=="add", KERNEL=="sd[b-z][0-9]", SYMLINK+="usbhd-%k", GROUP="users", NAME="%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/ln -s /media/usbhd-%k /mnt/usbhd-%k"
    # global mount options
    ACTION=="add", ENV{mount_options}="relatime"
    # filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
    ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
    # automount ntfs filesystem with ntfs-3g driver
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_r$
    # automount all other file systems
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    # unmounts and removes the mount points
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rm -f /mnt/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    This seemed to be working very well unitl I tried to boot this morning and the boot process stopped at "processing UDev events" with the following message:
    iTCO_wdt: Unexpected close, not stopping watchdog!
    It pauses at this point for 10-15 seconds and then reboots.
    Having searched a bit, I found the following similar post on the forums:  http://bbs.archlinux.org/viewtopic.php?pid=459375
    Which suggests that the problem might lie with this line:
    ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
    I have renamed the file so that it no longer has the udev .rules extension and now the system boots fine.  Does anyone have any suggestions as to why the above rules might be causing this behaviour and how I might go about fixing it?
    Thanks
    Last edited by useradded (2010-07-02 22:58:14)

    Hey falconindy
    That was the final kick up the logical a$$ that I needed to get some kind of grip on udev rules.  I now have a fully functional rule that applies only to /dev/sdxy and not to everything else as well, so no more boot trauma, THANK YOU.
    I will mark this thread as solved and post my new rule for the benefit of anyone who might read this.
    New rule (no boot problems):
    # automounts usb hdd and pendrives as label or as usbhd-sdxy if no label present
    # ensures the following is _only_ run for sdxy devices excluding internal hdd, sda
    KERNEL!="sd[b-z][0-9]", GOTO="personal_usb_automount_settings_end"
    # imports filesystem information
    # provides access to following variables:
    # ID_FS_UUID; ID_FS_UUID_ENC; ID_FS_VERSION; ID_FS_TYPE; ID_FS_VERSION; ID_FS_LABEL
    # accessible via ENV{variable}; $env{variable}|%E{variable}
    IMPORT{program}="/sbin/blkid -o udev -p %N"
    # Get a label if present, otherwise name usbhd-%k
    ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
    ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
    # creates mount points and sets up symlinks
    ACTION=="add", SYMLINK+="%E{dir_name}", GROUP="users", NAME="%k"
    ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}"
    ACTION=="add", RUN+="/bin/ln -s /media/%E{dir_name} /mnt/%E{dir_name}"
    # global mount options
    ACTION=="add", ENV{mount_options}="relatime"
    # filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
    ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
    # automount ntfs filesystem with ntfs-3g driver
    ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
    # automount all other file systems
    ACTION=="add",ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
    # unmounts and removes the mount points
    ACTION=="remove", RUN+="/bin/rm -f /mnt/%E{dir_name}"
    ACTION=="remove", RUN+="/bin/umount -l /media/%E{dir_name}"
    ACTION=="remove", RUN+="/bin/rmdir /media/%E{dir_name}", OPTIONS="last_rule"
    # exit
    LABEL=="personal_usb_automount_settings_end"
    Last edited by useradded (2010-07-02 22:59:20)

  • Unlimted License Patch fails for multiple versions of  Server Express

    I'm following the directions for installing and licensing two versions of Microfocus Server Express for a PeopleTools 8.52 upgrade. When I get to the point where I apply the Unlimited License Patch (ULP), the application to the first version goes fine, showing a successful "installed" message. After installing the other version of Server Express, I try to apply the ULP again and this time it returns an "uninstalled" message. Eventhough I had COBDIR set to the 2nd installation, the ULP deinstalled the patch for the first installation. I'm doing this as the root user but I have su'ed to root. This worked fine 2 years ago. What am I missing in the environment that prohibits me from installing the ULP for multiple versions of Server Express?

    LD_LIBRARY_PATH

  • Fail to gunzip the OracleAS 904 for HPUX version

    Hi,
    I have downloaded OracleAS 904 for HPUX version, gunzip is okay for Disk1 and Disk4, I got mesg like "unexpected end of file" for Disk3.gz and Disk4.gz.
    How to get the gunzip working for these two files? Are there anything wrong with them?
    Thanks.
    Eileen

    Please check the sum before using gunzip.
    If sum values are not matching with the ones
    shown on OTN download page for that file, it
    means the download did not complete and file
    is most likely corrupted.
    If sums are fine, gunzip should not be a
    problem.

  • Registry Detection Rule

    Hi
    I'm trying to deploy VLC  (exe file) as MSI deployment type with SCCM 2012.
    The application is installed, but the detection rules (Registry) I've entered doesn't work and SCCM will try to install over and over again. (As a work around Im checking for vlc.exe in the installation folder, but would be nice to know what the issue with
    the registry rules  below are.)
    HKEY_LOCAL_MACHINE
    SOFTWARE\Wow6432Node\VideoLAN\VLC\Version
    OR
    HKEY_LOCAL_MACHINE
    SOFTWARE\VideoLAN\VLC\Version
    Value: 2.1.3
    Datatype: Version
    (The option This reg setting must exist... is checked)
    (have also tried to just use the secound one and no OR on a 32 bit pc, but still no luck.
    Tony

    Also to note, if you use the VLC installer that can be downloaded from www.videolan.org, it actually opens another process that does the installation. If the detection method fails, it's probably because the actual installer process (that you've defined
    to be run in the deployment type) has ended and the detection method that you've configured haven't shown up on the machine yet (because there's another process still doing the installation in the background). This can easily be seen in the AppEnforce.log.
    To avoid this, you could wrap the VLC installer into a script that has a little wait time after running the installation command and use the script as your deployment type's installation command.

Maybe you are looking for

  • Format TC Drive to Mac OS Extended?

    been on the phone with mac support for about an hour about this but they could not help me even though they say it is possible. to cater for pc users the default format is fat 32 (according to support) which has a number of limitations like max file

  • New 5c charging dock not working!

    Got a charging dock for my 5c and it does not work.  Called Apple they sent a new one and it does not work either?  I am using the lightning cable provide with phone.  Ear buds do not work either through the dock.  What am i missing?

  • Mark detecting not working

    Hi: I've just put in a third tape using my Sony VX2100. First two tapes detected fine. Third tape sees not breaks in the tape. Perhaps I changed a setting without realizing it. Can anyone offer any possible solutions. I imagine it's just a wrong sett

  • Unusual DNS/DHCP requirement for 2012 Essentials at home.

    I have a Windows 2012 Essentials server acting as DNS and DHCP server with a domain providing backups etc. for my home network. This is all working fine, no errors, no problems. Works well in fact, telling me when the kids haven't installed updates o

  • Latest java update vanished from App store!

    Saw I had an update, so opened App Store. It was a Java update. As I was reading the content, it vanished from the page, and the little "1" next to "Updates" also vanished. Restarting App Store and clicking Update icon did not retrieve update. Anybod