http://www.thatsmyview.net/2009/05/29/using-client-information-in-vmware-view/ Virtualization at a glance Thu, 22 Jul 2010 22:20:13 +0000 hourly 1 http://wordpress.org/?v=3.0 http://www.thatsmyview.net/2009/05/29/using-client-information-in-vmware-view/comment-page-1/#comment-16 Christoph Dommermuth Mon, 08 Jun 2009 07:49:58 +0000 http://www.thatsmyview.net/2009/05/29/using-client-information-in-vmware-view/#comment-16 When they come through another broker (sec server) you could query the environment variable for the broker in your ThinApp script. I would suggest to open a new post in the ThinApp forums to ask if someone already has written a script for that. When they come through another broker (sec server) you could query the environment variable for the broker in your ThinApp script. I would suggest to open a new post in the ThinApp forums to ask if someone already has written a script for that.

]]> http://www.thatsmyview.net/2009/05/29/using-client-information-in-vmware-view/comment-page-1/#comment-13 Shawn Sun, 07 Jun 2009 15:54:00 +0000 http://www.thatsmyview.net/2009/05/29/using-client-information-in-vmware-view/#comment-13 I have a customer who has a (licensing) requirement to make MS Office unavailable to users if they access the desktop from the Internet. Since View makes desktops available on a user entitlement basis, you couldn't just make two versions of a desktop and expect that the user will choose the one without Office when they are remote. My thought was to ThinApp Office but use the information you mention to script the thinreg registration of Office only if a variable was true. The variable would have to be true only if they access the desktops internally. Outside users would be going through the View Security server and internal users would be direct to the View Connection server, so I think this would be possible. What do you think? I am not an experienced coder, so if you felt really charitable, could you share code that could be used in a script? I have a customer who has a (licensing) requirement to make MS Office unavailable to users if they access the desktop from the Internet.
Since View makes desktops available on a user entitlement basis, you couldn’t just make two versions of a desktop and expect that the user will choose the one without Office when they are remote.
My thought was to ThinApp Office but use the information you mention to script the thinreg registration of Office only if a variable was true.
The variable would have to be true only if they access the desktops internally. Outside users would be going through the View Security server and internal users would be direct to the View Connection server, so I think this would be possible. What do you think?
I am not an experienced coder, so if you felt really charitable, could you share code that could be used in a script?

]]>