With SEB 2.4.1 for Windows, you cannot use the "Launch SEB" button if you try to start the quiz in SEB from another browser (this also applies to the current iOS version). You can use "Download configuration" and then open the downloaded config file, which will start SEB 2.4.1 into the quiz.
The other option is to send your students a config file (or put it on some web server and send them a sebs:// link to it) saved with the option "Use SEB settings file for ... configuring a client". Create that config file manually and indicate your Moodle server as "Start URL" and don't use a Quit Password in that config. Also disable the setting in the Exam pane for Session Cookies "Clear on session end" (then students will stay logged in when they're starting the quiz with its own configuration).
After applying that client config once, students then can open SEB directly, navigate to the Moodle quiz inside of SEB and that error message should no longer be displayed.
Why do you prefer to use 2.4.1? 3.0.1 has various advantages, one of those being that indirect/authenticated seb(s) links from other browsers work (that's why the Launch SEB button works in 3.0, but not in 2.4.1).
The other option is to send your students a config file (or put it on some web server and send them a sebs:// link to it) saved with the option "Use SEB settings file for ... configuring a client". Create that config file manually and indicate your Moodle server as "Start URL" and don't use a Quit Password in that config. Also disable the setting in the Exam pane for Session Cookies "Clear on session end" (then students will stay logged in when they're starting the quiz with its own configuration).
After applying that client config once, students then can open SEB directly, navigate to the Moodle quiz inside of SEB and that error message should no longer be displayed.
Why do you prefer to use 2.4.1? 3.0.1 has various advantages, one of those being that indirect/authenticated seb(s) links from other browsers work (that's why the Launch SEB button works in 3.0, but not in 2.4.1).
