[THIN] Re: MetaFrame 3 Bug (feature)
- From: "Landin, Mark" <Mark.Landin@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Wed, 2 Mar 2005 13:39:39 -0600
There isn't.
What I've done is write and publish a wrapper script that checks for the
existence of some control file. If the file doesn't exist (or does
exist, the paradigm is up to you) then the script launches the
application as normal. If the file does exist, then script exits without
launching the app. I also have another published script that builds or
deletes the control file, so disabling or enabling an app is simple and
immediate.
Of course, disabling an app does not do anything to anyone already
running the app, nor is this approach possible if you are publishing
desktops without a lot more work on your part (you must make sure they
can't bypass the control script and launch the app themselves).
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
Sent: Wednesday, March 02, 2005 1:25 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MetaFrame 3 Bug (feature)
Not that I know of. It shouldn't be too difficult to create a
script that does just that.
Joe
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jensen, Jay
Sent: Wednesday, March 02, 2005 10:38 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: MetaFrame 3 Bug (feature)
On the same thought process, is there a command line that will
enable/disable logon to a published application?
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg
Sent: Wednesday, March 02, 2005 10:23 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MetaFrame 3 Bug (feature)
Joe,
Does putting that command before shut down override the IMA
value which re-disables logon?
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd. suite D8453
Scottsdale, AZ 85262
(602) 432-8649
(602) 296-0411 fax
steveg@xxxxxxxxxxxxxx
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
Sent: Wednesday, March 02, 2005 9:07 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MetaFrame 3 Bug (feature)
I thought about that but the customer is using softgrid and
there is a significant delay between when the shutdown/restart command
is sent and when softgrid actually restarts the server (The softgrid
client intercepts logoff/shutdown/restart commands). Some of the
softgrid client values can be tweaked, but only little.
Joe
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Landin, Mark
Sent: Tuesday, March 01, 2005 12:01 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MetaFrame 3 Bug (feature)
Not that I know of.
I just put a "change logon /enable" at the end of my reboot
script, immediately before the tsshutdn command. That's all I could
think of.
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
Sent: Tuesday, March 01, 2005 12:54 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] MetaFrame 3 Bug (feature)
Does anyone know how to disable the stupid 'Disable
logons' that survives a reboot feature that Citrix implemented? Adding
a chglogon /enable to the startup script doesn't always work as IMA
service may start after the startup script has executed.
Other related posts:
