Windows automated software deploy tool

From: Jerry Haltom (jhaltom_at_FEEDBACKPLUSINC.COM)
Date: 12/25/03

  • Next message: Paul Webster: "Re: Upcoming Windows XP SP2 NX feature"
    Date:         Thu, 25 Dec 2003 11:11:34 -0600
    To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
    
    

    Russ, I'm not sure if this is an appropriate message for this list, but
    I have seen a few similar such mailings come across since I subscribed.
    So, you'll either reject it or not. :)

    I have put together and have been using in production (about 25
    computers, no much) a very simple, bare-bones, Windows automated
    software installation and management tool. The basic idea follows that
    of SMS and other similar products: pushing software installs and
    upgrades to a variety of workstations, unattended, with no user
    interaction, with "profile" support for different system configurations.

    The difference between these other products is how simple this one is.
    It boils down to nothing except a 1200 line .js (JScript) script. It's
    very easy to maintain and understand, and has absolutely no server side
    overhead (it is installed on each workstation, as a service, and pulls
    it's package list from a standard Windows share).

    It's worth noting that I use it with a Samba PDC. No Windows server
    back-ends. A common problem I've noticed with all the commercial systems
    of similar class is they require something on the server end: either
    Active Directory, IIS, etc. This doesn't. This doesn't even require a
    Windows domain at all. Just a centralized file share.

    It also doesn't rely on any particular packaging method. MSIs are nice,
    but worthless until every piece of software you use comes in one.

    Since running it as a service is the best way to do it, it will install
    packages in the background, without user interaction. In fact, I've had
    instances when I've installed software such as Office while the user was
    using their system. The icons just appeared on the desktop while they
    were working.

    All the configuration files are in very simple XML. No GUIs. :)

    Anyways, it's free/open source (GPL) and such, so anybody is welcome to
    take a look at it, improve it, and use it themselves. I just now stuck
    the package up on SourceForge (for lack of a better place). The .zip
    includes some instructions for getting it up and running (Windows
    Resource Kit necessary). I welcome all feedback! I've only tested it on
    Windows 2000 by the way.

    The SourceForge project page is http://wpkg.sf.net

    If you reject this message, sorry for your time. :)

    Jerry Haltom
    Feedback Plus, Inc.

    ----
    NTBugtraq subscribers save $103.00 off the TICSA exam by using promo
    code "NT1003" when registering to take the TICSA exam at www.2test.com.
    Prove to your employer and peers that you have the knowledge and
    abilities to be an active stakeholder in today's enterprise security.
    Become TICSA certified www.trusecure.com/ticsa.  Promotion expires
    12/31/03 and cannot be used in combination with other offers.
    ----
    

  • Next message: Paul Webster: "Re: Upcoming Windows XP SP2 NX feature"

    Relevant Pages

    • Re: ActiveX component cant create object and Permission Denied Error (Widows 2003 and DCOM)
      ... ActiveX component can't create object. ... what am I missing to configuring the Package. ... Windows 2003 and can't use Domain admin at this point due to other reasons. ... Any help and link explaning setup and installation would be appreciated. ...
      (microsoft.public.vb.com)
    • This might help!
      ... Nero InCD: ... this handler into windows shell, ... And something else, remember every CD-RW drive comes in a package, unless ... DVD-ROM like PowerDVD), documentation, installation figures, and sometimes ...
      (microsoft.public.windowsxp.hardware)
    • RE: This might help!
      ... > this handler into windows shell, ... both 1.02 and 1.5; if you use InCD and you cannot access disks formatted ... > And something else, remember every CD-RW drive comes in a package, unless ... > itself, screws, installation disks (including vendor's software (unless it's ...
      (microsoft.public.windowsxp.hardware)
    • Re: Installing software or Add Ins on Client PCs
      ... The EXE file contains an MSI file that you can use to install the package via Group Policy Software Installation. ... Depending on what format the software is available, you'd so either Software Installation or the logon script. ...
      (microsoft.public.windows.group_policy)
    • Re: Linux and WLAN Internet access
      ... >> a clone of Windows, as if Unca Bill has the last word on worthiness. ... >installation process, but having nothing other than a dependency warning, ... >a package include all of the dependencies in his package, ...
      (alt.os.linux.suse)