Quantcast
Viewing all articles
Browse latest Browse all 19267

Re: Determine type and version of remote client

That's it, bang on. I've noticed a few things:

 

- I couldn't figure out a way to remotely connect to HKCU, if that's doable at all, never had to do this. The registry keys must be queried locally, under currently logged in user, and will disappear once the user logs off.

 

- I've created a script to run at connection time (and every hour while user is connected) under user context and export all these values to a text file on local machine, so they can be preserved after disconnect and picked up by other scripts doing network inventory overnight. For some reason, in some cases, ViewClient_Broker_DNS_Name isn't exported at all. I end up with 10 values in the text file instead of 11. Not sure why, I thought to mention it in case someone else runs into the same issue.

 

- When a user connects remotely, registry keys are populated. If they disconnect without log off, and then connect from another client to the same session, registry values will not change. You may end up with wrong data. In my test I connected from a Wyse P20 zero client and then from Windows. Registry still said ViewClient_Type was Teradici device, not Windows.

 

 

Thanks


Viewing all articles
Browse latest Browse all 19267

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>