Is it possible to remove the classic and modern home screen options

We are on our upgrade journey to go from 10.2.500 to 2023.2 and we are going to approach it in two stages, the plan is to go live with the desktop client and classic apps first in a couple of weeks and then start migrating everything over to Kinetic UI over the next few months. Once done we will be removing the desktop client from users computers and going to the browser exclusively.
We have some users who are still using the Classic home page and are very resistant to change. Given the option they will continue using the classis home screen until we remove the desktop client and are forced to use the kinetic home page in the browser.

What we want to do it force the kinetic home screen now with the classic desktop apps so these users get used to the new home screen while we are working on phase two and then at least when we force them to browser they will have a configured home screen and will be able to find things.

Is there an easy way to do this?

Thanks

Edit your config file to launch as “KineticHome”
Example:

2 Likes

We went the same route - to get user buy in early.

Hi jberger

Tried your suggestion but it does not seem to do anything, user can still use the drop down to select a different home screen, I want to remove these options from the drop down if possible.

image

I think you may need to adjust the sysconfig file on the deployment server instead of the client. The client updates the sysconfig every time it launches, so it may be getting overwritten.

1 Like

don’t know if I’m doing something wrong but it’s not making any difference to the log in prompt, can still select other options.
tried updating both the config in the deployment share and the one on the client machine.

Change the shortcut (desktop shortcut) append

 /Kinetic

At the end of the shortcut
image

4 Likes

Nope, does not stop the user using the drop down and selecting classic or modern. Also, that solution does not scale or stick, having to modify everyone’s shortcuts.
I would of thought there would be a way to do this, even if it required a little database hackery to remove the other two drop down options.
What we want is for that drop down to contain one option, Kinetic and nothing else, with no way the client user can get around it.

I looked at the code behind there’s no way without altering the file. Here’s the only “time” it hides that dropdown

public bool HideMenuTypeCombo
		{
			get
			{
				return BaseApp.SessionMgr.AutoLogOnInformation.IsSingleSignOn || this.IsInChangeUser;
			}
		}

If you are set to single Single on.

1 Like

Bugger, welp, guess that just means we will have to make it policy and just police the users during this transition. And if people insist on using the classic home screen they will just have to deal with the massive shock when we transition to the browser :man_shrugging: and are Kinetic UI everywhere.

1 Like

So for that - we had cloud update our config to also enable sso across the board - so our users don’t even get the option at launch it just logs them in based on AD and bypasses that basic login screen all together. Azure AD that is.