Thanks to the great help I received in this forum previously with a batch script, I figured I'd pop back in and ask for advice once again.

I have a software package that is to be installed across a large number of client machines, but each machine's output must be uniquely identifiable. Each machine will perform an identical task, but the setup process for the HOST software is labor intensive and prone to mistakes in entry. Ideally, I'd be the one to set them all up but I can't guarantee that will be the case, so I'd like to minimize error.

So my thought is this. The host software creates a working directory in which all configuration files exist. All of the config files are either .xml, .ini, or .par, and all are TEXT readable with a text editor. There are about two dozen config files that need to be updated on each client, some of them rather extensively, but the only difference between fully configured clients is the machine name in each of the config files.

So, I propose that I do a clean install and then backup the working directories.

Then, I go through the configuration process on Machine #1.

I now have two directories I can compare. I have verified that I can manually go in to each config file and change "Machine #1" to "Machine #2", then copy the new config files and associated directory STRUCTURE over a virgin install, and the software works as intended. The PROBLEM is that this isn't much less labor intensive than just going through the configuration process manually.

So...if I could automate the process that would be super duper swell. I don't know that batch would be the best way though. Any ideas would be greatly appreciated! I have about a week to get something in place before the clients start showing up.Total Uninstall...Just FYI, I have elected to use NSIS, using the following three examples as a guide.

Reusable installer script
Installer for SUCCESSIONAL Installations
TextReplaceInFolder