Trouble with GPO msi deployment on Windows 2008 R2 for Windows 7 - 64 machines.

Stellen Sie eine Frage

Freitag, 9. November 2012 21:43

0
Greetings.

I've been having some trouble setting up deployment of MSI package on our Windows 2008 R2 Machine.

Currently it's enabled only for 2 test machines (Both Windows 7 - 64 bit.)

It is basic GPO with "Computer Configuration / Software Settings / Software Installation" and one MSI package under it.

I have tried it with multiple different MSI files as test and even tried changing location where package is stored (Currently it's share on one of the Domain Controllers.)

I keep getting same errors on target machine event viewer (From what I understand this is pretty common set of errors )

Events: Error 101,103,108 Followed by Warning 1085.

(I am omitting names of policies and applications unless it is critical)

First 101:

The assignment of application ... from policy ... failed. The error was : %%2

Followed by 103:

The removal of the assignment of application ... from policy ... failed. The error was : %%2

Followed by 108:

Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was : %%2

And last 1085:

Windows failed to apply the Software Installation settings. Software Installation settings might have its own log file. Please click on the "More information" link.

I saw some suggestion on enabling "Startup Policy Processing Wait Time" and setting it for 30 seconds.

I tried that and even tried going up to 120 with no effect on installation.

I tried testing MSI with /quiet option on the machine to see if there is something wrong with it and installation went smoothly.

gpresult shows that policy is active for the machine in question.

Not really sure what would be the next step on troubleshooting this particular problem so hopefully someone here can help me.

Thank you very much for your help.

After following some of the advise and finding out that some of the GPO were corrupted (.ass files missing) and remaking them I got following in logs:

Software installation extension has been called for background policy refresh

11-12 18:10:17:568

Software installation extension has been called for background policy refresh

The following policies are to be applied, flags are 411.

    ZCL (unique identifier {05B89021-FCCD-4A71-9657-C68FB9563C5C})

        System volume path = \\arcs.cpmc.columbia.edu\SysVol\arcs.cpmc.columbia.edu\Policies\{05B89021-FCCD-4A71-9657-C68FB9563C5C}\Machine

        Active Directory path = LDAP://CN=Machine,cn={05B89021-FCCD-4A71-9657-C68FB9563C5C},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu

Set the Active Directory path to LDAP://CN=Class Store,CN=Machine,cn={05B89021-FCCD-4A71-9657-C68FB9563C5C},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu;.

Enumerating applications in the Active Directory for computer SYSOPS13 with flags 5.

CSTORE: Retrieving class store path for the system account.

CSTORE: Retrieved 1 class stores for the user or machine.

CSTORE: Attempting to bind to class store 0 with path LDAP://CN=Class Store,CN=Machine,cn={05B89021-FCCD-4A71-9657-C68FB9563C5C},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu.

CSTORE: Bind attempt returned error code 0.

CSTORE: Enumerating packages with search filter (&(objectclass=packageRegistration)(|(|(msiScriptName=*A*)(&(canUpgradeScript=*)(msiScriptName=*P*)))(!(msiScriptName=*)))) and flags ce00000.

CSTORE: Examining retrieved package APP.

The following applications were found in policy ZCL.

    Assigned application APP (flags a0024c70).

Found 1 applications in policy ZCL.

Enumerating the managed applications which are currently applied to this user.

No managed applications are currently applied to this user.

Found 0 applications locally that are not included in the set of applications from the Active Directory.

Application APP from policy ZCL is set for installation because it is assigned to this computer policy.

Software installation extension cannot perform removal or install operations during asynchronous policy refresh and will force a synchronous foreground refresh.

The assignment of application APP from policy ZCL failed. The error was : %1274

Removing application APP from the software installation database.

Calling Windows Installer to remove application advertisement for application APP from script C:\Windows\system32\appmgmt\MACHINE\{5eb6c4c2-0417-41d4-bfd8-a7f52d96030b}.aas.

Windows Installer cannot remove application advertisement for application APP from script C:\Windows\system32\appmgmt\MACHINE\{5eb6c4c2-0417-41d4-bfd8-a7f52d96030b}.aas, error 2.

The removal of the assignment of application APP from policy ZCL failed. The error was : %2

Policy Logging for Software Management is attempting to log application APP from policy ZCL.

Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %1274

Software installation extension has detected changes that require a synchronous foreground policy refresh.

Software installation extension returning with final error code 1274.

11-12 18:13:07:985

Software installation extension has been called for foreground synchronous policy refresh.

The following policies are to be applied, flags are 401.

    ZCL (unique identifier {05B89021-FCCD-4A71-9657-C68FB9563C5C})

        System volume path = \\arcs.cpmc.columbia.edu\SysVol\arcs.cpmc.columbia.edu\Policies\{05B89021-FCCD-4A71-9657-C68FB9563C5C}\Machine

        Active Directory path = LDAP://CN=Machine,cn={05B89021-FCCD-4A71-9657-C68FB9563C5C},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu

Set the Active Directory path to LDAP://CN=Class Store,CN=Machine,cn={05B89021-FCCD-4A71-9657-C68FB9563C5C},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu;.

Enumerating applications in the Active Directory for computer SYSOPS13 with flags 5.

CSTORE: Retrieving class store path for the system account.

CSTORE: Retrieved 1 class stores for the user or machine.

CSTORE: Attempting to bind to class store 0 with path LDAP://CN=Class Store,CN=Machine,cn={05B89021-FCCD-4A71-9657-C68FB9563C5C},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu.

CSTORE: Bind attempt returned error code 0.

CSTORE: Enumerating packages with search filter (&(objectclass=packageRegistration)(|(|(msiScriptName=*A*)(&(canUpgradeScript=*)(msiScriptName=*P*)))(!(msiScriptName=*)))) and flags ce00000.

CSTORE: Examining retrieved package APP.

The following applications were found in policy ZCL.

    Assigned application APP (flags a0024c70).

Found 1 applications in policy ZCL.

Enumerating the managed applications which are currently applied to this user.

No managed applications are currently applied to this user.

Found 0 applications locally that are not included in the set of applications from the Active Directory.

Application APP from policy ZCL is set for installation because it is assigned to this computer policy.

Assigning application APP from policy ZCL.

Calling the Windows Installer to advertise application APP from script C:\Windows\system32\appmgmt\MACHINE\{5eb6c4c2-0417-41d4-bfd8-a7f52d96030b}.aas with flags 69.

The assignment of application APP from policy ZCL succeeded.

Calling the Windows Installer to install application APP from policy ZCL.

The install of application APP from policy ZCL failed. The error was : %1605

Removing application APP from the software installation database.

Calling Windows Installer to remove application advertisement for application APP from script C:\Windows\system32\appmgmt\MACHINE\{5eb6c4c2-0417-41d4-bfd8-a7f52d96030b}.aas.

The removal of the assignment of application APP from policy ZCL succeeded.

Policy Logging for Software Management is attempting to log application APP from policy ZCL.

Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was : %1605

Software installation extension returning with final error code 1605.
- Bearbeitet fs2307 Montag, 12. November 2012 23:33
- Antworten
- Zitieren

Alle Antworten

Montag, 12. November 2012 07:22

Moderator

0

Hi,

Suggest you collect Gpsvcdebug log and AppMgmtDebug log for troubleshooting, you may find some clues:

http://support.microsoft.com/kb/246509

http://blogs.technet.com/b/mempson/archive/2010/01/10/userenvlog-for-windows-vista-2008-win7.aspx

Regards,
Cicely
- Antworten
- Zitieren
Montag, 12. November 2012 13:05

0

The assignment of application ... from policy ... failed. The error was : %%2

2 typically means "file not found". I suggest enabling AppMgmt Debug logging and checking the results:

In regedit, create the following key if not already present:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Then create a value named "AppMgmtDebugLevel" (REG_DWORD) with a value of 0x9b
Reboot, and open %windir%\debug\usermode\appmgmt.log
<meta name="ProgId" content="OneNote.File"> <meta name="Generator" content="Microsoft OneNote 14">
regards, Martin

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren
Montag, 12. November 2012 17:30

0

Thank you.

That was very helpful.

I had registry keys set before but I didn't create folders by hand (that was important note.) once I created folder logs started popping up and now I have some extra information.

This is what seems to be the problem

The script file for application ... from policy ... cannot be copied. Copy from \\arcs.cpmc.columbia.edu\SysVol\arcs.cpmc.columbia.edu\Policies\{93D5C04E-6981-4AA4-B737-77A350EB54D3}\Machine\Applications\{21A35CD2-8069-4A37-B638-0844D0D1D402}.aas to C:\Windows\system32\appmgmt\MACHINE\{61c3eb5d-77a3-4207-bb59-54ca1244d8e9}.aas failed, error 2.

I am not sure how those actually get created and why would this come up.

Any idea?
- Antworten
- Zitieren
Dienstag, 13. November 2012 10:27

0

> The script file for application ... from policy ... cannot be copied.

> Copy from

> \\arcs.cpmc.columbia.edu\SysVol\arcs.cpmc.columbia.edu\Policies\{93D5C04E-6981-4AA4-B737-77A350EB54D3}\Machine\Applications\{21A35CD2-8069-4A37-B638-0844D0D1D402}.aas

> to

> C:\Windows\system32\appmgmt\MACHINE\{61c3eb5d-77a3-4207-bb59-54ca1244d8e9}.aas

> failed, error 2.

Again, 2 means "file not found" - this refers to the source file. Check

your sysvol for replication errors (FRS or DFS logs), then refer to

http://support.microsoft.com/kb/315457

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren

Dienstag, 13. November 2012 15:35

I edited main post. I did figure out why it couldn't find this .aas file. Corrupted group policy.

I recreated it and that error went away, but it didn't solve the problem on the long run.

Just error message changed. It's 1605 error and it's seems generic enough.

Application APP from policy ZCL is set for installation because it is assigned to this computer policy.

Assigning application APP from policy ZCL.

Calling the Windows Installer to advertise application APP from script C:\Windows\system32\appmgmt\MACHINE\{5eb6c4c2-0417-41d4-bfd8-a7f52d96030b}.aas with flags 69.

The assignment of application APP from policy ZCL succeeded.

 

Calling the Windows Installer to install application APP from policy ZCL.

The install of application APP from policy ZCL failed.  The error was : %1605

 

Removing application APP from the software installation database.

Calling Windows Installer to remove application advertisement for application APP from script C:\Windows\system32\appmgmt\MACHINE\{5eb6c4c2-0417-41d4-bfd8-a7f52d96030b}.aas.

The removal of the assignment of application APP from policy ZCL succeeded.

 

Policy Logging for Software Management is attempting to log application APP from policy ZCL.

Failed to apply changes to software installation settings.  Software changes could not be applied.  A previous log entry with details should exist.  The error was : %1605

 

Software installation extension returning with final error code 1605.

I have MSI debuggin enabled.

I get this kind of log in windows temp folder:

=== Verbose logging started: 11/12/2012  19:10:21  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\system32\svchost.exe ===
MSI (c) (F8:14) [19:10:21:910]: User policy value 'DisableRollback' is 0
MSI (c) (F8:14) [19:10:21:910]: Machine policy value 'DisableRollback' is 0
MSI (c) (F8:14) [19:10:21:941]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (F8:14) [19:10:21:957]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (c) (F8:14) [19:10:21:957]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1097634090,LangId=1025,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (F8:14) [19:10:21:957]: Executing op: ProductInfo(ProductKey={15578C01-B0F0-44B9-8A2F-110A5AE46471},ProductName=APP for برنامج Microsoft Outlook,PackageName=ZimbraConnectorOLK_8.0.0.673_x86.msi,Language=1025,Version=134217728,Assignment=1,ObsoleteArg=0,ProductIcon=zimbra.ico,,PackageCode={46CB15E5-D036-4F9C-8D32-B2C532CC796D},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (c) (F8:14) [19:10:21:973]: Executing op: DialogInfo(Type=0,Argument=1025)
MSI (c) (F8:14) [19:10:21:973]: Executing op: DialogInfo(Type=1,)
MSI (c) (F8:14) [19:10:21:973]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=‏‏إجراء الإرجاع:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=‏‏إزالة ملفات النسخ الاحتياطي,CleanupTemplate=الملف: [1])
MSI (c) (F8:14) [19:10:21:973]: Executing op: ActionStart(Name=PublishFeatures,Description=‏‏نشر ميزات المنتج,Template=الميزة: [1])
MSI (c) (F8:14) [19:10:21:973]: Executing op: FeaturePublish(Feature=ZimbraMAPIProvider,,Absent=0,)
MSI (c) (F8:14) [19:10:21:973]: Executing op: ActionStart(Name=PublishProduct,Description=‏‏نشر معلومات المنتج,)
MSI (c) (F8:14) [19:10:21:973]: Executing op: IconCreate(Icon=zimbra.ico,Data=BinaryData)
MSI (c) (F8:14) [19:10:21:973]: Executing op: IconCreate(Icon=generic.ico,Data=BinaryData)
MSI (c) (F8:14) [19:10:21:973]: Executing op: CleanupConfigData()
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\10C875510F0B9B44A8F211A0A54E4617\Patches 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Executing op: ProductPublish(PackageKey={46CB15E5-D036-4F9C-8D32-B2C532CC796D})
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (F8:14) [19:10:21:973]: Executing op: UpgradeCodePublish(UpgradeCode={7053E159-FED6-4C51-9F8B-BCDBDA4D20AB})
MSI (c) (F8:14) [19:10:21:988]: Executing op: SourceListPublish(,,,,NumberOfDisks=1)
MSI (c) (F8:14) [19:10:21:988]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617\SourceList 3: 2 
MSI (c) (F8:14) [19:10:21:988]: Executing op: ProductPublishClient(,,)
MSI (c) (F8:14) [19:10:21:988]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (c) (F8:14) [19:10:22:004]: Note: 1: 2318 2:  
MSI (c) (F8:14) [19:10:22:004]: DoAdvertiseScript is returning: 0
=== Verbose logging stopped: 11/12/2012  19:10:22 ===

IF I instead manually execute MSI (msiexec /i app.msi /quiet) then i get log that look quite differently (only paste beginning cause it's way too long)

=== Verbose logging started: 11/12/2012  19:19:56  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\System32\msiexec.exe ===
MSI (c) (3C:08) [19:19:56:061]: Font created.  Charset: Req=0, Ret=0, Font: Req=, Ret=Arial

MSI (c) (3C:08) [19:19:56:061]: Font created.  Charset: Req=0, Ret=0, Font: Req=, Ret=Arial

MSI (c) (3C:7C) [19:19:56:076]: Resetting cached policy values
MSI (c) (3C:7C) [19:19:56:076]: Machine policy value 'Debug' is 0
MSI (c) (3C:7C) [19:19:56:076]: ******* RunEngine:
           ******* Product: \\dc3.arcs.cpmc.columbia.edu\programs\APP.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (c) (3C:7C) [19:19:56:076]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (3C:7C) [19:19:56:076]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (3C:7C) [19:19:56:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (3C:7C) [19:19:56:420]: SOFTWARE RESTRICTION POLICY: Verifying package --> '\\dc3.arcs.cpmc.columbia.edu\programs\APP.msi' against software restriction policy
MSI (c) (3C:7C) [19:19:56:420]: Note: 1: 2262 2: DigitalSignature 3: -2147287038 
MSI (c) (3C:7C) [19:19:56:420]: SOFTWARE RESTRICTION POLICY: \\dc3.arcs.cpmc.columbia.edu\programs\APP.msi is not digitally signed
MSI (c) (3C:7C) [19:19:56:420]: SOFTWARE RESTRICTION POLICY: \\dc3.arcs.cpmc.columbia.edu\programs\APP.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (3C:7C) [19:19:56:435]: Cloaking enabled.
MSI (c) (3C:7C) [19:19:56:435]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (3C:7C) [19:19:56:435]: End dialog not enabled
MSI (c) (3C:7C) [19:19:56:435]: Original package ==> \\dc3.arcs.cpmc.columbia.edu\programs\APP.msi
MSI (c) (3C:7C) [19:19:56:435]: Package we're running from ==> C:\Users\fs2307\AppData\Local\Temp\98298.msi
MSI (c) (3C:7C) [19:19:56:435]: APPCOMPAT: Compatibility mode property overrides found.
MSI (c) (3C:7C) [19:19:56:435]: APPCOMPAT: looking for appcompat database entry with ProductCode '{CDCA54BF-C448-4CAB-A8F7-91F7323A6957}'.
MSI (c) (3C:7C) [19:19:56:435]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (3C:7C) [19:19:56:435]: MSCOREE not loaded loading copy from system32
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'TransformsSecure' is 0
MSI (c) (3C:7C) [19:19:56:435]: User policy value 'TransformsAtSource' is 0
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'DisablePatch' is 0
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'AllowLockdownPatch' is 0
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'DisableMsi' is 0
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (3C:7C) [19:19:56:435]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (3C:7C) [19:19:56:435]: Running product '{CDCA54BF-C448-4CAB-A8F7-91F7323A6957}' with user privileges: It's not assigned.
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'DisableLUAPatching' is 0
MSI (c) (3C:7C) [19:19:56:435]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (c) (3C:7C) [19:19:56:435]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active
MSI (c) (3C:7C) [19:19:56:435]: APPCOMPAT: looking for appcompat database entry with ProductCode '{CDCA54BF-C448-4CAB-A8F7-91F7323A6957}'.
MSI (c) (3C:7C) [19:19:56:435]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (3C:7C) [19:19:56:435]: Transforms are not secure.
MSI (c) (3C:7C) [19:19:56:435]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\fs2307\AppData\Local\Temp\MSI98297.LOG'.
MSI (c) (3C:7C) [19:19:56:435]: Command Line: CURRENTDIRECTORY=\\dc3.arcs.cpmc.columbia.edu\programs CLIENTUILEVEL=0 CLIENTPROCESSID=316 
MSI (c) (3C:7C) [19:19:56:435]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{46CB15E5-D036-4F9C-8D32-B2C532CC796D}'.
MSI (c) (3C:7C) [19:19:56:435]: Product Code passed to Engine.Initialize:           ''
MSI (c) (3C:7C) [19:19:56:435]: Product Code from property table before transforms: '{CDCA54BF-C448-4CAB-A8F7-91F7323A6957}'
MSI (c) (3C:7C) [19:19:56:435]: Product Code from property table after transforms:  '{CDCA54BF-C448-4CAB-A8F7-91F7323A6957}'
MSI (c) (3C:7C) [19:19:56:435]: Product not registered: beginning first-time install
MSI (c) (3C:7C) [19:19:56:435]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (c) (3C:7C) [19:19:56:435]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (3C:7C) [19:19:56:435]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (3C:7C) [19:19:56:435]: Adding new sources is allowed.
MSI (c) (3C:7C) [19:19:56:435]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (c) (3C:7C) [19:19:56:435]: Package name extracted from package path: 'APP.msi'
MSI (c) (3C:7C) [19:19:56:435]: Package to be registered: 'APP.msi'
MSI (c) (3C:7C) [19:19:56:435]: Note: 1: 2205 2:  3: Error 
MSI (c) (3C:7C) [19:19:56:435]: Note: 1: 2262 2: AdminProperties 3: -2147287038

Dienstag, 13. November 2012 16:06

0

Calling the Windows Installer to install application APP from policy ZCL. The install of application APP from policy ZCL failed. The error was : %1605

ERROR_UNKNOWN_PRODUCT 1605 This action is only valid for products that are currently installed.

Seems some things are partially screwed up already... Is this a full msi package? Are there dependencies to other packages? Does the msi itself try to deinstall a different application and thus fails? Possibly, does the msi behave differently when installing manually or through AD (there's a public installer property ADDEPLOY=1 in the latter case)?

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren
Dienstag, 13. November 2012 16:33

0

I don't know how to answer question is this full MSI package or not.

I know that I can install it by itself manually and it doesn't look for any dependencies (yes you can install it without outlook for example despite the fact that in the log it mentions for outlook - so looks like it is full msi as far as I can tell.)

It doesn't try to deinstall anything (according to logs that comes with it when I try to run it by itself.)

It don't know if it is behaving differently when I try to install it from AD/

I tried running msiexec /i app.msi ADDEPLOY=1 /quiet and it installs.
Can you clarify "ADDEPLOY=1" meaning and how I can check it?
- Antworten
- Zitieren
Dienstag, 13. November 2012 21:11

0

> I know that I can install it by itself manually and it doesn't look

> for any dependencies (yes you can install it without outlook for

> example despite the fact that in the log it mentions for outlook - so

> looks like it is full msi as far as I can tell.)

Did you configure dependencies in the GPO? Something like "Packages this

package replaces"?

> I tried running msiexec /i app.msi ADDEPLOY=1 /quiet and it installs.

> Can you clarify "ADDEPLOY=1" meaning and how I can check it?

This property is automatically set when deploing MSIs through GPO. I

remember .NET installers that could not be deployed silently without

adding this property to the command line...

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren

Mittwoch, 14. November 2012 14:30

Did you configure dependencies in the GPO? Something like "Packages this

package replaces"?

> I tried running msiexec /i app.msi ADDEPLOY=1 /quiet and it installs.

> Can you clarify "ADDEPLOY=1" meaning and how I can check it?

This property is automatically set when deploing MSIs through GPO. I

remember .NET installers that could not be deployed silently without

adding this property to the command line...

So I tried following

I created new GPO and put previous version of this app in it. (We never deployed it before.).

I rebooted my test machine and package installed just fine. Then I added to that GPO new version and configure it to be upgrade.

The result - first error 1274 and next time error is 1605 again. Here is sample of the errors

The following 1 managed applications are currently applied to this user.
APP for Microsoft Outlook from policy ZCO with state 509 and assign count 1.
Found 0 applications locally that are not included in the set of applications from the Active Directory.
Application APP for Microsoft Outlook (2) from policy ZCO is set for installation because it is assigned to this computer policy.
Application APP for Microsoft Outlook (2) from policy ZCO is a potential upgrade of application APP for Microsoft Outlook from policy ZCO, states are 1 0 0 1 1.
Application APP for Microsoft Outlook from policy ZCO was superseded by application APP for Microsoft Outlook (2) from policy ZCO with reason 4.
Application APP for Microsoft Outlook (2) from policy ZCO is an upgrade of application APP for Microsoft Outlook from policy ZCO and
will cause the assignment of application APP for Microsoft Outlook to be removed.

Removing application APP for Microsoft Outlook from the software installation database.
The removal of the assignment of application APP for Microsoft Outlook from policy ZCO succeeded.

Software installation extension cannot perform removal or install operations during asynchronous policy refresh and will force a synchronous foreground refresh.
The assignment of application APP for Microsoft Outlook (2) from policy ZCO failed. The error was : %1274

Removing application APP for Microsoft Outlook (2) from the software installation database.
Calling Windows Installer to remove application advertisement for application APP for Microsoft Outlook (2) from script C:\Windows\system32\appmgmt\MACHINE\{556760c1-0096-46dc-9954-cd7ce33dde9b}.aas.
The removal of the assignment of application APP for Microsoft Outlook (2) from policy ZCO succeeded.

Application APP for Microsoft Outlook (2) from policy ZCO was configured to upgrade application APP for Microsoft Outlook from policy ZCO. The assignment or
install of the upgrade application APP for Microsoft Outlook (2) from policy ZCO failed with error : %1274 The upgrade will be aborted.

Assigning application APP for Microsoft Outlook from policy ZCO.
Calling the Windows Installer to advertise application APP for Microsoft Outlook from script C:\Windows\system32\appmgmt\MACHINE\{52d98a43-9381-47ed-88c5-3f761f35194b}.aas with flags 12d.
The assignment of application APP for Microsoft Outlook from policy ZCO succeeded.

Software installation extension cannot perform removal or install operations during asynchronous policy refresh and will force a synchronous foreground refresh.
The install of application APP for Microsoft Outlook from policy ZCO failed. The error was : %1274

Policy Logging for Software Management is attempting to log application APP for Microsoft Outlook (2) from policy ZCO.
Policy Logging for Software Management is attempting to log application APP for Microsoft Outlook from policy ZCO.
Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %1274

Software installation extension has detected changes that require a synchronous foreground policy refresh.
Software installation extension returning with final error code 1274.

this time.

...
The removal of the assignment of application APP for Microsoft Outlook from policy ZCO succeeded.

Assigning application APP for Microsoft Outlook (2) from policy ZCO.
Calling the Windows Installer to advertise application APP for Microsoft Outlook (2) from script C:\Windows\system32\appmgmt\MACHINE\{556760c1-0096-46dc-9954-cd7ce33dde9b}.aas with flags 69.
The assignment of application APP for Microsoft Outlook (2) from policy ZCO succeeded.

Calling the Windows Installer to install application APP for Microsoft Outlook (2) from policy ZCO.
The install of application APP for Microsoft Outlook (2) from policy ZCO failed. The error was : %1605

Calling the Windows Installer to install application APP for Microsoft Outlook from policy ZCO.
The install of application APP for Microsoft Outlook from policy ZCO succeeded.

Policy Logging for Software Management is attempting to log application APP for Microsoft Outlook (2) from policy ZCO.
Policy Logging for Software Management is attempting to log application APP for Microsoft Outlook from policy ZCO.
Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was : %1605

Software installation extension returning with final error code 1605.

this is how previous version looked by itself

oftware installation extension has been called for foreground synchronous policy refresh.
The following policies are to be applied, flags are 1.
    ZCO (unique identifier {1B5F3FBA-0731-44FA-AD7E-174BB1DED4BF})
        System volume path = \\arcs.cpmc.columbia.edu\SysVol\arcs.cpmc.columbia.edu\Policies\{1B5F3FBA-0731-44FA-AD7E-174BB1DED4BF}\Machine
        Active Directory path = LDAP://CN=Machine,cn={1B5F3FBA-0731-44FA-AD7E-174BB1DED4BF},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu
Set the Active Directory path to LDAP://CN=Class Store,CN=Machine,cn={1B5F3FBA-0731-44FA-AD7E-174BB1DED4BF},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu;.
Enumerating applications in the Active Directory for computer SYSOPS13 with flags 5.
CSTORE: Retrieving class store path for the system account.
CSTORE: Retrieved 1 class stores for the user or machine.
CSTORE: Attempting to bind to class store 0 with path LDAP://CN=Class Store,CN=Machine,cn={1B5F3FBA-0731-44FA-AD7E-174BB1DED4BF},cn=policies,cn=system,DC=arcs,DC=cpmc,DC=columbia,DC=edu.
CSTORE: Bind attempt returned error code 0.
CSTORE: Enumerating packages with search filter (&(objectclass=packageRegistration)(|(|(msiScriptName=*A*)(&(canUpgradeScript=*)(msiScriptName=*P*)))(!(msiScriptName=*)))) and flags ce00000.
CSTORE: Examining retrieved package APP for Microsoft Outlook.
The following applications were found in policy ZCO.
    Assigned application APP for Microsoft Outlook (flags a0024c70).
Found 1 applications in policy ZCO.
Enumerating the managed applications which are currently applied to this user.
No managed applications are currently applied to this user.
Found 0 applications locally that are not included in the set of applications from the Active Directory.
Application APP for Microsoft Outlook from policy ZCO is set for installation because it is assigned to this computer policy.
Assigning application APP for Microsoft Outlook from policy ZCO.
Calling the Windows Installer to advertise application APP for Microsoft Outlook from script C:\Windows\system32\appmgmt\MACHINE\{52d98a43-9381-47ed-88c5-3f761f35194b}.aas with flags 69.
The assignment of application APP for Microsoft Outlook from policy ZCO succeeded.

Calling the Windows Installer to install application APP for Microsoft Outlook from policy ZCO.
The install of application APP for Microsoft Outlook from policy ZCO succeeded.

Policy Logging for Software Management is attempting to log application APP for Microsoft Outlook from policy ZCO.
Changes to software installation settings were applied successfully.

Software installation extension returning with final error code 0.
Software installation extension has been called for background policy refresh

Mittwoch, 14. November 2012 21:38

0

>

> Software installation extension cannot perform removal or install operations during asynchronous policy refresh and will force a synchronous foreground refresh.

> The assignment of application APP for Microsoft Outlook (2) from policy ZCO failed. The error was : %1274

This seems to be a manual "gpupdate", not a reboot/logon processing.

1274 is quite usual in this case.

> Calling the Windows Installer to install application APP for Microsoft Outlook (2) from policy ZCO.

> The install of application APP for Microsoft Outlook (2) from policy ZCO failed. The error was : %1605

I'm starting to believe this MSI package is not suitable for GPO

deployment... There are lots of dependencies one can author into an msi

package.

Can you check %windir%\temp for files with a name pattern of msi*.log?

(current date and time, of course)

regards, Martin

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren

Donnerstag, 15. November 2012 20:29

Can you check %windir%\temp for files with a name pattern of msi*.log?

(current date and time, of course)

regards, Martin

Actually i get 3 MSI.log file everytime (I think I posted one of them before but here goes.)

=== Verbose logging started: 11/15/2012  14:54:22  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\system32\svchost.exe ===
MSI (c) (EC:2C) [14:54:22:767]: User policy value 'DisableRollback' is 0
MSI (c) (EC:2C) [14:54:22:767]: Machine policy value 'DisableRollback' is 0
MSI (c) (EC:2C) [14:54:22:798]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (c) (EC:2C) [14:54:22:798]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1097819651,LangId=1025,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (EC:2C) [14:54:22:798]: Executing op: ProductInfo(ProductKey={15578C01-B0F0-44B9-8A2F-110A5AE46471},ProductName=APP for برنامج Microsoft Outlook,PackageName=ZimbraConnectorOLK_8.0.0.673_x86.msi,Language=1025,Version=134217728,Assignment=1,ObsoleteArg=0,ProductIcon=zimbra.ico,,PackageCode={46CB15E5-D036-4F9C-8D32-B2C532CC796D},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (c) (EC:2C) [14:54:22:798]: Executing op: DialogInfo(Type=0,Argument=1025)
MSI (c) (EC:2C) [14:54:22:798]: Executing op: DialogInfo(Type=1,)
MSI (c) (EC:2C) [14:54:22:798]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=‏‏إجراء الإرجاع:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=‏‏إزالة ملفات النسخ الاحتياطي,CleanupTemplate=الملف: [1])
MSI (c) (EC:2C) [14:54:22:798]: Executing op: ActionStart(Name=PublishFeatures,Description=‏‏نشر ميزات المنتج,Template=الميزة: [1])
MSI (c) (EC:2C) [14:54:22:798]: Executing op: FeaturePublish(Feature=ZimbraMAPIProvider,,Absent=0,)
MSI (c) (EC:2C) [14:54:22:798]: Executing op: ActionStart(Name=PublishProduct,Description=‏‏نشر معلومات المنتج,)
MSI (c) (EC:2C) [14:54:22:798]: Executing op: IconCreate(Icon=zimbra.ico,Data=BinaryData)
MSI (c) (EC:2C) [14:54:22:798]: Verifying accessibility of file: zimbra.ico
MSI (c) (EC:2C) [14:54:22:798]: Note: 1: 2318 2:  
MSI (c) (EC:2C) [14:54:22:814]: Executing op: IconCreate(Icon=generic.ico,Data=BinaryData)
MSI (c) (EC:2C) [14:54:22:814]: Verifying accessibility of file: generic.ico
MSI (c) (EC:2C) [14:54:22:829]: Note: 1: 2318 2:  
MSI (c) (EC:2C) [14:54:22:829]: Executing op: CleanupConfigData()
MSI (c) (EC:2C) [14:54:22:829]: Executing op: ProductPublish(PackageKey={46CB15E5-D036-4F9C-8D32-B2C532CC796D})
MSI (c) (EC:2C) [14:54:22:845]: Executing op: UpgradeCodePublish(UpgradeCode={7053E159-FED6-4C51-9F8B-BCDBDA4D20AB})
MSI (c) (EC:2C) [14:54:22:845]: Executing op: SourceListPublish(,,,,NumberOfDisks=1)
MSI (c) (EC:2C) [14:54:22:845]: Executing op: ProductPublishClient(,,)
MSI (c) (EC:2C) [14:54:22:845]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (c) (EC:2C) [14:54:22:845]: Note: 1: 2318 2:  
MSI (c) (EC:2C) [14:54:22:845]: Note: 1: 2318 2:  
MSI (c) (EC:2C) [14:54:22:845]: DoAdvertiseScript is returning: 0
=== Verbose logging stopped: 11/15/2012  14:54:22 ===

=== Verbose logging started: 11/15/2012  14:56:43  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\system32\svchost.exe ===
MSI (c) (EC:5C) [14:56:43:816]: User policy value 'DisableRollback' is 0
MSI (c) (EC:5C) [14:56:43:816]: Machine policy value 'DisableRollback' is 0
MSI (c) (EC:5C) [14:56:43:816]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (c) (EC:5C) [14:56:43:816]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1097819651,LangId=1025,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (EC:5C) [14:56:43:816]: Executing op: ProductInfo(ProductKey={15578C01-B0F0-44B9-8A2F-110A5AE46471},ProductName=APP for برنامج Microsoft Outlook,PackageName=ZimbraConnectorOLK_8.0.0.673_x86.msi,Language=1025,Version=134217728,Assignment=1,ObsoleteArg=0,ProductIcon=zimbra.ico,,PackageCode={46CB15E5-D036-4F9C-8D32-B2C532CC796D},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (c) (EC:5C) [14:56:43:816]: Executing op: DialogInfo(Type=0,Argument=1025)
MSI (c) (EC:5C) [14:56:43:816]: Executing op: DialogInfo(Type=1,)
MSI (c) (EC:5C) [14:56:43:816]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=‏‏إجراء الإرجاع:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=‏‏إزالة ملفات النسخ الاحتياطي,CleanupTemplate=الملف: [1])
MSI (c) (EC:5C) [14:56:43:816]: Executing op: ActionStart(Name=PublishFeatures,Description=‏‏نشر ميزات المنتج,Template=الميزة: [1])
MSI (c) (EC:5C) [14:56:43:832]: Executing op: FeaturePublish(Feature=ZimbraMAPIProvider,,Absent=0,)
MSI (c) (EC:5C) [14:56:43:832]: Executing op: ActionStart(Name=PublishProduct,Description=‏‏نشر معلومات المنتج,)
MSI (c) (EC:5C) [14:56:43:832]: Executing op: IconCreate(Icon=zimbra.ico,Data=BinaryData)
MSI (c) (EC:5C) [14:56:43:832]: Executing op: IconCreate(Icon=generic.ico,Data=BinaryData)
MSI (c) (EC:5C) [14:56:43:832]: Executing op: CleanupConfigData()
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\10C875510F0B9B44A8F211A0A54E4617\Patches 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Executing op: ProductPublish(PackageKey={46CB15E5-D036-4F9C-8D32-B2C532CC796D})
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617 3: 2 
MSI (c) (EC:5C) [14:56:43:832]: Executing op: UpgradeCodePublish(UpgradeCode={7053E159-FED6-4C51-9F8B-BCDBDA4D20AB})
MSI (c) (EC:5C) [14:56:43:832]: Executing op: SourceListPublish(,,,,NumberOfDisks=1)
MSI (c) (EC:5C) [14:56:43:832]: Note: 1: 1402 2: UNKNOWN\Installer\Products\10C875510F0B9B44A8F211A0A54E4617\SourceList 3: 2 
MSI (c) (EC:5C) [14:56:43:847]: Executing op: ProductPublishClient(,,)
MSI (c) (EC:5C) [14:56:43:847]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (c) (EC:5C) [14:56:43:847]: Note: 1: 2318 2:  
MSI (c) (EC:5C) [14:56:43:847]: DoAdvertiseScript is returning: 0
=== Verbose logging stopped: 11/15/2012  14:56:43 ===

=== Verbose logging started: 11/15/2012  15:10:23  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\system32\svchost.exe ===
MSI (c) (F0:F0) [15:10:23:317]: User policy value 'DisableRollback' is 0
MSI (c) (F0:F0) [15:10:23:317]: Machine policy value 'DisableRollback' is 0
MSI (c) (F0:F0) [15:10:23:348]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (c) (F0:F0) [15:10:23:348]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1097819651,LangId=1025,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (F0:F0) [15:10:23:348]: Executing op: ProductInfo(ProductKey={15578C01-B0F0-44B9-8A2F-110A5AE46471},ProductName=APP for برنامج Microsoft Outlook,PackageName=ZimbraConnectorOLK_8.0.0.673_x86.msi,Language=1025,Version=134217728,Assignment=1,ObsoleteArg=0,ProductIcon=zimbra.ico,,PackageCode={46CB15E5-D036-4F9C-8D32-B2C532CC796D},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (c) (F0:F0) [15:10:23:348]: Executing op: DialogInfo(Type=0,Argument=1025)
MSI (c) (F0:F0) [15:10:23:348]: Executing op: DialogInfo(Type=1,)
MSI (c) (F0:F0) [15:10:23:348]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=‏‏إجراء الإرجاع:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=‏‏إزالة ملفات النسخ الاحتياطي,CleanupTemplate=الملف: [1])
MSI (c) (F0:F0) [15:10:23:348]: Executing op: ActionStart(Name=PublishFeatures,Description=‏‏نشر ميزات المنتج,Template=الميزة: [1])
MSI (c) (F0:F0) [15:10:23:348]: Executing op: FeaturePublish(Feature=ZimbraMAPIProvider,,Absent=0,)
MSI (c) (F0:F0) [15:10:23:348]: Executing op: ActionStart(Name=PublishProduct,Description=‏‏نشر معلومات المنتج,)
MSI (c) (F0:F0) [15:10:23:348]: Executing op: IconCreate(Icon=zimbra.ico,Data=BinaryData)
MSI (c) (F0:F0) [15:10:23:363]: Verifying accessibility of file: zimbra.ico
MSI (c) (F0:F0) [15:10:23:379]: Note: 1: 2318 2:  
MSI (c) (F0:F0) [15:10:23:379]: Executing op: IconCreate(Icon=generic.ico,Data=BinaryData)
MSI (c) (F0:F0) [15:10:23:395]: Verifying accessibility of file: generic.ico
MSI (c) (F0:F0) [15:10:23:395]: Note: 1: 2318 2:  
MSI (c) (F0:F0) [15:10:23:395]: Executing op: CleanupConfigData()
MSI (c) (F0:F0) [15:10:23:395]: Executing op: ProductPublish(PackageKey={46CB15E5-D036-4F9C-8D32-B2C532CC796D})
MSI (c) (F0:F0) [15:10:23:410]: Executing op: UpgradeCodePublish(UpgradeCode={7053E159-FED6-4C51-9F8B-BCDBDA4D20AB})
MSI (c) (F0:F0) [15:10:23:410]: Executing op: SourceListPublish(,,,,NumberOfDisks=1)
MSI (c) (F0:F0) [15:10:23:410]: Executing op: ProductPublishClient(,,)
MSI (c) (F0:F0) [15:10:23:410]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (c) (F0:F0) [15:10:23:410]: Note: 1: 2318 2:  
MSI (c) (F0:F0) [15:10:23:441]: Note: 1: 2318 2:  
MSI (c) (F0:F0) [15:10:23:441]: DoAdvertiseScript is returning: 0
=== Verbose logging stopped: 11/15/2012  15:10:23 ===

Freitag, 16. November 2012 14:20

0

> Actually i get 3 MSI.log file everytime (I think I posted one of them

> before but here goes.)

>

After reviewing the thread - yes, you did... Very strange...

So, now the "old" version is installed and the "new" version still fails

with 1605? You might give a last try:

create a batch file containing

msiexec /i ZimbraConnectorOLK_8.0.0.673_x86.msi /q /l*v Logfile.log

ADDEPLOY=1

(adjust paths to files as required)

create a scheduled task running as system that executes this batch file

run the task

examine the log file

regards, Martin

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren
Montag, 19. November 2012 16:36

0

That will work.

I even have start up script prepared to install it this way (and it works with or without adddeploy=1 .)

Problem is I really want to avoid using this method for obvious reasons.
- Antworten
- Zitieren
Mittwoch, 21. November 2012 20:02

0

> Problem is I really want to avoid using this method for obvious reasons.

There are no "obvious" reasons to use GPO MSI Deployment. It is old, it

is hard to handle in case of errors, and it hasn't evolved since it was

born back in 1999...

NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
- Antworten
- Zitieren

Trouble with GPO msi deployment on Windows 2008 R2 for Windows 7 - 64 machines.

Alle Antworten

Produkte

Ressourcen

Lösungen

Updates

Testversionen

Verwandte Websites

Training

Zertifizierungen

Weitere Ressourcen

Für Produkte

Weitere Supportlinks