SilloSyben

I'm trying to install MSMQ (v3) during an unattended install of the Windows 2003 server. I was hoping to add MSMQ entries to my unattend.txt but MSMQ won't install with the OS. MS claims that you cannot install MSMQ with the OS and it has to be done post install. This in itself isn't a big problem except when I use sysocmgr.exe to automate the task, it prompts me for the CD (mine is a network share). This is my unattended_MSMQ.txt file: [Version] Signature = "$Windows NT$" [Global] FreshMode = Custom MaintenanceMode = RemoveAll UpgradeMode = UpgradeOnly [Components] msmq_LocalStorage = ON [Msmq] Site = DefaultFirstSiteName This is the command I run to install MSMQ: sysocmgr.exe /i:sysoc.inf /u:msmq.txt My question is two-fold: A ) Has anyone solved the issue of sysocmgr prompting for files? B ) Has anyone been successful automating the installation of MSMQ during a Windows 2003 unattended install?

Hi, I recently inherited a Windows 2000 automated install that is having trouble running a VB script (link to a script on a network share) from the startup group when the machine reboots. The script uses case statements to install some apps and hotfixes in a particular order, shifts case and reboots. When the machine comes back up, it auto logs in and runs the script again until it runs out of software to install (5 cases). The problem occurs when the machine reboots and auto logs in, it attempts to run the link in the startup group and I get an error stating something to the effect, the \\FULL_PATH_TO_SCRIPT is not available. Seconds later, I can click start/programs/startup/SCRIPT_NAME and it runs fine. When it reboots and runs the next case, I get the same error. I've been thinking it was the script running before the machine could grab a DHCP IP address so I put a 10 second sleep using "run" in the registry. That didnt help because while the machine was sleeping, it tried to kick off the link. I'm looking for one of several things. Has anyone else encountered this behavior With Win2K/SP4 and been able to attribute it to a post SP4 hotfix? If it's a known Windows problem, I'd prefer not to change the scripting flow already in place and fix Windows. If not, can someone recommend a good way to approach this elusive problem? I'm not opposed to using RunOnceEx to access the script over the network. I do have a sneaking suspicion that running a link to a network resource vs. calling the script from a batch file on the local disk is the problem. Any tips would be greatly appreciated.

@SCP After workign with this menu, I really like it. One feature that seems to be missing from most menu systems is the ability to get user input. I use this menu to choose between operating systems, configurations, etc. The last option I present to a user is to provide a user name and password to access the network. I would like to be able to pass the input to a script. Is this a feature that can be added?

Is there a way to get the menu to display a single (default) language? In my case, I will only use English and don't want the overhead of other languages. Thank you.