Resolving ‘No Programs available from a Terminal Services Session’

Hey all,

  Another SCCM post here.  You’ve probably been in this scenario before:  You have a user complaining that an advertisement doesn’t work from his/her computer and they are being vague about it.  Typically, we would dive in with SCCM Client Center or read the logs (or status messages from a program, more on that in a bit) to determine what went wrong.  

  During the course of your troubleshooting, you may need to see what is happening on this user’s computer, so you Remote in with a tool like LogMeIn ignition or using the Remote Desktop Connection app with the /admin switch (‘MSTSC /ADMIN’).  

  You attempt to launch the advertisement from Run Advertised Programs, but then you see this:

1

 “No Programs available to run from a Terminal Services session”

  What?!  This is actually a strange one.  I’ve been searching around for the real reason behind all this but from what I’ve gathered thus far, SCCM determines the advertisements displayed to a user under RAP based on the user currently connected to the lowest session number.  If one user logs in to a computer another is already logged onto, RAP will lock the other user from launching software installs with this method.  

 Some people will restart the computer to get around this issue, which is a bit of an overreaction.  If you know your command line basics, you can get RAP up and working again in under 20 seconds!

 Lets use the query user command (QUSER, for short) to see if this is the case.

2

 Yep, sure enough, someone else was disconnected when we connected using mstsc /admin.  If we note their session ID (‘1’, in the above screen shot) we can feed this to the logoff command and get rid of their session. 

3

 Logoff is a bit of a laconic application, and performs its work silently.  Lets try refreshing Run Advertised Programs now and see if it works.

4

 

  And now we’re back in the running!  Enjoy, hope this helps you out!

Advertisements

5 thoughts on “Resolving ‘No Programs available from a Terminal Services Session’

  1. Bob Dickert November 14, 2014 / 8:48 pm

    Can you provide any other troubleshooting tips for this behavior? I’ve found several that only have me as being logged in. Thanks in advance. BD

    • FoxDeploy November 14, 2014 / 9:03 pm

      The cause is nearly always related to session count, make sure you’ve got the right session id!

  2. Jared August 8, 2016 / 10:28 am

    In my case, there was only one user signed in. Any updates on other causes of this issue?

    Forced shutdown after running an installation that appeared to fail. (An update to Google Chrome. Most updates managed through SCCM in our environment).

    • FoxDeploy August 8, 2016 / 10:33 am

      Kill exexmgr and restart ccmexec. What happened is you killed the program but sccm still thinks you’re executing, so you should kill the sccm executable manager and force the service to restart

      • Jared August 9, 2016 / 5:53 am

        Thanks @FOXDEPLOY I’ll try that next time we encounter the issue.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s