Console Connect Troubleshooting/FAQs

I started deploying the agent to an Intune Device, but it hasn’t finished. Is there a way to force it to finish?

Because we utilize the Intune Device Agent to deploy Intune related resources, we are at the mercy of the Intune check-in cycle (see Questions with policies and profiles in Microsoft Intune | Microsoft Learn). Because it could take-up to 8 hours for a sync to complete, it is hard to know where it is in the process.

One thing that we have found to help the process is to run the Install Console Connect agent task and then reboot the device. This sort of forces the device to check in to Intune and deploy the agent.

I was connected to a session and someone else connected

At the time of writing, only a single technician can be connected to a device, or a user’s AVD session, at a given time.

If another technician connects, the first technician sees a message like this:

The end user won’t see any change on their end, besides the connected user, but the first technician is not be able to see what is occuring.

If multiple technicians need to see the screen at the same time, you need to use another tool (for example, Microsoft Teams Screen Sharing) to share the screen while one person is connected with Console Connect to make administrative changes.

I just connected to someone’s session, and they didn’t get an authorization prompt first

There are several reasons this could happen.

• You connected to the user’s device before they logged in or unlocked their device

• A previous technician closed the Console Connect browser tab without exiting the session first.

Luckily, the solution to both reasons is the same. If you exit the session and reconnect, the user is prompted to authorize the connection.

Does the session automatically reconnect after the device is rebooted?

Yes. As long as the technician keeps the Console Connect browser tab open, the session automatically reconnects after the user logs back in.

Is there a limit to how long a session can be left open?

No. As long as the session is connected, and the device has access to the internet, the session can remain open.

Can I get unattended access to a device?

Yes and No.

As long as no one is actively logged in, you can access the device without approval.

However, if anyone walks by the device, they see the Console Connect connection dialog box in the bottom right-hand corner of the screen.

Can I record the session?

No. Currently, session recording is not available.

Can I run scripts with Console Connect?

Yes and No.

Yes, you can run PowerShell script files.

No, you cannot run Nerdio Scripted Actions from within the Console Connect Session.

However, you can run them from Nerdio Manager.

Does it support macOS?

No. Currently, Console Connect only supports Windows endpoints. However, you can connect from any modern browser regardless of the underlying OS.

Can I use Console Connect for Non-Nerdio Endpoints?

No. To be able to connect to a device using Console Connect, it needs to be manageable from Nerdio Manager.

Can I get the Console Connect Agent Installer?

Sorry, but no. Due to licensing restrictions, the installer is only able to be deployed using Nerdio Manager.

Are the tasks performed while in session logged?

Currently, no. Any tasks performed during the session are not logged.