Hi again
Well, I'm glad you have such a rugged monitor, but you must have sore knuckles and be all bruised by now :-)
http://www.youtube.com/watch?v=V6iDw5ykmwQhttp://www.youtube.com/watch?v=wt_n6w8Rwcghttp://uk.youtube.com/watch?v=D4a1z7NLnNIdeally, what you would be looking for is a universal CD or DVD from which you can run one or more scripts post-setup to configure and fine-tune everything the way you need it. The Share folder on the server seems to be the alternative method being prescribed by the company.
It sounds like the department that images the CDs or DVDs is using the standard System Builder utility programs available to create an OEM installation, or at least that's what YOU are really doing when you "restore" the hard drive data from the image. OEM System Builders are supposed to preinstall Windows in such a way that the end user is presented with an "Out of Box Experience" (oobe) where they then run through a Wizard that allows them to choose (or at least change) the Computer Name, Add themselves as a new user and create other user profiles, choose their time zone and regional settings, create a dialup connection, etc. and then "activate" Windows if it is WinXP and later.
This preinstall of Windows is supposed to show the OEM builder as the contact for Support, and the installation may include non-Microsoft utilities and applications. I'm not sure if you are fully aware of what is all installed on each "restored" hard drive image, or whether your job is restricted only to the steps you have detailed.
I believe that one of the main stumbling blocks you may have will be your step (f), where several applications need to be setup to run using a batch script. There SHOULD be utility programs available either from within Windows as installed, or from Admin Resource Packs or Support Tools, that allow most of the configuration up to and including step (e), but there are System Administrators on Experts-Exchange who have a LOT more experience with that particular aspect. Usually this involves the preparation of "login scripts" fetched at first run as a new user logs into the system.
For the programs and applications that need to be installed, there are a number of methods for doing this that vary slightly or greatly by setup program depending on how the installer packages were intended to run.
You can perform "automated installations" of Microsoft Office and probably also many of the larger applications like AutoRoute by creating a "share" ahead of time and generating a setup instruction file using the appropriate Microsoft utility.
For example, you can install the Office 2003 Resource Kit on a working PC and use the Custom Setup Wizard tool to create a new share from CD to hard drive, load the *.msi file used for the setup, and then complete the single steps in the wizard to generate an *.ini and/or "transform" file that will allow MS Office 2003 to install and create user settings without human intervention (ie. a fully automated setup).
Microsoft Office 2000 to 2007 Resource Kits:
http://technet.microsoft.com/en-us/library/cc308571.aspxOffice 2007 Resource Kit:
The primary administrative tools for deploying the 2007 Microsoft Office system are included with the product and are no longer available as a download as in previous versions Office.
Create a network installation point for Office 2007:
http://technet.microsoft.com/en-us/library/cc179063.aspxWhat you really need to become acquainted with are the command line switches for the "Windows Installer" setup routine.
Command-Line Switches for the Microsoft Windows Installer Tool Windows 2000:
http://support.microsoft.com/kb/227091For Windows XP:
http://support.microsoft.com/kb/314881/EN-US/For Windows Vista:
I don't know, because I don't have the experience with this OS.
Actually, the commands vary between versions of the Windows Installer (msiexec.exe and ancilliary files) rather than between versions of Windows:
http://msdn.microsoft.com/en-us/library/aa367988.aspxA great many Windows Installer-compliant setup packages from larger non-Microsoft software retailers are created using "InstallShield":
http://documentation.installshield.com/robo/projects/helplibdevstudio9/IHelpCmdLineMSI.htmSmaller third paty software companies sometimes use other Open Source or cheaper setup packages with which you may have to familiarise yourself in terms of command line switches. I provided some links in this question:
http://www.experts-exchange.com/Q_23876973.htmland will paste the relevant part here in case the asker closes it:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
most packages created with "InstallShield" are "Windows Installer" (msiexec.exe) compliant as far as setup switches are concerned.
http://support.installshield.com/kb/view.asp?articleid=q105473However, you also have:
1. InstallMaster/Wise Installation System from Wise Solutions - supposed to comply with the standard switches, but sometimes does not:
http://www.wise.com/2. Inno Setup - open source competitor documented here:
http://unattended.sourceforge.net/InnoSetup_Switches_ExitCodes.html3. Nullsoft Scriptable Install System (NSIS) - open source packager:
http://nsis.sourceforge.net/4. Ghost Installer by Ethalone - commercial packager:
http://forum.ethalone.com/5. Plenty more like "Setup Factory" -
http://www.indigorose.com/setup-factory/Other methods of creating automated scripts and compiling them into standalone *.exe's is exemplified by AutoIT3:
http://www.autoitscript.com/autoit3/Others:
http://support.microsoft.com/kb/231747/EN-US/http://support.microsoft.com/kb/257718/EN-US/http://support.microsoft.com/?id=264478Windows XP's "iexpress.exe" repackager:
http://support.microsoft.com/?id=197147OK, so the actual "package" may allow for standard or company-specific switches, but once the package is opened to the %TEMP% folder, or wherever, the Windows Installer may then be called and other switches may apply that could not have been used on the original package.
For this reason I normally fully unpack setup packages using WinZip, WinRAR, the Extract or Expand commands, and any other means possible to try and establish what's inside. In some cases the process is governed by a setup configuration file (eg. an *.ini) that is plain text and editable in Notepad. In other instances it's one of those cheap home-baked "installers" that is nothing more than an outer wrapping for standard Windows Installer files.
You will find a lot of pre-written setup scripts for common software here:
http://ubertechnique.com/unattended/Scriptshttp://www.appdeploy.com/packages/http://www.msfn.org/board/lofiversion/index.php/f80.htmlhttp://www.msfn.org/board/Application-Installs-f80.html<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Hopefully this may allow you to at least start looking in the right places when you know what programs and applications need to be installed. Some software vendors will have details on their support sites like this:
http://service1.symantec.com/SUPPORT/ent-security.nsf/0/daec50033554fec188256fda00651cf4?OpenDocumentbut most won't and you will have to use some of the "unattended" or "silent install" sites for details.
The difficult part of automated installations is knowing whether or not it is vital that the system reboots to instate settings. As you will be aware, there are a couple of "RunOnce" Registry keys into which a command is written, and this command is activated only once at the next reboot.
http://www.google.com/search?q=the+windows+runonce+key&btnG=Search&meta=It's easy enough when using one of the eg. MS Office Custom Installation Wizard utilities, because you can choose the option to reboot if required. It won't if it doesn't, and will if it does. It's that easy.
When you are unsure, and the setup routine doesn't have the option available, you could import the command into the RunOnce registry key and then run a batch command to make a Windows XP (can't verify for 2000 or Vista) computer reboot.
http://msdn.microsoft.com/en-us/library/aa906348.aspx http://www.aumha.org/win5/a/shutcut.phphttp://www.computerhope.com/shutdown.htm*.INF files can be used to Write or modify Registry values, but you need to know the syntax:
http://vlaurie.com/computers2/Articles/inf-file.htmhttp://www.google.com/search?hl=en&q=.inf+files+write+registry&meta=Windows XP (don't know about Vista) has the REG command that can be tuned with the appropriate switches and parameters to modify the registry:
REG /?
REG Operation [Parameter List]
Operation:
[ QUERY | ADD | DELETE | COPY | SAVE | LOAD |
UNLOAD | RESTORE | COMPARE | EXPORT | IMPORT ]
Return Code: (Except for REG COMPARE):
0 - Succussful
1 - Failed
For help on a specific operation type: REG Operation /?
Examples:
REG QUERY /?
REG ADD /?
REG DELETE /?
REG COPY /?
REG SAVE /?
REG RESTORE /?
REG LOAD /?
REG UNLOAD /?
REG COMPARE /?
REG EXPORT /?
REG IMPORT /?
Not forgetting *.REG scripts themselves. If you set up a computer the way you want it configured, and then export the registry keys containing the settings that you wish to replicate on other computers, then they an be Imported to the registry on other computers using the commands:
reg import filename.reg
or
regedit /s filename.reg
For a silent import using the regedit command, add the /s switch as above, and leave it out to be prompted and notified. It can be a *.txt file also.
Knowing what registry keys and values are helpful, but there are registry monitoring utilities you can use to compare the Before and After registry status when installing programs. A useful and free program for comparing text-based files side by side is ExamDiff Visual File Comparison Tool by PrestoSoft:
http://www.prestosoft.com/ps.asp?page=edp_examdiffInstaller:
http://www.prestosoft.com/download/ed17_setup.exeStandalone *.exe:
http://www.prestosoft.com/download/ed17.zipFor corporate and very much extended use, these are excellent tools:
http://www.prestosoft.com/edp_examdiffpro.aspBeyond Compare:
http://www.scootersoftware.com/moreinfo.phpAs far as tweaking Windows settings is concerned, then this SHOULD all have been done before the CD Image was created such that you don't have to start messing with the registry for anything other than non-Windows programs and applications. Nonetheless, you may find a use for TweakUI at some point, so here's the links:
TweakUI for XP:
http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspxNo such "Microsoft" utility for Vista:
http://forums.techarena.in/vista-help/700353.htmThat's just about all I can think of that may at least be of some help, if you weren't already aware already.
Bill
