Hi Biscuit, welcome to the board.

-1 How to create one master script that calls all other (sub)scripts?
You could use the Call command like shown below.

 Code:
?"Starting Outlook profile creation, please wait...."
Call @ldrive + "\outlookscript.kix"
?"Done."
?
?"Started mapping network drives, please wait...."
Call @ldrive + "\mapdrivesscript.kix"
?"Done."
?
?"Stated mapping network printers, please wait...."
Call @ldrive + "\mapprinterscript.kix"
?"Done."
?
?"Logon script is done.


-2 Where to put the files on the server?
You can put them in the netlogon/sysvol share on your domain controller.

-3 A startup script?
You'd be better of with a logon script because the mapped printers, drives and the outlook profile depend on the user that is logging on.
You can set it with a GPO just fine. If you use kix32.exe as the script and put the name of your master script in the parameters section then you should be done. I always use the full path to kix32 and the script (\\domain.local\sysvol\kix32exe and \\domain.local\sysvol\somescript.kix). It should look in the sysvol folder automatically but better safe then sorry.

Introduction to Assigning Logon Script via Group Policy
_________________________
Mart

- Chuck Norris once sold ebay to ebay on ebay.