I have created a GPO similar program specifically for deploying applications to workstations. Similar to how GPO can push software packages.
I like to call it wpkg. (dpkg for Windows :) It's very simple, but, very effective, and it works for more than MSI's. It consists of a script, which is run at STARTUP (not login) as a domain account. I did this by using FireDaemon to start it. The script examines a centralized XML file (on a share reachable by the service the script is started by). The XML file details packages, version, and command lines to add/remove/upgrade each package. There is another XML file, for profiles, which reference package's in the packages file. This is used for departments in my office. I have a profile named "it" which requires certain packages. Profiles can inherit from other profiles. The sum of all packages is collected. The script then compares the packages that should be installed, with those that are, from a local xml file (C:\WINNT\System32\wpkg.xml), and determines what action it needs to take for each file. Install, Upgrade, or remove. Each package has a list of command lines assoicated with each action. Such as running msiexec /i <path to an msi> for the install action, and msiexec /x for remove commands... some of my packages just run xcopy. It's pretty useful. The main problem im having with it is the FireDaemon service needs to start as a Domain user, so I need to edit the computers local security policy to enable that account to Log on as a Service. That would have been automated by group policy. :D Jerry Haltom Feedback Plus, Inc. On Wed, 2003-07-09 at 12:22, Erich Vinson wrote: > > However, the advantage that GPO's had when I used them is that they seem to > > take effect immediatly where some of the registry edits with kixtart > > don't... > > The reason for this is that in a native 2K domain, you can set a GPO > refresh interval that downloads and applies updated GPOs. We could > certainly implement something similar to that, whether with Kixtart or > developing a new app... > > I would like to start getting input from other admins that use Samba as > a 2KServer alternative as far as the features they would like to see, > how it should be deployed, etc. > > Not sure right now which is better, modify Kixtart or start from > scratch? I have been thinking more and more and definately want to get > something started, if for no other reason than it would make my life > easier ;-) Of course, I'm willing to share! :-D Also, this could really > help the cause of Samba as the GPO thing is a pretty major hurdle for 2K > admins to overcome when considering whether to switch or not. > > -- > Erich Vinson > Chief of Technology > IT, Inc. > ------------------------------------------------------------------------ > 64 6F 6E 27 74 20 66 65 61 72 20 74 68 65 20 70 65 6E 67 75 69 6E -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
