IIRC, assigning to a user doesn't actually install it until
the application is launched for the first time. I'd have to check that for sure,
though. It should create any shortcuts at the outset
however.
--------------------------------------------------------------
Roger D. Seielstad -
MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.
From: Michael Wassell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004 2:55 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Assigned software deployment via GPOOkay 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 :-)
