Deploying software in Server 2003

By k.jacko
Aug 28, 2007
Topic Status:
Not open for further replies.
  1. Windows Server 2003 SP2

    I'd like to 'attempt' to deploy a small 3rd party remote desktop viewing program onto each pc on the domain.
    Needless to say it would be a ball ache to do it manually at each pc.

    Can i do it through some relative deployment features in server 2003?
    Obviously i've never tried it before, or even have much knowledge of the admin/resoures kits available in 2003.

    So, any help would be most appreciated.

    Cheers
    :)
  2. Nodsu

    Nodsu Newcomer, in training Posts: 9,431

    Software deployment is a builtin feature of Active Directory, so in theory this is very possible. It's the details that will kill you though :p

    Anyway, unless your program is so simplistic that you can copy a handful of files and edit some registry keys, you need the MSI file. Some vendors suppli MSI files themselves, but usually one has to cheat and extract them from the executable installer.

    A common trick is to run the installer, but not do anything else. Then look in the system temporary files folder for the relevant .msi file (it may be in some obscure subdirectory). Once you have the .msi, you put it on a network share and set it up to be deployes using the GPMC.

    Edit a policy or create a new one. You create a new package in Software settings->Software installation.

    Feel free to read all about the software deployment feature of AD at Microsoft.
  3. k.jacko

    k.jacko Newcomer, in training Topic Starter Posts: 743

    Lol, thanks. That was my fear.

    I have read about how to create an msi installer using various 3rd party programs.

    Certainly need to read more and test it.
  4. LNCPapa

    LNCPapa TS Special Forces Posts: 4,271   +257

    Creating MSI's is not difficult with the right tools. The right tools will cost you quite a bit - I make packages all the time and typically use WISE to do so.
  5. Nodsu

    Nodsu Newcomer, in training Posts: 9,431

    Most installers use MSI anyway, and it would be rather pointless to create a wrapper MSI around and EXE that is a wrapper for a MSI. You should make sure the existing installer doesn't already use the MSI framework.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.