• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

passing thin/zero client details to connected OS?

S

shnelson

Limp Gawd
Joined
Feb 10, 2012
Messages
145
Currently, all of my users connect to a vmware linked clone desktop through a samsung zero client. Their profiles are managed through view persona, and it works quite well as far as their desk zero client is concerned.

Now, introduce a handful of conference rooms that I'm aiming to replace physical workstations with thin clients.. allowing the user to connect to their own virtual desktop when hosting a meeting. The problem is expecting the conference room sessions to have different group policy settings than the session the user holds at their own desk - lengthened screensaver timeout to be one example.

Anyone run into this scenario and found a suitable outcome? I'd like to avoid standing up another linked clone pool just for conference rooms, it will add confusion to the end users if they are given the prompt to determine which VM they should log into.

I am thinking WMI filtering on the GPO, maybe try to pull the mac address of the thin client to determine if the setting should apply? Playing around with the WMI Object Browser, I can't find anywhere that this detail might exist...
 
Last edited:
details are usually sent to the Guest OS, if you check the Set command u should see variables that talk about the client that includes the mac address... (Thin clients i know this works with i cannot remember if zeros do the same)
 
Thanks dasaint - that is exactly the level of detail I am looking for.

Further research has taught me that these variables are stored in the registry volatile environment at logon. Though, I haven't found a way to manipulate them through WMI - I was very hopeful I'd find them under root\CIMV2 Win32_Environment but no luck.


I'm not even certain I like the idea of WMI filtering on a GPO since it's so expensive, so I am very open to hearing how anyone else does location based policies for thin/zero clients!
 
You must log in or register to reply here.
Back
Top