Thanks Andrew.

I agree that the Deployment Wizard can do that, but I'm taling about the Deployment Utility which is run from the command line and does not require any user interaction when run in either Silent or Output mode.

What I want to be able to do, ideally, is to enable the IT Operations team to deploy an entire solution (containing a Database Project, SSIS Project and SSAS Project) via an installer process such as WiX to multiple environments. To do that, the installer needs to run the individual utilities to deploy each Froject. For Database Projects that's sqlpackage.exe, for SSIS Projects that's the SSIS Deployment Utility and for SSAS Projects it should be the SSAS Deployment Utility, but as I can't get the latter to work in the mode in which I want it to, that option does not seem to be available to me.

I suppose I could run the Deployment Wizard in the DEV environment, get it to produce an XMLA deployment script and then notify the Ops team of the changes they will need to make to the script to deploy into other environments, but that introduces the possibility of mistakes being made. Maybe I'll have to rely on that and make sure the the accompanying documentation is up to scratch! 😉

Regards

Lempster