none
MSI fails to run on client even though program is set to run under admin right

    Question

  • I've pushed out many msi packages before successfully under admin context whether or not user is logged on using SCCM, but this time I cannot seem to push out this particular msi.  The batch file that has the msi runs fine if the current user who logs on is a member of administator group, however the installation fails if a non-administrative account is logged on.  This should not be an issue since I specify to install under admin context whether or not the user is logged on.  What is wrong?  Here are the scripts in a batch file named "install.bat" that I attempted to push with SCCM:

    @ECHO on
    SETLOCAL
    ECHO %THISDIR%
    SET THISDIR=%~dps0

    cscript.exe %THISDIR%Exit.vbs //nologo

    msiexec.exe /q /norestart /X{AC8AE5A6-248A-41C8-B062-69440B14BE75} /l*v C:\medhostremove.log

    RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{8344847D-874E-4225-A829-5FFBFCA326E0}\setup.exe" /s /x /f1%THISDIR%uninstallmedhost.iss

    msiexec.exe /q ALLUSERS=1 /m MSIVHNKO /i "%THISDIR%EDIS 4.2.msi" /l*v C:\medhost.log

    cscript.exe %THISDIR%DB.vbs //nologo

    regedit /s %THISDIR%resolution.reg

    xcopy %THISDIR%registerall.bat C:\medhost\system /i /y

    xcopy %THISDIR%registerallsilent.bat c:\medhost\system /i /y

    C:\medhost\system\registerAllSilent.bat

    exit 0

    Tuesday, July 21, 2009 6:48 PM

Answers

  • If you updated the version of the package then you will have VMC0005A.3.System and not VMC0005A.2.System.
    Though I don't think this is the case since you have the same error for all of the packages. 

    "The batch file that has the msi runs fine if the current user who logs on is a member of administator group, however the installation fails if a non-administrative account is logged on.  "
    This is confusing because should fail if they are non-admins.  What you mean is that you run the installation as the "Run with adminstrative rights"  The one problem with ConfigMgr is that it uses localsystem as the admin and sometime packages don't act the same as if it were a administrative account.

    Obviously you have run this as a local admin to confirm the process works.   The application you are uninstalling might not have "nice" uninstaller.  Much like LookOut and some other apps they just don't uninstall nicely and you have to create large work arounds.


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Wednesday, July 22, 2009 12:47 PM

All replies

  • Where does it fail? What do the log files say? What error code are you getting back?
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Tuesday, July 21, 2009 7:28 PM
  • Here is a portion of the log for the program removal msi: msiexec.exe /q /norestart /X{AC8AE5A6-248A-41C8-B062-69440B14BE75} /l*v C:\medhostremove.log. 

    MSI (s) (E4:04) [12:56:00:915]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (E4:04) [12:56:02:071]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (E4:04) [12:56:02:071]: User policy value 'DisableMedia' is 0
    MSI (s) (E4:04) [12:56:02:071]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Looking for sourcelist for product {AC8AE5A6-248A-41C8-B062-69440B14BE75}
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Adding {AC8AE5A6-248A-41C8-B062-69440B14BE75}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Now checking product {AC8AE5A6-248A-41C8-B062-69440B14BE75}
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (E4:04) [12:56:02:071]: SOURCEMGMT: Trying source C:\WINDOWS\system32\CCM\Cache\VMC0005A.2.System\.
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Source is invalid due to client source our of sync (product code is the same).
    MSI (s) (E4:04) [12:56:04:524]: Note: 1: 1731 2: -2147483645 3: EDIS 4.2.msi
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Processing net source list.
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Trying source C:\WINDOWS\system32\CCM\Cache\VMC000AA.1.System\.
    MSI (s) (E4:04) [12:56:04:524]: Note: 1: 2203 2: C:\WINDOWS\system32\CCM\Cache\VMC000AA.1.System\EDIS 4.2.msi 3: -2147287037
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Trying source C:\WINDOWS\system32\CCM\Cache\VM4EE8~1.SYS\.
    MSI (s) (E4:04) [12:56:04:524]: Note: 1: 2203 2: C:\WINDOWS\system32\CCM\Cache\VM4EE8~1.SYS\EDIS 4.2.msi 3: -2147287037
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Trying source C:\WINDOWS\system32\CCM\Cache\VM4EE9~1.SYS\.
    MSI (s) (E4:04) [12:56:04:524]: Note: 1: 2203 2: C:\WINDOWS\system32\CCM\Cache\VM4EE9~1.SYS\EDIS 4.2.msi 3: -2147287037
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Trying source C:\WINDOWS\system32\CCM\Cache\VMC000AB.2.System\.
    MSI (s) (E4:04) [12:56:04:524]: Note: 1: 2203 2: C:\WINDOWS\system32\CCM\Cache\VMC000AB.2.System\EDIS 4.2.msi 3: -2147287037
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (E4:04) [12:56:04:524]: SOURCEMGMT: Trying source C:\WINDOWS\system32\CCM\Cache\VMC000~4.SYS\.
    MSI (s) (E4:04) [12:56:04:540]: Note: 1: 2203 2: C:\WINDOWS\system32\CCM\Cache\VMC000~4.SYS\EDIS 4.2.msi 3: -2147287038
    MSI (s) (E4:04) [12:56:04:540]: SOURCEMGMT: Failed to resolve source
    MSI (s) (E4:04) [12:56:04:540]: MainEngineThread is returning 1612
    MSI (c) (44:80) [12:56:04:540]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (44:80) [12:56:04:540]: MainEngineThread is returning 1612
    MSI (s) (E4:04) [12:56:04:540]: SOURCEMGMT: Failed to resolve source
    MSI (s) (E4:04) [12:56:04:540]: MainEngineThread is returning 1612
    MSI (c) (44:80) [12:56:04:540]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (44:80) [12:56:04:540]: MainEngineThread is returning 1612


    The log for the msi installation: msiexec.exe /q ALLUSERS=1 /m MSIVHNKO /i "%THISDIR%EDIS 4.2.msi" /l*v C:\medhost.log says that it fails because another version of this product is already installed which we can obviously see why due to the unsuccessful uninstallation prior to running this.

     

    Tuesday, July 21, 2009 8:55 PM
  • If you updated the version of the package then you will have VMC0005A.3.System and not VMC0005A.2.System.
    Though I don't think this is the case since you have the same error for all of the packages. 

    "The batch file that has the msi runs fine if the current user who logs on is a member of administator group, however the installation fails if a non-administrative account is logged on.  "
    This is confusing because should fail if they are non-admins.  What you mean is that you run the installation as the "Run with adminstrative rights"  The one problem with ConfigMgr is that it uses localsystem as the admin and sometime packages don't act the same as if it were a administrative account.

    Obviously you have run this as a local admin to confirm the process works.   The application you are uninstalling might not have "nice" uninstaller.  Much like LookOut and some other apps they just don't uninstall nicely and you have to create large work arounds.


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Wednesday, July 22, 2009 12:47 PM