Windows 7 32bit remote registry connection to Server 200x 64bit
We have a tool that runs against our servers registry. When we run this from a Windows 7 box it does not pick up all of the valid registry key entries under the 64bit servers. From our Windows XP 32bit machines this works without any issues and can see all of the correct entries.Thanks
February 16th, 2010 5:50pm

Hi, Is the tool a public product or an internal tool you developed? Do you have this issue on all your Windows 7 PCs? You can use the tool’s name to check if it is Windows 7 Compatible via Windows 7 Compatibility Centerhttp://windows.microsoft.com/en-US/windows7/Make-older-programs-run-in-this-version-of-Windows First of all, please refer the following URL to run this program under Windows XP compatible mode:http://windows.microsoft.com/en-US/windows7/Make-older-programs-run-in-this-version-of-Windows if the issue persists, you should provide more info so others can understand the issue more clear, e.g:1. Name or the tool2. Which type of registry key entries would be missing during query & collect? Did the tool miss random keys entries or constant branch?
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2010 5:57am

The tool is home grown and does have the same issues on other Windows 7 machines. It is missing a consistent keys from a specific branch under the registry, on only 64bit servers whether it is 2003 or 2008 server that does not matter. HLKM>Software>Microsoft>Windows NT>CurrentVersion>WinlogonKeys missing are allocatecdroms/allocatefloppies as examples.Running it under compatibilty mode Windows XP makes no different I think this has to do with Windows 7 32 bit connecting to 64 bit machines via remote registry.
February 17th, 2010 9:32pm

Hi, since this is a self-coding program, it’s really hard to find to root cause of the issue since it’s more coding related. Which type of programming language you are using? You can consider upgrade to the most recently version of the develop tool and use new function/Class supported Windows 7. This type of issue should be addressed in programing support forum such as MSDN:Application Compatibility for Windows Developmenthttp://social.msdn.microsoft.com/Forums/en-US/windowscompatibility/threads/?filter=answered meanwhile, if you would like to have a try, you can run this program in XP Mode as a test, it’s a Windows XP virtual OS other than compatibility mode. I’ve attached the following URLs for your reference: Windows Virtual PChttp://www.microsoft.com/windows/virtual-pc/Windows XP Modehttp://www.microsoft.com/windows/windows-7/features/windows-xp-mode.aspx
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2010 4:35am

No the issue is really with connecting to the remote registry of the server that is 64bit with a 32 bit Windows7 machine. My PC is not -V so the Windows XP mode will not work, thanks for the suggestions. If anyone else has any other suggestions that be much appreciated.
February 26th, 2010 5:56pm

Hi mj, I am experiencing the same issue; currently using VB.Net and when I run the application from a Windows XP all registry keys show just fine, run the application from a Windows 7 (32 Bit) and it can only read the hive + maybe 2 levels... after that it will not read. What is interesting is that I took a Windows 7 (64 Bit) computer, installed the application and voila... works just fine... At the moment we are troubleshooting Windows and User policies, which were (at least up to now) our main suspects. If you find anything, please reply to this post! there is not much out there that talks about this issue. Thank you!
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2010 6:45pm

An update to my earlier post... recreating the exact same behavior as my custom code with regedit I used regedit and connected to remote registry, Keys shown remotely are very different from when I log-on directly to the server... For example: The one I am working with is SQL Server 2005 registry keys (Read Only) Expand: <<ServerName>>\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server When Regedit (remote) expands this key the information is all wrong, some of the keys shown don't even exist when I log on the server itself a run the regedit locally. More specifically... Remote connection shows the following sub-keys: 80 90 BOL Services Local Connection shows: 90 BC ExceptionMessageBox Instance Names MSSQL.1 Services SQLXML4 See the difference? Furthermore, if I select the Microsoft SQL Server Key, the values shown from the remote connection are different from those on the local server. Has anyone come across this issue and found a solution? I've enabled and started Remote Registry service, and followed tips from the following sites to no avail: http://www.computerperformance.co.uk/vista/vista_registry_remote.htm http://www.windowsreference.com/security/how-to-disablerestrict-remote-registry-access-in-windows/ http://support.microsoft.com/default.aspx/kb/314837?p=1
March 31st, 2010 5:57pm

Hello, MSDN content on this http://msdn.microsoft.com/en-us/library/aa384129%28VS.85%29.aspx Also reg.exe has an option to view the other platforms registry remotely 948698 You cannot use the Reg.exe utility to access 64-bit registry keys on a 64-bit computer from a computer that is running a 32-bit version of Windows Server 2003, Windows XP, Windows Server 2008, or Windows Vistahttp://support.microsoft.com/default.aspx?scid=kb;EN-US;948698 Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2010 9:28pm

Thank you Darrell, This information was very useful; We never upgraded to Vista and our Windows XP machines work just fine, so is not until now that we are coming across this issue. The link you provided has information for all platforms except Windows 7 altogether. Do you know how or could provide a link on how to fix a Windows 7 32 bit client reading a 200x x64 bit Server registry? I tried to apply the Vista SP2 fix (just for kicks), but the msi rejected the install... In any case, I am making good use of a reference page that lists all the shared keys, and I am trying to circumvent this problem that way... but what a pain! Thanks again for your help!
April 1st, 2010 10:50pm

Hello Joserami, The update should have been in Windows 7 already so the reg.exe switch should work. So nothing should have to be installed on Windows 7 to get this to work.Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2010 3:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics