I noticed that this process was creating several new services, one of which, "Windows Internal Database" was listed as a dependency to the Remote Desktop Connection Broker.
On further investigation, this service would not start due to a log on error. It seems an automatically generated account was used to log on.
To resolve, once the installation process started I opened up this service and changed log on to local system account. Installation of the remote desktop services then continued successfully.
