It seems that the kix2001 causes an error on loading the ICA session under internet explorer

Anyone got any idea where I should be looking to change this
ie @citrix server, script etc etc

thanks
MikeC

I assume you are using NFuse.

What happens?

Are you using IIS 4.x or 5x?

Is this hosted on a NT or 2000 box? Is IIS on the same system as the TSE (Citrix) box?

I know that when I started to use our login script under 4.x, I had to make some minor changes. For example - using an EXIST statement required to change a "1" to a 1. Or EXISTKEY results from "0" to 0. Have you tried to debug it? That is -

code:

---

KIX32 Yourscript.kix /d

---

HTH,

- Kent

[ 13 August 2001: Message edited by: kdyer ]

IE just comes back with "can't connect to Citrix Server" after initial login

my script starts with

IF ($SYSROOTDIR = "WTSRV")
quit
ENDIF

Which I hoped would stop the script in it's tracks

You are very close..

code:

---

IF INSTR(%windir%,"WTSRV")
? "Running Terminal Server"
Else
? "Not Running Terminal Server"
Endif
sleep 2

---

HTH,

- Kent

Thanks for the nudge in the right direction

Below from DR Watson

code:
Application exception occurred:
App: (pid=1010)
When: 8/14/2001 @ 12:40:5.46
Exception number: c0000006 (in page io error)

Have you thought about the following two macros? Instead of using the INSTR...

quote:

---

@PRODUCTSUITE OS suite. Combination of any of the following values:
1 - "Small Business"
2 - "Enterprise"
4 - "BackOffice"
8 - "CommunicationServer"
16 - "Terminal Server"
32 - "Small Business (Restricted)"
64 - "EmbeddedNT"
128 - "DataCenter"
256 - "Single user Terminal Server"
512 - "Home Edition"
1024- "Blade Server"

@PRODUCTTYPE OS type. Possible values:
"Windows 95"
"Windows 98"
"Windows Me"
"Windows NT Workstation"
"Windows NT Server"
"Windows NT Domain Controller"
"Windows 2000 Professional"
"Windows 2000 Server"
"Windows 2000 Domain Controller"
"Windows XP Home Edition"
"Windows XP Professional"
"Windows XP Server"
"Windows XP Domain Controller"

---

HTH,

- Kent

Depending on how you start KIX32, you may be able fix the problem by using the "START /w KIX32.EXE" command.

Ruud

Seems a shame to run a batch file to run a script processor ;(

Ruud