Thanks for the reply Ralf. We're deploying Android profiles (trying to avoid Android legacy for a move to Android Pie). I thought the 1811 update sorted that issue, in the release notes it mentions that you can use Knox containers just by having a licence active (without the enable containers option checked) and that would make it possible to use a Knox container with Android Enterprise and avoids using Android Legacy profiles.
'You can now enable Knox for Android devices without using Android Legacy settings.
Under Intelligent Hub Settings the Knox license key field is no longer dependent on the Enable Containers setting. This means you can enter a Knox license key, without turning on Enable Containers (which only applies to Android Legacy). If Enable Containers is checked and Android EMM Registration is configured, this turns on Knox Play for Work (Android legacy enrollment mode).'
I might understand that incorrectly, i'm a bit lost and confused with the whole thing at the moment.
Whenever we build a device using this it builds and then asks us to accept the Samsung EULA in the notifications. You tap on that and it just seems to re-load up HUB and the notification stays there. Confusing as hell!