Troubleshooting Windows Endpoints Reporting to DEX

Users discussed troubleshooting for a Windows endpoint that is reporting to DEX but not allowing remote access or remote shell. Suggestions included checking the event log, running system scripts, and refreshing the shell window. One member shared having a similar issue with a terminal, resolving it by refreshing the shell window.

Read the entire ‘Troubleshooting Windows Endpoints Reporting to DEX’ thread below:

If we have a windows endpoint that’s reporting to DEX but we cannot remote into it or get a remote shell, where’s the best place to start troubleshooting?

this particular machine has/had been working fine with these functions

Check the event log on the target device.

From what i can see from the DEX console, there’s no logs pertaining to the CU. would it matter if the device is in a locked state?

Odd one. Can you run any system scripts?

Currently the machine is inaccessible, locked in an office so i’m not sure how we would know if any scripts actually run. can’t reboot it either from dex

@member We are having the similar Issue

i have even seen this with terminal / shell and yesterday i refreshed the shell window and it could start using it again , today im going to test the same with a remote session , only refresh / reload the Window that you are using for the remote session

Continue reading and comment on the thread ‘Troubleshooting Windows Endpoints Reporting to DEX’.  Not a member? Join Here!