Authorization code for Service Packs

altquark

Legendary Poster
According to the latest JDE announcement :
---------------------------------------------------------------------
Breaking News Data Classification: Confidential
---------------------------------------------------------------------
Title: Authorization Codes are Required When Installing Service Packs
---------------------------------------------------------------------
Abstract: Beginning with SP16, Xe Customers will be prompted for an authorization code during the Deployment Server Installation.
---------------------------------------------------------------------
Product OneWorld
Suite Technical
Release Xe
Document ID oti-01-0116
Date Created 07/24/2001
Date Reviewed 07/24/2001
Date Revised 07/24/2001

Based on changes to the OneWorld Xe Suite, Xe customers will be prompted for an authorization code during the Deployment Server Installation of SP16 and all future Service Packs. An authorization code is not required if SP16 and future Service Packs are being applied against B73.3.1 and B73.3.2.

To obtain the required authorization code, contact your local J. D. Edwards Global Support Services office, 24 hours a day, 7 days a week.

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

This sucks. Big time. This now means I have to call JD Edwards every single time I deploy a service pack onto the deployment server. For most of you, thats about 4 times a year - for those larger development shops - that can be as much as twice a month.

Since JD Edwards refuses to improve their Authorization Code "hotline" for international customers, I am pretty confident that theres going to be a LOT of complaints over this.

There is no reason for JDE to do this. Let me go through the reasons :
1. The deployment server requires an authorization code at installation time and at specific times - usually annually

2. The authorization code is tied directly to the Deployment server - it cannot be transferred to another box with a different name

3. The authorization code is extremely difficult to "crack" providing a FEW authorization codes are submitted. JD Edwards relies on ignorance for the majority of their security - if someone collects too many of these codes, it will become a LOT easier to "crack"

4. The autorization code is not required for Servers to operate with OneWorld

5. JD Edwards have had major issues with customers requesting authorization codes - as much as 3-4 days have gone by on some requests because the call gets "lost" in their system

6. Every time JDE provides an authorization code - they have to check the contract department and look up the contract based on purchased licenses and/or maintenance level. This is EXTREMELY time consuming - and usually takes almost 1 hour for someone to look up a complex agreement

7. A lot of the time, JD Edwards do not get the authorization codes correct. If, for example, a user is licensed for different modules - they often receive different codes. A lot of the time, authorization codes "forget" to license certain products like Autopilot

8. Service packs have been KNOWN to cause problems with authorization codes. Service packs have also been known to cause other types of issues - and I have certainly been told by JDE to "temporarily restore Service Pack 13" to complete a task. This will no longer be possible.

So why are JDE doing this ? My guess is that someone at Support has decided to create a task because they needed something to do to look busy. A pity that the above announcement leaves too much to the imagination rather than actually TELLING the users why they have gone down this timewasting path.

By the way, I believe that for every hour wasted on JD Edwards support calls and being kept on hold, that customers should be entitled to 1/2000th of their maintenance fee back.

All complaints over this timewasting exercise (both Customer and JD Edwards) should be posted to :

C Edward McVaney
Chief Executive Officer
JD Edwards
One Technology Way
Denver, Colorado 80111

ERP Sourcing
http://www.erpsourcing.com
cto@spla.sh
 
Have they upgraded their response line? It used to be closed on Sundays in
the USA and that meant for us in New Zealand we cant get a code on Monday
mornings because Singapore isnt online until luchtime NZ time.

Ive had to tell users to wait because JDE isnt open yet. Bit of a joke
really.

Cheers
Kieran




To obtain the required authorization code, contact your local J. D. Edwards
Global Support Services office, 24 hours a day, 7 days a week.
 

Carl_Fisher

Well Known Member
Add to this the normal JDE Licence agreement - why should we need to update
the Authorisation Code at all, unless we add extra Modules or increase the
number of Users, as I understand most Software Licensing, once we have
bought the licence, we should have an Authorisation Code for the lifetime of
the agreement, not annually, or when we apply a Service Pack.

It causes us a major headache every time we have to apply a new
authorisation code.

