That's what we did. A complete server, database , and Remedy upgrade. Went from 7.6.4 to 8.1. Went very smoothly. We're 100% custom, so your ITSM mileage may very.
Regards. Dave Fincher Lead Technologist Booz Allen Hamilton P.S. LJ don't have a cow because I actually posted something. :-) Sent from my HTC on T-Mobile 4G LTE ----- Reply message ----- From: "LJ LongWing" <[email protected]> To: <[email protected]> Subject: Upgrade to 8.1.2 Date: Wed, Apr 8, 2015 9:25 AM The most common way I have seen discussed is actually an 'upgrade in place on new hardware' That meaning, to standup a new server, install the current version of Remedy onto it, restore the prod DB to it, and follow the recommend upgrade path to bring it to the latest version/patch that you are moving to, then do vigorous testing to ensure that everything is cool...then do a DDM of data from current prod over to 'new prod'....and release it back into the wild. On Wed, Apr 8, 2015 at 9:17 AM, Koyb P. Liabt <[email protected]> wrote: > ** Hi, > > Our company is upgrading from 7.0.3 ITSM/AR System 7.5 to 8.1.2. > > We are trying to figure out if we should do: > a) implement new 8.1.2 install on a separate server, and bring selected > customizations over (after we modify them via Dev Studio) OR > b)" upgrade in place" the AR System and ITSM to 8.1.2 > > Any ideas/thoughts? > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
