Thanks for your help, but I have found the solution to this problem.
It appears when you are using Microsoft Volume Licensing Software... you need to set a flag in the setup.xml within the actual installation package itself. By default it selects premium even though you use a standard key.
Changing the flag to a standard installation and using a standard key has now fixed the issue.