Run as commandline

The situation is as follows :

We have an osd task sequence that runs a specific command line ( a vb script that modifies the ManagedBy attribute in AD ) as a specific user.

Tested with no additional apps deployed, all works fine. We redeploy with the core apps and we recieve an error during the run as specific account command line.

The error is : Cscript error : can’t find script engine “Vbscript” for script “<Full Path to called on vbscript>

Strange because if we run the task sequence without the core apps the step works without any error !

So after some searching we found that the guilty part of software was the Vmware Tools installation.

The installation modified the reg key HKLM\Software\Microsoft\Com3\REGDBVersion from 01 00 00 to 06 00 00.

I found that the key is related to COM+ settings but I did not find any specific explanation about the effect of changing the key.

In our case we modified the key back to the original value after the installation of the Vmware tools and the task sequence runs like a charm.

Success ….


One Response to Run as commandline

  1. Concetta says:

    I became pleased to get this net-site.I wanted to thanks on the time for this excellent learn!

    ! I positively enjoying each little bit of it and We’ve you bookmarked to have a look at new items you weblog post.

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 )

Google+ photo

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


Connecting to %s