Software Installation Failing

  • Thread starter Thread starter Sonny
  • Start date Start date
S

Sonny

Hello Everyone,

I'm trying to push out a msi package using the computer settings software
installation GPO.

I have the package setup and ready to go, permissions are given to domain
usres, even everyone to trouble shoot.

client side is an XP machine, gpudate /force /sync /boot was used numerous
times.

It's odd, it seems that I might be having replication issues, the GPO will
replicate within my interval, but my clients don't see the install package
when booting. The softwrae should install on the machine prior to the user
logging in.

I have it as assigned and have tried to implement the package numerous ways.
What could i be doing incorrectly?

Thanks
 
Also, when i do my gpupdate, i get the message that some processes run on
startup (my software install) so it asks to reboot. So it's seeing my
install... just not allowing it.

any way to specifically log this action?

Thanks guys!
 
If you are deploying the application per-computer, then the computer account
(or at least the Domain Computers group) has to have permissions to read the
MSI from the share. You can enable software installation logging by checking
out http://support.microsoft.com/default.aspx?scid=kb;en-us;249621 or
downloading my GP logging ADM at www.gpoguy.com/tools.htm. The generated log
will tell you why its failing to install, if its a problem with the SI
policy processing process rather than a problem with the MSI.

Darren
 
Thanks,

That debugging doesn't do much for me... i don't really understand what it's
reporting.

I'm going to install the adm template for gpo logging.
 
04-07 12:24:08:343
Software installation extension has been called for foreground synchronous
policy refresh.
The following policies are to be applied, flags are 401.
TRA_Install (unique identifier {704B9F05-0F3B-45D2-86C6-6B4BB7EA99A5})
System volume path =
\\traglobal.com\SysVol\traglobal.com\Policies\{704B9F05-0F3B-45D2-86C6-6B4BB
7EA99A5}\Machine
Active Directory path =
LDAP://CN=Machine,CN={704B9F05-0F3B-45D2-86C6-6B4BB7EA99A5},CN=Policies,CN=S
ystem,DC=traglobal,DC=com
Set the Active Directory path to LDAP://CN=Class
Store,CN=Machine,CN={704B9F05-0F3B-45D2-86C6-6B4BB7EA99A5},CN=Policies,CN=Sy
stem,DC=traglobal,DC=com;.
Enumerating applications in the Active Directory for computer PGHD006 with
flags 5.
The following applications were found in policy TRA_Install.
Assigned application KVS Enterprise Vault User Extensions 5.0 (flags
a0084c70).
Found 1 applications in policy TRA_Install.
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 KVS Enterprise Vault User Extensions 5.0 from policy TRA_Install
is set for installation because it is assigned to this computer policy.
Assigning application KVS Enterprise Vault User Extensions 5.0 from policy
TRA_Install.
Calling the Windows Installer to advertise application KVS Enterprise Vault
User Extensions 5.0 from script
C:\WINDOWS\system32\appmgmt\MACHINE\{0ee97a15-6546-4074-b8cc-177f9860c3a0}.a
as with flags 69.
The assignment of application KVS Enterprise Vault User Extensions 5.0 from
policy TRA_Install succeeded.

Calling the Windows Installer to install application KVS Enterprise Vault
User Extensions 5.0 from policy TRA_Install.
The install of application KVS Enterprise Vault User Extensions 5.0 from
policy TRA_Install succeeded.

Policy Logging for Software Management is attempting to log application KVS
Enterprise Vault User Extensions 5.0 from policy TRA_Install.
Changes to software installation settings were applied successfully.

Software installation extension returning with final error code 0.
 
So what this is telling me is that the software installation part of this
process is succeeding--its processing the policy and attempting to install
the app and not getting an error from the installation-- so maybe the
Windows Installer part is failing. The next step is to enable verbose
Windows Installer logging by setting the following policy: Computer
Configuration\Administrative Templates\Windows Components\Windows
Installer\Logging. Set this value to enabled and enable the most verbose
logging by setting the text box in that policy to iweaprucmvo

Once you set this, during the install a file will get created under
c:\windows\temp called something like msi*.log. Find the correct log file
generated by the following install and post here.
 
Seems as though my logging isn't working... I set the gp around 8 this
morning, it's now 10 and it's not creating it's log... I even searched for
newly modified files an did can't find it anywhere.

I think I'm having an issue with XP... I see that isscript is an issue,
wonder if it's effecting me?

I even set the elevated privileges for the msi install under the windows
installer GPO for user AND computer....

I even set the software install for user and computer and have both in my OU
with my install GPO... I even went as far as creating new users within the
OU so that permissions and GP were set from the start.

It just seems as though it doesn't want to cooperate with anything I try.

Do you have any suggestions?

Thank you for the help thus far!
 
Back
Top