We’ve determined that when we update to 10.2, we do not want any users to continue using Classic style. I’m looking for a way to disable/remove the option to login with Classic Style. Any suggestions?
Thanks!
You can force to a specific style in the shortcut that they use. It doesn’t really lock them out of it, but if they don’t mess with the shortcut, it doesn’t give them options to pick a different style.
Thanks for the info. It was very helpful. We actually want to push all the users to the new Active Homepage. It appears that is possible with the /active switch instead of /classic or /shell in the command line.
1 Like
@danvoss - where you able to successfully move your users to Active Homepage?
We would like to disable classic login option (Shell) so we can move users towards the Active Homepage when we test and release 10.2.600. The modern shell type would be a step in the right direction if users don’t adapt to active homepage right away.
Yes, we did deploy only with Active Homepage and got only a minimal amount of complaints. This was probably because we didn’t tell any users that the other options were still available. 
This plan was with the consent of other management stakeholders. We copied the new version and shortcuts via scripting so when users launched the new shortcut it was pre-configured with the /active switch.
In training, we also pushed users to use the search functions to find menu items instead of navigating the menu system.
1 Like
Thank you. I believe that we can accomplish the /active switch in our sys config file via the user setting note - Launch Type value as well.
We probably need to decide if we jump everyone to active homepage or not to accomplish this. We have users still using classic and it will be a jump for them. However as you mention if we don’t give other choices they will adapt with grumbling 