Classic Shell on Windows 10 allowed on Intune-managed Desktops?
Hello Experts,
I am migrating an organization to the Azure cloud and Microsoft 365. They are currently running Windows 10 Pro build 1903. However, the end users were not comfortable with the Windows 10 UI, so the IT manager installed "Classic Shell" (http://classicshell.net/) on all of the desktops to allow the users to have their familiar Windows 7 interface.
My question is: Once we migrate them to the cloud and start managing the desktops with Intune, will ClassicShell be allowed or blocked?
I have searched the ClassicShell forums, and also all of the Intune documentation, and there is no mention of customizable start menu programs being supported or blocked.
I guess it could possibly be whitelisted as an allowed app, but I'm not sure.
We are still about 2 months out from the migration, so I'd like to remove ClassicShell now and allow the end users to get used to the Windows 10 start menu early, rather than waiting until they are in the cloud and the have to get used to many things, including no ClassicShell.
Anyone have experience with custom start menu utilities and managed Windows 10 desktops in Intune?
Thanks in advance for your insight. Any info is greatly appreciated!
I am migrating an organization to the Azure cloud and Microsoft 365. They are currently running Windows 10 Pro build 1903. However, the end users were not comfortable with the Windows 10 UI, so the IT manager installed "Classic Shell" (http://classicshell.net/) on all of the desktops to allow the users to have their familiar Windows 7 interface.
My question is: Once we migrate them to the cloud and start managing the desktops with Intune, will ClassicShell be allowed or blocked?
I have searched the ClassicShell forums, and also all of the Intune documentation, and there is no mention of customizable start menu programs being supported or blocked.
I guess it could possibly be whitelisted as an allowed app, but I'm not sure.
We are still about 2 months out from the migration, so I'd like to remove ClassicShell now and allow the end users to get used to the Windows 10 start menu early, rather than waiting until they are in the cloud and the have to get used to many things, including no ClassicShell.
Anyone have experience with custom start menu utilities and managed Windows 10 desktops in Intune?
Thanks in advance for your insight. Any info is greatly appreciated!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
We don't know whether you configure Intune to block processes (as with applocker), in the first place.
The classic start menus by open shell or classic shell are simply a process, so it can be whitelisted.
The classic start menus by open shell or classic shell are simply a process, so it can be whitelisted.
ASKER
Thank you Experts for your insightful advice!
I can't help with you any issues about Classic Shell as it relates to Intune, but if you continue down the Classic Shell path for W10, you should know that the original Classic Shell is no longer in active development, and hasn't been for almost two years. It is probably not a wise idea to use it on current releases of W10. However, there is a fork of it called Open Shell, available at GitHub:
https://github.com/Open-Shell/Open-Shell-Menu
I haven't tried it yet, but it's likely a better bet than the last release of Classic Shell.
In terms of "custom start menu utilities", I wrote one called TrayLaunch, but rather than messing with the Start menu, I implemented the ability to launch all apps from icons in the notification area (aka system tray...hence, the name...TrayLaunch). The Quick Start Guide for a very early version of it (v1.1) is at this EE post:
https://www.experts-exchange.com/questions/29071583/A-tool-that-we-can-place-or-pin-a-menu-list-instead-of-an-apps-in-Windows-10-task-bar.html?anchorAnswerId=42406042#a42406042
It has been in active development for the two years since that post and is now at Version 5.0.16, which is light years ahead of v1.1. Let me know if TrayLaunch interests you. If not, your idea to get the end-users used to the W10 Start menu is a good idea, if they'll go for it. Regards, Joe