[THIN] Re: MFCom script for Published Desktop/Published App
- From: "Andrew Wood" <andrew.wood@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 29 Apr 2005 14:21:51 +0100
no no no no thats not a solution its far too easy ...
<wanders off to find a wall to hit head off>
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Raffensberger, Stephen
Sent: 29 April 2005 14:11
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MFCom script for Published Desktop/Published App
I'm still an old, simple cmd scripter. (Okay, really old.)
In a cmd file, you could do a "query process" and pipe the output to 'find
"explorer.exe"'. If it's successful, you have a desktop.
Steve Raffensberger
Sovereign Bank
Network Operations
Phone: (610)208-6351
Email: sraffens@xxxxxxxxxxxxxxxxx
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Andrew Wood
Sent: Friday, April 29, 2005 9:02 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] MFCom script for Published Desktop/Published App
We're working on a script as we need to determine at logon whether the user
is running a published desktop or a published application.
We've an MFCOM vb script as follows:
-----------------
Set objShell = Wscript.CreateObject("Wscript.Shell")
Set objFarm = CreateObject("MetaFrameCOM.MetaFrameFarm")
objFarm.Initialize 1
For Each objSession In objFarm.Sessions
If objSession.SessionName =
objShell.ExpandEnvironmentStrings("%SessionName%") Then
MsgBox(objSession.AppName)
End If
Next
-----------------
However for this to work the user needs to be a MF Administrator with this
custom permission Applications | Sessions | View Session Management...which
is less than desirable..
Does anybody know any other way of distinguishing between a published
desktop and a published application at logon in a user context?
tia
----------------------------------
Andrew Wood
Sunderland
United Kingdom
This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee),
you may not use, copy or disclose to anyone the message or any information
contained in the message. If you have received the message in error, please
advise the sender by reply e-mail, and delete or destroy the message.
Thank you.
- References:
- [THIN] Re: MFCom script for Published Desktop/Published App
- From: Raffensberger, Stephen
Other related posts:
- » [THIN] MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- » [THIN] Re: MFCom script for Published Desktop/Published App
- [THIN] Re: MFCom script for Published Desktop/Published App
- From: Raffensberger, Stephen