PDA

View Full Version : Automated distribution / Silent Setup


Wolfgang
03-31-2003, 12:21 PM
Hi all,

Now I found again the thread where someone was asking for a automated installation of OSD (Ernest Smit 10-01-2002 05:48 AM):
http://www.cocreateusers.org/forum/showthread.php?s=&threadid=3930
"
We have a large number of seats and want to migrate from ux to w2k. .... Is there anyone among you, who wants to share experiences?
"
So, here I am. ;)

How to automate an OSD installation?

There's a simple program around which can help a lot. It's called AutoIt (http://www.hiddensoft.com/AutoIt/) . It is basically working in the following way:
wait for (MS-window) window getting active
look for the title of the window
look optionally for a text inside the window
send mouse clicks / keystroke to the active window to simulate user inputs
wait for the next window getting active

Based on this you can automate (Auto-IT) a couple of things which are always the same. I wrote the script for AutoIt to install an OSD, and I'm using it since 3 years now and I'm glad to have it.
I have attached my script file for OSD 11.60 (remove the TXT extension!). I'm confident that it will still work with 11.50. Furthermore I changed the script and removed all my company specific stuff. So it will not run after you copied it to your disk! Every place where you will find a xxx in the script you will have to adjust to your own needs. (e.g. location of the 'CD', license server.. ). To make it easy for me too I'm using some environment variables at the top.
What does the script do for you:

connect to a network drive (inclusive a disconnect before)
start the setup.exe from within "Designer Modeling"
confirm welcome, copyright and so on...
choose program language(s) > adjust!
using customized installation, +IKIT -rendering > adjust!
does not show readme, does not start OSD
finish setup.exe
disconnect from the network drive again
do some cleanup (garbage caused by install shield)

The biggest restriction is: Installation has to run in the foreground. But please remind you that ONLY a window in the foreground can accept user inputs.. so it's an OS restriction and not one of the AutoIt.
But: with help of AutoIt and the script I create it's just a single mouse click for me to install a complete OSD! And it's a real installation without manipulation, with still available uninstall... + +
some remarks:

my current experience is based on version 2.61. For me there's no need to update
license : use is free (see below)
there's a '/reveal' option to help creating your own script
there's also a kind of recorder available in the meantime
you can create an executable from your script
for the 'ConTEXT (http://www.fixedsys.com/context/)' editor there's a syntax highlighter available

AutoIt:
"
This program is intended for performing simple automation tasks in Windows. .... The SOFTWARE PRODUCT is licensed, not sold ..... You may install and use an unlimited number of copies of the SOFTWARE PRODUCT.
"

Hope you enjoy it.

yeah, this is the first thread I started :)

jesm
04-02-2003, 12:25 AM
Hi Wolfgang,

It was some time ago that I posted this question and I also found AutoIt as the solution (or workaround). It works okay, but I still think it's not a 'solid' solution. Why doesn't CoCreate provide msi-files? We were used to perform silent installations on unix during a weekend (with Tivoli). So our users were not bothered with installation-stuff on the monday-morning. When migrating to a new major release it concerns ME10+SD+WM so it takes some time. A silent setup (overnight) is not possible (as far as I know) with AutoIt. With msi-files I think this can be done during the weekends again. Making auto-it scripts is still rather tedious too. Exceptions may occur you need to take into account.
So I'm still on the lookout for something better, and I hope CoCreate will support the MS-installer way soon.

Greetings,

Ernest

Wolfgang
04-04-2003, 12:21 PM
Hi, just for your information

there's a very similiar thread in the german cad.de forum. Overthere the starter of the thread is now using OSD via a network installation and a tiny change in the registry of the 'client' machine. He really starts OSD via a network drive and for him it seemed to work fine now.

OSD Installation in a network: in german (http://ww3.cad.de/foren/ubb/Forum29/HTML/000526.shtml)
OSD Installation in a network: in english (http://babelfish.altavista.com/babelfish/urltrurl?url=http%3A%2F%2Fww3.cad.de%2Fforen%2Fubb%2FForum29%2FHTML%2F000526.shtml&lp=de_en&tt=url), as an on-the-fly-translation ;) (made by babelfish)

The network he is using seemed to be quite fast. :eek: