![]() ![]() I founded my company to use this experience & knowledge to assist companies with their current & new projects. I started as a junior System Engineer in 2005, but over the years, I acquired more knowledge & skills as a DevOps engineer and have in depth knowledge of private, hybrid and public clouds. ![]() I hope this helps! Please leave a comment below if you have questions or remarks.ĪVD Client Cleanup script/tool Recent posts AVD Client Cleanup script/tool OctoMSIX app attach Start Menu fixed in Windows Virtual Desktop Windows Virtual Desktop Workshop December update JanuWindows Virtual Desktop Spring 2020 edition workshop JWindows virtual desktop ARM templates for the Spring 2020 edition JSee more Categories Now, all you need to do is do a GPUpdate on your WVD Sessionhosts & make sure your users do Logoff & Logon again. Then create a new GPO or modify your exising FSLogix profile GPO: Next, store the redirections.xml on a fileshare accessible for the WVD Sessionhosts, for example: \\«yourdomain»\netlogon ( \\cloud-architect.be\NETLOGON) Or add the following lines to your existing redirections.xml file:Ĭreate the FSLogix GPO to enable the redirections.xml.Not exactly quick or friendly, but it is there. Create a new redirections.xml file like this:ĪppData\Local\Packages\_cw5n1h2txyewy\TempState If you click up at the top of you RDP window on the computer icon it will open a drop down where you have the option of Remote commands > Start.To fix the issue, follow these steps: Create or modify redirections.xml This makes sure that FSLogix does not include your Start Menu in your Profile, which gives you a clean Start Menu at logon. To solve the issue, you have to exclude the %localappdata%\packages\_cw5n1h2txyewy\TempState folder and/or the %localappdata%\packages folder. You can exclude specific folders in FSLogix by using the redirections.xml file & the RedirXML file GPO: More info here. This should resolve the issue, but unexpected behaviour can always occur. More specific, the Start Menu Appx Package being cached by FSLogix in the FSLogix profile. Microsoft Support (I can only thank them because the response was quick and to the point, so thank you for that!) told us that there is () an issue with MSIX app attach & FSLogix. Next, go to the Processes tab and find the process of Windows Explorer. Tap the Ctrl + Shift + Esc keys to open the Task Manager. The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager. When removing the profile from a user, the new situation (new application or removed application) did reflect on the user his Start Menu. Option 1 Try to restart the Windows Explorer process. Or, simply go to the Desktop screen by pressing Windows key + D together. It turned out that newly published MSIX app attach applications were not showing in the Start Menu, or that removed applications were not removed from the windows Start Menu. Make sure that all your apps and files are closed. This made us raise an incident with the Microsoft Support, and this could be interesting for a lot of people, so I decided to blog about it □. While I was working on a project which includes MSIX app attach, we were experiencing some issues with applications published to the users using MSIX app attach. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |