Windows Server 2012 and IIS bindings problem

Just starting to deploy some 2012 servers. If you can live with the interface then they can be a lot quicker for some operations. However, when working in IIS we've found some interesting buglets, specifically, when setting up a site with multiple bindings, addition net.pipe or net.tcp will fail.
The solution to this is to set the site bindings from the command line using the appcmd command. Create the site as normal and set an http binding on port 80 or whatever. Then to add additional bindings, open a raised privilege command prompt, navigate to the folder where appcmd is (usually C:\Windows\System32\inetsrv and follow the syntax below:

appcmd set site /site.name:MySite /+bindings.[protocol='net.tcp',bindingInformation='40011:*']

appcmd set site /site.name:AService /+bindings [protocol='net.pipe',bindingInformation='AService']

Restart IIS and all should be fine.