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
[email protected]
---------------------------------------------------------------------
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
[email protected]
