Loading Fat Client

Is there any documentation regarding loading a Fat Client over a WAN? We currently export a computer to the US and then fly it almost 2,000 miles for our IS group to load the software. As you can imagine, this can be expensive and quite a pain.

Thanks in advance,

Mike

Mike-

Use the Product Packaging feature to create an installation CD - it is much
lighter, smaller, and cheaper to ship than a PC :=)

Running OneWorld across a WAN is a dicey proposition, much less installing
it over one.

Regards,
David

Brightpoint NA
Sun/Oracle 8.1.6 / Citrix Xe base Sp15.1 live
Update 4 / SP18.1 sandbox

Okay, really silly question. Why not cut a cd and just mail that? That
is how we distribute new fat clients to our remote users who are using
thick clients..

John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 6, SP 19.1_B1
Running on: WIN2K/SP2, SQL2k/SP2
Metaframe 1.8a
----------------------------------------------------------





Xe, Update2, SP16
SQL2k, Win2k
Metaframe 1.8a

Wouldn't it be easier to burn a CD and ship that instead of the PC?

We have some remote users where an install over the WAN is impossible. We burn CDs and have OneWorld installed/updated in that manner.

Bill

Mike :

I've read that fat clients can be installed via CDROM but never tried
to use that functionality.
However, I've tried to run a OneWorld fat client through WAN (256 Kbps)
and it's incredible slow! In that case, I recommend you a thin client
solution such as Citrix, Web client, etc.

Sebastian Sajaroff

Bill:
Burning a CD was also my first response. However, I'm told that we can burn CDs for other things but, not for JDE. I'm not sure why this is true.

We've loaded one Fat Client via the WAN. Unfortunately, the person that did this has left the company.

Thanks,

Mike

Mike,

what version of OneWorld are you running?

If its XE, then it can be done - its just that your IT/IS people don't know how to do it.

The other thing pointed out was that running OneWorld over a WAN using fat clients is not very smart. Again the IT/IS people should have setup a Windows Terminal Server - very standard technology - which is a relatively cheap and easy way to provide good response time to remote users.

Of course, I say your IT/IS people, but its management/money that usually is the roadblock here . . .

Good Luck,

Assuming you don't already have a Terminal Server solution implemented and
depending on the number of remote "fat" clients to receive any kind of
package you might want to think about a 2nd tier deployment server, assuming
it's still supported.

We implemented one back on B7.1.4.

Check out the multi tier deployment documentation in the KG. We use it to deploy to 2nd deployment server in a different location and citrix servers in that location gets installed from the 2nd deployment server. I bet you can do the same for the full clients. KG doc no: oti-99-0098

In the Technical Package Management is a section: Installing OneWorld Workstations from CD

Can you load it where the DS and ES reside and then transport it?

Thanks,
James

OneWorld CNC Consultant