Hey Guys, just new to LANDesk here. Trying to login to the 8.8 console on vista. I get the following error "Requested registry access is not allowed." What security settings do I need to change to grant access?
Add the group LANDesk Management Suite, with full access permission to the key :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg on the core
I have the same issue, so I take the chance to reply. the group LANDesk Management Suite is already in the permisson of the folder " winreg " with full acces but
it wont open it, same error message " Console Initialization error - Requested regitry access is not allowed ". I'm running a vista business 32 bits without sp1.
Work fine with an xpsp2
The permission added to the winreg key depends on your right to authenticate to the core server over the LAN. The username and password you use to log into Windows will be passed when attempting to access the remote registry. You can check if you have rights to the remote registry by doing the following:
1) On the computer you are trying to use the remote console go to Start | Run: Regedit 2) Go to File | Connect Network Registry... 3) Enter the host name of the core servr and click OK 4) Try to Open HKEY_LOCAL_MACHINE on the remote registry.
If you receive an error then the user that you are logged into Microsoft Windows as does not have permission on the core server.
BTW this solution works even when your "civilian" account is just given read access to the key Ty mentioned. I have the console loaded up and running on my Windows 7 box at the moment.
How did you get the console to install on Windows 7. I have the 64 bit version. When I try to run it I get the compatibility error.
I should have specified, It works on 32 bit but it freaks out on 64 bit. Until a 64 bit client is built you will be stuck running it on a 32 bit box or run it from Virtual XP.
Before I got it to work, I had it running on a virtual XP installation and it ran OK. Just after a month and a half or even two months can't remember which the virtual machine started to get a little wiggy. In the end I would have to open up the image, start it, login, close it then start the virtual application. But then again the box I ran it off of was a laptop and it was being shutdown and restarted daily.