Windows Scheduled Task MP now supports localized OS

Having thought about enabling the Scheduled Task Management Pack for non English operating system versions for some time, I finally found the time to update it. The new release (Version works with the following OS languages:

OS Languages Remarks
Windows Server 2008 any .
Windows Server 2003 English,
discovery will not work on other languages


The update is available here: Scheduled Task Management Pack understands 7 languages.

The reason why only 7 languages are currently supported on Server 2003 is that in order to discover and manage the tasks, the output of the ‘schtasks.exe’ command needs to be parsed. That output unfortunately varies between different languages. I decided to include support for those languages I have at least a basic knowledge of (very basic for 3 of them). If you need other languages to be added let me know.

Like a little language quiz? Here’s what Scheduled Tasks are called on other OS languages. Can you tell which expression is in what language?

tareas programadas / geplande taken / operazione pianificata / tâche planifiée  / tarefas agendadas / geplante Tasks

On Windows Server 2008 parsing ‘schtasks.exe’ is not required as Microsoft has included COM object with the OS that allows managing the tasks using scripts and that is language independent.

Many thanks to Romain Girot who’s helped a lot by testing the localization support accurately and patiently.


8 thoughts on “Windows Scheduled Task MP now supports localized OS

  1. You’re welcome, it has been also a pleasure to help you. And when I see the result, it was really worthwhile 😉

    And for the quiz : Spanish / Dutch / Italian / French / Portuguese / Dutglish 😉

  2. Romain, you are a language genious! And you have even spotted the Deutschlish expression. While it is at times near impossible to find god translations for computer terms: I don’t understand why Microsoft didn’t use the perfectly well suited noun Aufgabe here.

  3. Thanks Raphael for a great MP, really helpful, although I did unseal it, set the discoveries as disabled by default, extend the discovery interval and then reseal = selective enabling of discoveries.

    I do however get an identical discovery script errors on several Server 2003 boxes;
    Custom.Windows.ScheduledTask.ServiceDiscovery.vbs(254, 7) Microsoft VBScript runtime error: Subscript out of range: ‘-1’

    Any thoughts on this error?



  4. raphael – my question is nearly identical to the post above. i’m curious if you have any stated guidelines on how to set overrides so that your mp runs for just a group of computers, instead of all windows computers by default?

    much thanks!

    • I haven’t actually but I’ll look into including something with the MP. I am on vacation however so it might well take until mid August before I get to that.

      Until then – go to the Authoring pane, select discoveries. Then set the scope to Scheduled Tasks. You should then see the discoveries as they are described in the MP guide. One is for Windows 2003 and the other one for Windows 2008. Right click them and choose to override for all Windows Server 2003 respectively Server 2008 objects. Deselect the ‘enable’ box and save that override off to an MP of your choice (make sure it isn’t the ‘default MP’).

      Next you will want to remove the scheduled tasks that have already been discovered from SCOM’s repository. To do so start the SCOM Command Console and run the commandlet ‘Remove-DisabledMonitoringObject‘.

      No scheduled tasks should remain in SCOM’s repository now and you can repeat the override procedure to re-enable discovery for groups of computers or individual computers.

  5. Hi, it’s a perfect MP.
    There are two questions.
    1. If I had install PowerShell 2.0 on win2003 server, could I use the win2008 mp for win2003 servers ?
    2. Could you add new language (Tradiction Chinese , Zh_TW) for win2003 server ?
    Locale = “Chinese_Taiwan”
    LCID = “1028”

    • No good news for you there: The latest version of the MP is using the Schedule.Service COM object. It was introduced with Windows 2008 (Task Scheduler 2.0). It will not be available on Windows 2003 even if you had PowerShell installed.
      Also: I can no longer provide any support for the legacy 2003 MP version. Plus adding an extra language always was a lot of work. One I only dared doing in languages I understood myself more or less. With Chinese I would be totally lost, unfortunately.

Leave a Reply

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

You are commenting using your 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