Adding taskpads to MMC getting information from $COL<i> where i>2 RRS feed

  • Question

  • I am writing some scripts to help our servicedesk to some of their tasks, and I wanted to add it as Taskpads in MMC

    What I have done, open MMC, add ADUC . Then create a "taskpad" for an OU, and create a task to do "X", when I choose parameters and for instance choose "Name" it will write  $COL<0> in the parameters input field. That works fine. 

    If I use $COL<1> (type) or $COL<2> (description) it works fine as well, but if I choose for instance "Pre Windows-2000 logon Name" $COL<9>, then the Taskpad task does not show up at all. As soon as I change the parameter from $COL<9> to $COL<0> it shows up again.

    I have tried getting multiple different things from $COL<2+> but they all fail, resulting in the task not showing.

    I have tested this on Windows 8, 8.1, Server 2008R2 all with the behaviour, anyone has a clue as to what is happening ?

    Friday, July 11, 2014 10:25 AM

All replies

  • Hi Claustn,

    Do you follow this article to add RDP taskpad:

    Custom MMC and How to Create Add TaskPad

    If so, the “/v:$COL<0>“ means selected computer name you want to remote cnnoect.

    You can run the cmd like:mstsc.exe /v:"Target computer IP address"

    If I have any misunderstanding, please let me know.

    If you have any feedback on our support, please click here.

    Best Regards,

    Anna Wang

    TechNet Community Support

    Monday, July 14, 2014 5:03 AM
  • I can use $COL<0>,$COL<1>,$COL<2> but if I choose anything else, the task does not show up on the list.

    Say I have a script that takes a username as input,  in the task I click the little arrow and it gives me a bunch of option, where one of them is "pre Windows-2000 account name", I click that and "parameters" textbox gets filled in with $COL<9>.

    So I have a task called Disable user, which takes a username parameter. But when I choose $COL<9> the task is not visible in the taskpad. If I change the parameter to $COL<0> it shows up again.

    Does that make sense ?

    Monday, July 14, 2014 11:23 AM
  • Hi Claustn,

    Would you please post the script to help me to understand, cause I still have no idea of " $COL<0>,$COL<1>,$COL<2>".

    If you have any feedback on our support, please click here.

    Best Regards,

    Anna Wang

    TechNet Community Support

    Thursday, July 17, 2014 8:56 AM
  • I wrote an compiled exe file that takes input from the command line.

    So if you look at a task in the Task Pad, and you choose the Command Line pane

    If you click the little Arrow, you will get a bunch of option.

    Lets say I want to use the "Pre-Windows 2000 Logon Name"

    That results in I will get $COL<9> on the parameters line

    Putting $COL<9> on the paramters line, results in the task not being visible.

    Example 1 (Parameters Line contains $COL<0>, task is called fdffd)

    Example 2 ( (Parameters Line contains $COL<9>(It is the only change made to the task), task is still called fdffd)

    Friday, July 18, 2014 10:56 AM
  • I know this is several years after the fact, but this is the only thread I've seen on this topic/question.  @Claustn... Did you ever figure out what the solution was? I have the exact same issue and there is so little available on the topic. I was rather hoping to add some of my pre-existing PowerShell scripts in Taskpad but they need some of the other variables as you mentioned. In my case, most of my scripts would need $COL<21> which is the users login name (Which I'm assuming is linked to the samaccountname... but that's just a guess)
    Friday, October 11, 2019 7:54 PM