 OK, here's the solution:  What happens is that the setup also install a couple of prereqs. An update Windows6.0-KB958655-v2-x86.msu and DotNet 3.5. These both need a reboot. SCCM starts the setup. It starts the installs of the prereqs and reboots. SCCM does not know about these reboots and does not continue afterwards . Thats why i dont have the log file Michel talks about earlier in this thread.  I've created separate packages for both prereqs. SCCM takes care of the reboots and continues with the next step. When started now setup.exe notices these prereqs have been installed already and simply starts the msi with all the switches for finding SQL, database, etc.
Hi all,  Michel posted this: [URL]   Which is great, but i would like to perform an unattended install of the server extensions at the end of a SCCM2007 task sequence that installs a terminal server.  Can anybody help me in finding the right command line arguments for this?  thanks in advance....
Unattended install of server extensions on a terminal server