Just a patch or from version 6 ITSM to version 7? If you are talking about upgrading versions you are really talking about migration - as this is not really a straight forward stick in the CD and run an upgrade..
Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Moore, Christopher Allen Sent: Wednesday, March 12, 2008 1:38 PM To: [email protected] Subject: Re: What specifically breaks upgrades? ** Yes- we’re planning to update to the newest versions of all the ITSM apps. Thanks all of you for your advice! Chris ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Wednesday, March 12, 2008 12:10 PM To: [email protected] Subject: Re: What specifically breaks upgrades? ** Remember that in AR Server 7.1, licenses are treated differently. I noticed that when upgrading from 6.3 to 7.1 (patch 2) on Linux, the user licenses didn't get converted - only the Server license did. I would take a backup of my license file and my ar.conf file, to ensure that I can quickly restore anything that might not get upgraded correctly. Are you asking about ITSM as well? Rick On Wed, Mar 12, 2008 at 9:56 AM, Moore, Christopher Allen <[EMAIL PROTECTED]> wrote: ** Hey everyone- I'm putting together a plan to upgrade from 7.0 to 7.1. We have done some modifications to the system, but nothing too drastic. Form changes, additional workflow, but (as far as I know) no changes to the BMC OOTB workflow. What sorts of changes specifically are problematic when upgrading? Windows Server SQL DB Thanks! Chris No virus found in this outgoing message. Checked by AVG. Version: 7.5.518 / Virus Database: 269.21.7/1327 - Release Date: 3/12/2008 1:27 PM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
