
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2011 11:57 PM
I have followed all of the instructions on the site in regards to opening everything up for WMI. I have made sure all the proper services are running. I can even connect to everyones registry remotely in regedit. I have also disabled the firewall on my Windows 7 system and set all sorts of permissions in regards to my WMI and the permissions for the winreg key have been set properly.
Also all these systems pass the Test Connection application in lansweeper, but here is the error log. I also know for a fact that the 3 registry keys I am attempting to scan for are valid on most if not all the systems.
02/01/2011 10:00:44: J39XXXX REGISTRY Access denied
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at LansweeperService.MdlRegistry.LSRegistry(LSWComputer& mycomputer, String section, SqlConnection& sqlcon)
Solved! Go to Solution.
- Labels:
-
General Discussion

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2011 06:48 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2011 01:12 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 06:04 PM
As an example
HKEY_USERS\{SID}\Software\Open Systems\AppName\ClientUpg\Upgrade
SID = S-1-5-21-1292428093-1525645564-3455 (Last user login or scan all user SIDs)
Of course the other alternative is to find out how XP creates their psuedo paths which actually allows the Remote Registry to link to the proper HKEY_Users\{SID} path automatically when a key for the HKEY_CURRENT_USER path is requested.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 05:37 PM
Has lansweeper been tested from a 32bit system like XP vs scanning registry keys on 64bit systems? I am wondering if I would have this same issue if I was to install lansweeper on a 64bit Windows 7 computer.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 05:32 PM
Maybe it's a corrupt wmi repository?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 05:16 PM
This is the VB script I am using to make sure that my computer is indeed allowing my registry paths to be read properly and while it fails for everything related to HKCU on Windows 7 (even though it passes for users logged into XP), the script does pass just fine on the HKLM paths for windows 7.
' Constants (taken from WinReg.h)
'
Const HKEY_CLASSES_ROOT = &H80000000
Const HKEY_CURRENT_USER = &H80000001
Const HKEY_LOCAL_MACHINE = &H80000002
Const HKEY_USERS = &H80000003
' Chose computer name, registry tree and key path
'
strComputer = "MyCOMPUTERName" ' Use . for current machine
hDefKey = HKEY_LOCAL_MACHINE
strKeyPath = "SOFTWARE\Microsoft\Internet Explorer"
' Connect to registry provider on target machine with current user
'
Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
' Try to enum the subkeys of the key path we've chosen. We can't if the key doesn't exist
'
If oReg.EnumKey(hDefKey, strKeyPath, arrSubKeys) = 0 Then
wscript.echo "Key exists!"
Else
wscript.echo "Key does not exists!"
End If

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 04:58 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 01:03 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2011 11:20 AM
pjtech wrote:
the key I am looking for is in HKEY_CURRENT_USER and it would appear that entire path is blocked on Windows 7 but not XP. From the best I can tell the permissions are the same..
HKEY_CURRENT_USER refers to the user doing the scanning (not to the logged on user)
most likely there is no profile for this user on the computer.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2011 10:38 PM
