Michael-
SI uses the MSI product code (aka product id) to determine whether an
application is installed already or not. I think that if you have an
upgrade relationship between v.1 and v.2 and the Product codes are the
same, then it will ignore the upgrade. 

There are a lot of options for troubleshooting this. When an app is
deployed via GPO, it is registered in a couple of places (at least).
First, if you're doing a per-user deployment, its registered under
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group
Policy\AppMgmt. Regardless of whether it deployed via GPO, any MSI
package gets registered in HKLM or HKCU (depending upon whether its
per-machine or per-user) in Software\Microsoft\Installer. If you're
trying to deploy your app to machines where its already been deployed,
trying clearing it out from these two locations (doing a normal
uninstall should do that in the case of the Installer key, but just in
case). 

Also, you can turn on verbose MSI logging via policy to see if something
is going wrong during install. That policy is found in Computer
Configuration|Administrative Templates|Windows Components|Windows
Installer|Logging. Finally, there is a verbose SI logging capability
that you can enable. I recently created a custom .adm that lets one
enable a variety of GPO logging, including SI. Email me offline and I
can send that to you.

Darren

 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Wassell
Sent: Tuesday, April 06, 2004 12:27 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Assigned software deployment via GPO

Kind of had my hopes up for this one but I just tested it on 4 different
computers and still the same outcome :-P

I wonder if whatever *was* installed that was shown in the Event Log
tainted any further testing that I did afterwards.

That wouldn't make much sense though because I am forcing a required
upgrade between the GPO's so it should install even if it is detecting
that the application is already installed.  Or not?  I don't think GPO
is "smart" enough to detect if the the version installed is the same
version that is being "upgraded"?  Does anyone know?

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Wassell
Sent: Tuesday, April 06, 2004 3:11 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Assigned software deployment via GPO

Yes actually I was.  

I have done other tests using different machines, but that particular
test I used the same machine for.  I will try it using a different
machine.  I did force the GPO to uninstall the assigned application from
the previous GPO (eventhough it hadn't actually been installed, but
shown in the event log), but it is still worth a try I suppose.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004 3:03 PM
To: [EMAIL PROTECTED]
Subject: Re: [ActiveDir] Assigned software deployment via GPO


Are you testing it on the same PC in the Production OU that you used in
the Test OU?

-Peter


 

                      "Michael Wassell"

                      <[EMAIL PROTECTED]        To:
<[EMAIL PROTECTED]>

                      om>                            cc:

                      Sent by:                       Subject:
[ActiveDir] Assigned software deployment via GPO

                      [EMAIL PROTECTED]

                      tivedir.org

 

 

                      04/06/2004 02:55 PM

                      Please respond to

                      ActiveDir

 





Okay guys, I am at my wit's end here....

I've been trying to distribute an .MSI package via GPO as an Assigned
application to an OU in AD.

Test environment:  Worked perfectly fine in my test environment, I
copied the install package to a share on the server, set permissions,
assigned the application to a GPO and that was it.  Worked perfectly
ever since.

Production environment:  Exact replica of permissions, shared folder
names, the file is the same, the usernames/security groups are different
and the name/properties of the GPO used to deploy the application are
different.
Will not work for the life of me.

Thinking that it might be a problem with the GPO I created a test OU and
blocked inheritance (without linking any other GPO's), test user
account, test GPO and assigned the application in the new GPO,
redeployed the application.  Still no go.  The deployment works fine if
the application is published, but my boss wants 0 user interaction (I.E.
install at logon).

The weirdest thing is that the event viewer shows that the application
is installed successfully, but it isnt actually installed anywhere (no
registry keys, or program files etc.).  Which makes no sense because it
works perfectly in the test environment.

This should be something that is very simple but it has been the biggest
pain in the NECK!!! (for lack of a better term)

Anyone with any idea's, I'm ALL ears :-)



List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/


List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/


List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/

List info   : http://www.activedir.org/mail_list.htm
List FAQ    : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to