Expand Registry Environment Variable Strings on Remote Machine

views:

186

answers:

Expand Registry Environment Variable Strings on Remote Machine

After calling RegConnectRegistry(...) to open the registry on a remote machine, is it not possible to expand environment variables? I have looked at ExpandEnvironmentStrings and ExpandEnvironmentStringsForUser, but that only appears to be useful on the local machine. I think it must be possible considering that RegistryKey.GetValue() in .Net does expand the variables after calling RegistryKey.OpenRemoteBaseKey(), but I need to do this outside of .Net.

Any ideas?

+2 A:

Given that the environment variables running in a given process is based on the currently logged on user, how would you determine the set of environment variables that would be active on the remote machine?

Even if you could read that information (it's in the registry after all), what would you do about processes that change their environment?

Larry Osterman 2010-06-04 23:30:20

I need to expand registry key values under local machine under EventLog to get message resource dll path(s).

Mitch 2010-06-05 23:24:54

Given that the .Net function that does what you want expands environment strings using the current environment variables, couldn't you just call ExpandEnvironmentStrings on the string?

Larry Osterman 2010-06-06 05:48:59

Yeah, you're right. Seeing now that the .Net function only expands based on the current environment that would be the way to go.

Mitch 2010-06-10 05:40:08

Apparently you can use WMI to find this information for the remote machine...

Larry Osterman 2010-06-10 18:14:58

Yeah, I ended up using this query: select windowsdirectory from Win32_OperatingSystem. I only needed to expand %SystemRoot%.

Mitch 2010-06-10 21:43:43

ansaurus

tags:

views:

answers:

Expand Registry Environment Variable Strings on Remote Machine

related questions