Remote registry software

Thank you. Usage of cookies: In order to optimize the website and for continuous improvement vcloud-lab. You agree to the usage of cookies when you continue using this site. Virtual Geek Tales from real IT system administrators world and non-production environment. Powershell: Get registry value data from remote computer October 7, PM.

RegistryHive]::ClassesRoot [Microsoft. RegistryHive]::CurrentUser [Microsoft. RegistryHive]::LocalMachine [Microsoft. RegistryHive]::Users [Microsoft. Posted in Powershell. Important This article contains information about how to modify the registry. Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. Note To remotely edit the registry of a client computer, the following conditions must be true for the client computer and for the host computer: The computers must run the same operating system.

The computers must have the same service pack installed. Note In step 7, you can edit the registry keys because they're now part of the registry of the host computer. In this article. Best practice would be to do as dbeato said and test to determine if it needs to be enabled by disabling it on a small set of PCs and once you are confident that it had no adverse affect, disable it on additional PCs.

Why use it when you can just enable WinRM if it's not already. Use PowerShell Remoting to do all your admin work. I needed it enabled to push Symantec out to the clients, I gather that I can disable it after that. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Accepted Answer. Enabling the Remote Registry Service Go to the services manager.

Add comment. Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk.