It's a very common practice for System administrators to disconnect the active session and reconnect it using 'mstsc' command. By doing this, many sessions can get activated in the background. It happens especially when there are couple of administrators for single server.
If you attempted to perform SEPM upgrade when another Symantec Endpoint Protection Manager(SEPM) session is running in the background, you may get the following error message:
"The installation cannot finish because it detected that one or more SEPM apps were running"
Even can get following error message "To install the Symantec Endpoint Protection Manager from a remote desktop connection, the remote desktop connection must be session 0. You are currently running a differernt session. You can change you current session to session 0".
Check the screenshot for more details
All the active sessions will be disconnected once the System reboots. But, it is not a practical solution when you use a critical server.
A better solution is to logoff that session.
Check this screenshot for your` reference.
You should connect to the '0' session to continue with the upgrade process.
1) To connect '0' session, start the Task Manager and select the Users tab.The 'Users' tab shows all the active connections. The following screenshot shows two active sessions listed with the Server:
In the 'Users' tab all the active connections will be listed.
Right-click on ID-0 and select Connect. It will connect to particular session.
3) Right-click on the other session & select Log Off. You can thus close the active sessions one by one.
Sometimes, the session 0 may not be available. In that case, you need to initiate a new session:
- Click the Start button and then click Run.
- Type the following and click OK.
This should take you to the 0 session.
Please note that in Windows Server 2003, you can start the RDC client (Mstsc.exe) by using the /console or /admin switch to remotely connect to the physical console session on the server (also known as session ID=0). However, in Windows Server 2008 or Windows Server 2008 R2, the /console switch has been deprecated. In Windows Server 2008 and Windows Server 2008 R2, session 0 is a non-interactive session that is reserved for services.
For more information, please visit the following Microsoft article: http://support.microsoft.com/kb/947723
Screenshot for the reference:
You can use the new /admin switch to remotely connect to a Windows Server 2008-based server for administrative purposes. The /admin switch is introduced in RDC 6.1 so included in the following operating systems:
- Windows Server 2008
- Windows Server 2008 R2
- Windows Vista Service Pack 1 (SP1)
- Windows XP Service Pack 3 (SP3)
Also can verify sesion 0 using command prompt.
To ensure that you are on the console (Session ID=0) of the server, please run the command "query session" from a Command Prompt.
If you get an error message like "Symantec Endpoint Protection Manager upgrade rolls back: "SESM CA: files still locked...sleeping 1 second"
Refer the steps suggested above or you can go through the following Symantec KB article.
I hope it's informative.