![]() Microsoft have got me doing the following:ĭism /online /cleanup-image /restorehealthĤ- Click on “Hide all Microsoft services”Ĩ- Restart the machine and check whether it’s working or not. In regards to the multiple firewall rules and the cleanup, we did have an alleviation of the problem for a day or two after removing literally thousands of inbound and outbound rules + restarting all application servers affected however the issue has creptīack in and hit us full force as of today. We've tried GPOs to disable it and see the outcome, this is still been tested. Our Engineering team has observed some correlation with "Microsoft Toasts" - when users do have a broken task bar, some do have an Outlook toast which they haven't been able to clear an hour or two before the task bar issue occurred or right before The UPD, remove the ProfileList reg key left behind for the user, make sure the UPD is unmounted from the FS and check if they've logged into another server.) We end up running the fix of restarting Windows Explorer or getting the user to log off, log back in (we drain the server that the user was previously on, remove the mount point left behind from Up on the same server with the same issues after an hour or so. It seems that when User A from Server 1 calls up, there is a 90% chance that another 3 or 4 users will call Some servers we've rolled back the March CU but that hasn't made a difference. We've tried many different avenues, currently do have an MS ticket open. Some servers have almost 20K rules that were removed. Whole Windows Shell crash - cannot click / launch anything on task bar and desktop - full session lock up (where we then have to kill the Windows Login Application process for the affected user to log then off as log off doesn't work / register) Slow logins - we have seen correlation with duplicate firewall rules and have run PS scripts against all our terminal servers to remove duplicate entries + applied the registry fix. MS didĮnd up checking the permissions on the all relevant tile repository folders and did dig around the AppXPackage side. With the Start Menu not launching, this has been a common issue from day dot - we previously did raise a MS ticket on this however didn't get it resolved as MS believed it was environment specific - however as you probably know, this isn't the case. Our Helpdesk is now constantly getting flooded with called regarding: Stuck sessions - UPD left behind after log off, having to clean up in \ProfileList reg key + releasing UPD from FS Start Menu / Task Bar hung - clock frozen - restarting Windows Explorer gets the user going again, icon names and pictures disappear, Windows Peek function also ceases to work. Currently almost all our customers are affected, some ranging from 3 terminal servers to 20. Hosting multiple customers which run Windows Server 2016 terminal servers and file servers which host their UPDs. ![]() Windows Server 2016 Native RDP Farm deployment We did have a patching run which installed the March CU - there may be some correlation with this. We're also currently experiencing this issue with our customers which seems to have started after the. My admin account i ran the commands under is working great.īeware the early published fixes on this, they are apparently not proven (at least we can right click on it and also use the task bar). ![]() We went from a sporadic lockup issue that was hitting one of our 6 servers a day to now all users start menus dont open Get-AppXPackage -AllUsers | Foreach īut now all my users start menus are broken and wont launch at all I have read quite a few posts and I have re-installed the Windows apps with the following PS script: When the user reconnects and gets a new session, the Start Menu and Taskbar will work for several hours before it goes back to the locked state. To logout the user session using Task Manager or to reboot the server. The desktop apps like Microsoft Office will continue to function fine but if you minimize the running apps, the user can not click on the minimized apps as the Taskbar doesn't respond along with the Start Menu. The server is a physical server running a 12core Intel CPU with 32Gb of RAM and an NVME SSD Intel disk. We have 25 RDS CALs and there's normally about 20 users logged into the RDS server. No desktop or Start Menu redirection is setup. We are not using profileĭisks and each user connects to the RDS via our gateway server and their profile is stored locally on the RDS server. ![]() We're running a single RDS setup with Windows Server 2016 Standard and about 2 weeks back we started to experience Windows Start Menu and Taskbar issues where these functions would suddenly stop working for all of the RDS users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |