locked
Windows XP SP3 Shim and UAC RRS feed

  • Question

  • Happy New Year Everyone,
    need help with the below mentioned issue.
    I sequenced a software on a 32 bit VM and published it on 64 bit server 2012 VM.  The software is not an ideal candidate for sequencing though as it has COM+ and DCOM components. Requires a thorough testing to confirm.

    Now, On launch of one of the shortcut we get an error related to OLE components. Out of several things i tried to get rid of the error applying Windows XP SP 3 compatibillity shim to that particular EXE seems to be working without an error. However, after applying shim it prompts consent UAC which is probably normal but is not acceptable in our environment. Adding Run as Invoker to it didn't make any visible difference to the behavior.

    Possibly this shim can be avoided if I could pin point the group of files which might require mitigation but could not get to it so far.

    Appreciate any ideas or suggestions for an alternative solutions.


    Thursday, January 7, 2016 6:07 PM

All replies

  • Have you tried using alternate shims other than Run as Invoker? Have you tried setting permissions to the folder? Have you disabled run as admin in the shortcut?

    Can you check whether the executable has any external or internal manifest file? I have explained as how to check this (manifest file section) http://app2pack.blogspot.com/2015/11/uac-and-app-v-50-demystified.html


    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)

    app2pack.blogspot.com: app2pack.blogspot.com

    Friday, January 8, 2016 4:10 AM
  • Have you tried to deploy the COM+ components locally?


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Tuesday, February 16, 2016 4:37 AM