SCCM2007 Problem opening Task Sequence

[Jensb]

Hello

 

We have a problem at one of our customers with opening several task sequences. When we try to open it for editing we get the error message and the only error in the logs are the ones you see in the images below.

 

So what I can see its some problem with the WMI class called BDD_RunncommandlineAs and I can’t find that class in wmi either on the Central or the Primary site.

 

We also have tried to reinstall the integration features without any luck.

 

The setup is a Sccm2007 with 1 Central site and 1 Primary on the Central site (where all computers are connected to) there is a MDT 2010 installation with integrated features. On the primay there is a MDT 2008 also with integrated features.

 

We can’t export the tasksequence well we can but it becomes 1kb large and only 6 or so lines. But we can create a new one that we can edit and run. And the advertised TS can also be run it is just the editing and exporting that won’t work.

 

If anyone have any idea what this can be or if you need any more info from me to help me don’t hesitate to write.

 

 

With best regards

 

Jens

[Peter33]

That seems to be some pretty old task sequence. I think you need to get a copy of BDD2007 and install it on some computer. Then edit the task sequence and get rid of all the old BDD steps in your TS.

[Jensb]

It has been working up untill march this year and no real Changes has been done to the enviroment, and we cant even open the TS at the moment. Do you Think that installing bdd 2007 on a comp will help with opening the TS ? Oh and the step isnt a bdd step its a simple runcommandline step when I look at the documentation.

[Peter33]

OK, forget about the BDD2007 since it was working already before.

Can you open the TS on one of your servers, central or primary? Since you have different MDT versions installed, i guess you have just upgraded to 2010 and the TS stopped working then? If so, you should be able to open the TS on a computer with MDT2008 integration.

[Jensb]

Sorry no not a easy fix it is the same on both servers, and it is the same if you do it from a client. And no the problem didnt start because of the uppgrade it was done several years ago. I have also checked the wmi for the class but cant find it either on the central or the primary site.