code:

---

 
\IE             <- Internet Explorer Root
 \Current       <- Current (6.0) version
 \Archive       <- Prior version(s)
  \5.5          <- Version 5.5
 \Test          <- Version not yet supported by IT
 \SvcPack       <- folder for current release SP
  \Current      <- Redirects to actual SP folder
  \1            <- Service Pack 1
  \2            <- Service Pack 2
 \ResKit        <- Resource Kit
 \Support       <- other related tools
 \HotFix        <- All hotfixes
 

---

code:

---

 
Install IE            <- install current version
Install IE -a:5.5     <- install version 5.5
Install IE -t         <- install "test" version
Install IE -sp        <- install current SP
Install IE -sp:1      <- install SP 1
Install IE -rk        <- install the Resource Kit
Install IE -s:sec.bat <- Run sec.bat from Support folder.
Install IE -hf:Sec2   <- install group of hotfixes
                        defined in Security group 2
 

---

So, the idea is - with no args other than the application directory name, we install the current application version. With -a:##, we install from the archive\## folder, and so on.

The #Install batch files follow another guideline.. where possible they invoke an unattended install. This insures that each installation is done in the same manner, and permits unattended installation. We prefer unattended over silent methods - the distinction being that an unattended install still displays a progress bar or message.

Two parameters function differently - the -s:cmd runs the named command from the support folder. This can be any executable. We might use it to apply security lockdowns, registry changes, or other custom configurations. The other is the HotFix (-hf) parameter. This requires the name of an INI file - a "package" - that contains a list of hotfixes and rules for applying them.

Hotfix processing confirms that the hotfix is compatible with the target system (NT4-TS, NT, 2K, etc) and checks for specific arguments to override the defaults. It also allows commands to be executed before and after the application of the hotfix. When all hotfixes are applied, QChange.Exe is run to insure only the latest versions of files are installed.

Finally, some of the tools we use can be deployed against a remote target from an admin workstation. The LogCleanup script I posted earlier is one of them.. I can
Install LogCleanup -r:rmt_server
and install the script, config files, and schedult the tasks on "rmt_server" from my personal workstation. I'll be posting many of the UDFs that make this possible.

One of the benefits of this process is that we now have a consistent installation process.. with 12+ admins, 5 primary sites, and soon - over 550 servers - consistency becomes a "good thing". It also allows new staff to get up to speed quickly, installing components they aren't familiar with (but are smart enough to know when the process works or not).

I hope this plants some seeds in the fertile minds of those that visit this board.. I'll be posting many of the components necessary to implement such tools on your own site. Look for several functions in the UDF section and some tools (including one or two BAT files just to get Lonkero's juices flowing ) in the scripts section. BTW, we use BAT files to initiate unattended installs because Kix may not yet be installed.. Kind of a cart/horse issue, ya know?

Glenn