This is how we create the AppMasking rule: The advantage is, that we do not change the original layout file, so that admins can use it. We need a rule to redirect the standard layout xml file to the custom xml file. That’s the first job for FSLogix AppMasking. Now we have a template, but how can we assign it to our users? Place the layout file “LayoutModifications.xml” in the folder Startmenu tiles.Create the subfolders Startmenu\Startmenu tiles.We (meaning my team at S&L) use to name the folder C:\Program Files (x86)\SuL\Citrix Management Tools but you can name it whatever you want. Create a folder on your reference system or golden master in which you put the templates we need.To use this template, follow these steps: Here are the contents of the “LayoutModifications.xml” file: This template also cleans the task bar, which is perfect for our use case. Based on the blog post from my fellow CTA Kasper Johansen, we take a suitable layout.xml file. To achieve this, we need a layout that we use as a template. I recommend removing all the tiles, so that the admin and (or) the user can create their own tiles. To adapt the layout, we need a LayoutModifications.xml file. Normally, new user profiles get the layout from the file “C:\Users\Default\AppData\Local\Microsoft\Windows\Shell\DefaultLayouts.xml” Common start menu folders and items like Administrative Tools, Windows System, etc.OK, let’s start! There are five things we take care of: Of course, there are many others, but I can’t list them all here… ![]() The websites from CTPs Manuel Winkel, James Rankin and James Kindon are really great resources. You’ll find lots of documentation about installing WEM and FSLogix, so I don’t want to go into detail here. We need to install both, the WEM agent and FSLogix AppSuite on a Windows Server 2019, of course we also need a WEM Infrastructure server or the WEM cloud service. Same here for Citrix WEM, it’s included in your license (except standard edition), so give it a try, if you don’t already do so. Even if you don’t use FSLogix profiles yet, you should at least use the great AppMasking feature. I have a script that takes care of some special settings and future updates. I always recommend installing the FSLogix apps these days. So, no additional cost in most cases for third party software. The only tools we need to create a customized start menu are Citrix Workspace Environment Manager (WEM) and Microsoft FSLogix. This one looks so much better, doesn’t it?Īnd this is a what a Win-X menu can look like! It doesn’t take much to create a user (and admin) friendly start menu. ![]() Of course, you can (and should) restrict or block these apps, but why should a user see and access them at all? Customized Start Menu Just think of PowerShell, Computer Management, Administrative Tools, Device Manager, Windows Security, etc. There are a lot of items and links we like to hide from the user. This is what a normal start menu looks like after a user logs on to a Windows Server 2019!Īnd this is what the Win-X menu (right click on start) looks like: So, let’s face the challenge! Default Start Menu In this post, I will show you how to create a start menu for your RDSH users. Unfortunately, Microsoft only offers a few options for making changes to the start menu with standard tools like group policies. Without making any changes, users get a start menu that is fine for administrators, but not for normal users. You all know the challenge on a RDSH Windows Server 2019 to turn the start menu into a suitable start menu for the users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |