Al
Tue May 25 20:00:20 CDT 2004
"BrianEdwardo" <brianedwardo@mail.uophx.edu> wrote in message
news:uh5eP4nQEHA.556@TK2MSFTNGP10.phx.gbl...
> Save this as .wsf file, and then drap and drop your script onto it, this
> will create .vbe file, which is an encrypted vb script. the code cannot be
> seen but windows 2000 and above will process it normally.
Just beware that screnc hacks exist that actually can read your screnc
encoded files.
/Al
> <?xml version="1.0"?>
> <package>
> <comment>
> Encodes a VBS or JS script file with a script file!
>
> For more scripts, visit www.wshscripting.com
> </comment>
> <job id="Encode">
> <reference id="FileSystemObject"
> guid="{420B2830-E718-11CF-893D-00A0C9054228}" version="1.0"/>
> <object id="Encoder" progid="Scripting.Encoder" events="false"/>
> <script id="Encode" language="VBScript">
> <![CDATA[
>
> Option Explicit
>
> Dim fso
> Set fso = WScript.CreateObject("Scripting.FilesystemObject")
>
> Dim argv
> Set argv = WScript.Arguments
>
> Dim SourcePath
> SourcePath = argv(0)
> If SourcePath = "" Then WScript.Quit
>
> Dim szExt, bstrScript, destExt
> Select Case fso.GetExtensionName(SourcePath)
> Case "vbs"
> szExt = ".vbs"
> bstrScript = "VBScript"
> destExt = ".vbe"
> Case "js"
> szExt = ".js"
> bstrScript = "JScript"
> destExt = ".jse"
> Case Else
> MsgBox fso.GetExtensionName(SourcePath) & " files not supported in this
> script."
> WScript.Quit
> End Select
>
> Dim bstrStreamIn
> bstrStreamIn = fso.OpenTextFile(SourcePath, 1).ReadAll
>
> Dim enc, EncodedText
> Set enc = WScript.CreateObject("Scripting.Encoder")
> EncodedText = enc.EncodeScriptFile(szExt, bstrStreamIn, 0, bstrScript)
> Set enc = Nothing
>
> Dim DestPath
> DestPath = Replace(SourcePath, szExt, destExt)
> If Not fso.FileExists(DestPath) Then
> Dim DestFile
> Set DestFile = fso.OpenTextFile(DestPath, 2, true)
> DestFile.Write Left(EncodedText, Len(EncodedText) - 1)
> DestFile.Close
> Set DestFile = Nothing
> End If
>
> Set fso = Nothing
>
> ]]>
> </script>
> </job>
> </package>
>
> --
> BRIAN EDWARDO
> "R Dunn" <q1c2_3m4e5t6a7l8@hotmail.com> wrote in message
> news:OzhLPLnQEHA.3232@TK2MSFTNGP11.phx.gbl...
> > It can be utilized to run at logon - so you could do it either way.
> >
> > The script could easily be modified so as to add whatever executable you
> > wish to perform the runas function...
> >
> > If you decide to look at it, let me know - I'd be glad to help.
> >
> > Rob
> >
> >
> > "E. Heaton" <anonymous@discussions.microsoft.com> wrote in message
> > news:4B92CE41-367A-47FE-9B57-80DE65B602EC@microsoft.com...
> > > Great solution, but it wouldn't have worked for my situation. I looked
> > into PSInfo and PSExec (from SysInternals.com) which is what VBSHF is
> based
> > off of. It requires that the systems be on to apply the fix or update.
> > >
> > > I have roughly 2,500 computers spread accross 5 buildings in a school
> > district, to ensure all machines have the updates applied, I'd rather
they
> > be applied via. a login' script than a remote installation/execution.
> >
> >
>
>