Hi,

I added one task to run:

Type: Run Command Line

Command Line: cscript c:\windows\system32\slmgr.vbs /ato

Start in: c:\windows\system32

Run this step as the following account: a domain admin account

The image is already having MAK key.

And this is the last task in the task sequence.

The error I am getting is:

CScript Error: Can't find script engine "VBScript" for script "c:\windows\system32\slmgr.vbs".

Because of this error it is not activating the machine. And the task sequence execution aborts with error: Failed to run the action: Activate Windows. Execution has been aborted

Fortunately, this is the last task in TS.

The same task ran successfully in Baremetal Task Sequence and activated the newly installed OS.

Please help.

Regards,

Amit Anand

 

Older Issue:

Initially, I had an image which was not having MAK key. I added two tasks: one for changing the key to MAK key and second to activate windows. There also, the task for changing the key used run successfully all the time, but activate windows task used to give problem (success for some time and failure for some time)

 

• Edited by Amit Anand Tuesday, April 06, 2010 6:50 AM

CScript Error: Can't find script engine "VBScript" for script "c:\windows\system32\slmgr.vbs".

My favorite search engine came back with the following troubleshooting step (re-register vbscript.dll): "regsvr32 /s %SystemRoot%\System32\vbscript.dll"
I don't kow if that will help in your scenario but it's worth trying.

• Proposed as answer by Robinson Zhang Wednesday, April 07, 2010 9:22 AM
• Marked as answer by Eric Zhang CHN Monday, April 19, 2010 3:18 AM

If anyone is struggling with this problem, and is not able to run a script under a given user in a windows 7 task sequence.

Can't find script engine "VBScript" for script. We have had huge problems with this in a standard windows 7 image. Nothing worked! 

We tried to reregister vbscript.dll but to no avail. 

We got it solved after opening a case with Microsoft support. Here is the solution:

"I would suggest you to perform a test with setting this value as 1 before running the script in Task Sequence. You can probably add one more command line before running the Task Sequence with following entry.

 

REG ADD HKLM\SOFTWARE\Microsoft\COM3 /v REGDBVersion /t REG_BINARY /d 010000 /f

 

If this works then probably the solution would be to export the reg key before running the script and set a value as 1 and then again restore it back"

This works for us every time! 

• Proposed as answer by Anders Horgen Sunday, April 24, 2011 9:03 AM