Your company runs Remote Desktop Services.
You plan to install an application update for the lobapp.exe application on the Remote Desktop Session Host Server.
You find instances of the lobapp.exe processes left behind by users who have disconnected.
You need to terminate all instances of the lobapp.exe processes so that you can perform an application update.
What are two possible ways to achieve this goal? (Each correct answer presents a complete solution. Choose two.)
A. Run the Get-Process cmdlet on the Remote Desktop Session Host Server.
B. Run the Tskill lobapp /a command on the Remote Desktop Session Host Server.
C. End all instances of lobapp.exe in the Remote Desktop Services Manager console.
D. Run the Tasklist /fi "IMAGENAME eq lobapp.exe" command on the Remote Desktop Session Host Server.
Correct Answer: BC
Explanation/Reference:
Good Awnsers:
Tskill lobapp /a
tskill {<ProcessID> | <ProcessName>} [/server:<ServerName>] [/id:<SessionID> | /a] [/v]
Source: http://technet.microsoft.com/en-us/library/cc753101(WS.10).aspx
Remote Desktop Services Manager:
Wrong Awnsers:
Tasklist
Displays a list of currently running processes on the local computer or on a remote computer. Tasklist replaces the tlist tool.
Source: http://technet.microsoft.com/en-us/library/cc730909(WS.10).aspx
Get-Process
Although the following will work for a single instance:
(Get-Process lobapp).Kill()
This will not work on multiple instances:
(Get-Process lobapp).Kill()
But one could argue that using the ForEach-Object commandlet circumvents the issue:
(Get-Process lobapp)|ForEach-Object {$_.Kill()}
However because this requires more than just the Get-Process cmdlet, I choose to render this answer invalid.
