Knowledge Center

How to determine if a Remote Desktop Session is running as console (session 0)
Technical Articles ID:   KB68446
Last Modified:  12/21/2018


McAfee Vulnerability Manager 7.x


McAfee Vulnerability Manager (MVM) requires that all applications started up during a Remote Desktop Protocol (RDP) session run from the console (session 0). If they do not run from the console, they are started in Microsoft virtual memory space using the Microsoft virtual memory space manager. This can cause performance issues with various MVM components such as FSUpdate.


To determine the session number, use the SET command at the Command prompt.
  1. Click StartRun, type CMD and click Ok.
  2. Type SET and press ENTER.
  3. In the output, locate the SESSIONNAME=<> line.

    This line will list the session as either CONSOLE or RDP#. If either CONSOLE or RDP-Tcp#1 is listed, then you are correctly connected to the console session.

    If RDP-Tcp#<number greater than 1> you must log out of the RDP connection and perform the following steps to log in again:
  4. Click StartRun.
  5. Type MSTSC /console or MSTSC /admin and press ENTER.

    To determine which switch to use, see the Microsoft article at http://blogs.msdn.com/rds/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx
If you are in a command prompt session, confirm that you are connected to the console session. Type the following command and press ENTER:
shadow 0

If you are logged on to the console of the server that is running Terminal Services and you try to shadow another user's session from the console of the computer, you see the following error:
Your session may appear frozen while the remote control approval is being negotiated. Please wait...
Remote Control Failed. Error Code 7050.
Error [7050]:The requested session cannot be controlled remotely.
This may be because the session is disconnected or does not have a user logged on. Also, you cannot control a session remotely from the system console and you cannot remote control your own current session.

If you do not see this error, then you are not connected to the console session. Log out and perform the steps above to connect to the Console session.

Microsoft reference: http://support.microsoft.com/kb/278845 

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.