OpenRemoteBaseKey Method OpenRemoteBaseKey Method. OpenRemoteBaseKey Method. I was laid off for a while and have really gotten rusty on my skills with Powershell. At Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName) It seems pretty clear that this is because the user I'm running the powershell script as doesn't have the appropriate credentials to access the remote registry.

In common terms, you need to supply the credentials any period you're carrying out a information pull from the remote control device. When you're manipulating information that you currently have got from the data draw, you wear't need to perform anything special. In your very first instance, you pass the creds when you make the WMI call - you make use of WMI to obtain a collection of items about the remote control machine. After that, you put on't need creds because you currently have got all the information in regional items.

The second example can be a little trickier. Mainly because very much as I can tell, the.Internet class you're using, Win32.RegistryKey, doesn'testosterone levels have any conditions for impersonating another account.

Obtaining a remote control registry hive will be unfortunately quite difficult from what I've noticed in my very own lookups on the subject previously. Do you possess PowerShell Sixth is v2 set up on both the nearby and remote control devices? If therefore, this becomes much less complicated. You can make a script block of PowerShell instructions and after that they will run on the remote control device, as if ran in your area.

In your case you might have got something identical to this. In general conditions, you need to provide the credentials any time you're also performing a data draw from the remote machine. When you're manipulating information that you already possess from the information draw, you don't want to perform anything specific. In your very first illustration, you pass the creds when you make the WMI call - you make use of WMI to get a collection of objects about the remote machine. After that, you wear't want creds because you currently have got all the data in regional objects.

The 2nd example is certainly a little trickier. As very much as I can inform, the.NET course you're using, Get32.RegistryKey, doesn'testosterone levels possess any procedures for impersonating another account. Obtaining a remote registry hive can be unfortunately pretty difficult from what I've observed in my very own lookups on the topic previously. Do you have PowerShell V2 installed on both the regional and remote machines? If so, this will become much easier. You can create a script mass of PowerShell instructions and after that they will run on the remote control device, as if ran locally. In your situation you might have something comparable to this.

Hi Ed, I know this is certainly heading to become a n00b issue (but we all have to begin somewhere, and I'meters overly careful when enjoying with the régistry)) I ahve á quantity of remote devices where I have to edit the exact same key but each with a various value. As it will nearly all most likely NOT be me running it all the time (devolving obligation to the HeIldesk Oops HELPDesk), whát I would like them to end up being capable to perform is usually something like; d:>repair NBK1234 22029 Where NBK1234 is the device AD title, and the number following is the mobile phone extension for their VoIP cell phone. We have to upgrade this whenever a device is replaced or reimaged.

Any suggestions would end up being greatly valued (and of course I'll have to write the appropriate mistake checking and back-up routines around it).