![]() We're using a couple of Linksys Wireless Access Points (Linksys Opens a new window) for our internal wireless network.I noticed the other day that although we're running the latest firmware, that firmware was released in Dec 2018 - getting on for 5 years. No updates to firmware - concerning? Networking.The only ones remoting into the host is myself from 2 machines and our MSP. host is Server 2016 (Dell PowerEdge720?) running 13 VMs with Hyper-V, 2 VMs are RDS servers, 1 VM is RDS gateway/broker. **related side note, this is happening on my server host, not in RDS. Only one I found was for Server 2012 and that doesn't work on 2016. The strange thing for me was, it only killed the processes for the ghost logons I had to close and reopen taskmgr before all those ghost accounts disappeared.ĭoes anyone know how to PREVENT this from happening? I tried finding a patch for Server 2016, but there doesn't seem to be one. just check the box next to "LogonUI.exe (PID:xxxxx)" and click "End process" and it kills it. I was doing it with Process Explorer, but decided to give it a shot from taskmgr and it worked. but I also discovered that if you're already logged in as administrator, you can kill the process in the "Analyze wait chain" screen. We don't use user profile disks so it's not that. When it happens, the server is brutally slow, strangely nothing is spiked when it happens either (cpu, mem, disk). I have this issue on 3 Session Host servers, randomly. After that is done the ghostuserlogon will be killed without a reboot Search for the corresponding svchost PID en kill the process. Use Process explorer (sysinternals) and run it as admin. Unfortunately, you can't kill the svchost PID with taskmgr. There you will see a svchost proces with a particular PID. Rightclick winlogon.exe en select "analyze wait chain " You will go to the winlogon.exe proces in the detail tab for this user. Go to users > expand (4) user proceses en rightclick "Windows logon application" > select "go to details" Logon to the RDSH where the ghostuser (4) is happening and start taskmgr It's a bit dirty but in my case its working. I have found a workarround to kill/logoff this mysterious (4) user session without having to perform a reboot. When the user is stuck in the logoff process we see these (4) ghostusers appear. In our environment it happens randomly and we see a lot of 6006 eventID's in our application log with very slow logoff times (hundreds of seconds). I still don't know what is causing this issue, but it seems related to using User Profile disks which we use. You'll need this later.We also have this annoying thing happening to our servers. Make note of the name of this PC under How to connect to this PC. When you're ready, select Start > Settings > System > Remote Desktop, and turn on Enable Remote Desktop. To check this, go to Start > Settings > System > About and look for Edition. For info on how to get Windows 10 Pro, go to Upgrade Windows 10 Home to Windows 10 Pro. Select the remote PC name that you added, and then wait for the connection to complete. On your Windows, Android, or iOS device: Open the Remote Desktop app (available for free from Microsoft Store, Google Play, and the Mac App Store), and add the name of the PC that you want to connect to (from Step 1). In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect. On your local Windows PC: In the search box on the taskbar, type Remote Desktop Connection, and then select Remote Desktop Connection. Use Remote Desktop to connect to the PC you set up: ![]() Make note of the name of this PC under PC name. Then, under System, select Remote Desktop, set Remote Desktop to On, and then select Confirm. When you're ready, select Start, and open Settings. Then, under System, select About, and under Windows specifications, look for Edition. For info on how to get Windows 11 Pro, go to Upgrade Windows Home to Windows Pro. To check this, select Start, and open Settings. Set up the PC you want to connect to so it allows remote connections:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |