Put VBScript into AutoIt Script

[taypatte]

I wrote a VBScript to get the current machine name from SCCM. I need to use the variable that the machine name is in in an AutoIt script because I need to display that name as a label in the GUI. I can't do it all in AutoIt because it doesn't have access to the Microsoft.SMS.TSEnvironment, where the SCCM stuff is stored. I have looked at threads similar to this, but I cannot find a straight answer that works. I am also an AutoIt newbie, so this is beyond my level. Can someone at least steer me in the right direction? I would really appreciate it.

[seadoggie01]

Can you pass it in through the command line? Use your VBScript to call your AutoIt and and get it from $CmdLine[1] or something similar?

If not, write it somewhere, a text file at worst, the registry would likely be best and read it with AutoIt

Edited September 23, 2019 by seadoggie01
Forgot this wasn't StackOverflow, no inline code

[BrewManNH]

Pst your VBScript and your AutoIt script and let us see if the VBScript can be totally translated to AutoIt, more than likely it can be.

[taypatte]

8 hours ago, BrewManNH said:

Pst your VBScript and your AutoIt script and let us see if the VBScript can be totally translated to AutoIt, more than likely it can be.

set oTaskSequence = CreateObject("Microsoft.SMS.TSEnvironment")
computerName = oTaskSequence("_SMSTSMachineName")
WScript.Echo computerName & "=" & oTaskSequence(computerName)

Here is the VBScript. I can't do this in AutoIt because AutoIt cannot access Microsoft.SMS.TSEnvironment.

[JLogan3o13]

Why not? Does this not work?

$oTaskSequence = ObjCreate("Microsoft.SMS.TSEnvironment")

 

[taypatte]

29 minutes ago, JLogan3o13 said:

Why not? Does this not work?

$oTaskSequence = ObjCreate("Microsoft.SMS.TSEnvironment")

 

It does not work. I have tried that and other ways and it seems AutoIt just can't access it for some reason. The problem with that line of code is that it doesn't actually create the object.

[Werty]

try downgrading your autoit installation to version 3.12.0 as there are problems with COM objects in newer autoit versions.

 

/edited for error :/

Edited September 24, 2019 by Werty

[JLogan3o13]

1 hour ago, taypatte said:

The problem with that line of code is that it doesn't actually create the object.

Which is weird, since I wrote the SCCM UDF (admittedly not updated in a couple years now). If I get a chance to get to a machine with SCCM installed, I will take a look.

Edit: Just to clarify what SCCM build are you on?

Edited September 24, 2019 by JLogan3o13

[taypatte]

20 hours ago, JLogan3o13 said:

Which is weird, since I wrote the SCCM UDF (admittedly not updated in a couple years now). If I get a chance to get to a machine with SCCM installed, I will take a look.

Edit: Just to clarify what SCCM build are you on?

Yes it is very weird. I believe I'm on the 1906 build.

[taypatte]

On 9/23/2019 at 2:44 PM, seadoggie01 said:

Can you pass it in through the command line? Use your VBScript to call your AutoIt and and get it from $CmdLine[1] or something similar?

If not, write it somewhere, a text file at worst, the registry would likely be best and read it with AutoIt

Could you elaborate more on how to run it through the command line?

[seadoggie01]

Sure... just have the VBScript run your AutoIt script and pass the computer name as a parameter... like this:

set oTaskSequence = CreateObject("Microsoft.SMS.TSEnvironment")
computerName = oTaskSequence("_SMSTSMachineName")

Set objShell = WScript.CreateObject ("WScript.shell")
objShell.run "myAutoIt.au3 " & computerName
Set objShell = Nothing

Then, in your AutoIt Script, you can retrieve command line parameters with the $CmdLine array...

If UBound($CmdLine) > 1 Then
    Global $computerName = $CmdLine[1]
EndIf

Edit: I'm really fuzzy on VBScript, but I find this site super helpful: SS64.com

Edit 2: I can't test this code, but I think it should work... the Microsoft.SMS.TSEnvironment line throws an error for me.

Edited September 27, 2019 by seadoggie01

[taypatte]

12 minutes ago, seadoggie01 said:

Sure... just have the VBScript run your AutoIt script and pass the computer name as a parameter... like this:

set oTaskSequence = CreateObject("Microsoft.SMS.TSEnvironment")
computerName = oTaskSequence("_SMSTSMachineName")

Set objShell = WScript.CreateObject ("WScript.shell")
objShell.run "myAutoIt.au3 " & computerName
Set objShell = Nothing

Then, in your AutoIt Script, you can retrieve command line parameters with the $CmdLine array...

If UBound($CmdLine) > 1 Then
    Global $computerName = $CmdLine[1]
EndIf

Edit: I'm really fuzzy on VBScript, but I find this site super helpful: SS64.com

Edit 2: I can't test this code, but I think it should work... the Microsoft.SMS.TSEnvironment line throws an error for me.

Thank you! This helps a ton. Yeah, the Microsoft.SMS.TSEnvironment only works inside the task sequence. Also, does the AutoIt script have to be .au3? I think the file I need to use needs to be .exe.

Edited September 27, 2019 by taypatte

[seadoggie01]

No problem, glad to help, even if it's the slightly cheaty way

No, it's better if the file is an exe, then you don't need to worry about executing vs opening the au3 file