• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Re: Package Install

kjjdelist

Well Known Member
Re: Package Install

Make sure you are adding the package through the 'Add/Remove Programs' app
on the Windows Control Panel on the TermServer. Do NOT run the Setup.exe
from the OneWorld Client Install directory and do NOT deploy a package to a
Terminal Server. It MUST be done manually through the Add/Remove programs
app.
 

CHo

VIP Member
Re: Package Install

According to GATS document, "Deployment of OneWorld Packages to Windows Terminal Servers", there are three deployment methods. Deploy as per email below or accept the mandatory package or execute workstation install. If the document is wrong, then please let the list know. Thanks.

Make sure you are adding the package through the 'Add/Remove Programs' app
on the Windows Control Panel on the TermServer. Do NOT run the Setup.exe
from the OneWorld Client Install directory and do NOT deploy a package to a
Terminal Server. It MUST be done manually through the Add/Remove programs
app.






--------------------------


C Ho
Intermediate Programmer/Analyst
B7322 SP 12.4
AS/400 coexistant with SQL Server 7.0
Sandbox: Xe AS/400 coexistant with CO on SQL 7.0
 

KBohn

Active Member
RE: Package Install

Has the JDE recommendation changed then? There is a KG document otm-00-0048
Title: Windows Terminal Server - Update Packages. The details are as
follows:

Issue:

Installing an update package to a Windows Terminal Server client.

Resolution:

Windows Terminal Servers can have update packages deployed to them as long
as none of the terminal server users are signed into the terminal server
with a terminal server session. The process is the same as a fat client at
that point.

Put the terminal server in install mode to prevent users from connecting to
the terminal server.
Log into the terminal server as an administrator.
Sign into OneWorld and take the scheduled update package.

Kimberley Bohn
QNX Software Systems Ltd., Canada
B73.3.2, NT, SQL7.0, SP10
WTS-W2K
 

lisa_stinebuck

Active Member
RE: Package Install

C Ho,
You are correct regarding package install on WTS/Citrix. There is
another way as well;
Go to DOS prompt on WTS.
Type; change user /install (this puts WTS in install mode)
Then you can use the setup.exe file to install
When complete you must
Type; change user /execute (this places WTS back in user mode)
at the DOS prompt
You must still place the TNSNAMES.ora file (from the Deployment Server)
in the orant\net80\admin directory on the WTS as well as place the HOSTS
file (from the Deployment Server) in the \winnt\system32\drivers\etc
directory on WTS when doing your first package install.
However I still prefer your method of install. Just wanted to give
everyone a choice. :)
Thanks,

Lisa G. Stinebuck
Senior Service Delivery Technician
Logical EBOC Cincinnati
513-412-7950 x1021
lisa.stinebuck@us.logicaleboc.com
 

tswoods

Member
RE: Package Install

You can also just use Oracle Net8 Easy Config to configure Oracle on the
WTS box rather than copy files and if WINS is configured properly there is
no need to have a Hosts file on any NT server in the domain. Hosts files
often create more problems and extra work when changes are made at a later
date and every server and/or PC has to be updated rather than just the WINS
database.
Something to keep in mind.

Tim Woods
CNC / System Administrator
PTC Alliance <http://www.ptcalliance.com/>
(330) 829-5240
tswoods@amtp.com <mailto:tswoods@amtp.com>



OW&Number=8884
 

Dawn_Detz

Member
RE: Package Install

Why????....."Do NOT run the Setup.exe
from the OneWorld Client Install directory and do NOT deploy a package to a
Terminal Server. "

This is exactly how I deploy my latest package to the citrix servers... I
do it exactly like a FAT client... setup.exe. I have always had success
while doing it this way....on both FAT and citrix.
 
Re: Package Install

Actually, the "need" to install through Add/Remove and just launching the
setup is because of the Terminal Server mode. Our environment is using
Application Server mode as Terminal Services Licensing is a required
component that licenses clients on a Terminal server in application server
mode. This Add/Remove programs ensures that "applications" (could be JDE OW
itself, notepad, MS Excel, etc, not refer to service pack installation, etc)
are installed for use in a multisession environment. You can view your TSE
setting by going to Administrative Tools->Terminal Services
if your terminal services mode is remote administration mode, and there is
no impact on applications when you disable Terminal Services.
As I see it, this is more towards Citrix management rather than the JDE. JDE
says that required to Add/Remove program when doing setup is because to
cater to the Citrix for it to publish correctly as most of our server need
to store licenses for other servers as well (more than one Terminal/Citrix
server). For more information, you can refer to the booklet that comes when
you buy the Terminal Services. Hope this gives some useful information to
you. Rgds.

Bell
OneWorld Developer
One World B7332,SP 9, AS/400 V4R4M0
Windows NT; Win2000+Citrix Metaframe 1.8a

PS You do not need to enable Terminal Services Licensing when enabling
Terminal Services in remote administration mode. A maximum of two concurrent
connections are automatically allowed on a Terminal server in remote
administration mode. You can install programs either before or after
enabling Terminal Services, unlike in Application Server mode.

----- Original Message -----
From: "Dawn Detz" <Dawn.Detz@orionpowermw.com>
To: <jdelistml@jdelist.com>
Sent: Wednesday, April 11, 2001 1:12 AM
Subject: RE: Package Install


a
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
8908
 

larryb

Member
RE: Package Install

You must also make certain that no one is signed on to OneWorld on the terminal server the entire time
you are installing the package. This is necessary to avoid potential corruption.
 
Top