Registry reporting problem

[Guest]

First of all please accept my ignorance as I'm new to Hyena & Exporter Pro. I'm using v6.6"B" of Hyena & v1.8.2 of Exporter Pro.

I'm trying to list all of the string values for the following Registry Key "HKCUSoftware\Microsoft\Office\11.0\Common\General " on all PC's in a particular OU.
The report contacts all of the machines successfully but doesn't list all of the string values that are actually in the registry. The particular one i'm after "SharedTemplates" is one of those not listed!

I've set the Registry Export Template Properties to the following;
Registry Key Paths=HKCU\Software\Microsoft\Office\11.0\Common\G eneral

Registry Value Names= %OBJECT_NAME%, %KEY_PATH%, %VALUE_NAME%, %VALUE%

I'm obviously missing something with this setup but I haven't found out what yet!!

Any help with this would be hugely appreciated.

[cmccullough]

Re: Registry reporting problem

Are you getting any data from this registry location? If so, what is being returned?

[Guest]

Re: Registry reporting problem

I'm getting 17 values returned but on most of the PC's there are 26 strings so it's not retrieving them all.

[cmccullough]

Re: Registry reporting problem

Send the following screen shots to [email protected]:

1. Your registry template in Exporter Pro
2. The registry keys you are trying to export from regedt32.exe or Hyena

[kstanush]

Re: Registry reporting problem

Look at the datatype for one of the missing values, and let us know what it is.

[kstanush]

Re: Registry reporting problem

I think you are running into a limitation or perhaps a bug in Windows. When you remotely access a computer, Hkey_current_user might not be what Windows expects it to be. You might be accessing the hive of yourself instead of the currently logged on user. Microsoft's documentation does not show any problems with doing this, but I know we modified Hyena awhile back to prevent accessing HKCU remotely because Windows would present the information for any user is wanted to.

I don't know of a workaround for this, as its usually impossible to get this information from HKEY_USERS.

You might be able to duplicate this problem by using regedit or regedt32 on a remote computer and attempting to access HKEY_CURRENT_USER, and compare the values to what you see if you have a way to access a remote session on the same computer.

[This message has been edited by kstanush (edited 02-28-2006).]

[Guest]

Re: Registry reporting problem

As a workaround is it possible to extract the whole HKU hive? I could then sort the data in something like Access. I've tried using HKU\* as the Registry Key Path but that hasn't worked.

[kstanush]

Re: Registry reporting problem

Right now, you can't do this, but I've modified the beta for Exporter Pro v2.0 to do this. The problem now is that you have to supply a key or the OK button won't enable itself; this was easy to fix.

The bigger problem was that EP was not designed to traverse through all registry subkeys under a key, which has been changed.

I should have a new version available to test by the end of next week. To join the beta list, send a blank email to [email protected]

Thanks