Using Run as ... - Page 2
Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: Using Run as ...

  1. #11
    Senior Member
    Join Date
    Oct 2004
    Posts
    183
    Thank you sec_ware but that doesn't work either, whether I try it from Start>Run or a CMD screen.

  2. #12
    Senior Member
    Join Date
    Mar 2004
    Posts
    557
    Hi

    You may have to make sure that Launch folder windows in a separate process is checked.

    Optionally, you may check one of the following two commands:
    Code:
    runas /user:administrator "explorer.exe /e,::{7007ACC7-3202-11D1-AAD2-00805FC1270E}"
    runas /user:administrator "explorer.exe /e,/root,::{7007ACC7-3202-11D1-AAD2-00805FC1270E}"
    This works on different versions of XP, XP SP1 and XP SP2.
    Otherwise, there may be something custom on your box
    (any particular group policies etc...)?

    Cheers
    If the only tool you have is a hammer, you tend to see every problem as a nail.
    (Abraham Maslow, Psychologist, 1908-70)

  3. #13
    Senior Member
    Join Date
    Oct 2004
    Posts
    183
    Hi sec_ware

    No joy, I'm afraid. I made sure that Launch folder windows in a separate process is checked. None of the commands works for me, either from Start>Run or a CMD screen. I'm not connected to a domain (and never have been).

    I might have to concede that I'm not going to be able to do this!

    As a matter of interest, I came across something similar(http://www.autoitscript.com/forum/in...de=linearplus). The final contributor mentioned that the explicit path has to be given using CLSIDs. I've not been able to get this to work either.

  4. #14
    Senior Member
    Join Date
    Mar 2004
    Posts
    557
    Hi

    I start to take this personally

    Since the junction point in discussion is a subfolder of the desktop,
    I don't think that the full path solves the problem. Anyway, try
    using explorer.exe rather than iexplorer.exe, with/without /n,/e,/root
    (I am guessing...)

    Code:
    runas /user:administrator "c:\windows\explorer.exe /n,/e,/root,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{7007ACC7-3202-11D1-AAD2-00805FC1270E}"
    Note:[1]
    {20D04FE0-3AEA-1069-A2D8-08002B30309D} = My Computer
    {21EC2020-3AEA-1069-A2DD-08002B30309D} = Control Panel


    If this does not work, try a vbs-script (runas /user:administrator "wscript.exe c:\test.vbs"), like
    Code:
    Set oShell = WScript.CreateObject("WScript.Shell")
    oShell.Run "c:\windows\explorer.exe /n,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{7007ACC7-3202-11D1-AAD2-00805FC1270E}"

    If one of them works, we will try understand why ...

    Cheers

    /edit: if none of them worked, try to start explorer.exe as administrator
    (runas /user:administrator c:\windows\explorer.exe), then fill the
    address bar with ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{7007ACC7-3202-11D1-AAD2-00805FC1270E}


    [1] http://www.autohotkey.com/docs/misc/CLSID-List.htm
    Last edited by sec_ware; January 15th, 2008 at 05:04 PM.
    If the only tool you have is a hammer, you tend to see every problem as a nail.
    (Abraham Maslow, Psychologist, 1908-70)

  5. #15
    Senior Member
    Join Date
    Oct 2004
    Posts
    183
    Thanks sec_ware for your patience with this!

    Some progress, at last. When I killed explorer and restarted it as administrator, your previous suggestions for opening Network Connections (and their properties) worked as they should. Needless to say, the desktop changed to that of the administrator and all open applications disappeared until I killed explorer and restarted it as the user with limited rights. It's a bit fiddly, but a lot quicker that formally logging out and logging back in with admin rights.

    I recall reading something a while ago about the way that explorer runs and that may be relevant. I was less experienced (and willing to experiment!) then so I can't recall details - it went way over my head. I just wonder exactly WHY this behaviour is exhibited only with Network Connections. I guess that we, mere mortals, will never know the thought processes of the MS planners!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

 Security News

     Patches

       Security Trends

         How-To

           Buying Guides