We had a big issue over Authorisation Codes when we upgraded to Xe, because
they changed what was included in the Authorised Modules, suddenly we could
not use Fixed Assets!! They have fixed it now, but it took a while.

Also they always get the Authorisation wrong for us, because we have added
different modules at different times, we always get a code that only covers
Financials first, because that was the module we had first, you can tell
them as many times as you like what should be licensed, but they have a
spreadsheet (never updated) and use that!!!

If you are live you can end up locked out completely for most of a day,
which is not good enough.

Also, why do clients have to get a new authorisation Code once a year as
well?



OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development
 

altquark

Legendary Poster
Re: RE: Authorization code for Service Packs

I wonder how many customers have been locked out of their product due to a mishandled Authorization code by the Response line ? I know that most companies I have seen the authorization code is the one thing they dread most. Maybe JDE should get a little more "internetified" and use the Knowledge garden to publish Authorization codes ?! When the customer logs in, then they could go to a form and submit all the information online. That would make this a LOT better. (See - I don't just complain ! I come up with good suggestions too sometimes !)

Hope someone from JDE is listening to this thread...

Jon Steel
erpSOURCING LLC
http://www.erpsourcing.com

ERP Sourcing
http://www.erpsourcing.com
cto@spla.sh
 
Re: RE: Authorization code for Service Packs

Good idea and definitely needed.

Since last year everytime we get a new code they stuff it up. They keep
missing out the Procurement stuff even though they said that our company
information has been updated and is all OK. This has happened about 3 times
even after I have had a go at all the local JDE people. Next time I have
told to give them some warning so they can make sure it goes smoothly.
Unbelievable really.

Lucky we are not on Xe

Cheers
Kieran


I wonder how many customers have been locked out of their product due to a
mishandled Authorization code by the Response line ? I know that most
companies I have seen the authorization code is the one thing they dread
most. Maybe JDE should get a little more "internetified" and use the
Knowledge garden to publish Authorization codes ?! When the customer logs
in, then they could go to a form and submit all the information online.
That would make this a LOT better. (See - I don't just complain ! I come
up with good suggestions too sometimes !)

Hope someone from JDE is listening to this thread...

Jon Steel
erpSOURCING LLC
http://www.erpsourcing.com

ERP Sourcing
http://www.erpsourcing.com
cto@spla.sh
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=OW&Number=17838
 

jdeperson

Active Member
Re: RE: Authorization code for Service Packs

We are locked out of Autopilot now--after putting on SP16. We're waiting on
JDE to look at the contracts and confirm that we have purchased it (WE DID).
Then they'll help me get the people back into it... hmmmmmm

Lori
OW Xe SP16 Update 2
AS400 V4R5
NT
Citrix
email: jdeperson@hotmail.com
 
RE: RE: Authorization code for Service Packs

Sorry People, I've come in a bit late on this discussion, but need some
advice.

We want to install SP16 for testing prior to going live with it. In order to
do this we are setting up multiple OneWorld foundations according to the
documentation on the knowledge garden. I have done the Enterprise server but
have come to a halt with the deployment server due to our friend the
authorisation code. I am a more than a bit nervous applying a new
authorisation code when we are not going live with this immediately. We are
currently at security revision 5 and when we apply the new code we will be
at security revision 6 on the deployment server with all our production
clients at revision 5.

Are they going to be asked to obtain a new security code from the deployment
server and if so what effect will it have the fact that they are still
running on the old service pack. We do not want to go live immediately with
SP16, rather we want a controlled testing phase for it. Once we have built a
package and deployed it to a couple of clients, we want to go back to our
current service pack for production use.

On top of this we have been informed this morning that SAR 5157875 needs to
be applied immediately after applying SP16!

Has anybody been through this process who could offer some advice and point
out any pitfalls? Thanks in advance

Regards

Marty Fleming
Business Analyst
Richmond Limited

Phone: +64 +6 8786464 Ext 8168
Mobile: +64 +21 478946
Fax : +64 +6 8780959
Email: mailto:marty.fleming@Richmond.co.nz
 
Top