Re: Running a logon script under another account

Just out of curiousity does anyone know a solution for this using WMI?
Reason being is that we would have to rely on the user not doing anything.

"Peter Avalos" <petera@xxxxxxxxxxx> wrote in message
news:%233jI792yFHA.2652@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks, I'll give it a try and let you know how it works out.
>
> I guess this solution depends on the focus being in the password textbox.
>
> "JHP" <goawayspam@xxxxxxx> wrote in message
> news:O$Pp%2332yFHA.2792@xxxxxxxxxxxxxxxxxxxxxxx
>> Not sure if this will work for you, but it's worth a try:
>>
>> Option Explicit
>>
>> Dim objShell
>> Const WindowStyle = 2
>> Const WaitOnReturn = False
>>
>> Set objShell = Wscript.CreateObject("WScript.Shell")
>> objShell.Run "RunAs /user:ACCOUNT@DOMAIN " &_
>> "C:\DIRECTORY\VSSetup.exe""", WindowStyle, WaitOnReturn
>> WScript.Sleep 100
>> objShell.Sendkeys "PASSWORD~"
>> Set objShell = Nothing
>>
>> "Peter Avalos" <petera@xxxxxxxxxxx> wrote in message
>> news:e6hWTT1yFHA.1856@xxxxxxxxxxxxxxxxxxxxxxx
>>> Does anyone know how to run a .vbs logon script under a different
>>> account than the account that's logging in? The reason I need to do
>>> this is that the script installs a software package if it's not already
>>> installed on the machine that the user is logging onto. The Active
>>> Directory Group Policy restricts software installation to domain
>>> administrators, so I wanted to run this script with elevated priviledges
>>> to get around this restriction imposed by the Group Policy. Has anyone
>>> effectively dealt with a similar issue?
>>>
>>> Some background info:
>>> --All client machines are Windows XP Pro
>>> --Main AD Server (Global Catalog) is 2003. Other domain controllers
>>> are 2003 and 2000
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: A8N-SLI LAN1 not working.(solved)
    ... The reason I have always advocate reinstalling windows ... there are versioning problems with these installs. ...
    (alt.comp.periphs.mainboard.asus)
  • Re: $ENV{CONTENT_LENGTH} / STDIN
    ... >> reason for a form in the first place. ... than about every other aspect of writing a script. ... > insecure may be perfect in the lab, but useless in the real world. ... hard-coded validation, rather than hard-coded names. ...
    (comp.lang.perl.misc)
  • Re: Switch between AccessXP and Access2003
    ... The script successfully installs 2003, ... error indicating automationsecurity is not supported. ... Repair on 2003 and keep it installed, then my script will work because it ... Dim PathToMDE ...
    (microsoft.public.access.security)
  • Re: Switch between AccessXP and Access2003
    ... kills the shell, creates an instance of Access, sets its automationsecurity ... The script successfully installs 2003, ... Repair on 2003 and keep it installed, then my script will work because it is ... Dim PathToMDE ...
    (microsoft.public.access.security)
  • Re: Is there a correct place to put javascript within a html file?
    ... The HTML specification tells you where script elements are permitted: ... script files have downloaded and if they're all in the head ... ... like the sensible thing to do; at least there's a reason for it. ... javascript is positioned just before the then the various html ...
    (comp.lang.javascript)