Anybody using Shell Launcher with Win10 user based/subscription licensing? I'd like to use it for VDI clients to replace local thick workstation shell with Citrix/VMware Horizon client. My issue is Shell Launcher needs Enterprise OS, but we're using Windows 10 E3 user subscription so the OS doesn't become enterprise until a user logs in. (steps up from Pro). However, Shell Launcher (eshell.exe) runs before this process takes place resulting in shell not loading at all. Seems Microsoft may not have taken this scenario into account. Trying to create a pseudo thin client that is still managed/domain joined but when most users log in acts like a thin client/kiosk device.