Make sure they are going to the LANDesk Console Icon and right clicking on it, and choosing "Run as different user" and that they LAUNCH it with the same credentials that they use to LOG into the console
additionally to the good tips of billyc and James, we solved a lot of performance problems with a local LANDesk Console after we add the core(s) and their database server(s) in our local hosts file with shortname (NOT FQDN!)!
I hope LANDesk will change the need to open the local Console with a administrative account...
Installed LDMS 9 SP2 console in a W7 enterprise box with the firewall activated and only default rules. If we log into the W7 box with a local user that belongs to the Local W7 administrators group then LDMS console opens correctly and we have access to all LDMS console funcionalities assigned to the LDMS user. But if we log in Windows 7 box using a normal user that does not belongs to the local administrators group then LDMS console fails to open when trying to connect to the MS SQl 2005 server, with error message : 'Invalid Authorization Specification - Invalid Connection String Attribute'.
Now if we disable the firewall, the same user with no local admin rights can happily open the LDMS console with no problems at all. The firewall rules applied to the W7 box have default rules and both local administrative and non local administrative users share the same rules applied to the firewall.
This issue does not appear in Windows XP machines that uses the same accounts and firewall rules as W7 boxes. We have verified the system as per DOC-8172 and DOC-1105 to no avail. Do we need to follow a specific procedure to open a LDMS 9 Sp2 console in a W7 box with firewall enabled when using a non administrative account?
This king of error ? A way to get arround this, is to check for the following registry entries (here 64bit):
Hope it works....
Strangely enough we don't have some of the registry keys you point out. In spite of so, if we use a local administrative account to log on into W7 workstation (with firewall enabled) we can happily open the LDMS console, but when login on to W7 box (with firewall enabled) with a non local administrative account then the LDMS console fails to open.
Is this second case, we have learned that creating a firewall exception for the "Console.exe" and "runddrviewer.exe" files enables the LDMS console to be opened correctly by using a non local administrative account with the firewall enabled. So for us is more easy to add a GPO firewall rule than to create new registry keys in the W7 box.
But the thing is that we would like to know why the LDMS console behaves differently when launched under a local administrative account than when using a normal user with no administrative rights with firewall enabled.