"HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\" Registry Entry Not On My Client Machine about rdp-battmon HOT 20 CLOSED

I run as a regular user. Could the domain permissions be denying rdp access unless you elevate your privileges?

from rdp-battmon.

It's hard to say without knowing more detail. What OS version are you on?

You can try enabling logging as described in the README to see if we can get some debug info.

Silly question, but you're definitely using MSTSC.exe and not the new Win 10 RDP app right? Also MSTSC must be running 64-bit. Check the Platform in task manager.

from rdp-battmon.

Hey @transistor1

I figured it out, MSTSC.exe needs to be run as an administrator for whatever reason. Is there any way around this? I have computers on a domain and they do not have the privileges to execute MSTSC.exe as an administrator. I suppose I could enable the local admin account on certain laptops but I rather not if I can avoid it.

from rdp-battmon.

Glad you figured it out. As far as I know, I'm not running as an admin on my machine. I'll double check that when I get a chance. Is there any possibility that running as admin might only need to be done the first time you run it?

from rdp-battmon.

It actually loses connection to the client if I ex out of remote desktop and reconnect without running as administrator. Let me dig a bit deeper into my privileges as a normal user, I may be a bit more restricted than your normal user which is why you are able to execute MTSTC normally.

from rdp-battmon.

from rdp-battmon.

@transistor1 I have debugging enabled, and I moved the log filepath to my BattMon folder. I only get log output when running as admin (when the app is actually working). Otherwise, it seems like BattMon dll doesn't even know that the server application is trying to communicate.

I think it's a user permissions issue. Not sure what exact setting would cause this behavior but I will keep looking. Thanks for your help with this I really appreciate it!

from rdp-battmon.

from rdp-battmon.

@transistor1 Yes I'm sure.

I noticed these computers have TSPrint installed (remote to local printing) which is the same kind of client / server MSTSC setup as your application, so I will look into how that works. Sorry, I just inherited this setup at a new job and I'm not very sure on what setting is enabled/disabled that would restrict this kind of access.

from rdp-battmon.

from rdp-battmon.

@transistor1 Great idea! Looks like MSTSC.EXE can't create or open any registry keys. Let me see if I can modify that and I will report back!

from rdp-battmon.

from rdp-battmon.

273 of them, most in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers

from rdp-battmon.

Interesting. That's not a path that I've explicitly written to. That seems to have something to do with Windows Performance Monitor. Seems unusual. You're getting an Access Denied on those subkeys when filtering ProcMon for MSTSC.exe (and running MSTSC without admin privileges)?

from rdp-battmon.

@transistor1 yes, filtering MSTSC.exe without admin. I think MSTSC.exe may open some registry keys for whatever reason?

from rdp-battmon.

from rdp-battmon.

Oh sorry for the confusion, I 100% think that they are getting access denied even when your plugin isn't running. This issue I believe is solely on my end.

from rdp-battmon.

from rdp-battmon.

@transistor1 guys I apologize I am an idiot!

I was running Regedit as an administrator when I installed BattMon. This created the registry key for the administrator account, not my normal user....

I just ran Regedit as a normal user and noticed BattMon wasn't there, once I installed the reg key it worked fine. In fact even the Terminal Server Client reg key folder was there which was the reason for this whole post.

So I am sorry for this witch-hunt, running Regedit as Admin was my issue here.

from rdp-battmon.

Don't be silly; you are not an idiot in the least!! On the contrary -- this is hard to track down. Thanks for sharing your experience. This will be helpful to others.

If you have time, would you please update the README.md file to note that we should run Regedit as a normal user? If you don't have time, I'll try and get to this later this evening, after work & kids!

from rdp-battmon.