Announcement

Collapse
No announcement yet.

Editing Remote Registries - How

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Editing Remote Registries - How

    Is there any way, using Hyen and a custom tool to be able to right click on a computer and select the tool that will automatically open up regedt32 on the remote computer.

    When I try this it only opens the registry on the local computer.

    Thanks.

  • #2
    Re: Editing Remote Registries - How

    I was just thinking about this today, hopefully someone can help.

    thanks

    Comment


    • #3
      Re: Editing Remote Registries - How

      You can do this by creating a Custom Tool.

      For regedit, you will need the reg.exe program from the NT Resource Kit. You go into Tools>Settings>Tools then click New.

      Type in a caption, and then the command-line will be:

      cmd /C c:\WINNT\system32\reg update HKCU\Software\Microsoft\regedt32\settings\registry =%E% & regedt32.exe

      Then, whenever you want to view the registry for a machine just right-click on that machine select Tools, then the custom tool that you have created, and Hyena will open up the registry for that remote computer.

      Comment


      • #4
        Re: Editing Remote Registries - How

        Perfect - Works like a charm.

        Thanks for the help, yet again.

        Comment


        • #5
          Re: Editing Remote Registries - How

          thanks i tried that, but it still brings up local registry info. I am using windows 2000, could that make a difference.

          Comment


          • #6
            Re: Editing Remote Registries - How

            It should work for 2000 but we haven't done any testing on it. I know there appears to be a problem on XP.

            Go into your registry and see if that key exists, and if so set that value manually to a remote computer, then see if the next time you open regedt32 it opens the remote computer.

            Comment


            • #7
              Re: Editing Remote Registries - How

              I too have tried connecting to remote registry using this custom tool, but it also only opens local registry. Using Win 2000.

              Comment


              • #8
                Re: Editing Remote Registries - How

                This happened to me too. But I copied the wrong reg.exe file. It didn't support the UPDATE option. The file that did not work was dated 9/25/99, 49KB. After I replaced it with the correct one from the resource kit - dated 7/12/98, 55KB it worked fine.

                Comment


                • #9
                  Re: Editing Remote Registries - How

                  Correct - I found this to be the problem to. When I cahnged the file that I was using - No problem. I can edit remote registries withou tnay error.

                  Comment


                  • #10
                    Re: Editing Remote Registries - How

                    Okay, maybe I am missing something big time, not sure. I have Hyena installed on my Win2k Pro PC. I have installed the custom tool, and like others mention, it pulls up the local registy. What do I need to do to get it to work on the Win2k Pro PC, as I can't install NT Resource kit on it. Thanks everyone!

                    [This message has been edited by Pete B (edited 09-20-2002).]

                    Comment


                    • #11
                      Re: Editing Remote Registries - How

                      WooHoo, I got it! Great custom tool, will definitely come in handy!

                      Comment


                      • #12
                        Re: Editing Remote Registries - How

                        I have this custom tool working on Win2000, but it doesn't work on XP Pro. The Registry value was not in the XP Pro registry so I added one and the tool or command line will edit the value, but the regedt32 on XP seems to be ignoring the value. Has anyone else got this working on XP Pro? Is this the correct key for XP Pro.

                        Comment


                        • #13
                          Re: Editing Remote Registries - How

                          On XP create the key/value
                          HKCU\Software\Microsoft\regedt32\settings\registry

                          Reg.exe won't update a value that doesn't exist.
                          Copy the 55k reg.exe and the Windows2000 regedt32.exe to a folder/share and run both from there. N:\Hyena\ in my example.

                          Setup the Custom Tool command:
                          cmd /C N:\Hyena\reg update HKCU\Software\Microsoft\regedt32\settings\registry =%E% & N:\Hyena\regedt32.exe

                          Comment


                          • #14
                            Re: Editing Remote Registries - How

                            XP doesn't seem to offer a way to do this "out of the box". With the registy key drigdon and chuck point out, it only works with the regedt32.exe from Win2k and earlier.

                            If anyone is interested, I have a script that will set this key (without needing the old reg.exe, which, btw, must ALSO be an older version), launch the old regedt32.exe from a specific location, then reset the key (so that when you open regedt32 again, it'll open your registry). It's an easy addition to your Hyena Tools.

                            I haven't dug around, I hope nobody's already posted a script like this and I'm just wasting my fingers typing this...

                            Let me know!

                            Joel

                            Comment


                            • #15
                              Re: Editing Remote Registries - How

                              Now that I finally worked the bugs outta this thing. Talk about a brain far+...

                              '================================================= =========================
                              '
                              ' VBScript Source File -- Created with SAPIEN Technologies PrimalSCRIPT(TM)
                              '
                              ' NAME: Launch Remote RegEdt32.vbs
                              '
                              ' AUTHOR: The Supply Guy (thesupplyguy26*nospamthanx*@yahoo.com)
                              ' DATE : 11/10/2002
                              '
                              ' COMMENT: Launch RegEdt32.exe (older version) from a specific location
                              ' to open a remote registy
                              '
                              '================================================= =========================
                              Option Explicit

                              Dim WshShell : Set WshShell = WScript.CreateObject("WScript.Shell")
                              Dim objArgs, strTargetComp, Root, key1, key2, valname, sregval

                              ' Initialize variables.
                              Root = "HKCU"
                              key1 = "\Software\Microsoft\RegEdt32"
                              key2 = "settings"
                              valname = "Registry"

                              ' --- collect the argument sent ------------------
                              Set objArgs = WScript.Arguments

                              If objArgs.Count >= 1 Then
                              strTargetComp = objArgs(0) ' assign the passed computer name to a variable
                              Else ' quit the script, no variable given, or too many variables passed
                              WScript.Echo("Could not determine the target computer's name, or too many arguments passed to the script. Quitting the script.")
                              WScript.Quit
                              End If

                              ' set the registry key
                              WshShell.RegWrite Root & key1 & key2 & valname, strTargetComp, "REG_SZ"

                              ' run the specific regedt32, waiting for it to return
                              WshShell.Run "c:\Scripts\regedt32.exe",3,True

                              ' pause to give regedt32 time to close
                              WScript.Sleep 2000

                              ' delete the keys to reset
                              WshShell.RegDelete Root & key1 & strTargetComp & ""
                              WshShell.RegDelete Root & key1 & key2 & valname

                              Comment

                              Working...
                              X