captore.blogg.se

#WINDOWS 10 START MENU NOT OPENING CONTEXT MENU NOT OPENING HOW TO#
#WINDOWS 10 START MENU NOT OPENING CONTEXT MENU NOT OPENING WINDOWS 10#
#WINDOWS 10 START MENU NOT OPENING CONTEXT MENU NOT OPENING WINDOWS#

Using AppMasking rules, we can create the perfect junk-free Start Menu with simplicity and ease, also allowing for an immediate rollback of any changes should things go pear-shaped, reverting the user profile and OS itself to an unaltered state in no time. Enter FSLogix AppMasking to once again simply my life. Results are grand (and by grand I mean simple) but it’s complex to achieve what should be simple, and admittedly some components are intrusive and there is no easy way to come back from the changes that get made.

A custom Start Layout to handle the user experience in relation to tiles as a baseline and sometimes for ongoing control.

Remove the WinX menu’s that are not relevant for users in a shared hosted environment, once again typically handled by WEM or GPP.

This has typically been handled by the likes of Citrix Workspace Environment Management or Group Policy Preferences

Remove junk from the user profile once created (sourced from the default user profile).

Typically, I have driven this via Group Policy What they can’t read they can’t see, and thus we non-intrusively remove junk the users start menu.

Remove user permissions from the unwanted junk in the “common start menu” directories.

I have a process that I use consistently with success and have been more than happy with the results, however it required a few moving parts to achieve my simple requirements as outlined below:

windows-10-start-menu-custom-folders-and-shortcut-aggregation.

modern-start-menu-management-and-windows-toolbars.

selective-control-of-the-immersive-control-panel-settings-in-server-2016.

windows-10-start-menu-declutter-the-default.

citrix-wem-modern-start-menus-and-tiles.

customizing-the-windows-10-start-menu-part-ii-what-to-do-post-deployment.

customizing-the-windows-10-start-menu-to-enable-better-control-better-experience.

I also had a conversation recently with CTP legend Dave Brett who was discussing how he and his team had been able to completely change their whole strategy of application and desktop publishing based on App Masking everything that turned up….which I tend to now agree with 100% and initially got me thinking about the below… Traditionally Handling the Start Menu Funįor years I have been hunting down and ranting on about all sorts of different ways to handle the Start Menu, from Tile management to custom toolbars, WEM and simply stripping it all out:

Just as I was going to post this write-up, the man himself decided to post his own guide on how to achieve the same thing, so I am going to restrict this post to focus on the default Start Menu. I am hoping this is one of those James Rankin “final say” style blog posts where I can put this bad boy to bed because I am pretty sure I have my silver bullet to providing a nice start menu environment consistently and efficiently.

I will test this with Windalso and provide the infos.Back again banting on about the Windows Start Menu (surprised?). So I ended up with running a script in user policy, which restarts the explorer 15 seconds after login. Several people had similar problems and provided some fixes, but none of them helped me with this problem. I also opened a thread in Microsoft technet forums. I had a Ticket open with Citrix, but they could not help. I'm not roaming AppData\Local\microsoft\. This doesn't happen when using windows profiles. This only happens if I implement profile management. Have any of you opened a ticket with Citrix. It's really frustrating because I want to take this to production! I've rebuilt my test environment and it happens every single time. I didn't think to restart explorer which does fix it. When the start menu won't come up at all I can right click on it but I cannot right click any icons pinned or open on the taskbar. It's not every time and the start menu will go from no icons, to only some UWP icons to not working at all.

I just started a project trying to get profile management in place using WEM and this keeps happening to my Windows 10 VDA's.

#WINDOWS 10 START MENU NOT OPENING CONTEXT MENU NOT OPENING HOW TO#

#WINDOWS 10 START MENU NOT OPENING CONTEXT MENU NOT OPENING WINDOWS#

#WINDOWS 10 START MENU NOT OPENING CONTEXT MENU NOT OPENING WINDOWS 10#