Push install of update packages

[hscheper]

Does anyone have any experience with Push installs of update packages under B7331?? Any traps to worry about, etc??

Thanks for your help.

Harry Scheper

B7331 SP11.3, NT4SP4 ES, NT4SP6a DS, Oracle 8.0.5

 

[kjjdelist]

No problems under 7332 except that you need to make sure that you are only
deploying to active workstations. I've had some unused PCs in my deployment
list before and someone will try to sign-on to it and have a rather long
list of packages to deploy. I just manually remove those packages using the
Package Deployment app, but just something to look-out for.

P.S. Is there a reason your ES and DS are on 2 different SP's for NT?


>From: hscheper <[email protected]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Push install of update packages ~~0:4712
>Date: Mon, 29 Jan 2001 08:39:57 -0800 (PST)
>
>Does anyone have any experience with Push installs of update packages under
>B7331?? Any traps to worry about, etc??
>
>Thanks for your help.
>
>Harry Scheper
>
>B7331 SP11.3, NT4SP4 ES, NT4SP6a DS, Oracle 8.0.5
>
>
>--------------------------
>Visit the forum to view this thread at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=4712
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

 

[Coroneos]

Do you have any experience pushing to NT Workstation machines? It used to be that the user receiving the package needed to have Local Admin rights on their workstation for the package to install successfully.. Is this still true?

Thanks,

Alex Coroneos
IT Manager
Serrot International, Inc.
[email protected]
B7332 SP10
NT 4.0 SP6a
SQL 7.0 SP3

 

[vap]

Harry,

I hope you mean installation by use of OneWorld client listener when you say
about Push install. When you use Push install, installation is started when
you run Push Installer UBE. You can also schedule packages to be installed
on workstations, and install happens at sign on - it's a different story,
not covered below.

Traps... Well, it depends on how you define traps. Under B7331 it was a
mess, and we never made it work for more then 10 PCs out of 30. Situation
slightly improved in B7332, but not really. Also, statistics in the report
is very unreliable - it'll often say package was installed, when it was not.
I never tried it in XE or any XE SP on B7332.
A couple of things to watch out (information was valid in B7332, SP11.3-):
1. JDEdwards consultant advised us against using Push deployment (this
happened on SP13.3).
2. If you have more then one pathcode on a PC, after a push install you'll
only have one, the rest will be deleted.
3. To install a full or partial package, user must have local Admin rights
(which is a VERY bad idea, especially if you have unrestricted Internet
access). I think this can be avoided by setting an admin account to Client
Listener, but I never tried it.
4. Sometimes it takes Listener like foreeeever to start the actual install.
I've seen delays up to 2 hours.

Regards,
Vladimir Ponomarev

 

[cdawes]

A long time a go I took a look at the JDEdwards Push install listener - I
didn't like it. I currently use Microsoft SMS for all FAT client deployments
and it is amazing. It's much easier than the JDE solution (if you can afford
and manage it) and can do much more. We already had it so it was an obvious
and easy solution.

Like the Push install listener there are a few pitfalls with SMS. With the
Push install listener if you are deploying new workstations I suggest you
configure the listener in the 'Ghost' image. Unfortunately if you're not
using something like Norton Ghost or SMS for your deployment then running
around to workstations can become very time consuming and expensive.

When you configure the JDE Push install listener make sure you use a domain
account (Win NT) to start the service as opposed to a system account.

Contrary to unpopular belief, you do not need to have local admin rights to
accept any form of JDE package. You do however need FULL access to the
JDEdwards software key in the registry and if you're using SQL you'll need
access to the ODBC key. You'll also need READ access to the following
directories on the Deployment Server (in addition to what JDE tells you)

\SYSTEM
\PACKAGE_INF
\SYSTEMCOMP
\HELPSCOMP

The registry access can easily be done if you're using Norton Ghost or have
SMS.

Another option is to not do a JDE Push install or a JDE Interactive Install
- do a JDE silent install. You can do this by adding a command to every
users login script. This works great and has many command line options. The
only thing is that users can not access OW until the install is done. You
can script a batch file to inform them when the package is done or they can
look at the NT task monitor to see when it drops below 90%. The basis syntax
to silent installs on B7332 is in the install guide and in the sys admin
guide in the SMS section.

Good Luck,


Colin Dawes

B73.3.2 SP13.1_GUE
Intel/NT/NT 4.0/Oracle 8.1.6.2
200 Fat, 60 Citrix



Colin Dawes, MSc
City of Guelph
B7332 SP13.1, Oracle 8.1.6, NT 4.0, Fat & WTS

 

[Kieran_Mahony]

Hi
I have to agree with Vladimir. I spent months trying to make it work along
with numerous calls to the response line. I struck it lucky with one call
becaause I got a guy from denver who was in aussie for a while and knew it
well.

Consulants from JDE said that it doesnt work properly under B7331 but with
60 fat clients (mostly across a WAN)and only me I had to try to make it
work. Even so I only ever made it work twice. When I tried the third and
subsequent times it didnt work and eventually I gave up.

Your best bet is something like TSE or web/Java in XE which I'm sure you've
already being told.

Cheers
Kieran

B7331 SP10.1 AS400 V4R3 NT4.0 SP5



Harry,

I hope you mean installation by use of OneWorld client listener when you
say
about Push install. When you use Push install, installation is started when
you run Push Installer UBE. You can also schedule packages to be installed
on workstations, and install happens at sign on - it's a different story,
not covered below.

Traps... Well, it depends on how you define traps. Under B7331 it was a
mess, and we never made it work for more then 10 PCs out of 30. Situation
slightly improved in B7332, but not really. Also, statistics in the report
is very unreliable - it'll often say package was installed, when it was
not.
I never tried it in XE or any XE SP on B7332.
A couple of things to watch out (information was valid in B7332, SP11.3-):
1. JDEdwards consultant advised us against using Push deployment (this
happened on SP13.3).
2. If you have more then one pathcode on a PC, after a push install you'll
only have one, the rest will be deleted.
3. To install a full or partial package, user must have local Admin rights
(which is a VERY bad idea, especially if you have unrestricted Internet
access). I think this can be avoided by setting an admin account to Client
Listener, but I never tried it.
4. Sometimes it takes Listener like foreeeever to start the actual install.
I've seen delays up to 2 hours.

Regards,
Vladimir Ponomarev




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=4742

*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************