laggerific

We have a build process that installs a basic setup with standard apps and such and we can tweak a post-install script to customize the machine for various departments and divisions. I am trying to figure out how to enable quicklaunch and to have it set so that any new user that logs on will get the same set of icons in the quicklaunch. I've seen some quick launch related info, but it all seems to be for the currently logged on user, or am I way off on that? Are there any suggestions for enabling quick launch for "default users" and then populating the quicklaunch folder that will be created for any new user on that machine? I was thinking of creating a script that adds the quick launch registry tweak to enable it, and then copying the shortcuts to the quicklaunch folder, but I don't know the path of the quicklaunch folder for the "default user" so that it will copy to every created user. Or is it possible to put this in the All Users Application Data folder to do the same thing? Thanks for any suggestions. PS: I'm also hoping to be able to put the quicklaunch icons in a certain order...I imagine that is in the registry part, though, so hopefully it'll just be a matter of getting it in the registry. But where would I put it in the registry if I wanted it to be for everybody?

I have decided to start looking into a script that will start monitoring the processes and wait for the one that is spawned by the filemaker installer to finish. I am currently looking into just looking for the process name of the executable, iassist.exe in this case, and then waiting for it to no longer be there before moving to the next part of the script. Does anyone have any sample code that does something similar to this? I am trying to figure out the best way for it to detect the process, and while I am new to all of this, I am starting to look into WMI for this functionality. Any suggestions as to which way to start would be greatly appreciated...as you can see I've already started, but anyone with a better understanding of WMI or VBScript that can point me in a useful direction would be great, as right now I am in a trial and error stage that could take a long time to get out of.

I've just tested both of these methods and the problem is still there. Is that something that they need to fix on their end? It looks like the setup.exe file for FileMakerPro7 just calls an MSI file, which could be why the scripts think that the process has finished, when it has actually just called another process. The problem is that the setup.exe file has a setup.ini file which is where the licensing info and silent install info is, so I don't think I can just install it off of the .MSI file. Is there any place that focuses on dealing with these sort of problem installers? I'm thinking that I might need to add some code to the script to keep looking for the existence of the installer process and then proceed once it's no longer there, but that would far exceed my current scripting knowledge. I look forward to that challenge, but I would also be interested if anyone has any other ideas that are more elegant. Thanks everyone!

I am working on a script that will install my main applications once the OS is installed, and one of the apps I want to install has several patches that need to be installed afterwards. Does anyone know if it's possible to have a batch file that will call the install of an app and wait for it to finish before continuing on to install the updates? Or is that something I will have to look at WSH or something to be possible? Hopefully, this isn't off topic...thanks all!