locked
Windows 7 Pro - Group Policy Issue RRS feed

  • Question

  • Hello,

    Using IEAK 11 I created an MSI which should config IE 11 on win 7 computers.  I created a Software Installation under USER CONFIG\POLICIES\SOFTWARE SETTINGS (points to \\server\scripts\ie11-setup.msi".

    I've confirmed the user can access the MSI as I've tried to install it manually by browsing to the UNC path and executing the MSI.  Needed admin privileges to run it this way. However when logging in as the user on other systems, based on the log file, it appears it tries to install the MSI, but it doesn't.  HEre is the log:

    === Verbose logging started: 9/11/2015  16:19:13  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\system32\svchost.exe ===
    MSI (c) (48:EC) [16:19:13:743]: User policy value 'DisableRollback' is 0
    MSI (c) (48:EC) [16:19:13:743]: Machine policy value 'DisableRollback' is 0
    MSI (c) (48:EC) [16:19:13:749]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (c) (48:EC) [16:19:13:750]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1194033724,LangId=1033,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
    MSI (c) (48:EC) [16:19:13:750]: Executing op: ProductInfo(ProductKey={BE44006E-D2EA-42E2-98CA-D6F1EADB0F8A},ProductName=Internet Explorer 11,PackageName=IE11-Setup-Branding.msi,Language=1033,Version=184549376,Assignment=1,ObsoleteArg=0,,,PackageCode={BE44006E-D2EA-42E2-98CA-D6F1EADB0F8A},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
    MSI (c) (48:EC) [16:19:13:752]: SHELL32::SHGetFolderPath returned: C:\Users\melanie\AppData\Roaming
    MSI (c) (48:EC) [16:19:13:752]: Executing op: DialogInfo(Type=0,Argument=1033)
    MSI (c) (48:EC) [16:19:13:752]: Executing op: DialogInfo(Type=1,Argument=Internet Explorer 11)
    MSI (c) (48:EC) [16:19:13:752]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
    MSI (c) (48:EC) [16:19:13:752]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing Product Features,Template=Feature: [1])
    MSI (c) (48:EC) [16:19:13:752]: Executing op: FeaturePublish(Feature=Complete,,Absent=0,)
    MSI (c) (48:EC) [16:19:13:754]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
    MSI (c) (48:EC) [16:19:13:754]: Executing op: CleanupConfigData()
    MSI (c) (48:EC) [16:19:13:754]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-1638338925-285223764-1845911597-2809\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8\Patches 3: 2
    MSI (c) (48:EC) [16:19:13:754]: Executing op: ProductPublish(PackageKey={BE44006E-D2EA-42E2-98CA-D6F1EADB0F8A})
    MSI (c) (48:EC) [16:19:13:754]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:754]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:755]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8 3: 2
    MSI (c) (48:EC) [16:19:13:761]: Executing op: UpgradeCodePublish(UpgradeCode={23198898-9C95-43BC-9647-30AEC21DD079})
    MSI (c) (48:EC) [16:19:13:762]: Executing op: SourceListPublish(,,,,NumberOfDisks=1)
    MSI (c) (48:EC) [16:19:13:762]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8\SourceList 3: 2
    MSI (c) (48:EC) [16:19:13:762]: Note: 1: 1402 2: UNKNOWN\Installer\Products\E60044EBAE2D2E2489AC6D1FAEBDF0A8\SourceList 3: 2
    MSI (c) (48:EC) [16:19:13:765]: Executing op: ProductPublishClient(,,)
    MSI (c) (48:EC) [16:19:13:767]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
    MSI (c) (48:EC) [16:19:13:772]: Note: 1: 2318 2: 
    MSI (c) (48:EC) [16:19:13:773]: DoAdvertiseScript is returning: 0
    === Verbose logging stopped: 9/11/2015  16:19:13 ===

    The UNKNOWN errors don't look like a good thing, but I don't know enough about what I'm looking at to determine if that's the issue and what they mean.  Does the admin privilege play a role in this as well? Do users need to be admins to install MSI packages?  If so, how do you get around that? I'm sure admins aren't giving their user local admin rights.

    Any help would be great.

    Thanks.

    Friday, September 11, 2015 8:34 PM

Answers

  • Hi NJAX,

    The MSI software packet was applied depend on the GPO configuration, the local system account could not have permission to run the installed program, we could refer to the following link:

    https://technet.microsoft.com/en-us/library/cc738858(v=ws.10).aspx 

    Best Regard,

    Jim

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    • Proposed as answer by jim-xu Sunday, September 27, 2015 12:09 AM
    • Marked as answer by Michael_LS Thursday, October 1, 2015 1:36 AM
    Wednesday, September 23, 2015 1:48 AM

All replies

  • Hi NJAX,

    Thank you for your question.

    The user could not use administrator privilege, there is a similar thread which we could be refer to: 

    https://social.technet.microsoft.com/Forums/pt-BR/9c2c2b3c-d007-4ad8-96c4-42c9afa9dc18/trouble-with-gpo-msi-deployment-on-windows-2008-r2-for-windows-7-64-machines?forum=winserverGP 

    If there are any questions regarding this issue, please be free to let me know.

    Best Regard,

    Jim

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Monday, September 14, 2015 6:59 AM
  • Thank you, I reviewed your suggested post, but I didn't see how it addresses my issue.

    I have placed a logon script (VBS) to run at logon in the COMPUTER SETTINGS of a policy. My understanding is, this script will run with the local SYSTEM account.  Why wouldn't the system account have enough privileges to run the program?

    How does Microsoft recommend admins deploy applications which require admin rights to users without making end users administrators?

    Thank you

    Tuesday, September 15, 2015 8:10 PM
  • Hi NJAX,

    The MSI software packet was applied depend on the GPO configuration, the local system account could not have permission to run the installed program, we could refer to the following link:

    https://technet.microsoft.com/en-us/library/cc738858(v=ws.10).aspx 

    Best Regard,

    Jim

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    • Proposed as answer by jim-xu Sunday, September 27, 2015 12:09 AM
    • Marked as answer by Michael_LS Thursday, October 1, 2015 1:36 AM
    Wednesday, September 23, 2015 1:48 AM