[gptalk] Re: auto install

Agreed. Netlogon is probably not the place for these--you don't necessarily
want your packages replicating to every DC.. A good DFS share somewhere on a
file server is your best bet. Eric I think your best bet again is to use the
msi*.log files in c:\windows\temp to troubleshoot why the per-computer
assignment is not working.
 
Darren

  _____  

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Robert Mariani
Sent: Tuesday, September 19, 2006 6:24 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: auto install



Although a valid suggestion i would not be putting my msi files in the
Netlogon directory -

I believe best practice is to create a shared folder on the network and
allow access via security groups etc...

just my 2c

Rob


On Wed, September 20, 2006 11:08 am, Jim Bangle said: 



Eric, 

Are your msi files in Netlogon or a subfolder thereof? They must be stored
there, though the assign process will allow you to browse to other locations
and point to msi's elsewhere. I was caught by this early on. 


-----Original Message----- 
From: gptalk-bounce@xxxxxxxxxxxxx 
To: gptalk@xxxxxxxxxxxxx 
Sent: Tue Sep 19 15:51:18 2006 
Subject: [gptalk] auto install 

I have tried to make group policy auto install programs. I can make it do it
via user config but I would like to it do it via computer config. I have
added the msi and they are set to assign. At startup the computer sais
something briefly about managed software but then does nothing. Anyhelp
would be great.

Other related posts: