![]() The Registry provider permits access to the Registry in the same manner as the file system provider permits access to a local disk drive. With Windows PowerShell 2.0 the inclusion of remoting makes it possible to make remote registry changes as easily changing the local registry. Unfortunately, without remoting, you were limited to working with the local computer or using some other remoting mechanism (perhaps a logon script) to make changes on remote systems. In Windows PowerShell 1.0, the Registry provider made it easy to work with the registry on the local system. (There were other ways, but for one coming from a VBScript background, using the WMI classes makes sense.) Understanding the Registry provider This meant that if you wanted to edit the Registry on a remote computer, you might very well end up using the same WMI classes that you used in the VBScript days. In Windows PowerShell 1.0, there was no remoting. You may ask, “Why is Ed talking about remoting when I asked about the Registry?” Well, it is because of the way that you will work with the registry in Windows PowerShell. In fact, you can open a Windows PowerShell console that targets a remote computer, and work as if you were logged on to the console. In Windows PowerShell 2.0, we got true remoting, which makes it easy to run a single command or a series of commands on one or more remote computers. This is a great time to be using Windows PowerShell. Microsoft Scripting Guy, Ed Wilson, is here. Does Windows PowerShell make it easier to edit the registry? In fact, it worked remotely, but it was pretty much a mess. ![]() So here is my question: In the past I used WMI to modify Registry settings. In addition, there are always lots of TechNet articles that talk about changing the registry. Hey, Scripting Guy! I know that I am not supposed to mess around with the Registry on my computer, but the simple fact is that many times there are Registry values that need to be changed. Powerful yet compact (the executable file is only 1.4MB), it's packed with powerful features, and is well worth a place in your portable troubleshooting toolkit.Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use the Windows PowerShell registry provider to simplify access to registry keys and properties. If you're at all unclear about any of these steps then make sure you get yourself some insurance by running System Restore and making regular system backups.įor the most part, though, yaru is an easy way to restore lost Registry keys. If you make a mistake there, restore the wrong Registry keys by accident, then you could make your situation even worse. You shouldn't assume it gives you leeway to freely delete whatever Registry settings you like, for instance - there's no guarantee yaru will be able to recover any particular value.Īnd you also have to be careful in deciding what to restore. You do need to be careful with this technique. If you're 100% sure that you want to do it, though, click "Yes", they'll be imported, and that's it - your lost Registry settings have all been recovered. Windows will warn you that setting a block of Registry keys in this way can be dangerous. With that done, now find and double-click the file you've just saved. And save the results to a file called "recover.reg" (or something similar) on your desktop. Just right-click the top-level lost key and choose the appropriate export option, which will probably be "Export keys to file " this means export everything beneath this level to a Registry file. ![]() If yaru managed to find your lost settings, though, then you'll need to export these in a format which can re-imported into your current Registry. System Restore will restore your entire Registry back to a previous version, for instance, and if you've a full system backup then that may also help. Confirm that you really are looking in the right area of the Registry, and if so then you'll need to look at some other possibility for recovery. If you don't act quickly after deleting a setting then there's a chance it may be overwritten by some other value, and that's what has probably happened here. Open this, browse through what's on offer, and with any luck you'll find your deleted settings. The tree for your chosen section of the Registry should now appear, and at the bottom of this will be a branch called Deleted Keys. To open HKEY_CURRENT_USER, say, click File > Open User Hive (local) and choose your user account to open HKEY_LOCAL_MACHINE\Software click File > Open Software (Local) to open HKEY_LOCAL_MACHINE\System click File > Open System (local), and so on. You won't see any Registry values immediately because yaru works offline, and you'll need to open the relevant hive file first. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |