Axiant 3.4D1 Deployment & Citrix

[Glenn]

Hello List,
 
Specifically Axiant NT, Thin Client Deployment and any Citrix Users!
 
We have an NT Server 2003, running PH8, a second NT Server 2003 running SQL
Server - in the client site. (Site A)
We have built a successfull deployment package to a development Nt Server
2000, which also runs SQL Server 2000. (Site B)
Deployment to clients within Site B are successfull. All delpoyments use
Remote connections via NETD on/to the Nt 2000 server.
We plan to run in Thin Client mode in Site A, with only Bitmaps and the
Axiant Runtime Client on each Workstation.
This has been successfull on Site B and other sites.
 
Deployment under Site A today; to a second server {not a client} saw the
Axiant Client hang at startup, after a NETD logon, consuming 80-100% of the
machines CPU.
The same thing happened after installing the deployed version to Server A. I
know this is a bit convoluted!
A Ctrl+Alt+Delete was required to free both machines.
 
Site A is a bit tricky. We get access to the Powerhouse Server via a VNC
connection; from a Citrix menu. 
We are not really deploying via Citrix at this stage. 
Our goal has only been to deploy a working subset of menus; then install the
deployed Axiant Run Time and the user app to a workstation/server/another
machine and run it.
 
All forms run from the Axiant IDE on Site A, via either a Local Run Profile;
or a Remote Run Profile, so I would expect a deployed version to do the
same. It all works well under our development Site B.
 
There may be many reasons, so I am seeking some/any "watch out" advice from
the community.
 
We are sure that: 
- Site A is visible from the Client machine.
- NETD is logging on; this can be seen at the Nt 2003 Server running NETD
and PH8.
 
The client "stalls" at the point at which the "menu" or "first screen"
should be displayed. Yet when run from the server; from within Axiant IDE;
using a Remote connection; it works perfectly.
 
Any advice or recent experiences would be appreciated. It is a little hard
to supply all information that may be required. We are reasonably happy that
all aspects of the deployment "should run" - technically that is.
 
Beyond our immediate problems; We are seeking any advice or pointers with
respect to Citrix installations. ie
- deploying a thin client connection verses
- a fat client deployment within Citrix.
 
My instincts tell me that Thin Client would be ideally suited to Citrix. Our
Citrix engineer is in Belgium, so any information we can gather for him will
be appreciated.
 
I understand my case above is a little scant, so please don't hesitate to
hit us with a barrage of questions - please!
 
Thanks, In Anticipation!
Glenn Baxter
=======================
Baxter IT Solutions Pty Ltd
456 Victoria Parade, East Melbourne
Victoria, Australia 3002
p: 03-9415-8733
m: 0412-826-503
f: 03-9415-8911
e:  <mailto:glenn at baxterit.com.au> glenn at baxterit.com.au
=======================
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20060104/e53b3aca/attachment.html