Issue is that there’s one thing that organizations love about Windows that isn’t really catered to in any Linux distribution: Nannying the users and not letting them do their own things with their own systems.
For example, no Linux distribution out there will help you prevent the end-users from changing their own desktop wallpaper, or what to show when the user locks their screen. When my company hands out laptops, the users are blocked from changing out the ugly propaganda slides they make our systems display. Just the tip of the iceburg for how much the enduser can be screwed with by a microsoft admin that just isn’t possible in any significant Linux desktop environment.
So user may love Linux, but their employer still wants to make sure they are running Windows.
Uhhhh yeah there is? You can customize any user profile and centrally control it just as you can on Windows. You can even PXE boot all workstations with new images whenever you want instead of relying on individual machines to issue updates, something that Windows isn’t capable of.
Not sure where you got this idea, but you’re misinformed.
You can’t to the same degree. If you let the user use a typical desktop environment like gnome or plasma., then they can set their wallpaper.
Now if you want to make a kiosk thing, so much easier in Linux. But if you want to have a general purpose desktop experience but restrict stupid stuff like wallpaper, windows has got you.
I would rather use and administer Linux systems at scale any day, but if you hated your users and wanted to lock personalization, then Windows has done the work to enable that.
Sorry, ma dude. This is 100% incorrect. Been doing this a long time, and have managed massive numbers of desktop sessions for enterprise end users.
Lookup dconf. It’s the tool that manages the underlying configuration engine for Gnome specifically.
Outside of the granularity there, you could also just lock everything to a group and exclude logged in users from that group. That’s a very simplistic way of explaining it, but achieves the exact same thing. You build a base image with only the apps the user needs, set execution to an inclusive group that user belongs to, and everything else to some other groups, and there you go. Dead simple.
Of course that’s not how you’d do it for an org with thousands of users, but you get the point.
Issue is that there’s one thing that organizations love about Windows that isn’t really catered to in any Linux distribution: Nannying the users and not letting them do their own things with their own systems.
For example, no Linux distribution out there will help you prevent the end-users from changing their own desktop wallpaper, or what to show when the user locks their screen. When my company hands out laptops, the users are blocked from changing out the ugly propaganda slides they make our systems display. Just the tip of the iceburg for how much the enduser can be screwed with by a microsoft admin that just isn’t possible in any significant Linux desktop environment.
So user may love Linux, but their employer still wants to make sure they are running Windows.
Uhhhh yeah there is? You can customize any user profile and centrally control it just as you can on Windows. You can even PXE boot all workstations with new images whenever you want instead of relying on individual machines to issue updates, something that Windows isn’t capable of.
Not sure where you got this idea, but you’re misinformed.
You can’t to the same degree. If you let the user use a typical desktop environment like gnome or plasma., then they can set their wallpaper.
Now if you want to make a kiosk thing, so much easier in Linux. But if you want to have a general purpose desktop experience but restrict stupid stuff like wallpaper, windows has got you.
I would rather use and administer Linux systems at scale any day, but if you hated your users and wanted to lock personalization, then Windows has done the work to enable that.
Sorry, ma dude. This is 100% incorrect. Been doing this a long time, and have managed massive numbers of desktop sessions for enterprise end users.
Lookup
dconf. It’s the tool that manages the underlying configuration engine for Gnome specifically.Outside of the granularity there, you could also just lock everything to a group and exclude logged in users from that group. That’s a very simplistic way of explaining it, but achieves the exact same thing. You build a base image with only the apps the user needs, set execution to an inclusive group that user belongs to, and everything else to some other groups, and there you go. Dead simple.
Of course that’s not how you’d do it for an org with thousands of users, but you get the point.