Tasks can be used to start different actions directly from the Service Manager Console without leaving the Console. This indeed makes sense because you can save a lot of time because you do not have to switch between multiple consoles and your desktop. Out of the box you will find a bunch of tasks that are available, but it could make sense to add your own tasks. One task that I’m using a lot is th ability to start the SCCM Remote Control Client directly from the Service Manager Console to connect to other Systems – especially when the Remote Desktop Connection can not be used (Client Computers …).
There are multiple ways to get to the desired solution, I will show a very simple one. So let’s start by creating a new task.
After naming the new task we need to define the target and the Management Pack to store the new task. I choose “Windows Computer” and a Management Pack that stores al of my tasks.
Next we must choose in what categories the task should be visible. Because I wanna see the tasks in almost every menu I’m using, I choose “Configuration Item” and “Work Item”.
No we have to configure the command itself. To start the SCCM Remote Control Client we have to fire up a tool called “rc.exe” from one of the SCCM Servers. We could also copy the tool to a local path, but I will start it directly from the SCCM Server by using a shared folder. You will find the tool on the SCCM Servers at this location –> Program Files (x86)\Microsoft Configuration Manager\AdminUI\bin\I386\rc.exe. For this example i shared the “I386”-folder using the share name “SCCMTools”.
Now we wanna test the new task that should be visible.
When the console opens you must specify the name of the client or server that you want to connect to.
After the user have given the needed permissions (depending on the SCCM remote control configuration), you will get connected to the desktop.
Now have fun by creating your own tasks!
Pingback: Starting the SCCM Remote Control Client from the Service Manager Console, Part 2 (aka “how to dynamically add information to tasks”) | SCSMfaq.ch
Great blog! I have been using it for a ton of research. I am working on the SCCM Remote Control Client from the Console using the parameters below. When I go into an incident that has a CI added to it and click the task I get a new window asking me to enter in the Principle Name even though the CI is already added to the incident. After I type in the name it works without a problem but it is not automatically pulling in the computer principal name. Any ideas on this would be much appreciated. Thanks!
1 $Context/Path[Relationship=’CustomSystem_WorkItem_Library!System.WorkItemRelatesToConfigItem’ TypeConstraint=’CustomMicrosoft_Windows_Library!Microsoft.Windows.Computer’]/Property[Type=’CustomMicrosoft_Windows_Library!Microsoft.Windows.Computer’]/PrincipalName$
Hmm, where did you add the CI? On the General Tab or on the Related Items Tab? Does this make a difference?
I run into the same issue. It does not work for me either. Do you have a solution for this?
This is pretty slick! The problem is that our service desk team (who are using user roles based on advanced operators) are unable to see the task… any ideas?
Sorry for the delayed response. Maybe the User Roles you are talking about does not have access to the task. Please check your User Role configuration.
Pingback: System Center Service Maneger 2010 « Fen-Shu