[THIN] Re: Published applications in a mixed OS environment
- From: "Rick Mack" <ulrich.mack@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 13 Nov 2008 19:30:25 +1000
Hi,
Kixstart is brilliant but seeing as Citrix use ctxhide to hide usrlogon.cmd
so there's no reason that couldn't be used to hide any other batch file.
regards,
Rick
--
Ulrich Mack
Quest Software
Provision Networks Division
On Wed, Nov 12, 2008 at 4:08 AM, TSguy92 Lan <tsguy92@xxxxxxxxx> wrote:
> My work around for launching CMD files / custom scripts for starting
> published apps is to use Kix as the app execution script engine.
>
> www.kixtart.org
>
> Very robust scripting language that you can generally port DOS commands
> directly into.
>
> So, the Pub App calls a CMD / BAT file which then calls to the KIX script.
> Just in case you can also flag the console to hide within Kix.
>
> Since you already have the logic worked out for the Batch script. You could
> probably do the following:
>
> CMD / BAT script =
>
> @echo off
>
> IF /I "%PROCESSOR_ARCHITECTURE%"=="AMD64" (
>
> kix32.exe C:\scripts\64bitexcel.kix
>
> ) ELSE (
> kix32.exe C:\scripts\32bitexcel.kix
>
> )
>
> Exit /B 0
>
> Kix script1 = "64bitexcel.kix"
>
> SETCONSOLE="HIDE"
> RUN "%ProgramFiles(x86)%\Microsoft Office\Office12\EXCEL.EXE"
>
> Kix script2 = "32bitexcel.kix"
>
> SETCONSOLE="HIDE"
> RUN "%ProgramFiles%\Microsoft Office\Office12\EXCEL.EXE"
>
>
> All that's needed for this, would be the Kix32.exe under
> C:\windows\system32 on any of the TS servers which might execute it.
>
> It would be cleaner to convert the processor identity logic into the Kix
> script, so that you only need 2 scripts per app (CMD just calls to a single
> Kix script, which checks proc types, then runs correct app), but the above
> should at least get you going for testing this out.
>
> HTH
>
> Lan
>
>
>
>
Other related posts:
